Help with "NTLDR is missing"

[dhuss]

I have a friend that I'm trying to help with a "NTLDR is missing" problem.

Toshiba Laptop Windows 7
Background: He brought me the computer a few weeks back because it was freezing about 5 minutes after it would boot into Windows. I ended up using the HD partition to restore it to factory settings and everything seemed to be fine when I gave it back to him.

So he just emailed me and said all of sudden last night it BSOD on him and shut down. He restarted the machine and it said "NTLDR is missing, press Ctrl Alt Del to restart". After that it goes into the Windows Boot Manager and says "Windows failed to start...Please insert the installation disc..."

So, I'm curious if I should attempt to find the problem or just see if I can restore to factory settings again? If option 1, then where should I start? From what I've read online about the NTLDR error is that it could be any number of things.

Thanks,
Dale

 

[NYJimbo]

Ok, but did you even try anything ? This is likely more than just the file system going bad, it could be anything from ram to failing HD to reinfection with a virus or even something subtle like excessive heat causing a temporary system problem leading to corruption.

If you already did the restore and it failed a couple weeks later wouldnt it be likely to fail again if you just do a system restore again ?

Begin the regular diagnostic process.

 

[dhuss]

At this point I'm just trying to help out a friend so I don't have a "regular diagnostic process".
Before I restored Windows the first time I booted into safe mode and ran memtest (no errors), chkdsk (no errors), and Malware bytes (nothing found). I had a feeling it was a faulty hard drive at first so I booted into a linux live cd and ran the computer for about an hour.
As far as a heat issue, the laptop stays on top of a cooling fan all the time.

 

[Encrypted Existence]

At this point I'm just trying to help out a friend so I don't have a "regular diagnostic process".
Before I restored Windows the first time I booted into safe mode and ran memtest (no errors), chkdsk (no errors), and Malware bytes (nothing found). I had a feeling it was a faulty hard drive at first so I booted into a linux live cd and ran the computer for about an hour.
As far as a heat issue, the laptop stays on top of a cooling fan all the time.

Running a diagnostic test on the HDD would be a great place for you to start. Try using either the HDD manufacturer's utility or a program called gsmartcontrol. Testing the HDD is where I usually start my diagnostic procedure (after visual inspection of course). I know you are new to the forums and I encourage you to get comfortable using the search function as well as google. This is very basic stuff you are asking about and tons of info can be found in the older threads by doing a simple search.

http://www.technibble.com/forums/showthread.php?t=37192&highlight=diagnostics+procedure

 

[Xander]

Another good read is:

How to ask Good Questions For Faster Tech Help
by Bryce W


My own tip: Don't waste time scanning for viruses on what is rarely a virus-related issue. Windows glitches -- it doesn't need a virus' help.

 

[nagidar]

Ntldr

http://www.computerhope.com/issues/ch000465.htm

 

[ComputerRepairTech]

Whats ntldr doing on there? windows 7 would normally be bootmgr is missing. unless you are dual booting or had an xp installation on there.

Edit: oh it came like that factory settings? hmm yeah I would test HD

 

[rjframe]

Windows glitches -- it doesn't need a virus' help.

Can I use that? First reason I've had to laugh all day.

 

[lcoughey]

Step 1 - Backup the data, if important (if cannot backup, you might need assistance of a data recovery pro)
Step 2 - Run a full scan of the hard drive with a diagnostic program like MHDD
Step 3 - If the drive tests 100%, then deal with windows issue by running a restore

Odds are, the hard drive is failing. We get lots of drives here for recovery after end users and their technicians run system restore and lose their data...all because they didn't backup first and properly diagnose.

 

[oldtech]

I guess my question is - Why are you all helping an obvious end user?

 

[lcoughey]

I guess my question is - Why are you all helping an obvious end user?

End users pay my bills.

 

[FoolishTech]

I guess my question is - Why are you all helping an obvious end user?

That he is, but I looked at the intro thread and it seems he is trying to break into the biz...

At this point I'm just trying to help out a friend so I don't have a "regular diagnostic process".

Unfortunately this isn't the best forum to learn how to repair computers from scratch, and it definitely isn't for people who aren't PC technicians by trade. This forum is more for people who at least have a basis or background in that area.

That being said... I understand you are trying to get started, so my best advice is to READ the forums, and start by looking up info and working on that diagnostic process that you don't have yet.

Regardless of your diagnostic process, you need one, period. Why would you try to fix a problem, without knowing what the problem actually is?! Just performing a format/reload of Windows on your friend's computer was not fixing anything nor doing him any favors.

While some people on here will argue that you should perform full diagnostics on every component of the system that it is possible to run a diagnostic on regardless of what the problem is, I will say that without arguing that point, you should have at least run a hard drive diagnostic INITIALLY when you first had the computer, based on the type of problem you may have had; you DEFINITELY should run one on it now. AFTER you back up any important data, which should be your top priority at this point.

Full diagnostics can include a lot of areas, the bare minimum are HDD and RAM tests, sometimes CPU and even GPU stress tests, maybe even a PSU voltage/load check, definitely visually checking the caps on the motherboard in a desktop system, making sure all fans are operational and checking for excessive heat on various components especially when under stress testing, etc. etc.

Once you get that out of the way, you can start worrying about software issues. Many (even somewhat experienced techs) will assume an issue is software related and post here for answers when they haven't even run related diagnostics, much less full diagnostics. So just for future reference, this is a big no-no.

 

[dhuss]

Once you get that out of the way, you can start worrying about software issues. Many (even somewhat experienced techs) will assume an issue is software related and post here for answers when they haven't even run related diagnostics, much less full diagnostics. So just for future reference, this is a big no-no.

You're absolutely right. I should have run basic diagnostics before posting the question to the forums.

Thanks for the diagnostic procedure recommendations as well as the software recommendations.
I'm going to run those diagnostics as see if the problem might be a hardware related issue.