BSOD when Win8 x64 goes to Hybrid Shutdown

[piotrb]

Host OS: Windows 8 Pro AMD64

VirtualBox's 4.2.6 VboxNetFlt driver causes BSOD 0x9F (DRIVER_POWER_STATE_FAILURE). See minidump and analyze log of memory.dmp.

Attached is the WinDbg log of the crash dump with !analyze -v and !irp <blocked_IRP> commands executed.

[piotrb]

Windbg log

[anshul makkar]

Hi,

We have been unable to reproduce the crash in the lab.

Please can you share the exact details of what all operations you performed when the crash is observed and what is the guest that you are using. Is it repetitive and reproducible?

[Frank Mehnert]

Also, how often do you see this BSOD -- on every shutdown of the host?

[anshul makkar]

And also please can you let us know if the guest network was configured in bridged or NAT mode. ?

[Frank Mehnert]

Is anybody else experiencing the same problem and can answer the above questions?

[piotrb]

„1) Please can you share the exact details of what all operations you performed when the crash is observed and what is the guest that you are using. Is it repetitive and reproducible? 2) Also, how often do you see this BSOD -- on every shutdown of the host? 3) And also please can you let us know if the guest network was configured in bridged or NAT mode. ?”

Crash happened at hybrid shutdown of host. Guests: Windows XP, Debian Wheezy, Fedora 19. All were turned off at least a few minutes before turning off the computer. Crash happened often(but not every time) at hybrid shutdown. Guest network was bridged. On the same network adapter runs Qbik Wingate7 NAT. Solution for me was:

1. Remove VirtualBox Bridged Networking Driver from network connections
2. Switch virtual machines to Host only adapter
3. Make bridge in system between host only adapter and adapter connected to home LAN.

Since then, this bsod didn't occur.

[anshul makkar]

Even with the above steps, crash is not reproducible in the lab.

Working on the issue to find a fix.

[anshul makkar]

The reporter of the issue has informed that the issue is not reproducible after updating the NIC driver. So , if facing this issue, please update your NIC driver. If, still facing the issue, please update the bug with the error report.