BUGCHECk

Allanag

Distinguished
Jan 15, 2002
97
2
18,635
Hi everyone.

For the last month or 2 I have been getting a bug check error. It can happen at any time and regardless of what application I am working on. I will be working and suddenly my computer will restart. It doesn't happen every day. I went to the event viewer and copied down 2 of the bug checks that occur. I also went to Microsoft's website to see if I could get any more information. I did find some information regarding bugchecks but they are different than what I am getting. Can anyone tell me what my bugchecks mean and how to resolve them? I'd greatly appreciate it.

The bugchecks are the following:

1. The computer has rebooted from a bugcheck.
The bugcheck was: 0x0000000a (0x00000000, 0x00000002, 0x00000001, 0x80439e14). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini060202-01.dmp.

2. The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0xbfcc9291, 0x00000000, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini051802-01.dmp.
 

Toejam31

Distinguished
Dec 31, 2007
2,989
0
20,780
The great majority of the time, what this means is that you have an incompatible software or driver issue, and the problem, with the default system settings, is causing a memory dump and reboot.

Here is a page that contains more information on 0x0000000a and 0x0000001e Stop Errors, which is actually what is happening to your computer.

<A HREF="http://www.labmice.net/troubleshooting/errorcodes.htm" target="_new">Windows 2000 Error Codes</A>

The rebooting and memory dump can be disabled, which will nearly always cause a BSOD (Blue Screen Of Death), which usually contains more specific information about the file (or files) that is the source of the problem.
This is located in My Computer\Properties\Advanced\Startup and Recovery\Settings, under System Failure.

However, once you disable the restart option, if the computer has a BSOD at startup, you may not be able to load Windows, even in Safe Mode. But you should go ahead and set the Write debugging information to (none) to stop the memory dumps, as this is just a waste of disk space for the average user.

I would suggest looking in the Event Viewer at the System and Application Logs to find extra information about the error. My Computer\Manage\Event Viewer. You can use this information to search the Microsoft Knowledge Base, either by the Stop Error, or the Event ID # assigned to the event.

Toejam31

<font color=red>First Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=17935" target="_new"><font color=green>Toejam31's Devastating Dalek Destroyer</font color=green></A>
<font color=red>Second Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new"><font color=green>Toey's Dynamite DDR Duron</font color=green></A>
__________________________________________________________

<font color=purple>"Some push the envelope. Some just lick it. And some can't find the flap."</font color=purple>
 

Allanag

Distinguished
Jan 15, 2002
97
2
18,635
Thanks for the information ToeJam. I respect your knowledge. You seem so widely versed on so much and it is apparent you are very very very very computer savvy. :)

I have gone to the knowledge base and I think I did enter the event id in but if I remember correctly, nothing came up. However, I will try it again when I have a moment to see if I can get any further info from the knowledge base. And thanks for the link I'll be checking that out :)
 
G

Guest

Guest
Toey is way past savvy, he be good, better, best!

He da man and a good human being.



<A HREF="http://www.koalanet.com/australian-slang.html" target="_new">Aussie slang</A>