I just tried to ghost an external HD to another which also is plugged in a usb port. It locked up then when I rebooted I got the message 'Windows could not start because the following file is missing: \windows\system32\config\system"
This went on to say that this repair could be done with the XP install disk. So I put this in and when I hit the R to repair the blue screen of death came up. It had the error of
One of the hard drive I just recovered for a relative and got the data off it. The other is a refurbished from Electronicscafe (Ebay/Victor business).
I am presently running Avira Rescue disk to try and catch what is happening.
I tried Safe Mode but that won't start either.
I am fairly careful with security on my machine. Super Antispyware (purchased), Windows Defender, Avast (purchased), Malware Bytes...
Ironically, I have been trying to fix a neighbors machine with a similar problem except his just goes in an endless loop from startup to diagnostic to windows sign on screen to blue screen. (NO I have not plug swapped anything between the two. Only diagnostic CDs)
What is going on here? Presently on the other machine (my neighbors Acer laptop with XP home) I am running a deep scan with SpinRite.
My machine is HP desktop AMD x2 3 GB ram XP Pro 50% free HD.
From what I have read on Google this may be a registry issue... yuk.
Help? (presently I am working on a different computer than the one I receive my emails. I will check back OfteN!)
I worked on this machine for over six hours trying all these works mentioned. I realized that after that amount of time that I may be making matters worse. (I need this computer for certain aspects of my business.)
Consequently I sent it off to a well-spoken of shop to get repaired... That was three days ago and still no fix yet. They indicated it may have something to do with an internal modem or it may have a certain virus that has a 'scheduler' in it that continues to reinfect.
Is there a certain protocol to a repair like this so a person can avoid or minimize the time spent on 'hit or miss' or 'trying this or that' until something clicks? This all seems so time consuming. Correct diagnosis seems to be the first step. Correct?
The shop may be well-spoken of but it doesn't seem like they know what they're doing. Like I said in my earlier post, I use a IDE (or SATA) to USB cable to connect the hard drive to a running computer, copy the 5 registry files to C:\Windows\Temp, gain access to the System Volume folder and start restoring the newest version of the backup copies of the registry files until I find the set that works. Doesn't usually take longer than 30 minutes.
I have the original hard drive that I tried to clone. I am glad I did not clone it because even though Iwas able to see it with administrative storage tool I cannot access the data.
This is the drive that caused all the problem to begin with.
I have tried a variety of ways to access this and recover the HD at no avail... as of yet. (All this for a relatives computer HD 3,000 miles away.)