, or any configuration? It all began when I received the fatal blue screen stating that my NTFS.SYS file was corrupted, windows simply would not boot. So I got a new hard drive and figured I would copy what I needed off the old SATA (WD120) drive. I installed the new drive Seagate 300 GB SATA, and windows, boots fine. Installed the old drive as a slave, won't boot, remove the drive, system boots fine. I even copied the entire contents of the old drive to a secondary partition on the new drive, and unhooked the old drive, it still won't boot, it either flashes the blue screen or perpetually reboots. There seems to be no way to access the files on the old drive, I ran a virus scan with no hits. The contents of the old drive seem to corrupt any drive they are on and take control of the system. Please advise
This conversation is currently closed to new comments.
Sounds as if your file system has become corrupted on the drive. Does the drive show any dead sectors when you scan it with a hard disk utility like chkdsk?
No bad sectors, I have done every check I could think of do verified this drives integrity. Neither the Dell, Windows or WD utilities report any errors. I was thinking I could buy a SATA to IDE adapter and connect the drive to an external drive bay. But im looking for other options. The big surprise is when I copied the drive to a secondary partition of the new drive, which caused the new drive to inherit the same problems.
Sounds likes the drive is dead. It might be possible to access he drive by changing the drive order in BIOS to prevent it reading SATA drive first.
Also, you could try booting system up and then attaching the SATA drive and use Disk Management to rescan for new disks (not recommended but possible).
I tried changing the drive order in the BIOS, regardless of what order the drive boots, I will either get a perpetual boot loop. or the NTFS.SYS blue screen, as long as the drive is activiated in Bios the problem occurs. All available diags report the drive as healthy, not even any bad sectors reported, its strange
Well you have a few options the best would be to buy a USB to SATA Caddy and see if you can plug it in them and recover the data with the computer running that way it shouldn't interfere with the Boot Sequence which appears to be what is happening here.
Failing that you'll need to reformat the drive and use a Data Recovery Tool to recover your Data this is not cheap or fast. Ontrack have an excellent tool for this but it isn't cheap you can have a look at
There is a Download option on this page but unless you buy the complete thing you'll only be able to recover the first 200 K of any file. What you do is download the file check what it can recover and then if it suits your needs you can purchase the program and you'll get a Registration Code E-Mailed to you which will activate the product.
If you use any of these options remember never to actually write anything at all to the drive with the data on it but save the recovered filed to a Folder that you have created on a different HDD.
OK, here is what is happening in our latest battle of ?The Lost Hard Disk?. I took a 200 GB IDE drive and attached it to the secondary IDE port of the mother board. The system recognized it after adjusting the bios settings. I then used a Seagate utility to copy the contents of the unusable hard drive to the IDE disk. It worked, Eureka !!, I then take the IDE drive and place it in a USB drive caddy, adjust my bios setting so only the one SATA drive is on and boots, the system starts without incident. I then plug in my USB caddy, the system recognized the caddy, and just before the drive letter appears the system reboots and begins its typical behavior all over again. Unreal.
Now as far as running a windows repair on the hard disk in question. I tried that; I could not get to the Windows sets up screen because anytime the hard disk is scanned in any way the system reboots. This leads me to the last option of formatting the disk and then recovering the information via utility, I am skeptical to this though, as if the data on the disk in causing reboots now, it will certainly do it again if the drive is formatted then recovered to another disk, Yes?
OK, here is what is happening in our latest battle of ?The Lost Hard Disk?. I took a 200 GB IDE drive and attached it to the secondary IDE port of the mother board. The system recognized it after adjusting the bios settings. I then used a Seagate utility to copy the contents of the unusable hard drive to the IDE disk. It worked, Eureka !!, I then take the IDE drive and place it in a USB drive caddy, adjust my bios setting so only the one SATA drive is on and boots, the system starts without incident. I then plug in my USB caddy, the system recognized the caddy, and just before the drive letter appears the system reboots and begins its typical behavior all over again. Unreal.
Now as far as running a windows repair on the hard disk in question. I tried that; I could not get to the Windows sets up screen because anytime the hard disk is scanned in any way the system reboots. This leads me to the last option of formatting the disk and then recovering the information via utility, I am skeptical to this though, as if the data on the disk in causing reboots now, it will certainly do it again if the drive is formatted then recovered to another disk, Yes?
How did you copy old drive to partition on new drive? Imaging software? If so you may have two bootable partitions on the same drive causing confusion.
OK, here is what is happening in our latest battle of ?The Lost Hard Disk?. I took a 200 GB IDE drive and attached it to the secondary IDE port of the mother board. The system recognized it after adjusting the bios settings. I then used a Seagate utility to copy the contents of the unusable hard drive to the IDE disk. It worked, Eureka !!, I then take the IDE drive and place it in a USB drive caddy, adjust my bios setting so only the one SATA drive is on and boots, the system starts without incident. I then plug in my USB caddy, the system recognized the caddy, and just before the drive letter appears the system reboots and begins its typical behavior all over again. Unreal.
Now as far as running a windows repair on the hard disk in question. I tried that; I could not get to the Windows sets up screen because anytime the hard disk is scanned in any way the system reboots. This leads me to the last option of formatting the disk and then recovering the information via utility, I am skeptical to this though, as if the data on the disk in causing reboots now, it will certainly do it again if the drive is formatted then recovered to another disk, Yes?
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Drive prevents booting as Slave