Checking BSOD dumps

Syxx_Killer · 08-21-07, 09:42 AM

I reinstalled Windows (XP Pro with SP2) about a little over a week ago (also formatted HD). I was getting random BSODs and thought reinstalling Windows would help. Since then, I have got two BSODs, which gives me a sore stomach. Both have been IRQL_NOT_LESS_OR_EQUAL messages. I found an article on MS's Knowledge Base called: How to gather information after a memory dump in Windows XP.

http://support.microsoft.com/kb/314084/en-us

I was led there after clicking the link in Event Viewer for more info at the Help & Support Center. This is the message that was entered into the Event Viewer a few mintues ago after the BSOD:

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x0000000c, 0x000000ff, 0x00000000, 0x8053196a). A dump was saved in: C:\WINDOWS\Minidump\Mini082107-01.dmp.

This is the one that was entered back on the 18th.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000000, 0x00000002, 0x00000001, 0x8051e106). A dump was saved in: C:\WINDOWS\Minidump\Mini081807-01.dmp.

I've got the dump files, but is there a way I can check them for a reason why I am getting the BSOD? I tried the Dumpchk.exe thing stated in that article above, and it either doesn't work or I am doing it wrong. I bring up the CMD prompt and type in what the article says to and I get an error:

Loading dump file memory.dmp
**** DebugClient cannot open DumpFile - error 80070002

I also get an error if I replace the Memory.dmp above with the file name of the dmp file in the Windows folder.

08-21-07, 09:42 AM	#1
Syxx_Killer Admiral Join Date: Aug 2003 Location: Michigan, USA Posts: 2,387 Downloads: 21 Uploads: 0	Checking BSOD dumps I reinstalled Windows (XP Pro with SP2) about a little over a week ago (also formatted HD). I was getting random BSODs and thought reinstalling Windows would help. Since then, I have got two BSODs, which gives me a sore stomach. Both have been IRQL_NOT_LESS_OR_EQUAL messages. I found an article on MS's Knowledge Base called: How to gather information after a memory dump in Windows XP. http://support.microsoft.com/kb/314084/en-us I was led there after clicking the link in Event Viewer for more info at the Help & Support Center. This is the message that was entered into the Event Viewer a few mintues ago after the BSOD: The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x0000000c, 0x000000ff, 0x00000000, 0x8053196a). A dump was saved in: C:\WINDOWS\Minidump\Mini082107-01.dmp. This is the one that was entered back on the 18th. The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000000, 0x00000002, 0x00000001, 0x8051e106). A dump was saved in: C:\WINDOWS\Minidump\Mini081807-01.dmp. I've got the dump files, but is there a way I can check them for a reason why I am getting the BSOD? I tried the Dumpchk.exe thing stated in that article above, and it either doesn't work or I am doing it wrong. I bring up the CMD prompt and type in what the article says to and I get an error: Loading dump file memory.dmp **** DebugClient cannot open DumpFile - error 80070002 I also get an error if I replace the Memory.dmp above with the file name of the dmp file in the Windows folder.