Hard Disk Failure

R

rory.groves

Inherited a barebones box, so I put in 1 GB RAM, new video card, a
300gb hard drive and installed Windows XP. About every other day the
machine crashes and reboots, but fails to detect the hard drive. When i
turn on the monitor, it has the "primary drive not recognized..." error
on the DOS screen.

All I have to do is turn off, then turn back on the computer and the
hard drive is recognized automatically, and boots normally. But then
crashes again within 48 hours. Windows event log has no indication of
any problems, so i'm pretty certain its a hardware issue.

Question is, which piece of hardware? HD? Memory? Motherboard? The only
thing i have tried replacing is the HD cables inside the box, but that
didn't help anything.
 
R

Rod Speed

Inherited a barebones box, so I put in 1 GB RAM, new video card,
a 300gb hard drive and installed Windows XP. About every other day
the machine crashes and reboots, but fails to detect the hard drive.
When i turn on the monitor, it has the "primary drive not recognized..."
error on the DOS screen.
All I have to do is turn off, then turn back on the computer and the
hard drive is recognized automatically, and boots normally. But then
crashes again within 48 hours. Windows event log has no indication
of any problems, so i'm pretty certain its a hardware issue.

Yep, almost certain.
Question is, which piece of hardware? HD? Memory? Motherboard?

Its most likely to be the motherboard, could be the power supply.
Have a look at the capacitors, these are usually blue or black
plastic covered post like things sticking up vertically from the
motherboard. They should be flat on top, check if any bulge
or have leaked visibly on top. If they have, replace the mb.

If the motherboard looks fine, its cheaper
and easier to try another power supply.

Memory doesnt usually produce those symptoms,
particularly the hard drive not visible on a reboot.

I did see an intermittent short to case produce those
symptoms, but it isnt common. The test for that is to
run with the motherboard loose on the desktop and see
if the problem goes away.
The only thing i have tried replacing is the HD cables
inside the box, but that didn't help anything.

Those wont usually produce a crash like that.
 
A

Arno Wagner

Previously said:
Inherited a barebones box, so I put in 1 GB RAM, new video card, a
300gb hard drive and installed Windows XP. About every other day the
machine crashes and reboots, but fails to detect the hard drive. When i
turn on the monitor, it has the "primary drive not recognized..." error
on the DOS screen.
All I have to do is turn off, then turn back on the computer and the
hard drive is recognized automatically, and boots normally. But then
crashes again within 48 hours. Windows event log has no indication of
any problems, so i'm pretty certain its a hardware issue.
Question is, which piece of hardware? HD? Memory? Motherboard? The only
thing i have tried replacing is the HD cables inside the box, but that
didn't help anything.

I would say drivers (fail to initialise controller and disk poperly)
or controller (fails to reset the HDD properly). If there is a bus
problem, the HD becomes inaccessible. I had this on very few
occasions with a Promise IDE controller, that crashed under
Linux and then needed a reboot or hard-reset (button) to find
the disk again.

One thing you can try is make the IDE bus a bit slower, i.e.
reduce it ot 66MHz if it runns at 100MHZ or to 100MHz if
it runns at 66MHz. This may prevent the problem from happening
in the first place.

Arno
 
R

Rus

(e-mail address removed) wrote in @g49g2000cwa.googlegroups.com:
Inherited a barebones box, so I put in 1 GB RAM, new video card, a
300gb hard drive and installed Windows XP. About every other day the
machine crashes and reboots, but fails to detect the hard drive. When i
turn on the monitor, it has the "primary drive not recognized..." error
on the DOS screen.

Question is, which piece of hardware? HD? Memory? Motherboard?

If I was you (and I have been in similar situations no doubt about it), I'd
be sitting there right now thinking, "Aha -- no wonder I got this thing for
free."

Nevertheless ...

Four things I'd consider:

(1) The drive controller chips are on the motherboard. If they're faulty or
if some component of the motherboard is faulty, there's only one thing to do.
MB replacement kinda ruins the deal.

(2) Maybe it's a simple matter of that 300GB hard drive size? Once you go
beyond about 137GB, isn't it true that the BIOS must be able to utilize 48-
bit Logical Block Addressing (LBA)?

Is that MB capable of managing a 300 GB hard drive?

(3) Have you tried another hard drive in that computer to see if elimination
of that one drive allows you to run successfully?

(4) Windows XP can be really picky about CRC (data integrity checking). You
can de-sensitize XP so that it will be more tolerant.

Look at the Microsoft Knowledge Base Article located at:
http://support.microsoft.com/kb/817472/

Maybe you could try that M$ fix?

//rus//

//rus//
 
R

Rod Speed

Rus said:
(e-mail address removed) wrote
If I was you (and I have been in similar situations
no doubt about it), I'd be sitting there right now
thinking, "Aha -- no wonder I got this thing for free."

There's plenty of systems tossed by people who dont have the
knowledge or diagnostic capability to fix less than obvious problems.
Nevertheless ...
Four things I'd consider:
(1) The drive controller chips are on the motherboard. If they're
faulty or if some component of the motherboard is faulty, there's
only one thing to do. MB replacement kinda ruins the deal.
(2) Maybe it's a simple matter of that 300GB hard drive size?
Once you go beyond about 137GB, isn't it true that the BIOS
must be able to utilize 48- bit Logical Block Addressing (LBA)?

Nope, the lack of 40bit LBA support in the bios just
produces some effects with utes that get their info
from the bios that can be readily worked around.

And that doesnt produce that set of symptoms anyway.
Is that MB capable of managing a 300 GB hard drive?
(3) Have you tried another hard drive in that computer to see
if elimination of that one drive allows you to run successfully?
(4) Windows XP can be really picky about CRC (data integrity checking).

Again, doesnt produce that set of symptoms.
You can de-sensitize XP so that it will be more tolerant.
Look at the Microsoft Knowledge Base Article located at:
http://support.microsoft.com/kb/817472/
Maybe you could try that M$ fix?

It wont be that.
 
R

Rus

Geesh. I'm just trying to help and you're slammin' me!

There's plenty of systems tossed by people who dont have the
knowledge or diagnostic capability to fix less than obvious problems.

Your post says it might be the MB or the PS. Well, in a "barebones" system,
there's not much besides a case, memory, motherboard and a power supply. If
we replace the motherboard and/or the power supply, isn't that tantamount to
"tossing" a system? I mean, the MB and PS covers two of the most expensive
components. Unless that barebones system has a really good looking "tricked
out" case, I think I'd "toss" the system for sure after cannibalizing the
memory and CPU for another project.

It looks like, in other words, you are saying that if I get a car for free
from someone and it has a good radio, then I shouldn't "toss" the car just
because the engine and transmission are bad. According to your logic, I'm
"tossing" a perfectly good car because I lack the knowledge and/or diagnostic
capability to fix the less than obvious problems which require replacement of
the engine and transmission.

Nope. I'll save the radio and scrap the car unless the car is some rare
classic that deserves to be restored.

In his case, if the MB and/or the PS are bad, I'd take the CPU and memory and
scrap the "barebones" unless that "barebones" is some rare antique that's
worth a complete restoration.


Nope, the lack of 40bit LBA support in the bios just
produces some effects with utes that get their info
from the bios that can be readily worked around.

And that doesnt produce that set of symptoms anyway.

Don't you mean 48-bit LBA instead of 40-bit?

And ... by the way ... What's a "ute." Are you Joe Pesci? Or are you
referring to a utility? What's a utility got to do with a crash while in XP?
Are you referring to drive overlay software or something of the sort?

It wont be that.

How do you know? Wouldn't take but a couple of registry entries to try.

Or, perhaps, we should not waste time trying a few hacks and just go ahead
and plunk down the cash for a new MB and PS?

And suppose it is capacitors on the board that are at fault? It's not easy
to find properly spec'd caps to replace them. Total the time it takes to
find replacement caps, repair the copper traces that might have lifted from
the board and it gets to be a time consuming job without adequate return on
investment. If it takes more than an hour to do the whole job, I'd have to
say it's not worth it since a new MB can be had for around $35.

//rus//
 
R

Rus

(e-mail address removed) wrote in @g49g2000cwa.googlegroups.com:

All I have to do is turn off, then turn back on the computer and the
hard drive is recognized automatically, and boots normally. But then
crashes again within 48 hours. Windows event log has no indication of
any problems, so i'm pretty certain its a hardware issue.

I forgot to mention: Did you turn off the auto restart after failure in
WinXP?

Start-->My Computer-->Right Click-->Properties-->Advanced-->Startup &
Recovery-->Settingsk-->System Failure-->uncheck "automatically restart."

//rus//
 
F

Folkert Rienstra

That's not the DOS screen.
If I was you (and I have been in similar situations no doubt about it), I'd
be sitting there right now thinking, "Aha -- no wonder I got this thing for
free."

Nevertheless ...

Four things I'd consider:

(1) The drive controller chips are on the motherboard. If they're faulty or
if some component of the motherboard is faulty, there's only one thing to do.
Nope.

MB replacement kinda ruins the deal.

So you don't replace it, install an add-in controller instead.
(2) Maybe it's a simple matter of that 300GB hard drive size? Once you go
beyond about 137GB,
isn't it true that the BIOS must be able to utilize 48-bit Logical Block Addressing (LBA)?
Nope.


Is that MB capable of managing a 300 GB hard drive?

And what has that got to do with not recognizing the HD after
it has been demonstrated to be able to work fine for a while.
 
R

Rod Speed

Rus said:
Geesh. I'm just trying to help and you're slammin' me!

No I'm not. Just pointing out some potential problem
areas which wont produce the symptoms he is seeing.
Your post says it might be the MB or the PS. Well,
in a "barebones" system, there's not much besides
a case, memory, motherboard and a power supply.

Its not a barebones system NOW, he's added what else
is needed to produce a usable system and the problem
he is seeing could just as easily be in what he has added.
If we replace the motherboard and/or the power supply,

I wasnt suggesting both be changed, I clearly said that its
cheaper to try a different power supply and its may well be
possible to try a different power supply without buying one.
isn't that tantamount to "tossing" a system?

Nope, most obviously if he tries a power supply out of the system
he is posting from etc to see if that makes any difference.
I mean, the MB and PS covers two of the most expensive components.

No it doesnt with the total of components he has in that system NOW.

And I told him how to check the motherboard visually for the most
common way motherboards fail. If it has got bad caps, it may well
be that the original barebones system wasnt of much value, but now
that he has added 1G of memory and a 300G hard drive and a video
card, if he's bought those, it may be worth getting another motherboard
now and write it off to experience, that it would have been better to
test the barebones system before spending on the extra hardware.
Unless that barebones system has a really good looking
"tricked out" case, I think I'd "toss" the system for sure
after cannibalizing the memory and CPU for another project.

Really depends on whether that extra hardware was purchased
for that new system based on the discarded barebones.
It looks like, in other words, you are saying that if I get a car for
free from someone and it has a good radio, then I shouldn't "toss"
the car just because the engine and transmission are bad.

I said NOTHING like that. I JUST pointed out that it wont be
lack of 48bit LBA support in the bios, because that produces
quite different symptoms to the ones he is seeing.
According to your logic, I'm "tossing" a perfectly good
car because I lack the knowledge and/or diagnostic
capability to fix the less than obvious problems which
require replacement of the engine and transmission.

PCs are much less obvious for many users than cars.

You cant even manage to work out that the lack of 48 bit LBA
support in the bios wont produce the symptoms he is seeing.
Nope. I'll save the radio and scrap the car unless the
car is some rare classic that deserves to be restored.

And if the problem with the barebone system is JUST the
power supply, a new one will cost a small part of what he
has already spent on 1G of ram, 300G hard drive and a
video card if he has purchased those to add to the barebone.
In his case, if the MB and/or the PS are bad, I'd take the CPU
and memory and scrap the "barebones" unless that "barebones"
is some rare antique that's worth a complete restoration.

That would be silly if he has has already spent on 1G of ram,
300G hard drive and a video card if he has purchased those
to add to the barebone and it just needs a new power supply.

It may well make sense to replace the motherboard if it
has got bad caps and he has already bought the 1G of
ram, 300G hard drive and a video card for the barebone.
Don't you mean 48-bit LBA instead of 40-bit?

Yep, just a typo.
And ... by the way ... What's a "ute."

You worked that out for yourself.
Are you Joe Pesci?
Nope.

Or are you referring to a utility?

Yep, it aint anything like rocket science.
What's a utility got to do with a crash while in XP?

The need for 48bit LBA support in the bios is because
some drive utes use the data from the bios with drives.
Are you referring to drive overlay software or something of the sort?
Nope.
How do you know?

I know that doesnt produce the symptoms he is seeing.

And that KBA says it doesnt. It sees the drive used in PIO mode.
Wouldn't take but a couple of registry entries to try.

Pointless, he isnt seeing the drive in PIO mode.
Or, perhaps, we should not waste time trying a few hacks and
just go ahead and plunk down the cash for a new MB and PS?

No point in trying stuff that doesnt produce the symptoms he is seeing.
And suppose it is capacitors on the board that are at fault?
It's not easy to find properly spec'd caps to replace them.

And even harder to replace them. The only viable
approach is to replace the motherboard or scrap it.
Total the time it takes to find replacement caps, repair the
copper traces that might have lifted from the board and it
gets to be a time consuming job without adequate return
on investment. If it takes more than an hour to do the
whole job, I'd have to say it's not worth it since a
new MB can be had for around $35.

Duh. I never ever suggested replacing the caps.
 
R

Rod Speed

Rus said:
(e-mail address removed) wrote
I forgot to mention: Did you turn off the auto restart after failure in
WinXP?
Start-->My Computer-->Right Click-->Properties-->Advanced-->Startup &
Recovery-->Settingsk-->System Failure-->uncheck "automatically restart."

Fat lot of good that will do, he has to turn the
system off to get the hard drive recognised again.
 
R

rory.groves

An update... I replaced the CMOS battery as a first step, and haven't
had a problem since. its only
been 1 week, but it looks very promising..

Thanks to all who provided suggestions.
 
R

rory.groves

Well, it might not have solved things after all. Came downstairs
tonight to find it on the dos boot screen again. It lasted almost a
month without incident instead of crashing every other day.
 
R

rory.groves

Found this little tidbit in the eventviewer just before the last crash:

Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 2/25/2006
Time: 1:06:46 AM
User: N/A
Computer: SOLAR
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout
period.


MS Online Help lists this as a CD-ROM error....
 

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

Top