Random reboots

[Janice]

My son's PC has started to reboot randomly. I took it into my local PC store
to have it checked out. They tell me that they have checked out the memory,
video card, virus checking etc but could find nothing. In the three days
they tested it, it did not reboot once! However I would have to say that it
happens when my son is doing something, not just the PC sitting there doing
nothing.

So I take it home, connect it up and it crashes just as MSN is automatically
signing in. I'm told it must be a piece of hardware that I'm using at home.
However all it's connected to is a monitor, cordless keyboard & mouse, and a
LAN cable.

Event viewer shows up these problems - both mentioned to the PC store but
nothing done about them.

Event Type: Information

Event Source: Save Dump

Event Category: None

Event ID: 1001

Date: 17/06/2004

Time: 19:47:29

User: N/A

Computer: GRAHAM

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f
(0x0000000d, 0x00000000, 0x00000000, 0x00000000). A dump was saved in:
D:\WINDOWS\Minidump\Mini061704-03.dmp.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



Event Type: Error

Event Source: atapi

Event Category: None

Event ID: 5

Date: 17/06/2004

Time: 19:45:34

User: N/A

Computer: GRAHAM

Description:

A parity error was detected on \Device\Ide\IdePort1.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 0f 06 10 00 01 00 64 00 ......d.

0008: 00 00 00 00 05 00 04 c0 .......À

0010: 03 00 00 80 00 00 00 00 ...€....

0018: 00 00 00 00 00 00 00 00 ........

0020: 00 00 00 00 00 00 00 00 ........

0028: 00 00 00 00 00 00 00 00 ........

0030: 00 00 00 00 01 00 00 00 ........



Event Type: Error

Event Source: Disk

Event Category: None

Event ID: 11

Date: 17/06/2004

Time: 21:35:35

User: N/A

Computer: GRAHAM

Description:

The driver detected a controller error on \Device\Harddisk1\D.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 03 00 68 00 01 00 b6 00 ..h...¶.

0008: 00 00 00 00 0b 00 04 c0 .......À

0010: 01 01 00 00 00 00 00 00 ........

0018: 00 00 00 00 00 00 00 00 ........

0020: 00 00 00 00 00 00 00 00 ........

0028: a8 00 00 00 00 00 00 00 ¨.......

0030: ff ff ff ff 02 00 00 00 ÿÿÿÿ....

0038: 40 00 00 8f 02 00 00 00 @......

0040: 00 20 0a 12 40 03 20 00 . ..@. .

0048: 00 00 00 00 0a 00 00 00 ........

0050: 00 20 37 82 78 f9 3c 82 . 7,xù<,

0058: 00 00 00 00 70 6e 3d 82 ....pn=,

0060: 02 00 00 00 00 00 00 00 ........

0068: 28 00 00 00 00 00 00 00 (.......

0070: 01 00 00 00 00 00 00 00 ........

0078: f0 00 04 00 00 00 00 0b ð.......

0080: 00 00 00 00 08 03 00 00 ........

0088: 00 00 00 00 00 00 00 00 ........





I've also got a similar error on "atapi" for the same IDE port. I've changed
the IDE cable but that didn't help.







This is another I also saved before taking the PC in.



Event Type: Error

Event Source: System Error

Event Category: (102)

Event ID: 1003

Date: 15/06/2004

Time: 08:01:18

User: N/A

Computer: GRAHAM

Description:

Error code 1000008e, parameter1 c0000005, parameter2 bf877e1b, parameter3
f223f818, parameter4 00000000.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 53 79 73 74 65 6d 20 45 System E

0008: 72 72 6f 72 20 20 45 72 rror Er

0010: 72 6f 72 20 63 6f 64 65 ror code

0018: 20 31 30 30 30 30 30 38 1000008

0020: 65 20 20 50 61 72 61 6d e Param

0028: 65 74 65 72 73 20 63 30 eters c0

0030: 30 30 30 30 30 35 2c 20 000005,

0038: 62 66 38 37 37 65 31 62 bf877e1b

0040: 2c 20 66 32 32 33 66 38 , f223f8

0048: 31 38 2c 20 30 30 30 30 18, 0000

0050: 30 30 30 30 0000



Is it hardware related or software?



Janice

 

[WinGuy]

----- Original Message -----
From: "Janice" <[email protected]>
Newsgroups: microsoft.public.windowsxp.help_and_support
Sent: Monday, 12 July, 2004 1:20 PM
Subject: Re: XP Home rebooting randomly

It all started this way when the system was bought in July 2002 - worked
fine since then. In May of this year, my elder son changed over the CD-Rom
drive for a newer, faster one. Everything worked fine for a month - or at
least so we thought. When the rebooting problem appeared, I started looking
into things and noticed that the 2nd HD was missing.

When the errors first appeared, MS help pointed out that the usual cause was
a faulty cable. I replced the cable at that point. So basically I have now
use two IDE cable and both give the same error. Do you want me to try a
third cable? Although I'm not sure I actually have a third cable. Can't
imagine that both cables would be faulty though.

I didn't notice that you'd indicated that fact before. So, no. At most you
could completely still swap the existing 2 flat cables around and that would
rule out some outlandish coincidence and astronomical probabilities. So, now
I think the cable is ruled out. Doesn't leave much else to blame, does it.

Unfortunately, I still get the rebooting problem even with no devices
connected to the secondary IDE.

That could be caused by a faulty motherboard, in this case more specifically
the IDE controller chip. It's the only thing reflecting errors in Event
Viewer, so ipso facto it's probably the culprit. No devices connected, so no
device to report about, but the chip still malfunctions regardless. Just
because it has no device load on it doesn't mean it's not loading down a
system buss regardless. I bet it eventually results in errors even with only
one device connected to it, master or slave. I think that is my final
diagnosis, the best I can do remotely and without the laying on of hands.
The diagnosis does not bode well for the continued welfare of your C drive,
either.

Hopefully, the shop will prove me wrong.

 

[Janice]

----- Original Message -----
From: "Janice" <[email protected]>
Newsgroups: microsoft.public.windowsxp.help_and_support
Sent: Monday, 12 July, 2004 1:20 PM
Subject: Re: XP Home rebooting randomly



I didn't notice that you'd indicated that fact before. So, no. At most you
could completely still swap the existing 2 flat cables around and that would
rule out some outlandish coincidence and astronomical probabilities. So, now
I think the cable is ruled out. Doesn't leave much else to blame, does it.


That could be caused by a faulty motherboard, in this case more specifically
the IDE controller chip. It's the only thing reflecting errors in Event
Viewer, so ipso facto it's probably the culprit. No devices connected, so no
device to report about, but the chip still malfunctions regardless. Just
because it has no device load on it doesn't mean it's not loading down a
system buss regardless. I bet it eventually results in errors even with only
one device connected to it, master or slave. I think that is my final
diagnosis, the best I can do remotely and without the laying on of hands.
The diagnosis does not bode well for the continued welfare of your C drive,
either.

Hopefully, the shop will prove me wrong.

It is a complete mystery to me.

However thank you for your patience and help. I'm going to run an extended
memtest whilst my son is away for a few days and see if it throws up
anything just in case although I'm beginning to doubt it.

Thanks again.

Janice

 

[Janice]

so

It is a complete mystery to me.

However thank you for your patience and help. I'm going to run an extended
memtest whilst my son is away for a few days and see if it throws up
anything just in case although I'm beginning to doubt it.

Thanks again.

Janice

Just thought you might be interested in an update.

I tried the system out with a completely different monitor, keyboard, mouse,
LAN cable, power cable and socket. Still the problem remains.

I mentioned it to the guys in the shop again. One of the techs suggested
using SETI, a little program that uses all your CPU power when you're not
using it. It's used for cancer research. Anywat that had stopped in March
but I did find another - UD Agent.

First time I ran it - the PC froze after 3 minutes.

Second time - froze again

Third time - froze again and also emitted a long continuous sound.

The techs at the shop say motherboard or CPU - most likely motherboard. They
would try another CPU to rule that out. However a moderator on a PC help
forum still says his bet is on memory even though I've run memtest86 for
about 3 days in total - says the test is not infallible.

Anyway, cost to fix would be about £45-£55 depending on whether it's memory,
CPU or motherboard. I've just bought an upgraded system so the plan was to
sell this - is it worth fixing?

Specs are;

AMD XP2000
512 MB DDR ram
Cd writer
Cd-Rom
60GB HDD and 13GB HDD
Win XP Home

Janice