Random Bugcheck Reboot

  • Thread starter Kenneth John Barclay
  • Start date
K

Kenneth John Barclay

Over the course of the last three months I have received numerous reboots on one of my W2K machines. It is running SP2 and I'd like to upgrade to SP3 but am nervous because of the randomness of the bugcheck problems, thinking I may not get my system to boot at all. My other three W2K systems (all running SP3) are fine.

Below are the composite bugcheck codes. There does not seem to be any consistency in the codes even though several do repeat. All the Event Types and Event IDs are the same. Any help would be greatly appreciated.

Thank you in advance.

Bugcheck results.
***********************
Event Type: Information
Event ID: 1001





Date: 3/13/2004

Time: 5:16:34 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfeb27cc8, 0x00000001, 0x00000000, 0x80433a8e). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini031304-02.dmp.



Date: 3/13/2004

Time: 5:09:42 PM

Description:

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



Date: 3/7/2004

Time: 7:18:28 AM

Description:

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



Date: 3/5/2004

Time: 11:16:28 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffffffc, 0x000000ff, 0x00000000, 0x80467552). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini030504-03.dmp.



Date: 3/5/2004

Time: 11:13:09 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x5f524447, 0x000000ff, 0x00000000, 0x80467552). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini030504-02.dmp.



Date: 3/5/2004

Time: 7:32:51 PM

Description:

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



Date: 3/4/2004

Time: 9:26:35 AM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xd900000e, 0x000000ff, 0x00000000, 0x80467552). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini030404-01.dmp.



Date: 3/3/2004

Time: 8:44:49 PM

Description:

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



Date: 2/17/2004

Time: 8:48:38 PM

Description:

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



Date: 2/11/2004

Time: 10:20:51 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000099, 0x814773fc, 0x00000000, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini021104-01.dmp.



Date: 2/10/2004

Time: 6:12:28 AM

Description:

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



Date: 2/1/2004

Time: 1:03:27 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x07018031, 0x00000002, 0x00000000, 0x80466fdb). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini020104-02.dmp.



Date: 2/1/2004

Time: 7:57:11 AM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000004, 0x000000ff, 0x00000000, 0x80414414). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini020104-01.dmp.



Date: 1/28/2004

Time: 8:11:39 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000063, 0x00000002, 0x00000000, 0x8042a190). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini012804-02.dmp.



Date: 1/28/2004

Time: 8:06:44 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000e3 (0x80472a80, 0x81481000, 0x8149c668, 0x00000003). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini012804-01.dmp.



Date: 1/25/2004

Time: 7:14:12 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x6302e22d, 0x000000ff, 0x00000000, 0x80467552). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini012504-02.dmp.



Date: 1/25/2004

Time: 7:11:01 PM

Description:

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



Date: 1/20/2004

Time: 1:52:44 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xa929a925, 0x000000ff, 0x00000000, 0x80467552). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini012004-02.dmp.



Date: 1/20/2004

Time: 1:21:17 PM

Description:

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



Date: 1/19/2004

Time: 1:35:01 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xde491eec, 0x00000000, 0x80433a8e, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini011904-02.dmp.



Date: 1/19/2004

Time: 7:52:33 AM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000023 (0x000e00c8, 0xeda6a840, 0xeda6a498, 0x804176bd). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini011904-01.dmp.



Date: 1/17/2004

Time: 11:37:28 AM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000023 (0x000e00c8, 0xf81299b4, 0xf812960c, 0xbff6867e). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini011704-01.dmp.



Date: 1/16/2004

Time: 9:27:49 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xaa01ef0e, 0x000000ff, 0x00000000, 0x80467552). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini011604-01.dmp.



Date: 1/2/2004

Time: 11:43:37 PM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xc0a85d19, 0x00000001, 0xa00754e4, 0x00000002). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010204-01.dmp.
 
M

Mistoffolees

Kenneth said:
Over the course of the last three months I have received numerous
reboots on one of my W2K machines. It is running SP2 and I'd like to
upgrade to SP3 but am nervous because of the randomness of the bugcheck
problems, thinking I may not get my system to boot at all. My other
three W2K systems (all running SP3) are fine.
Click to expand...

<<snipped>>

Right now, it looks like there is a bad or corrupted driver
file. The stop error of 1/2/2004 is pointing to the hard drive
(0x00000050) and also for 1/17/2004 and 1/19/2004 (0x00000023),
possibly a small, unmarked bad sector on the hard drive where
the corrupt driver file is stored (0x0000000A) or (0x0000001E).
Recommend complete backup, re-partition and format the HD (to
remark bad spots and update table), and re-install.
 
M

Mistoffolees

Dan said:
Misto - does chkdsk /r not find & mark such bad sectors?
Click to expand...

<<snipped>

Good question. Have not run Chkdsk from the command prompt
in some time. But both chkdsk /r and chkdsk /f might work.
While it should mark out the bad sector, the driver file,
whatever it might be, may be already beyond recovery. Let's
see if there is more follow-up responses. Perhaps the OP
might give be able to provide some more clues.
 
K

Kenneth John Barclay

I did set the flag to run chkdsk /r on the next boot when I had the system up a while ago. It ran fine with no errors on the files or folders or in the free space. Also, most of the time that there was a crash and the dump was created the ScanDisk ran on the next boot with no problems. (Just some extra information.)

I've made an image of my disk and saved it. I'm going to wait for a bit to see if anyone else weighs in on a similar problem before I re-partition and re-format and reload.

Does anyone out there know how to interpret the savedump (mini-dump)???? I've got them all saved but don't know how to open or read them.

Dan said:
Misto - does chkdsk /r not find & mark such bad sectors?
Click to expand...

<<snipped>

Good question. Have not run Chkdsk from the command prompt
in some time. But both chkdsk /r and chkdsk /f might work.
While it should mark out the bad sector, the driver file,
whatever it might be, may be already beyond recovery. Let's
see if there is more follow-up responses. Perhaps the OP
might give be able to provide some more clues.
 
G

Ghostrider

Kenneth said:
I did set the flag to run chkdsk /r on the next boot when I had the
system up a while ago. It ran fine with no errors on the files or
folders or in the free space. Also, most of the time that there was a
crash and the dump was created the ScanDisk ran on the next boot with no
problems. (Just some extra information.)
Click to expand...

This situation has all the appearances of one of those random
on-off happenings. Something is being written to the hard drive
in the region where the pagefile.sys seems to reside and, by
chance, run into the bad (or "soft"), physical sector in the
HD spanned by it.
I've made an image of my disk and saved it. I'm going to wait for a bit
to see if anyone else weighs in on a similar problem before I
re-partition and re-format and reload.
Click to expand...

The perceived problem with this image file is that it just
might contain a corruption of the driver file because a disk
image is made by doing a sector-by-sector read and write. If
the flawed code is present in the imaged area, then it will be
transferred when used to recover the image.
Does anyone out there know how to interpret the savedump (mini-dump)????
I've got them all saved but don't know how to open or read them.
Click to expand...

Ever see the instructions on how to set up the computers and do
the read? Ain't worth it.

:)) HTH.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Crashing 2
Windows 2000 Server w/ Exchange 2003 keeps crashing and rebooting. 1
The computer has rebooted from a bugcheck. 1
BugCheck 1
BugCheck 1
rebooted from a bugcheck 1
Bugcheck? 2
The computer has rebooted from a bugcheck 1

Top