After installing Hyper-V Integration Services on the next reboot the VM displays BSOD 0x0000007B


Hi,


 


Recently,  I had some customers with VMs they just P2V’ed, or even had them running already on Virtual Server or Hyper-V. Now, they installed the latest Integration Components that came with the R2 Release.


 


After the required reboot, the VM shows a Bluescreen 0x0000007B INACCESSIBLE_BOOT_DEVICE


 


During Debugging I found that the Storage Driver of the ICs require the Windows Driver Framework (WDF), which was not loaded in this case. So the Storage Driver fails to load.


Looking into the Registry of the VM, shows that the WDF Driver was already installed previously, but had the wrong Group relationship, so it is initialized too late.


 


So here’s how to fix this issue:


 


1.       Boot the VM into LastKnownGood. Press F8 during boot.


2.       Open the Registry and drill down to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000


3.       There is a Group Value that should have the Value WdfLoadGroup. In my cases it was wrongly set to base. Change this to WdfLoadGroup


4.       Then remove the Integration Components from Control Panel/Software.


5.       Reboot the VM (now without ICs)


6.       Install the ICs once again


 


Cheers


Robert


 


Comments (36)

  1. BT says:

    Thanks, this saved me a ton of time.   It happens EVERY time we do a P2V for some reason.

  2. Peter Forster says:

    Robert, you are my hero! I run the first time into this issue and you solved my life! Thanks for that!

  3. AS says:

    Fantastic, have been fighting this one all day.  Working like a charm now, thanks for your help

  4. Max says:

    Thank you, but what I should to do, if by F8  I has same error… πŸ™

  5. Faye says:

    Saved me big time with this post!  Thank you

  6. John Nance says:

    Does anybody know why P2V does not change base… to WdfLoadGroup?

  7. John Nance says:

    Does anybody know why P2V does not change base… to WdfLoadGroup?

  8. zan says:

    Thanks so much.  Didn't want to be here four more hours trying to re p2v and then have it fail again.

  9. Mark1408 says:

    You are a star. I thought my virtualisation effort was doomed when my blue screening started. Thanks for this.

  10. AubreyJones says:

    You are the MAN! I was having all kinds of difficulties with the blue screens at one of our company locations. The strange thing is that this is the first time I've run into these issues and have P2V'ed multiple machines at various locations. Thank You!

  11. Declan says:

    Thanks for the fix

    it took me 2 days to find it – strange thing – this is my 300th, or so, P2V 50th with Hyper-v 20th on this server and the first time I've seen this

    Thanks

    Declan

  12. Takiska says:

    My frient YOU ARE SIMPLY THE BEST….  THANK YOU THANK YOU THANK YOU

  13. Mark Wolzak says:

    You are a lifesaver!!!… Thank you!!! (**Deep sigh of relief**)

  14. Steve says:

    Great job, first time I ran into this and your blog saved my a butt load of time and heartache explaining the server outage.  Thanks

  15. Tyar says:

    Thanks for posting this. Worked like a charm!

  16. I had the same issue when migrating from windows 2000 server to Windows server 2003  at the last reboot just befor loading the system , a  Bluescreen 0x0000007B  , but this resolution isn't a way to resolve it , please if there is a way to fix it tell me how !!!

  17. Geoffrey says:

    Wow… wonderful ! Thank you very much, we were totally blocked with this fuc*in error ! πŸ™‚

  18. JP says:

    Just did a P2V using XenConvert -> VHD and booted the server on Hyper-V 2012.

    After installing Integration Services I had the same issue…

    Thx. a lot for your good old post – it still works!

    /JP

  19. Frank says:

    VMM 2012 SP1 (rollup 2)  still suffers from this  when doing a P2V. Thankfully I was able to boot a rescue disk and edit the registry. Didn't have to uninstall anything, simply booted and it was fixed. Thanks!

  20. Paul says:

    Thanks so much, I was stuck on this for hours and all the other posts didn't help.  I owe you a beer!

  21. James says:

    THANK YOU SO MUCH this was causing me near suicidal stress, trying to P2V 2 old 2003 metaframe servers.

  22. ROBERT_RULES says:

    Dude that worked perfectly! This should be in the disk2vhd code πŸ™‚  many thanks

  23. JFG says:

    I had the same problem but Last Known Good wasn't working. Here's what I did on my Hyper-V Server 2012 (console only):

    1. Make sure you are in a PowerShell window (just type "powershell" at the command prompt).

    2. > Mount-VHD *path to your vhd*

    3. Figure out the letter it used to mount the VHD, usually the next available D, E, F, G, whatever.

    4. > regedit

    5. Select HKEY_USERS then File -> Load Hive.

    6. Browse your mounted VHD to C:WindowsSystem32Config and load the SYSTEM file.

    7. Follow Robert's great instructions on fixing this problem.

    8. Select you loaded hive. File -> Unload Hive and close Regedit.

    9. > Dismount-VHD *path to your vhd*.

    10. Boot your VM and enjoy!

    Thanks Robert!

  24. Danny Newton says:

    Cheers! Not what you want to see mid migration, worked a treat

  25. SeanPT says:

    I'm just coming in from the future to let you know this is still helpful 4+ years later and that the US will lose back to back in the Olympics to Canada.

  26. RobB says:

    WOW – Thank you, first time this happened to me on a P2V and this fix worked GREAT!

  27. Rob says:

    I'm getting a 0x00000CA STOP error after installing Hyper-V 2012R2 Intergration Services on 2008R2 VM

  28. Justin says:

    Spent 2 days on this. Found this article and worked like a champ! Wish I could buy you a beer! Thanks!

  29. Brad Baird says:

    DUDE, If I could hug you I would.  I have had a server down for several hours doing this conversion from VMware to Hyper-V and this saved my life!!  Thank you, thank you!!!!

  30. Phillip Husari says:

    This helped me out big time!! THANKS!

  31. Franko says:

    Didn't work, I have the correct registry info but it still BSOD. Any other suggestions?

    It's a 2012 R2 with 2008 SP2 host

  32. hahahaha says:

    VMware. Stop using shite hypervisors.

  33. Anonymous says:

    This definitely was a time saver for me as well. Same scenario, Windows server 2003 to Hyper-V on a brand-new server 2012 host. So the problem still does exist with the IC installation as of this date.

    Thanks for the article!

  34. Anonymous says:

    Hi All,

    I did all above modifications,but still my problem not resolved..

    Please help me on this issue..

  35. Jamie says:

    3 1/2 years on still relevant!

    Thanks

  36. Stephane says:

    Hello,

    6 years after your post, you are still making people happy πŸ™‚

    Big thanks…