Crash! - which component fails?

[Lars]

I have a problem after replacing HDD. Cloned old to new and then started
machine which got very
instable. Froze and had to be restarted. Brought back old HDD but had same
problem. Could not even
install WinXP as screen froze halfway.

Got even worse and I decided to test memory as I have had similar problem
before which turned out to
be a bad memory module. I used "Windows Memory Diagnostics", from Microsoft.
Performed a test
on my other PC which went OK. Tried to test fauly machine but tester only
ran for < 10 seconds and then
froze. Runs under DOS.

Any experience of what might caus the problem will be appreciated. Could a
faulty HDD cause this as
the problem occured when changing? Any other component? Any good diagnostic
tool to use to test
components in machine?


Lars

 

[Jerry G.]

I would think by coincidence you have a bad RAM, or a bad RAM I/O buffer on
the mother board. I have had bad RAM or a defect on the mother board,
in-fact corrupt a hard disk. If the factory disk drive table-record part of
the drive is damaged, then you technically have a defective drive. In this
case, I would say it was the bad RAM that caused the drive failure, not the
reverse.

Fix the problem with the computer so that the RAM test will pass. Then see
of you can get the software for the factory low level setup for your drive.
Then after you re-setup the drive again, then re-install your ghosted image.
This should work for you.

If you have to change the mother board to fix the fault, you will most
likely need to re-install the operating system to have it properly match.


--

Jerry G.
======


I have a problem after replacing HDD. Cloned old to new and then started
machine which got very
instable. Froze and had to be restarted. Brought back old HDD but had same
problem. Could not even
install WinXP as screen froze halfway.

Got even worse and I decided to test memory as I have had similar problem
before which turned out to
be a bad memory module. I used "Windows Memory Diagnostics", from Microsoft.
Performed a test
on my other PC which went OK. Tried to test fauly machine but tester only
ran for < 10 seconds and then
froze. Runs under DOS.

Any experience of what might caus the problem will be appreciated. Could a
faulty HDD cause this as
the problem occured when changing? Any other component? Any good diagnostic
tool to use to test
components in machine?


Lars

 

[Enry]

I had a similar problem. It was a contact between the RAM module and the IDE
bus. Check if they are separated.It is possible that during installation
that cable was moved. I had problems with RAM because this contact caused
some sort of interference and the system bacame unstable. I've tried
everything, but at the end I've solved the problem simply. Sorry for my
english.