General discussion
May 20, 2006 at 11:36 AM
xdrylandx

Slave Drive Causes Boot Loop

by xdrylandx . Updated 19 years, 12 months ago

My Original HD wouldn’t boot into windows or the windows xp cd. It would give me an stop message of 0x00000024. Using KNOPPIX, I can see all the files are still on the corrupt disk. I’ve installed a new hard drive, installed windows, and set the corrupt hard drive as a slave attempting to move the files from the old hard drive to the new.

The problem is, if the old, corrupt hard drive is hooked up at all, no matter if it is a slave, I cannot boot into Windows and causes the boot loop. I’ve tried the recovery console on the cd but it will not let me get far before the stop error message is displayed.

Without the old disk connected the new hard drive works fine. I’m on it now. I’ve tried to hook the old hard drive up on the IDE by itself, and slaving it from my CDRW drive. Nothing works. Seems like the computer is going to read whatever is causing the problem when it scans the disk at startup.

I’ve searched and searched but couldn’t find this exact problem or a close solution. Most people are able to boot into safe mode, last good config, or something. All of these cause the PC to reboot.

Has any experienced this issue? Or is there something I have not done correctly?

Thanks in advance for your help.

This discussion is locked

All Comments