BOOTMGR is missing

Toggle sidebar Toggle sidebar
K

KhanSuhaib

Prominent
Jun 20, 2017
3
0
510
This is the first time I am asking a question so I am sorry if I make some mistakes.
Recently when I started experiencing CPU overheating issue, I reset my BIOS setting (by removing the motherboard battery and reseating it) to make sure no one had overclocked it (previously I had given my PC to a service centre for an unrelated problem so I was concerned that they overclocked it).
But when I attempted to boot my computer again I got the "BOOTMGR is missing" error message.
Now I have a SSD (which has the OS) and HDD, so I tried various things suggested on the other threads and on my own accord.
The problem is the computer boots into Windows only when, only the SSD is connected, if the HDD is connected I get the same error message.
I tried using different SATA ports switching the cables nothing worked if the HDD is connected.
My computer does detect the HDD and I made sure the boot order was correct, still the same problem.
However when I make the particular SATA port to which the HDD is connected a hot plug and then if I boot without the HDD and connect it afterwards everything works.
I even tried formatting and repartitioning the HDD.
None of the solutions on the other threads work.
Specs:
CPU: Intel i5 4690K
Motherboard: Gigabyte H97
Graphics: Gigabyte Windforce GTX 970
HDD: Western Digital Caviar Blue 1TB
SSD: Samsung 850 EVO 120GB
Power Supply: 500W Unbranded
Thanks in advance.
 
Solution
A
1. In view of your previous experience involving a "CPU overheating issue" it would be wise for you to check out the current health of the processor with Intel's Processor Diagnostic Tool. You can download the tool from: https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool. The likelihood is that no harm has been done to the processor (and has no effect on the problem you raised but just as a precaution check it out.

2. Can we assume your HDD originally contained the OS (Win 10?) and you cloned that drive to the SSD so that the latter would serve as your new boot drive? If so, I suppose it's of no import now since you've indicated formatting the HDD and the HDD does NOT contain an OS. That's right, isn't it...
Sort by date Sort by votes
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
1. In view of your previous experience involving a "CPU overheating issue" it would be wise for you to check out the current health of the processor with Intel's Processor Diagnostic Tool. You can download the tool from: https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool. The likelihood is that no harm has been done to the processor (and has no effect on the problem you raised but just as a precaution check it out.

2. Can we assume your HDD originally contained the OS (Win 10?) and you cloned that drive to the SSD so that the latter would serve as your new boot drive? If so, I suppose it's of no import now since you've indicated formatting the HDD and the HDD does NOT contain an OS. That's right, isn't it?

3. Or did you fresh-install the OS (Win 10?) onto that SSD?

4. You also indicated multi-partitioning the now-secondary HDD. What was (is) the purpose of that? Does that HDD contain any data? If so, please describe in general terms.

5. Can you submit a screenshot of Disk Management after you successfully booted to the SSD and subsequently connected the HDD as a secondary drive?

6. Finally, just to confirm the problem you're experiencing as you reported it...
A. If you boot the system with ONLY the SSD connected the system boots to the OS without incident and functions problem-free.
B. But if the HDD is installed/connected at the time of the boot, the system will fail to boot to the OS.
C. If the system does boot to the OS with only the SSD boot drive connected you can then connect the HDD as a secondary drive and access the contents of that drive without any problem in the system.

Is all that correct?

7. Assuming it is, when the WD HDD can be accessed, test the drive with the WD Data Lifeguard diagnostic program available from WD's website - just to ensure there's no problem with the drive.

8. If you can't provide a screenshot of Disk Management as indicated above, provide a partition-by-partition description of the system's drives configuration, describing in detail each drive's partitions reflected in DM, including the partition title, partition size, amount of data in each partition, and any other info you deem relevant.

9. We'll assume - unless you indicate to the contrary - that both drives are MBR-partitioned.
 
Upvote 1 Downvote
Solution
K

KhanSuhaib

Prominent
Jun 20, 2017
3
0
510
1. I'll do that thank. (I was really worried that is damaged by CPU)
2. No the HDD never contained the OS (Windows 7).
3. Yes, the service center did a fresh install of the OS on the SSD, and previously the OS was on the SSD.
4. I tried booting when the HDD was formatted with only one partition, but that didn't work either, since that didn't work I partitioned into 4 partitions as it was previously and restored my data.
The data was the usual stuff like games, movies, images, music and a few applications.
5.
T38jUBk

Link: http://imgur.com/T38jUBk
6. Yes, all of those are correct.
7. No problems with the either of the drives. (Tested HDD of WD Diagnosis and both HDD and SSD on HDTune).
9. Yes both drives are MBR partitioned.
 
Upvote 0 Downvote
K

KhanSuhaib

Prominent
Jun 20, 2017
3
0
510
I seem to have solved the problem randomly. I set the HDD as the first drive in the boot order instead of the SSD and everything worked. I still don't have any idea as to why this worked. The boot times are still extremely fast (same as when I was booting only from SSD) so I doubt that it is actually booting the OS from the HDD, I am a bit lost as to why this happened, but happy that it is solved. Thanks a lot for your help
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
Unquestionably the system is booting to the Win 10 OS installed on your SSD. The fact that you've set the HDD first in boot priority order is irrelevant since that drive does not contain a viable OS. So the system defaults to an installed drive that contains a viable OS - in this case your connected SSD. Obviously if the SSD was disconnected/uninstalled and you attempted to boot to the HDD, the boot would fail.

But I still can't see how your problem has been resolved. There should be NO problem if both the SSD & HDD are connected in the system and you power-on the PC. The system should boot to the OS contained on the SSD, and the HDD (as a secondary drive) should be detected in the system and its data accessed. Period.

But do I understand you to indicate that this is still not so?

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom