VirtualBox

Ticket #7959 (closed defect: worksforme)

Opened 3 years ago

Last modified 3 months ago

Windows 7 host BSOD with VirtualBox 4.0.0

Reported by: Igloo Owned by:
Priority: critical Component: host support
Version: VirtualBox 4.0.0 Keywords: bsod DRIVER_POWER_STATE_FAILURE crash
Cc: Guest type: other
Host type: Windows

Description (last modified by frank) (diff)

Hello,

After upgrading to VB 4.0.0, my Windows 7 x64 host crashes with a  ''DRIVER_POWER_STATE_FAILURE'' blue screen of death.

This happened to me twice, and I have deduce that it is because of VirtualBox because it is the only installation that touch the drivers I've done recently.

It seems to happen after waking up from sleep mode (with a delay of about five minutes). This corresponds to the indication of Microsoft about this BSOD :

This bug check indicates that the driver is in an inconsistent or invalid power state.

You should have more information in the minidump attached.

Maybe this ticket can be related to this other.

Attachments

123010-43212-01.7z Download (111.1 KB) - added by Igloo 3 years ago.
Core dump
windbg.txt Download (7.2 KB) - added by sunlover 3 years ago.
WinDbg output for the minidump

Change History

Changed 3 years ago by Igloo

Core dump

comment:1 Changed 3 years ago by sunlover

Thanks for the minidump. Actually it shows that the bugcheck happened in atapi.sys windows driver. It is unlikely that VBox is the direct cause of the crash.

Do any of your VMs use host DVD/CD drive passthrough? Does the crash happen only after a VBox VM has been running?

comment:2 Changed 3 years ago by Igloo

Do any of your VMs use host DVD/CD drive passthrough?

I use this feature sometimes. Unfortunately I don't remember if it was enabled when the crash happened.

Does the crash happen only after a VBox VM has been running?

Apparently yes, although I did not do further testing. And It's never happen before I upgrade to VB 4.0.0.

On the second crash, I remember that I had two VBox VMs running, one Windows XP and one Debian Lenny.

Actually it shows that the bugcheck happened in atapi.sys windows driver. It is unlikely that VBox is the direct cause of the crash.

Could you send me all informations you have got from the minidump and that allowed you to deduct it, or tell me how to get them, so I can understand what happened? And fix the problem if it's not Vbox. Thank you.

Changed 3 years ago by sunlover

WinDbg output for the minidump

comment:3 Changed 3 years ago by sunlover

I've attached the WinDbg output.

comment:4 Changed 3 years ago by Igloo

Thank you for the WinDbg output. It seems that sptd.sys driver was also at fault. I have Daemon Tools installed, so I think it is responsible. But I installed it for over a year, without any issue before. So I think that an Windows update or maybe VB 4.0 came into conflict with Daemon Tools.

If the problem appear again, I'll uninstall Daemon Tools.

Sorry for the inconvenience and for having falsely accused Virtualbox, and thanks again.

comment:5 Changed 3 months ago by frank

  • Status changed from new to closed
  • Resolution set to worksforme
  • Description modified (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use