[mellocello]

I recently upgraded to a new motherboard, and since it no longer supported SCSI, had to remove a disk which contained the boot manager.

 

To attempt to resolve this, I followed these articles in order to make one of my existing ATA drives bootable.

http://technet.micro...y/hh824874.aspx

http://windowsforum....bootable.37277/

 

Specifically, I:

* Booted into a recovery usb

* Modified, using diskpart, my C: drive to make the primary partition (partition 1) the active partition.  Its partition layout looks like this:

  Partition 1  Primary 837GB   

  Partition 0 Extended 93GB

  Partition 2 Logical 89 GB

  Partition 3 Logical 4093MB

* Ran bcdboot C:\Windows to copy the bcd template into the boot partition for that drive, at least I presume it did that, since it indicated it was successful.

* Ran windows recovery to see if it found anything wrong with things.  It did, and offered to solve the problem.  The issue involved the boot manager - sadly, I didn't copy down what issue it thought it found.  Anyhow, upon restart, I still have a BSOD.  The exact error code is:  0x7b (0xFFFFF880009A97E8, 0xFFFFFFFFC0000034, 0x0, 0x0)

 

Here's a dump from the bcdedit command, if it's useful.  I assume that this describes the boot manager for the disk I'm attempting to recover, not that of the usb recovery disk.

 

 

Windows Boot Manager

----------------------------

identifier                     {bootmgr}

device                         partition=C:

path                            \bootmgr

description                 Windows Boot Manager

locale                          en-us

inherit                         {globalsettings}

default                        {default}

resumeobject             some guid

toolsdisplayorder       {memdiag}

timeout                      30

 

Windows Boot Loader

-------------------------

identifier                     {default}

device                         partition=C:

path                            \Windows\system32\winload.exe

description                  Windows 7

locale                           en-us

inherit                          {bootloadersettings}

osdevice                     partition=C:

systemroot                 \Windows

resumeobject             some other guid

nx                               OptIn

detecthal                    Yes

 

 

Any help would be much appreciated!

 

Thanks!

[Advertisements]

Do you have a current backup of your data? If not, I recommend we go through the steps for that first. If you do have a backup, here are some more commands you can try:

bootrec /fixmbr

bootrec /fixboot

bootrec /rebuildbcd

[Trevorever]

Do you have a current backup of your data? If not, I recommend we go through the steps for that first. If you do have a backup, here are some more commands you can try:

bootrec /fixmbr

bootrec /fixboot

bootrec /rebuildbcd

[mellocello]

So, I've resolved the problem.  I had to change the operating mode for my disks from AHCI to IDE in the BIOS.

 

Reading a bit more, it seems like Windows selects the operating mode for the disk at the time of installation, persists the mode in the registry, and then fails to start if the modes don't match.  My suspicion is that when I installed the OS originally on my old mobo, the operating mode in its BIOS was set to IDE.

 

Oh, Windows...

 

Next thing to try:

http://forums.guru3d...ad.php?t=313676

[Trevorever]

Good to hear. Personally, I would not edit that in the registry. Instead, run sysprep with the generalize and shutdown options. Then change it in the BIOS and boot to Windows. You will have to re-enter your Windows product key afterwards though.

[mellocello]

Hmmm... the mode was already set to AHCI in the registry.  That means that I'm running these disks in a slower mode than previously (which is not surprising because there is in general substantially more idle disk activity than has been in the past.

 

I'll try the bootrec commands you suggested.

 

Also, does anyone know why changing it to IDE would solve the problem for me?

Edited by mellocello, 10 April 2014 - 09:49 PM.

[mellocello]

My last reply:  Restarting into the BIOS and setting the mode back to AHCI caused the system to boot perfectly fine.  Now my suspicion is that when windows started after its initial reboot in IDE mode, it reconfigured itself so that it could function in either AHCI or IDE mode (i.e., set the registry value).  So all I had to do was to put the BIOS in the right mode and things were fine.

 

Hope this trial of absurdities is useful for others who upgrade their very old motherboard to a new shiny one while keeping their hard drives the same.

 

OK!  Time to go buy an SSD drive, install Windows on it, and make this entire exercise pointless!

 

Thanks!