Wierd computer lock-ups

[AN O'Nymous]

Any idea what might be causing this? I've had 2 hard disks die in the
span of a few weeks, including a brand new 300GB Seagate. The other was
an 80GB Maxtor. Bad luck or is something on this work PC dying? (Antec
Smartpower 350W + Abit NF7).

Windows Event Viewer logs:

Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 11
Date: 23/03/2006
Time: 22:01:50
User: N/A
Computer: WORK
Description:
The driver detected a controller error on \Device\Ide\IdePort0.

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.

Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 23/03/2006
Time: 22:01:50
User: N/A
Computer: WORK
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout
period.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 64 00 ......d.

Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 23/03/2006
Time: 22:01:39
User: N/A
Computer: WORK
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout
period.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 64 00 ......d.


Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 23/03/2006
Time: 22:01:26
User: N/A
Computer: WORK
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout
period.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 64 00 ......d.

Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 23/03/2006
Time: 22:01:15
User: N/A
Computer: WORK
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout
period.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 64 00 ......d.


Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 23/03/2006
Time: 22:01:04
User: N/A
Computer: WORK
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout
period.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 64 00 ......d.

 

[AN O'Nymous]

I forgot to mention...the computer freezes when this happens for
several seconds. Then, all of a sudden, everything is back to normal.

 

[kony]

Any idea what might be causing this? I've had 2 hard disks die in the
span of a few weeks, including a brand new 300GB Seagate. The other was
an 80GB Maxtor. Bad luck or is something on this work PC dying? (Antec
Smartpower 350W + Abit NF7).

<logs snipped>

The logs are typical of the drives failing, are mostly a
symptom of that and reveal nothing in particular.

Were they running hot? Was there a LOT of very fine
particulate dust that might penetrate the drive breather
filter (If they are so equipped, I haven't been checking
drives for those recently and some hide them fairly well) ?

Check your power supply voltages too. Certain system
configurations with the NF7 might be too high a load for
that PSU.

 

[AN O'Nymous]

Hi Kony. Thanks for the info. I'm guessing the problem could be either
(or more):
1) Damaged Abit NF7 motherboard;
2) Bad Antec Smartpower 350W PSU;
3) Bad generic IDE cables;
4) Permanently damaged components (hence why the errors are appearing
even on a separate system)

The logs are typical of the drives failing, are mostly a
symptom of that and reveal nothing in particular.

What I don't get is that the logs refer to an atapi problem (under the
"source" column). Microsoft's explanation for it is a dodgy disc in
drive, I had no discs in them. Also, a very slow responding computer +
lock ups are more symptomatic of hard drive failures, based on past
experience.

Were they running hot? Was there a LOT of very fine
particulate dust that might penetrate the drive breather
filter (If they are so equipped, I haven't been checking
drives for those recently and some hide them fairly well) ?

I've recently brought down my system's temperature by opening up the
casing and using a 19" fan.

Check your power supply voltages too. Certain system
configurations with the NF7 might be too high a load for
that PSU.

I am now increasingly worried. My last 3 hard drives (Seagate 160GB
HDD, 2x IBM/Hitachi 120GB HDDs) have errors detected in them. The other
2 drives that failed were a Maxtor 80GB and Seagate 300GB. I have taken
screenshots of all (with my digital camera - I don't have a floppy
drive) and if you're interested in looking at any, let me know.

The main errors were file structure errors and 1 set of cable errors
(56, actually). I have replaced the suspect cable, but I hope no
permanent damage was done.

All except the 80GB and 300GB HDDs were full, and I have critical work
data on these remaining drives. I am FTPing the most important ones
(source codes) to my work servers now but some, including data and
computational results are simply too big to FTP or even backup to DVDs
in any reasonable time.

Most of the hard drive errors are file structure errors. Is this
permanent damage or recoverable? I got such an error even on a 1 week
old 300GB HDD I re-formatted on a fresh system.

Recently, I installed a Gigabit ethernet card. I got a wierd error
while using my CD/DVD drives to burn, which I read was due to not
enough power. I unplugged one and the 2nd one started working.

Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 25/02/2006
Time: 17:46:12
User: N/A
Computer: WORK
Description:
The device, \Device\CdRom0, has a bad block.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 01 68 00 01 00 b8 00 ..h...¸.


All my USB devices do not work now, even on a "pared down" system that
has 1 HDD, 1 DVD-RW, 1 PCI/ATA card, 1 Radeon 9800 Pro and 1 Audigy.
Previously, my system had 3 HDDs, 2 CD/DVD-RWs, 1 PCI/ATA card, 1
Radeon 9800 Pro, 1 Audigy, 1 Gigabit ethernet, 3 extra fans.

Sometimes the USB devices do not even light up/are detected. Other
times I get the error log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 24/03/2006
Time: 10:00:44
User: N/A
Computer: WORK
Description:
The General Purpose USB Driver (adildr.sys) service failed to start due
to the following error:
The service cannot be started, either because it is disabled or because
it has no enabled devices associated with it.

Recently, I also tried overclocking my AMD XP 2500+ to a 3200+. It
worked after some trial and error on the voltages (upped to 1.8v).
Before installing the Gigabit ethernet, I set it back to its factory
setting.

 

[AN O'Nymous]

To clarify, the USB devices work on the separate, fresh system. This
suggests permanent damage to either the Antec PSU or NF7 motherboard,
perhaps by the overclock tests of mine and/or too high power loads.

 

[kony]

To clarify, the USB devices work on the separate, fresh system. This
suggests permanent damage to either the Antec PSU or NF7 motherboard,
perhaps by the overclock tests of mine and/or too high power loads.

When overclocked, did you test stability with tools like
Prime95's Torture Test (large FFT setting) and memtest86+?
I would wonder if there were errors partially to blame, but
if you had reinstalled the OS, not o'c since then and still
the errors newly occuring then obviously that it's it.

Your voltage was a bit high for the 3200 speed, it seems
your CPU isn't such a good o'c candidate. If you had raised
AGP/PCI rather than leaving fixed at 66/33, that could
account for filesystem errors. Otherwise I'd suspect
cables, jumpers, one of the drives failing making the other
also appear bad and would consider disconnecting all
non-critical drives but the HDD running the OS, temporarily.
As for moving this data off the system you might take
another hard drive(s), temporarily connect and copy it all
off, checking that it appears intact then leaving that HDD
disconnected.

Providing your temps aren't too high, including the
southbridge, I'd suspect the PSU more than the board. On
those nForce2 boards I own I have epoxied on small heatsinks
to the southbridge, nothing elaborate, just whatever was
handy as I've collected quite a few 'sinks from misc.
electronics work as well as computer related. I'd imagine
something like the following would be the most economical
way to 'sink a NF2 southbridge but it is only a guess, since
the ones I've used were slightly larger and epoxy works
better than typical pre-applied adhesive material.
http://www.alltronics.com/heat_sinks.htm
(# 22Z014)

Another example,
http://www.excesssolutions.com/cgi-bin/item/ES3441

This is more similar to what I've used but on NF7 it looks
like the adjacent screw and crystals might be in the way, it
probably wouldn't fit,
http://www.excesssolutions.com/cgi-bin/item/ES2279
it's base is pretty thin though, a hacksaw and some elbow
grease would fix that.

Even so, I may be leading you on a wild goose chase with the
heatsink but in that era I'd heard some comments about the
SB running hot on some boards so I went ahead and 'sinked
mine.

As for the PSU, you might unplug it for awhile, open and
inspect areas such as the larger caps near the wiring
harness, output for venting, as well as trying other cables,
even underclocking the FSB temporarily to see if it helps.

 

[AN O'Nymous]

When overclocked, did you test stability with tools like
Prime95's Torture Test (large FFT setting) and memtest86+?

Yes, Prime95 is how I determined the "working" voltage to be 1.8v.
Anything under and it would lock up.

I haven't overclocked my PC since I got a new cooling system though...a
fully open case with a 19" fan blowing straight into it

I would wonder if there were errors partially to blame, but
if you had reinstalled the OS, not o'c since then and still
the errors newly occuring then obviously that it's it.

Unless there is some permanent damage I didn't notice. Is this a
possibility?

Your voltage was a bit high for the 3200 speed, it seems
your CPU isn't such a good o'c candidate. If you had raised
AGP/PCI rather than leaving fixed at 66/33, that could
account for filesystem errors. Otherwise I'd suspect
cables, jumpers, one of the drives failing making the other
also appear bad and would consider disconnecting all
non-critical drives but the HDD running the OS, temporarily.

I'm doing a full surface scan on the 300GB Seagate. Do you know if
power issues might make hard disks make a squeaking + beeping sound? It
was very worrying when I heard it.

What about "Windows can't read the boot sector"?

Even so, I may be leading you on a wild goose chase with the
heatsink but in that era I'd heard some comments about the
SB running hot on some boards so I went ahead and 'sinked
mine.

Is there a way for me to determine the SB temp? What temp does the
"mobo temperature" Sisoft sandra report refer to? Don't forget I've got
a 19" fan blowing right on the mobo...

As for the PSU, you might unplug it for awhile, open and
inspect areas such as the larger caps near the wiring
harness, output for venting, as well as trying other cables,
even underclocking the FSB temporarily to see if it helps.

I will try, although since unplugging everything except 1 HDD, things
seem to be working again, except the USB devices.

It could mean its the PSU, mobo or that the HDDs I unplugged so
happened to be the problem ones.

 

[kony]

Yes, Prime95 is how I determined the "working" voltage to be 1.8v.
Anything under and it would lock up.

I haven't overclocked my PC since I got a new cooling system though...a
fully open case with a 19" fan blowing straight into it


Unless there is some permanent damage I didn't notice. Is this a
possibility?

Besides filesystem damage, no there is generally no remants
of damage after overclocking. It can degrade (cheap
silicone based) thermal compound faster, the extra heat can
wear out capacitors faster, or if the CPU was overheating a
LOT, that can physically damage the CPU itself (typically on
an Athlon, you'd see a dark(er) brown patch on the back
behind the core). In general, these are extreme cases and
not *likely* the problem.

I'm doing a full surface scan on the 300GB Seagate. Do you know if
power issues might make hard disks make a squeaking + beeping sound? It
was very worrying when I heard it.

I wouldn't say it's impossible, but generally the drive
itself would have the problem.

What about "Windows can't read the boot sector"?

Could be system instability in general but also the drive
itself is suspect.

Is there a way for me to determine the SB temp? What temp does the
"mobo temperature" Sisoft sandra report refer to? Don't forget I've got
a 19" fan blowing right on the mobo...

With the fan it's probably not the southbridge overheating,
but a couple ways to test are a simple put_your_
finger_on_it (crude but if it feels really hot, it is), or
attach a thermal sensor. Obviously the thermal sensor is
the desired method or an infrared type of thermometer.

I will try, although since unplugging everything except 1 HDD, things
seem to be working again, except the USB devices.

It could mean its the PSU, mobo or that the HDDs I unplugged so
happened to be the problem ones.

You might have more than one problem, perhaps a blown USB
fuse or too much trying to use 5VSB power. That is, if your
board is jumpered to deliver 5VSB to the USB ports, rejumper
to regular 5V power instead. This is assuming system is
still at stock speed, overclocking obviously has it's own
potential to foul up USB.