Quote: Originally Posted by Music46
Guys has the tut changed... as its 2 years old... or can we still use the above method to still debug?
It still works. I just installed all
of the Common Utilities including the Debugging Tools
. However, since it is 2 years later, even though I installed as per the tutorial's instructions for a shorter program path, the SDK v7.1 installed it anyway into its default location:
"C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe"
I now have the SDK v7.1 installed in 2 locations, its default above and also on my D: partition. The D: partition only has 2.5 MB's and the default above has about 41 MB's and probably about 255 MB's somewhere else on the C: O/S partition. I recommend you disregard the older tutorial's instructions regarding program location installation and simply use the default location now. This way everything is together. However, I also followed the tutorial's instructions regarding a separate Symbols folder and it already has 65 MB's so continue following that.
Many thanks to H2SO4
for posting his tutorial. Today, on my relatively new 9 month old system, I got my third BSOD in as many months. I was using BlueScreenView and it wasn't giving me enough specific information. I did get a kick out of the reproduced BlueScreen though. When you see a real MS BSOD, it gives you about 15 seconds to read it and then your system reboots. You practically need a camera to be able to study it!
WinDbg gives me accurate information. Microsoft has really improved their software. I was able to pinpoint the problem to nvlddmkm.sys, an nVidia
file. I will update them later. One thing I find difficult are the "kd>
" commands on the bottom of the screen. I looked in the help file and I cannot find any list or explanation for them. Can someone please tell me where in the Help file these commands are located?