Missing NTLDR - repeatadely

[hawkinsa21]

Hey all.

Well, after I managed to get my PC up and running again with a new PSU after my Tagan literally blew up, I now keep getting the 'missing NTLDR' error message on boot up, and it keeps prompting to use Ctrl Alt Del to restart the system.

Easy fix yeah? Course! Just run repair then cmd line from the Win 7 installation DVD, cd to relevant disk, then type 'bootrec /fixmbr'...

Works fine, BUT, once I power off the machine I'm finding that about 50% of the time the same 'missing NTLDR' message reappears, so I have to repeat the process!

Any suggestions on why this keeps coming back?

I have Vista 32bit and Windows 7. Win 7 is my primary OS, although it USED to be Vista 64 Ultimate, until that partition became heavily corrupt and I had to format that part of the disk... I had to use the cmd line trick to fix ONE missing NTLDR message then, but since that happened about 3 months ago its been fine, until my PSU blew and I had to replace it. Now it is happening 50% of the time on boot up.

Any ideas? I'm stumped... I'll dig around on google later as well, but thought I'd share the woes in case anyone has seen it before (repeatadely that is!)

Cheers

Alex

 

[tinytomlogan]

I hate this problem repeatedly after a mega clocking session, tbh mate I did try to fix it the many times it happened but just ended up formatting in the end.

Now I always keep an up to date image of my OS drive to flash back over should the worst happen.

 

[hawkinsa21]

Thanks for your reply Tom, sounds like this may be terminal!

I don't mind formatting my Windows installation although I may hold out until 22nd October and then get me a copy of Windows 7 Ultimate 64 ftw:yumyum:

 

[Rastalovich]

It's an fsb issue in relation to the mobos drive control.

The file is there, just the drive isn't being read correctly. Albeit cos of the controller issue or memory not liking it.

Every case I've had of this, stepping back the fsb (or whatever I've messed with) has solved it.

Very impressed u managed a full OS install if u didn't change anything in the bios

 

[hawkinsa21]

It's an fsb issue in relation to the mobos drive control.

The file is there, just the drive isn't being read correctly. Albeit cos of the controller issue or memory not liking it.

Every case I've had of this, stepping back the fsb (or whatever I've messed with) has solved it.

Very impressed u managed a full OS install if u didn't change anything in the bios

Hmm, my FSB is at stock at present because whilst troubleshooting my dead PSU issue, I reset CMOS.

I'll have a play with the BIOS settings anyways and see whats going on.

Didn't do a full OS install , I had all three OS's installed at once and then the primary one (Vista 64) died, so was just left with the two.

 

[zak4994]

The is more than one way of getting this problem.

It happened to me once just because I took the hard drive to wipe it clean.

I stick it back in and the error comes up.

I take it out and stick it back in and it works! lol.