Re-Start lock up

nicthetool

New Member
the last time my pc rebooted it froze/locked up at windows logo page at times the puter wont even start in safe mode.
i even went to the extreme of attempting a clean install of xp, however at the setup screen where you would select a partition, it said unknown drive, then goes to blue error screen with this error
*** STOP: 0x0000008E (0x0000005, 0xF7418CAD, 0xF6FF27E4, 0x00000000)
*** setupdd.sys - Address F7418CAD base at F73EC00, Datestamp 41107c8f

any help on this issue/error or ideas on how to diagnose the problem would be great
i run an acer aspire intelD 2.8g 2.0gram 300g hd
thanks
 
If the hard drive isn't failing it may be due to either a cable needing replacement or something unwanted infected the system. You can try an extra cable if you have one onhand but you will most likely need to clean the drive off in order to see a good installation of Windows go on. Just trying to reinstall Windows over itself doesn't work with XP.

The current installation iwith the exception of a repair install would need to be removed. That will often require the deletion of the current primary partition it is on. Is this on a sata or ide type drive?
 
If the hard drive isn't failing it may be due to either a cable needing replacement or something unwanted infected the system. You can try an extra cable if you have one onhand but you will most likely need to clean the drive off in order to see a good installation of Windows go on. Just trying to reinstall Windows over itself doesn't work with XP.

The current installation iwith the exception of a repair install would need to be removed. That will often require the deletion of the current primary partition it is on. Is this on a sata or ide type drive?

i believe it is a sata drive. the thing with it is after several attempts the pc starts and gives all appearances of running well.
is there something i can do to check/repair any problems there may be
 
I can look at two things that may help there besides monitoring your system temps(cpu, board). Have you updated the bios or recently installed anything new? Another thing to note is that the manufacturers generally have disk utilities readily available for maintaining their brand drives.

A sata cable won't usually see the problems with intermittency like ide ribbon cables will after getting hardened up and somewhat brittle over time. But I've seen brand new cables that had to be tossed at times. It does sound like a flaky connection or perhaps a bios problem now being seen. How old is the board on the system there? Even new boards need an update when initial problems are seen at times.
 
I can look at two things that may help there besides monitoring your system temps(cpu, board). Have you updated the bios or recently installed anything new? Another thing to note is that the manufacturers generally have disk utilities readily available for maintaining their brand drives.

A sata cable won't usually see the problems with intermittency like ide ribbon cables will after getting hardened up and somewhat brittle over time. But I've seen brand new cables that had to be tossed at times. It does sound like a flaky connection or perhaps a bios problem now being seen. How old is the board on the system there? Even new boards need an update when initial problems are seen at times.

It is an 06 build board, i havent knowingly updated any bios recently
 
On many model boards now you simply download the winflash type update where you run that while Windows is loaded. That would be too new to consider a battery having gone weak enough to see problems. Why the installer is seeing hardware detection failure with the drive can point at three main things basically.

The first being a failure of the bios for some reason in properly detecting and posting the drive where the installer then properly detects it. The second is the worst case of seeing the drive going on you.

The second is the three things can result in seeing the first with one being the low cost battery, the second a cable, and the third being a loss of bios information by a weak battery or the worst being a failing chip on the board itself.

The third and surprisingly more common is a need to examine the installation disk itself for smudge marks from fingers or scratches if the drive is clean of any type of virus/malware or simply failing.
 
Back
Top