BSOD - Random Occurance

t4528js said:

Thank you for your help. I did as you suggested. What program do I need to be able to read a .dmp file? I really, really, hate bothering you and others.

Not a bother. We enjoy helping in any way we can. WInDbg is the gold standard but there are a couple of easier apps to start with.

Bluescreen view (by nirsoft) and who crashed. They are less comprehensive and often less reliable

Thanks again for the help. You guys are awesome and it's nice to know there is somewhere we can go for help.

John

I tried to download the WInDbg program but it states that I'm using .NET Client instead of the full version and that some of the files of WInDbg will not load. Do I need to download the full version first or is there a work around?

Install Windbg v6.11.1.404 (MSI file) --> Install 64-bit Native x64 version 6.11.1.404 [15.2 MB]

From MSDN - Debugging Tools for Windows 64-bit Version

.NET 4.0 not a prerequisite for v6.11

Regards. . .

jcgriff2

`

OK..I got Windbg downloaded and I've been messing around trying to get my dump files in it. I got a couple in there (I think accidentally) but there is the following message:

Your debugger is not using the correct symbols.

In order for this command to work, your symbol path must point to .pdb files that have full type information.

Certain .pdb files (such as the public os symbols) do not contain the required information.

Contact the group that provided you with these symbols if you need this command to work.

Type referenced: nt !_KPRCB

Is there a manual I can read on how to get my dump files into the debugger and how to operate the program?

Open Windbg, press CTRL+s keys, paste this in for symbol path -

Code:

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Then File, Save Workspace

Re-run the dump file.

I did as suggested but still seem to be having problems getting the .dmp files into windbg. This is what I get

I guess cut and paste doesn't work here so I'll attach screen shot.

I think I figured it out. If I open Windbg then drag and drop one dump file, let it debug and get the cause of the BSOD it works fine, but then I need to close Windbg and open it again to do the next file. I can't keep dropping one file at a time for debugging without opening and closing Windbg first.

Copy \windows\minidump to your Documents folder.

Or - run Windbg at elevated admin level -
RIGHT-click on Windbg, "Run as Administrator"

Regards. . .

jcgriff2