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

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

Rate This
  • Comments 29

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

 

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

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

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

  • Thank you, but what I should to do, if by F8  I has same error... :(

  • Saved me big time with this post!  Thank you

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

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

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

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

  • 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!

  • 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

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

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

  • 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

  • Thanks for posting this. Worked like a charm!

Page 1 of 2 (29 items) 12
Leave a Comment
  • Please add 6 and 6 and type the answer here:
  • Post