BootMgr Is Missing After Upgrade from Win7

Topic

New Reply

I recently upgraded from Win 7 to Win10. The upgrade went smoothly with one big exception: after I boot Win 10 it inevitably crashes a day or two later with the dreaded “BootMgr is missing Press Ctrl-Alt-Del to restart” error message. To be clear, Win 10 starts and runs fine for a day or so and then crashes. Each time I have to restart Win10 with the start button on my computer, and lo and behold Win10 starts normally. I did not have this problem with Win7. I tried the usual recommended fixes: startup repair from the installation disk, and CHKDSK C: /f; but nothing has worked. At one point when I booted Win10 I was assigned a temporary profile, and I had to fix that through some registry entries. That problem apparently has disappeared, but the “BootMgr Is Missing” problem persists . Any ideas or suggestions would be much appreciated.

Reply | Quote

Replies

Try running the System File Checker Open a Command Prompt as Administrator and type sfc /scannow

Reply | Quote

Thank you for the suggestion, but I did that as well. It came up with no errors.

Reply | Quote

OK, so I did the reinstall outlined above, and now my Win10 system continually reboots. Each time the system boots up it remains stable for a few minutes, but after a few minutes of inactivity it reboots. The rebooting does not occur while I am actually using Win10, but only when it is idle. I set Windows Update to restart only after warning me. Sleep is off. Any further ideas or suggestions? Could it be a hardware problem, e.g. bad hard drive or BIOS? I am stymied.

Reply | Quote

A memory fault could cause this, but the first thing I would suspect is the drivers. Go to Device Manager and work your way through the drivers checking for updates. You could use SlimDrivers to speed things up but dont use the big green button to download. There be PUPs. Use the direct link underneath.

https://www.slimwareutilities.com/slimdrivers.php

Reply | Quote

Sounds like it’s restarting after a system failure which is the default behaviour.

To change that & hopefully get a pointer to the cause of the restarts right click on the start button and click on system then advanced system settings. In the advanced tab click settings under startup & recovery and make sure that automatically restart is unchecked.

44962-startuprecov

If it is indeed bluescreening that will at least give time to note down the details and help further troubleshooting.

Reply | Quote

I disabled automatic restart as suggested above and received this BSOD error: kernel data inpage error. What next? I Googled the error, but what I found wasn’t helpful, e.g Bootrec /fixmbr and /fixboot. I also did Bootrec /scanos, which pointed to my old Win7 OS. Any further help would be greatly appreciated.

Reply | Quote

If it’s restarting after a system failure, then there should be an entry in the system event log. Have you looked in there?

Reply | Quote

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

When the BSOD shows (or in the logged data), there will be 4 blocks (Parameters) of 8 chars listed after the BSOD type, the 2nd block might give us further clues:

Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes.

Unfortunately, it’s not always that easy, if you follow the instructions at Sysnative and attach the resulting zip file back here, we’ll try to work out where the problem lies.

Any crash dumps obtained should give us the base data (above) and potentially a lot more, the other data collected will enable us to work through the Event, WER (Windows Error Reporting) and other data logs, etc. to build up a bigger picture of what’s been going wrong.

Reply | Quote

According to Event Viewer, just before the automatic reboot I receive Event ID 51. “An error detected in deviceHarddisk 0 DRO during a paging operation.” Is this illuminating?

Reply | Quote

With that message, it’s likely to be bad block(s) in the paging file (Paging file corruption), I would disable and then attempt to delete pagefile.sys (try the answer here if you cannot delete it), then run CHKDSK C: /f /r, followed by an sfc /scannow before re-enabling the paging file.

Then use the maker’s software to fully check your hard drive, your description/history doesn’t look good.

Reply | Quote

Backup now! (to an external disk)

The disk error could be controller, driver or disk.
Check for a driver on the mobo manufacturers web site.
Re-seat the cable between your hard disk and mobo.
Run the disk manufacturers disk test program.

cheers, Paul

Reply | Quote

I have concluded I have a bad hard drive. Seagate’s SMART test produced a “fail.” So the queston becomes: how do I reinstall Win10 on a new hard drive? To reiterate, I installed Win10 as an update from Win7. Is my best bet cloning the bad drive? Or can I simply use a Win10 install disk and use my Win7 key?

Reply | Quote

If I understand the above, I can use the Activation Troubleshooter to activate a Win10 installation on a replacement hard drive on the same computer. Out of curiosity how does the Activation Troubleshooter determine I am using the same computer if the system hard drive is being replaced and I am not inputting a product key?

Reply | Quote

Your Microsoft account stores the details of your PC and will reactivate Windows when you log on.
If the drive is still bootable, its worth trying to clone it as it will save you having to reinstall all your programs. I use Drive Clone free, which is an excellent program.
Consider investing in an SSD, the results are worth the extra cost.

http://www.farstone.com/software/drive-clone.php

I’m also curious about the effect of a new motherboard. If anyone has tried it, please start a new thread.

Reply | Quote

Clone the drive and see how you go. May save lots of work.

cheers, Paul

Reply | Quote