• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

What is a Win2k Bugcheck?

D

debugger

Member
So, there I am, having suffered from occasional unexpected shutdowns from my Win2k Pro computer. After some head scratching, I end up in the Event Viewer, and I find out that the PC was rebooted because of a "bugcheck". The message I get is: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0xbf8b2227, 0x00000000, 0x1a8b1a8f). Microsoft Windows 2000 [v15.2195]. A dump was saved in... Unfortunately, I can't make anything from the minidump since it is some form of binary file. Does anybody know what to do with this? How can I determine what is the cause of the problem? I'm sure that if I call the local reseller and tell him that I've had a shutdown because of a "bugcheck", he'll tell me that the problem is with (random selection here) the hard disk. Thanks.
 
Never heard of a "bugcheck" but try searching on that stop error message: they usually get you pretty close to the source of the problem.
 
I'm on service pack 2. Tried searching on "bugcheck", and couldn't find anything. I've just been to the Microsoft site, and found a lot of stuff (albeit somewhat cryptic) on the "minidumps". I've also downloaded this Debugging Tools for Windows (a.k.a. WinDbg), which I am now trying to make some sense of. Although I can now read the minidump, making sense of it is the challenge (its almost as bad as those old trace packages on mainframes... but at least the information is not in octal). For what its worth, it now appears that the minidump is not the way to go as it does not log information from processes other than the one that is currently running on the cpu, and that I should perhaps set up the system to record the big logs. There is a way to do that, but I have yet to find out how to do that too. Looks like a long night...
 
Well, if you wanted to have your computer record more than the standard minidump then right click on my computer, select properties. Select the Advanced tab and then look under startup and recovery near the bottom of that tab. Click the button and then in the next pane you should see a "write debugging information" section near the bottom. Change that to kernel or complete. While you are at it, you might consider unchecking the automatically reboot box above this section. This lets you see the information that comes out. Sometimes these errors don't register in the logs for some reason.
 
A bugcheck is the good old blue screen of death. Unless your a driver developer the mini-dumps won't be usefull to you. I recommend turning of the 'automatically reboot' option so next time you blue screen you'll have a better chance of seeing what driver was faulted with the problem. If it turns out to be the same driver multiple times, time to look at it's version (and make sure it's associated hardware is ok). If it seems to be 'random' drivers causing it, time to look at overclocking, overheating, general 'random' type crash causes.

Bill
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top