Missing NTLDR

rulocal

rulocal

rulocal

Associate
Joined
2 Oct 2005
Posts
507
Location
London
I have recently upgraded from an 80gb IDE drive to a WD5000AAKS SATA drive. The drive is wonderful to use, quick and quiet, but I have been getting the odd BSOD followed by the "missing NTLDR" message. Alternatively I sometimes get the message when booting up in the morning.

When I go into the Bios, the WD drive has vanished, hence the missing NTLDR message, and only the old 80gb drive shows which I have kept to back up certain files, but is not bootable.

Unplugging and refitting the drive seems to sort it out so I am thinking it might be a dodgy cable and am going to explore this possiblity. Any other ideas though? If a SATA cable comes loose during use woold this cause a BSOD. I could test it but don't want to damage anything/corrupt by windows installation.


Many thanks

Paul
 
Ive seen this and will post back after shower/shave.

I cant remember but its not the same as fixing your Boot and Master Boot files.

http://forums.overclockers.co.uk/sh...5&highlight=full+format+username_helmutcheese

http://forums.overclockers.co.uk/sh...4&highlight=full+format+username_helmutcheese

Im pretty sure (90%) thats your issue, it only stung my backside once, cause once is enough lol.

When you need to rewrite your Master Boot its a different MSG than the one you get (again about 90% sure as been a long time since errors).
 
Last edited:
Thanks for the reply.

I am not sure this is the problem though as I was able to fix it by simply unplugging and plugging in the drive which does not (I think) fit with the situation you describe where I would have thought the drive would have been visible in the bios. I am also pretty sure I did a Full NTFS Format before I installed. Even so, I will log your comments in the back of my mind for future disasters.

Another thought I have had is that my MB (GA_P35_DS3R) is somehow getting confused by having an IDE drive and SATA attached but my research suggests this should not be the case.

Any further comments would be much appreciated.
 
I have ocassionally had to set the Boot Priority to point it to the right drive but more often than not the SATA drive is completely invisible. Could this be caused by anything other than a loose connection? The fact that I am getting ocassional BSODS followed by "missing NTLDR" also suggests some sort of loose cable, doesn't it?? :confused:
 
You must log in or register to reply here.
Back
Top Bottom