Windows 7 / Server 2008 R2 Bare Metal Restore 0x0000007B Stop Error

  • Article

Question

Monday, August 16, 2010 4:03 PM | 1 vote

Hi,

 

I am tring to restore a Server 2008 R2 Standard Ed (full installation) RTM to a virtual machine, from a full Windows Server Backup image taken of a physical machine (Dell PE 2970).  All restores fine, and looks good until it tries to boot, when a Stop Error occurs, with the following error:

*** STOP: 0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

I believe the non-bracketed portion means "INACCESSABLE_BOOT_DEVICE".

There is only the System Reserved volume + a C: volume (system volume) + F: volume (DVD drive) on the original server.  It has had other volumes in it before, which are correctly listed in the MountedDevices registry key, but they have not been physically present for a while.

The virtual disk I'm trying to restore to is several GBs larger than the original virtual disk on the RAID controller (2 disks in RAID 1).

I can't figure out why the server isn't booting.  I've successfully restored Server 2008 machines from physical machines to VMs before, including servers using hardware RAID cards (e.g. Dell SAS 6/iR).  The only difference I can think of is that this is Server 2008 R2, this is a 2 proc server (I've tried several virtual proc numbers on the VM to no avail), and the RAID controller is PERC 6/i, and this is the first server I've tried with that particular RAID card.

 

Any help would be greatly appreciated, even if it's to point out that I'm looking in the wrong direction.

 

Many thanks,

 

Chris

All replies (41)

Friday, April 29, 2011 6:27 AM ✅Answered | 6 votes

I solved problem. I use the following link : http://www.minasi.com/forum/topic.asp?TOPIC_ID=31980

You have to change only and i mean only :

10) Change Intelide/Start from 4 to 0
11) Change Pcide/Start from 0 to 3

 

Nothing else, if you change anything else, it will not work, that is a bummer. Why it is not written at any SCDMP manual or KB, I do not know, I `m not the only  one with these error.

Sunday, October 16, 2011 10:29 PM ✅Answered | 28 votes

Hi MailStane,

 

Sorry for the long delay in getting time to test this, been flat out but got a chance today to rigorously run through some scenarios - and I'm absolutely thrilled to confirm we have a solution!!! :¬)  At long last, thank you immensely for your post and the original link - the steps above alone didn't work so I kept testing and and with the help of the link you gave modified the process a bit, and here's the the final working solution (all of this works for Windows 7 as well):

 

After completing the BMR process don't restart.
Select Command Prompt.
regedt32<CR>
Highlight HKEY_LOCAL_MACHINE, File>Load Hive>[restored volume]:\Windows\System32\Config\SYSTEM>Open>Key Name = Restored_HKLM>OK.
Expand Restored_HKLM\ControlSet001\services and ensure the following are set:
  If restored to a (VMWare) VM then ensure intelide>Start = 0 and LSI_SAS>Start = 0; msahci>Start = 3 and pciide>Start = 3
  NB: I have only tested this with VMWare VMs (Player/Workstation and vSphere) but will likely translate across to Microsoft (e.g. HyperV) VMs. The LSI_SAS value is definitely required, I couldn't boot in a VM until this was chaned to 0.
  Or if restoring to a physical machine with native HDD controller then ensure **msahci>Start = 0 and pciide>Start = 0; intelide>Start = 3 and LSI_SAS>Start = 3
**Highlight Restored_HKLM and then File>Unload Hive.
Close windows and restart.

You should now have a successfully booting restored Server 2008 R2! :¬)

(Remember if it's a new add-in RAID card and you supply the drivers it will successfully inject them into the restored OS - see previous posts in this thread)

NB: Don't worry if you have restarted without making the changes and it Blue Screens, come back through these options and if set correctly it will boot normally - nothing is damaged by the Stop Error, and the ide settings can be turned on and off with no permanent effect on the OS. I.e. change and restart until you hit the right combination required - I've tested this copious times and when changed back to the correct settings the OS boots again without issue.

If in doubt, turn on all possible required services e.g. set both intelide = 0/pciide = 0 and msahci = 0, or set all of these to 0 and it will still boot with the correct driver/s:
   aliide, amdide, atapi, cmdide, iastorv, intelide, msahci, pciide, viaide and LSI_SAS.
I don't recommend this due to the overheads it could introduce, but it will work and will get the machine up as quickly as possible if confidence in the exact combination required is in doubt.

 

Settings for typical destination machines - skip if desired:

VMWare VM:
aliide 3
amdide 3
atapi 0
cmdide 3
iastorv 3
intelide 0
msahci 3
pciide 3
viaide 3
LSI_SAS 0

Dell PE2970 physical machine with RAID card:
aliide 3
amdide 3
atapi 0
cmdide 3
iastorv 3
intelide 3
msahci 0
pciide 3
viaide 3
LSI_SAS 3

Dell PET100 physical machine on native SATA adapter:
aliide 3
amdide 3
atapi 0
cmdide 3
iastorv 3
intelide 3
msahci 0
pciide 0
viaide 3
LSI_SAS 3

Win 7 64x custom built physical machine on native SATA adapter:
aliide 3
amdide 3
atapi 0
cmdide 3
iastorv 3
intelide 3
msahci 0
pciide 0
viaide 3
LSI_SAS 3

 

KEY FOR SERVICE START VALUES:

0 = ?
1 = ?
2 = Automatic
 with DelayedAutostart = 1 = Automatic (Delayed Start)
3 = Manual
4 = Disabled

 

MailStane thank you once again for posting - it's helpded no end resolving a big bug bear with Server 2008 R2 and Win 7's backups, and while I'm still nonplussed at to why these manual steps are necessary when 2008/Vista worked flawlessly without intervention (wondering if all the drivers are on by default but haven't checked it out yet), we now have a confirmed quick and viable fix.  Thanks for being generous enough to share and well done!

 

Vikas, thank you for at least giving us a look in when the rest of Microsoft refused.  If you want to publicise this information feel free (any credit to MailStane and/or me I'm sure would be much appreciated) - it affects anyone in a Server 2008 R2/Win 7 DR scenario where the original hardware can't be replaced or emergency measures dictate using whatever's available whether home or business, and as SCDPM 2007/2010 uses the built-in backup this procudure applies equally.  On another note, this has also again opened the doors (IMO) to DPM as a viable all round backup solution, as the one stop backup including system state restores is a big bonus over third party block based backup solutions that painlessly allow different hardware restores for R2/Win 7 (personally tested) but do not allow for system state restores.  Now if compression were included in an SP or the next version it will have reached that always elusive "ideal" ;¬).

 

RidvanSeber - if you're still having difficulty hope the steps above to load the restored Registry hive help.

 

Case closed.

 

Many thanks,

Chris

Monday, August 16, 2010 9:22 PM

Update: I've tried restoring another machine (HP) running Server 2008 R2, with the drives also in hardware RAID 1 config, same size, but this one has 1 "virtual" disk on the RAID card and 2 volumes.  The drives are mirrored via an Adaptec RAID card.

Same result - exactly the same Stop Error as above.

 

I've successfully restored several physical servers of different kinds over the past two years to both VMs and alternate physical machines using Server 2008's BMR, including servers with and without hardware RAID cards, going both ways, and to and from Intel and AMD architectures, and it's been flawless so far.  I've also tested restoring from VMs to physcial machines and that also worked without issue.  I just finished testing a restore of a Server 2008 64x installation on an HP server (chose a DC to really test it) to a VM on the same host as above, and it was faultless.

 

I've made sure to create virtual disks at least a large as the originals on all of the above.

 

Something appears to have seriously broken in the BMR process from Server 2008 to 2008 R2.   Does anyone have a resolution to the Stop Error above, or any suggestions to pursue?  I'll post back any results.

 

Not sure if this issue is related:

http://support.microsoft.com/kb/922976

I checked the the values in both keys offline (recovery environment, then added the hive from the SYSTEM file in Windows\system32\config on the restored volume), and they already match the values in a Server 2008 R2 VM installed from scratch on that host.  Could it be possible this needs to be operated in reverse?  Still, haven't once make these changes on Server 2008.

 

Any help would be very much appreciated.

 

Many thanks,

 

Chris

Wednesday, August 18, 2010 1:41 PM

Update 2: I've tried the following to no avail:

Tried booting into Safe Mode (with no options), same Stop Error.

Booted into recovery environment and ran "bcdedit /set {default} detecthal yes", rebooted, no effect.

Booted into recovery environment, loaded the SYSTEM hive from the system volume, and tried several data values for the "Start" value in the following 3 keys in both "HKLM\tempsystemname)\ControlSet001\services" and "HKLM\tempsystemname)\ControlSet002\services": msahci, iaStorV, and pciide.  Restarted and same Stop Error.

Booted into recovery environment and checked values in the "MountedDevices" key of the same loaded SYSTEM hive.  Checked the drives are assigned the correct drive letters by first running "mountvol" from a command prompt to get the boot and system volume GUIDs (C = boot, D = system in recovery environment), matching them to values in the registry to get the key data values, and matching the data values to the data values of each \DosDevices\drive letter) value.  The system volume is not assigned a drive letter as expected, and the boot volume (containing Windows) is correctly assigned the letter C.

Booted into recovery environment, and checked the bootmgr and osloader settings using "bcdedit /enum all" - all appears to be present and correct.

 

My hunch is that once Windows gets to loading from the boot volume it is trying to load using the PER 6/i RAID card drivers.  To compound this, the Stop Error occurs a couple of seconds after the 'loading Windows' green scroll bar appears.  Would anyone agree, or have any suggestions on how to remove/unload the drivers, or force Windows to re-detect the storage controller (or fall back to the standard SATA/SAS one)?

 

Or can I assume that this BMR just isn't going to work and I'm going to have to purchase a new machine with the same specs in order to restore the server?  If this is the case it's a pretty serious step backwards from the BMR process in Server 2008, and is going to push people into purchasing 3rd party BMR software for every live R2 server, where for us Server 2008 BMR has performed really well.  I'm aware restoration to different hardware isn't guaranteed, but Server 2008 BMR hasn't failed me yet, and this and the other server running R2 I tested (mentioned previously) are a lesser jump than Server 2008 has managed to overcome without difficulty.

 

Many thanks in advance for any help.

 

Chris

Wednesday, September 8, 2010 8:59 PM

Is anyone able to help?

 

The issue seems to lie squarely with loading the storage controller.  If it is the problem, can anyone suggest how to have it redetect the controller to which the disks are attached, or unload the original controller?

Tuesday, October 19, 2010 3:28 PM

got the same issue, trying to restore a HP Proliant system with Tivoli Storage Manger in a vmware. restore was finished successfully, but after reboot i got this stop code 0x7B. on none-R2 Systems we got it also but can fix it with bcdedit /set {default} device "partition=c:" and bcdedit /set {default} osdevice "parititon=c:". now i have read some forums and was not able to fix it. i've tried bcdedit before and after reboot, all your stuff above but nothing, same error as before. maybe i should load new harddisk drivers before rebooting the system, i will give an answer on this tommorrow.

 

regards

 

Exar Kun

 

Monday, October 25, 2010 4:18 PM

Hello,

It's not guaranteed the the OS will boot after it's been restored to a different hardware. When the OS boots, it selects boot device drivers that matches certain criteria. The boot critical device drivers could be diffferent for different machines. When you restore the backup through BMR the machine might have problems in pickin up the right driver and it would fail during Boot.

BMR also injects the third party drivers present in WinRE (Windows Recovery Env) to the restored OS and expects that correct driver will be used for system boot. If you want to disable injecting the third party drivers in restored OS, you may use the reg key mentioned below:

Please set the following registry key in WinRE - “HKLM\SYSTEM\CurrentControlSet\Services\wbengine” and create DWORD “DoNotInjectDrivers” with value 1.

Recovery won’t inject the drivers. Try BMR recovery and boot the system.

Note: HKLM = HKEY_LOCAL_MACHINE

Regards,
Vikas Ranjan [MSFT]
This information is provided as-is without any warranties, implicit or explicit.

Wednesday, February 9, 2011 11:26 AM

Hi Vikas,

 

Thank you for the reply, much appreciated that you took the time to outline the driver injection details above.  I had been working on other projects since October but am lookiing at this again now to try to finally resolve the issue or write R2's BMR backup off as a viable solution for mission critical servers.  Here are the newest developments:

 

Preventing driver injection as above did not have any effect.

I've pinpointed the issue down to definitely being the change in storage controller, and ironically appears to be the opposite of the above - when I added an Adaptec card to the physical machine I was using for testing restores the BMR worked successfully and the OS booted in its entirety.  So injecting a driver for a storage controller that is not present in the original OS actually allows it to work, just as it does when restoring to the original machine.  The issue is when the storage controller driver for the destination machine should be built-in and no additional driver is required.

 

To confirm the above I created an R2 OSE on a test source machine and took several backups with completely different hardware configurations, except that I used the same PCIe add-in storage controller in all cases on both the source and destination machines, and it worked every time.  This was regardless of differences in architecture vendor (Intel to AMD), number of CPUs or cores, disk type or number, RAM type and count, and motherboard generation (age) or chipset.

Indeed I even forwent BMR entirely during one test and just shut down and moved the disks (no sysprep'ing or any changes) from the original server to the destination, maintaining identical Adaptec RAID cards, and it worked without any issues!  (all I had to do was import the array)

Furthermore I then took several other production physical and virtual R2 machines' WSB backups and BMR'd them to the destination, and every single one worked on the RAID card with the drivers injected.  Finally, all failed to the built-in storage controller when I removed the Adaptec card.

 

The puzzling thing for me is, when performing BMR on physical or virtual machines with onboard/built-in/native storage controllers no drivers need to be supplied in the WinPE environment.  Also when installing vanilla from a DVD the installation environment also has no issues whatsoever detecting and using the disks, without any intervention or supply of storage controller drivers, and nor does the finally booted OS once installation is complete.

So why does it fail during boot after BMR?  Is there any way to force the BMR process to redetect the controller, or use one of its other built-in drivers because none are supplied by the hardware manufacturer as it already exists in the Windows base and therefore can't be explicitly injected?

 

I'd also like to add, Server 2008 had no issues like this, in all of the cases above I've also tested 2008's BMR and as long as the destination disks are at least as large as the originals it has worked every single time without fail.  I'm wondering why or how this has been broken in R2 and if there is a simple way to overcome this issue, otherwise 2008's WSB utility has been better than many 3rd party utilities and will drive us to revert to 2008, and with huge regret cease deploying production R2 machines.

Also as a side note, for myself and others this is also particularly relevant to SBS 2011 deployments and will drive up costs for 3rd party utilities if there is not a resolution to this, and is particularly gutting as 2008's was fantastic as a one-stop backup and DR solution for SMEs.

 

I understand BMR to different hardware is officially unsupported, but any help at all will be greatly appreciated for all of the reasons above, or would be grateful even for a final word on the matter if this is the end of the road for this issue.

 

Many thanks,

 

Chris

Thursday, February 10, 2011 5:12 PM

Hello Chris,

Can you contact me at my email id vikas(dot)ranjan(at)microsoft(dot)com
Please replace the contents (dot) with . & (at) with @

Regards,
Vikas Ranjan [MSFT]
This information is provided as-is without any warranties, implicit or explicit.

Thursday, February 17, 2011 6:02 PM

Hi Vikas,

Did you receive my email from last Thursday?

Thanks,

Chris

Tuesday, April 12, 2011 8:23 AM

Has the solution been found? I have the same problem with HP when recovering to Hyper-V. Joke is, that storage driver (IDE) is already present in 2008 R2.

Sunday, April 24, 2011 2:27 PM

Hi MaliStane,

 

Unfortunately not, Vikas sent me a nice email on th 16th of March, assuring me he would look into it with his contacts, but I've not heard anything back as yet.

 

I completely agree, it's when it the driver is already be present that the issue arises - which is the case for almost everything that's not on a physical RAID array controller.  There was a lot of noise about how Server 2008's BMR could be restored to almost anything when it came out, which in my extensive testing is a very valid claim to make - it's brilliant (and I can live with the same or larger hard drive requirement if it gets us up and running).  But to break at such a fundamental step in R2 is ridiculous.

 

Vikas also suggested I open a support case to take it further if he didn't turn anything up, which is probably fair enough given that this is a forum and I appreciate that he has even replied (I don't want to put the onus on Vikas, at least he's taken the time to offer some help), but as this is a fundamental step in any BMR scenario, and more infuriatingly that it worked in 2008, I'm not spending my or my company's money opening a support case for something I feel Microsoft should be addressing as a critical bug. We've already paid for licensing the R2 servers, and copious amounts on other MS licensing, and we're not paying Microsoft any more to fix their own bugs.

 

See these for the same issue:

http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/de0ec60e-a51f-4747-be42-f3b7563f1fa9

(I agree entirely with leihu's point)

http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/268e5d38-fc99-41b0-9d79-31e6f5e98d96

(almost the same, but the RAID controller is compatible in our scenarios, and Chirag's suggestion to use the CLI is a non-starter - that only works if the storage controller is exactly the same, so doesn't solve this issue)

 

I also believe the technologies in 2008/R2's backup are the same as in DPM, just that it's not centrally manageble as with the latter.  I have now lost the will to test DPM with R2 and Win 7 as it's most likely to encounter the same error.  In other words, MS just lost a customer to 3rd party vendors - this is far too important to rely on something that breaks with the next version of Windows, while other vendors keep up (tested and confirmed).

 

That may change if this is resolved, as the rest of the hardware changes haven't mattered during my testing, it's just this one sticking point.  If anything changes I'll be sure to post it here.

 

Thanks,

 

Chris

Friday, April 29, 2011 3:17 PM

Thanks MaliStane for the good info.

Irish Chris - could you try that out with your configuration and publish the results for everyone's benefit.

Regards,

Vikas Ranjan

This information is provided as-is without any warranties and confers no rights.

Tuesday, June 28, 2011 8:46 AM

hence i can't boot the computer, how am i suppose to make those cahnges. As i was making a clean install, it fails after couple of seconds i see the windows logo...

i think it is a raid controller issue, but i don;t know how to work around...

 

thanks, if you bother to respond.

 

Ridvan

Tuesday, August 7, 2012 4:55 PM

+1

Worked perfectly for my VMware vm.

Background:

  1. Physical domain controller being backed up by Symantec Backup Exec 2012
  2. Restored using the B2V or Convert to VM function
  3. Immediatley BSOD's on boot with the "INACCESSABLE_BOOT_DEVICE" error
  4. Booted using a WinPE and mounted registry hive
  5. Modified the ControlSet001\System\xxx services as directed

NOTE: I had to modify ALL the ones listed under "Irish Chris's" VMware heading, and also LSI_SAS2, in addition to LSI_SAS

Thanks for the help guys!

Friday, January 11, 2013 10:26 PM

Just to say to me this post was worth more then gold it has saved me over 1000 labor hours to date and i can not thank the writer enough if he ever reads this message 

your solution works like a charm every time i have tried it thank you

Thursday, April 4, 2013 12:56 PM

Hello Chris,

i was having the same issue(bluse screen) and you saved me.

Thanks a lot.

Monday, June 24, 2013 3:52 PM

Thank you for the post! It saved lots of my time.

Tuesday, August 13, 2013 1:48 PM

Hello,

thanks a lot for posting and investigating, you saved my day! :-)

itcc

Tuesday, September 10, 2013 9:51 AM

Pulled my VHD from my old workstation as we used to boot from them, couldnt boot inside a VM ...done your fix and it works fine! didnt think i'd get it back ..

genius!

cheers,

JOn

Saturday, September 21, 2013 5:56 PM | 1 vote

Thanks for posting your successes with the info, gives me a stupid grin on my face and awesome to know it's helped you.  Makes all the time put into it worth it!

Found that Windows 8 has changed the AHCI driver from msahci to storahci, so this might save you some time if you encounter the same thing with Win 8 or Server 2012 - you additionally to change these values to activate AHCI in Win 8:-

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci:
Start = 0 (default = 3)
Error Control = 0 (default = 3)

Then in the StartOverride sub-key set:
0 = 0 (default = 3)

StartOverride doesn't show in my loaded registry when Win 8 is normally booted so I couldn't do this in advance.  If you find the same then you might need to do the following, similar to above:-

  1. Boot from a Win 8 CD/DVD of the same architecture (32 or 64-bit), select Repair then in the advanced tools open the command prompt.
  2. regedt32>Enter
  3. Highlight HKEY_LOCAL_MACHINE, then File>Load Hive>[choose volume with Windows installed]:\Windows\System32\Config\SYSTEM>Open>Key Name = Restored_HKLM>OK.
  4. Expand Restored_HKLM\ControlSet001\services\storahci.
  5. Update the key values as required from above.
  6. Close (updated values are saved as soon as you hit OK), type Exit and press Enter at the command line, shut down, boot up and enjoy Windows 8/Server 2012 with AHCI.

Cheers,

Chris

Thursday, October 17, 2013 9:12 PM

It's been almost two years to the day since you posted this, and you totally just fixed my issue as well.

FYI - confirmed VM fix on Hyper-V - thank you very much!

Wednesday, January 29, 2014 2:05 PM

Hi,

I also confirm, that setting start DWORD 0x0 to the services registry brings server online.

However there is one catch. If the server doesn't starts correctly after the Chris'es "basic" setup, You should zeroed all services, which has "SCSI Miniport" as the Group value. This makes huge overhead for loaded drivers, but makes sure, that all registered drivers will be available to the kernel during system load.

So, get opened registry editor, and search for "SCSI Miniport" string. For each one change the start value to 0x0.

And than, for sure the server will bring on line again!

Regards,

Stanislaw

Thursday, January 30, 2014 12:08 PM

Backup harddisk/storage controller driver using any decent driver backup tool.

inject the driver in WINRE using cmd

drvload yourdriver.inf

start /w wpeinit

resume restoration process

BOOM u have your OS up and running

I have tried this with an image taken from HP dl380 server and restored to a tower PC

EDIT:

in the driver backup step, you should install windows on the target mechine first then backup the driver from there and inject it during the restoration process.

Friday, March 14, 2014 11:02 AM

Hey Chris,

Thank you so much for taking your time to find the solution, this has just saved me hours and hours of work trying to sort out why our BMR was rebooting.

Took a few attempts to get the combinations right in the registry, but I'm now sat here with a login screen!

Thanks again,

Matt

Friday, July 18, 2014 8:57 AM

Just found this post after restoring a Server2008R2 to a VM - changing the registry values as mentioned helped - thanks !

Friday, November 7, 2014 4:04 AM

HOLY CRAPP!!!!!

This just saved my bacon and all of my PlexMedia settings on my Home Server 2011. I was so ready to give up after a 3am power outage messed the machine up. (Installing the UPS drivers so it shuts down gracefully next time.)

I spent 3 days trying to figure out why the machine would just reboot and go into recovery mode.

Narrowed it down to the 0x0000007B when I figured out how to use safe mode to disable automatic reboot.

Came across this post and was like no way, it can't be this.

Changed all the values in your second suggestion and I booted into safe mode to watch the driver list scroll by and it got to the atipcie.sys where it's always hung up every other time, paused like it was going to hang, screen went black for a second and then the Login Screen greeted me. YEAH!!!!

Bookmarking this post.

Friday, December 26, 2014 3:16 PM

Thanks Irish Chris for the good info

Friday, January 30, 2015 11:31 AM

Hi! Just logged in to say thanks!!

This worked when trying to restore a 2008R2 on ESXi 5.5 as well!

Wednesday, April 8, 2015 3:53 PM

Hi. This answers saved my day. Thank you.

My way to get things working:

  • Mounted VHD on a server and loaded the System Hive.
  • Browsed to ControlSet001/service and changed the following Start values:

intelide - changed from 3 to 0
Pciide - changed from 0 to 3
lsisas - changed from 3 to 0
lsisas2 - changed from 3 to 0

  • Unloaded the System Hive.
  • Dismounted the VHD.
  • Started a new VM with the VHD and went straight to Normal Mode.
  • Windows found the drivers and applied settings. Within 15 minutes I was login into the system and no issues.
  • Created a Snapshot of the VM and began cleaning previous hardware devices and software.

Thank you.

Tuesday, February 9, 2016 1:05 PM

Thanks, this was required for and worked for me to do a bare metal backup/restore for a Windows Server 2008 R2 x64 image transfer from VMWare to a real system.

Thursday, November 24, 2016 7:50 PM

Amazing! Five years after Irish Chris's post and his information helped me out today. Thank you a lot Irish Chris!

I was on a situation where I had a Windows 7 SP1 Pro 32-bit image backup, and needed to restore it to a Hyper-V machine (running on Windows 10 Pro).

The SATA mode was set to IDE "(Compatible)" in BIOS setup where this Windows 7 was running (the physical machine). I have done the Windows image backup, then the network restore on a VM (Generation 1), and after the restore process have completed, I was getting those annoying BlueScreens!

So, after a little web search, found this thread, and Irish Chris's post was the one which saved my brain!

For me, I got my Windows 7 running after modifying the values suggested on his post (intelide>Start = 0 and LSI_SAS>Start = 0; msahci>Start = 3 and pciide>Start = 3).

Hope it helps someone else in a similar situation.

Chris, thank you again buddy!

Friday, August 4, 2017 6:57 PM

You my friend are my HERO!!!

Needed to restore my SBS2011 to VMware and received BSOD, followed your instructions and am up and running again.

Thanks!

Tuesday, April 3, 2018 8:45 PM

I'm having identical problem virtualizing SBS 2011 physical machine (dell with perc raid), it boots into the VHD ONCE, windows replaces the VIRTUAL HD ATA DEVICE and from that point it blue screens on following boots with 0x000007b.

I have tried all combinations of settings here and am at a loss to solve the problem, any advice?

Thursday, May 31, 2018 7:15 AM

Start

This defines when in the boot sequence the service should be started. You can also set these by using the Services control panel applet.

Value Start Type Meaning
0x00 Boot The kernel loaded will load this driver first as its needed to use the boot volume device
0x01 System This is loaded by the I/O subsystem
0x02 Autoload The service is always loaded and run
0x03 Manual This service does not start automatically and must be manually started by the user
0x04 Disabled The service is disabled and should not be started

Sunday, June 3, 2018 7:36 AM | 1 vote

I have made the export to VHD from VDI from VirtualBOX to Xenserver with this error

<style type="text/css">p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 26.0px 'Helvetica Neue'; color: #000000} </style>

*** STOP: 0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)  I believe the non-bracketed portion means "INACCESSABLE_BOOT_DEVICE".

And have make the change to the regedit with this parameters and booted with out problem:

Xen Server:
aliide 3
amdide 3
atapi 0
cmdide 3
iastorv 3
intelide 0
msahci 3
pciide 3
viaide 3
LSI_SAS 0

Tuesday, July 10, 2018 9:21 PM

Absolute lifesaver! With 6 hours before a deadline to convert a server it's running.

If it helps anyone, I've just restored a Server 2008 R2 box with AHCI SATA drives from one Dell system (physical) to a different Dell system (physical) and had to set ATAPI to 0 for it to boot.

Saturday, December 15, 2018 5:06 PM

I know this is old but in case this can help someone in the future.

Sometimes you'll do all these changes and still get the error. What ended up being my issue was there's an LSI_SAS2 that ALSO needs to be changed from 3 to 0.

This was restoring a 2008R2 server from physical to HyperV VM.

Sunday, November 3, 2019 3:04 PM

Thank you very much sir, this saved my day when restoring baremetal to hyper-v was showing BSOD after a successful restore. Thanks a lot.

Monday, November 25, 2019 3:35 AM

Hi Chris and All,

I already follow the Chris's step but it still get error stop 0x0000007B.

We restore the windows server 2008 R2 from Supermicro with SAS disk to HP Proliant DL 380 G8 with SSD Disk.

Could you help me?

Regards,

Nana

Monday, November 25, 2019 12:08 PM

Hi All,

The problem solved by searching for every key containing the value “SCSI Miniport” where the “Start” value was a “3” and changed the “Start” value to a “0”.

https://www.think-like-a-computer.com/2011/03/03/stop-0x0000007b-windows/

with the step above, are there impact to the windows system?

Regards,

Nana