BSOD STOP0x000000d1 bridge.sys Windows 8 Hyper-V

I’m running Windows 8 with the Hyper-V Role enabled on my LAB-top.
To connect my VMs to the outside world, i have created two Hyper-V Virtual Switches; one connected to my WiFi adapter, and one connected to the Onboard NIC.
Both connections are bridged, using the “Allow Management operating system to share this network adapter” setting, allowing the Host OS (Windows 8) to also use these interfaces.
vswitches
This worked fine for me the last couple of months, but today i got a BSOD. 😦
Specifically: DRIVER_IRQL_NOT_LESS_OR_EQUAL(d1)
After starting the Crash Analyzer tool, which is part of DaRT (Diagnostics and Recovery Toolset), the cause of the BSOD appeared to be the bridge.sys driver.

bridge.sys

This is the driver that provides the functionality for the network bridging that is done when you enable the “Allow the management OS to share this network adapter” in hyper-v.
It seems I’m not the only one that experienced this issue; Marius Sandbu and Henk hoogendoorn also encountered this, and have provided some workarounds (disable bridging on the WiFi nic)

For now, i will continue using the bridging, unless i get more BSODs…

For what it’s worth; i have been running this setup for 3 months now, and i have used the bridging over WiFi and the onboard NIC quite extensively, but have never had any problems with it.

So my question is; why did this start now? Updates? Patches?

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: