WinDBG vs BSOD exe

I'm slightly familiar with the BSOD_Windows7_....exe provided on this forum, but I also see reference to the Microsoft-provided WinDBG and would like to understand their purposes. The BSOD thing seems to be mostly a data collection tool, but doesn't have much built in debugging. Is that correct, or am I underestimating it?

"Debugging Tool for Windows" sort of implies it's a debugging tool rather than just a data collection tool. Is that correct, or is it's name an exaggeration? Is it worth installing? I currently have just the client part of .NET and WinDBG requires the full .NET; I'm reluctant to go through the hassle of installing it if WinDBG isn't going to buy me anything.

Pat

pokeefe0001 said:

I'm slightly familiar with the BSOD_Windows7_....exe provided on this forum, but I also see reference to the Microsoft-provided WinDBG and would like to understand their purposes. The BSOD thing seems to be mostly a data collection tool, but doesn't have much built in debugging. Is that correct, or am I underestimating it?

"Debugging Tool for Windows" sort of implies it's a debugging tool rather than just a data collection tool. Is that correct, or is it's name an exaggeration? Is it worth installing? I currently have just the client part of .NET and WinDBG requires the full .NET; I'm reluctant to go through the hassle of installing it if WinDBG isn't going to buy me anything.

Pat

The BSOD "thing" here is solely a data collection (from many sources) script. It collects the information for BSOD analysts to use winDB and other tools to figure out the problems with various systems and their components. It also collects some personal information which some users object to.

WindDB is the premier app for BSOD analysis and worth installing BUT required hundreds if not thousands of analysis before you will start to become familiar with it.

It is as much art as science and require much use.


Good Luck

zigzag3143 said:

WindDB is the premier app for BSOD analysis and worth installing BUT required hundreds if not thousands of analysis before you will start to become familiar with it.

It is as much art as science and require much use.

I seriously hope I will not have hundreds (let alone thousands) of needs for either tool. :) But I am experiencing occasional crashes (restarts with no BSOD even though I've requested no automatic restart), freezes, and (very rarely) hung reboots, so I'm looking for any help I can get. Maybe I'll give WinDBG a try.

BTW, I currently have BSOD_Windows7_Vista_v3.02_jcgriff2_.exe and I see there is now a Windows_NT6_BSOD_v3.03_jcgriff2_.exe. Is there anything significant in the name change - especially "Vista" vs. "NT6"? I assume Win7 is NT6. Yes?

Pat

cluberti said:

zigzag3143 said:

But I am experiencing occasional crashes (restarts with no BSOD even though I've requested no automatic restart), freezes, and (very rarely) hung reboots, so I'm looking for any help I can get.

Completely ignoring all but this one small section of your post, I think you may want to do some hardware testing, starting with RAM. The description of your issues as provided does not sound like a software problem...

I don't actually think it is a software problem, but I'm hoping the software (some software somewhere!) might be logging hints of some problematic hardware. I was suspecting my SSD C: drive (for no good reason), but maybe I should consider RAM.

Pat