Opened 14 years ago
Closed 11 years ago
#7959 closed defect (worksforme)
Windows 7 host BSOD with VirtualBox 4.0.0
Reported by: | Igloo | Owned by: | |
---|---|---|---|
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 )
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 (2)
Change History (7)
by , 14 years ago
Attachment: | 123010-43212-01.7z added |
---|
comment:1 by , 14 years ago
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 by , 14 years ago
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.
comment:4 by , 14 years ago
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 by , 11 years ago
Description: | modified (diff) |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Core dump