d_blk

• Defrag Tools: #36 - CLR GC - Part 4

  Apr 20, 2013 at 8:08 AM

  thanks for the info...

• Defrag Tools: #36 - CLR GC - Part 4

  Apr 16, 2013 at 8:19 PM

  Cool introduction to the perfview tool. I want to know more about managed code... What route would you suggest? Do you have any suggested reading? As always thanks very much for your time.

• Defrag Tools: #33 - CLR GC - Part 1

  Mar 26, 2013 at 7:23 PM

  Andrew,

  You guy's have to cover the perfview tool Maoni referenced. Dude I downloaded it and began the tutorial. That tool is awesome. It would be nice to see how experts utilize this tool.

• Defrag Tools: #33 - CLR GC - Part 1

  Mar 26, 2013 at 9:28 AM

  Wow... that was a really cool and informative episode. 

• Defrag Tools: #32 - Desktops

  Mar 19, 2013 at 5:41 AM

  Cool show...

  Bring on Xperf - I would love to see a series on the utilization of Xperf to diagnose I/O issues.

  Like determining what is acceptable latency for i/o completion.... thorough walk through. 

  You'll are providing an awesome service. 

• Defrag Tools: #25 - WinDbg - Events

  Jan 29, 2013 at 9:20 AM

  Excellent video. The content really reiterates and compliment concepts in the new Windows internal books. Great stuff... what do I need 4 years of Univ for when I got you guys.

• Defrag Tools: #23 - Windows 8 SDK

  Jan 20, 2013 at 10:52 AM

  What is the difference between the !db extension and db ?

• Defrag Tools: #22 - WinDbg - Memory Kernel Mode

  Jan 08, 2013 at 8:24 PM

  Happy New Year!!! 

  Dudes I love this series its totally awesome... I feel you guy's are providing a great learning outlet especially for a beginner like myself. However at times the show gets hi jacked and it never gets back on course. I felt the past two episodes could have been a bit more linear and detailed.

  keep up the good work dudes.

• Defrag Tools: #19 - WinDbg - OCA

  Dec 19, 2012 at 7:13 AM

  My machine is no longer opening the correct architecture windbg (x64 vs x86) when I double click a dump file. The x64 version opens arbitrarily now. It was working as demonstrated by Andrew. However after setting procdump as JIT debugger that functionality went away. Is there a registry entry I should look into?

  How can I correct this?

  Thanks is advance you guys are awesome!

  OBTW please bring Graham back for more Demos!!

• Defrag Tools: #15 - WinDbg - Bugchecks (BSOD)

  Nov 19, 2012 at 6:21 PM

  Chad I see in the windows internal 6th edition that the virtual address space for 32-bit x86 is 0x00000000 - 0x7fffffff for user process and 0x80000000 - 0xffffffff for protected operating system memory.

  What are the values for a 64-bit x64 system?

  I agree with Andrew that was an awesome demo. Can't wait for more!!!

See more comments…