Having trouble with a bugcheck reboot in Windows 2000 Pro

[DirkStanford]

Windows has been rebooting for some reason and in the event viewer is says (The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000044, 0x00000002, 0x00000001, 0x80443b71). Microsoft Windows 2000 [v15.2195]. A dump was saved in: E:\WINNT\Minidump\Mini110402-01.dmp.).

I cant find a site that has the same number configuration as above so I am at a loss.

If anyone has any info on the subject please reply.

 

[b5passat]

See the Technet article at:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q254723

this will tell you how to read the minidump logs. I've been quite successful in pulling information from the minidump logs and tracking down problems from it. Matt

 

[wolluf]

Good luck with bugcheck cracking, eg

http://support.microsoft.com/default.aspx?scid=KB;EN-US;q130802&

Try Google

I've never actually found the root cause of a problem by chasing down the bugcheck codes - so now I try to get general idea if its likely to be hardware or drivers (2 most common causes) & then try things out from there.

 

[b5passat]

The trick is to not bother with the stop codes. Generally they are generally too broad based to tell you what is wrong. You need to read that minidump log. You really only need to install the symbols and the reader from the support\tools folder on the W2K CD. You don't need to download all 100+MB of the files MS recommends, the first file contains the symbols. Matt

 

[DirkStanford]

I thank you for the replies but I have no idea how to read the file. I got the debuggers and ran the file with dumpchk.exe but I dont have a clue what I am looking at or looking for after it runs.

If anyone has some additional help I would greatly appreciate it.

 

[b5passat]

Did you output the dumpchk file to a text file? Once you do that, go back and read the file that you dumped the log to.

One of my more recent troubleshooting tasks using the dumpchk was throwing an Exception Code 0X80000003 I turned around and searched that exception code on Google, found an article in the MSDN Library, said to run diagnostics, sure enough, the DIMM0 module had failed. Replaced the module and the system ran perfectly. Matt