Hello, I'm on a windows 7 64 bit machine and today I had a 9f blue screen error (Driver Power State Failure) while the machine was entering standby.
I debugged the memory.dmp and related minidump and that's the relevant part:
Probably caused by : VBoxNetAdp.sys
So it looks like the net adapter driver had a problem with standby mode and didn't shut down in time.
Has this happened to anyone else? It may be a rare occurrence, I usually disable the driver but this time when I installed the latest vbox some days ago I forgot to disable it.
My machine enters standby mode at least 5 times a day, so it may be something which happens only once in a while, but I thought it was worth mentioning.
9F blue screen error caused by virtual box
-
- Posts: 19
- Joined: 9. Apr 2009, 14:19
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Windows 8
-
- Volunteer
- Posts: 1064
- Joined: 10. May 2007, 10:27
- Primary OS: MS Windows Vista
- VBox Version: PUEL
- Guest OSses: Windows, Linux, Solaris
Re: 9F blue screen error caused by virtual box
Please open a ticket in our bug tracker and attach the minidump. Thanks.
-
- Posts: 19
- Joined: 9. Apr 2009, 14:19
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Windows 8
Re: 9F blue screen error caused by virtual box
Ok, I'll do that right away, thanks.
-
- Posts: 5
- Joined: 9. Nov 2009, 18:27
- Primary OS: MS Windows Vista
- VBox Version: PUEL
- Guest OSses: Ubuntu 9.10
Re: 9F blue screen error caused by virtual box
I think that I'm having a similar problem. When my machine goes to sleep for power management reasons, VirtualBox crashes and pulls the machine down.
Although WinDbg reports that the process is VirtualBox, but I can't pin point the driver (see debugging details below). Is there an FAQ out there on how to identify drivers from the call stack?
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+0
fffffa80`042de32a ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: ffffffffffffffff
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: VirtualBox.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80001a5ba57 to fffff80001a79450
STACK_TEXT:
fffffa60`0470dee8 fffff800`01a5ba57 : 00000000`0000001e ffffffff`c0000005 fffffa80`042de32a 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0470def0 fffff800`01a792a9 : fffffa60`0470e628 fffffa60`09cc5000 fffffa60`0470e6d0 fffffa60`09ce2980 : nt! ?? ::FNODOBFM::`string'+0x29117
fffffa60`0470e4f0 fffff800`01a77e8d : fffff800`01b9bdc0 fffff800`01b0813f fffffa80`04274060 fffff880`00000100 : nt!KiExceptionDispatch+0xa9
fffffa60`0470e6d0 fffffa80`042de32a : 00000000`bfaea000 fffffa80`042e1978 fffffa60`0014cc12 00000000`00000001 : nt!KiGeneralProtectionFault+0xcd
fffffa60`0470e860 00000000`bfaea000 : fffffa80`042e1978 fffffa60`0014cc12 00000000`00000001 00000000`00008000 : 0xfffffa80`042de32a
fffffa60`0470e868 fffffa80`042e1978 : fffffa60`0014cc12 00000000`00000001 00000000`00008000 fffff880`08b05140 : 0xbfaea000
fffffa60`0470e870 fffffa60`0014cc12 : 00000000`00000001 00000000`00008000 fffff880`08b05140 fffffa60`01bbf000 : 0xfffffa80`042e1978
fffffa60`0470e878 00000000`00000001 : 00000000`00008000 fffff880`08b05140 fffffa60`01bbf000 fffffa80`042dd148 : 0xfffffa60`0014cc12
fffffa60`0470e880 00000000`00008000 : fffff880`08b05140 fffffa60`01bbf000 fffffa80`042dd148 fffffa80`081de040 : 0x1
fffffa60`0470e888 fffff880`08b05140 : fffffa60`01bbf000 fffffa80`042dd148 fffffa80`081de040 00000000`00000000 : 0x8000
fffffa60`0470e890 fffffa60`01bbf000 : fffffa80`042dd148 fffffa80`081de040 00000000`00000000 fffffa80`04274060 : 0xfffff880`08b05140
fffffa60`0470e898 fffffa80`042dd148 : fffffa80`081de040 00000000`00000000 fffffa80`04274060 fffffa80`03c25010 : 0xfffffa60`01bbf000
fffffa60`0470e8a0 fffffa80`081de040 : 00000000`00000000 fffffa80`04274060 fffffa80`03c25010 fffffa60`09cc5000 : 0xfffffa80`042dd148
fffffa60`0470e8a8 00000000`00000000 : fffffa80`04274060 fffffa80`03c25010 fffffa60`09cc5000 fffffa80`05618c80 : 0xfffffa80`081de040
Although WinDbg reports that the process is VirtualBox, but I can't pin point the driver (see debugging details below). Is there an FAQ out there on how to identify drivers from the call stack?
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+0
fffffa80`042de32a ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: ffffffffffffffff
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: VirtualBox.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80001a5ba57 to fffff80001a79450
STACK_TEXT:
fffffa60`0470dee8 fffff800`01a5ba57 : 00000000`0000001e ffffffff`c0000005 fffffa80`042de32a 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0470def0 fffff800`01a792a9 : fffffa60`0470e628 fffffa60`09cc5000 fffffa60`0470e6d0 fffffa60`09ce2980 : nt! ?? ::FNODOBFM::`string'+0x29117
fffffa60`0470e4f0 fffff800`01a77e8d : fffff800`01b9bdc0 fffff800`01b0813f fffffa80`04274060 fffff880`00000100 : nt!KiExceptionDispatch+0xa9
fffffa60`0470e6d0 fffffa80`042de32a : 00000000`bfaea000 fffffa80`042e1978 fffffa60`0014cc12 00000000`00000001 : nt!KiGeneralProtectionFault+0xcd
fffffa60`0470e860 00000000`bfaea000 : fffffa80`042e1978 fffffa60`0014cc12 00000000`00000001 00000000`00008000 : 0xfffffa80`042de32a
fffffa60`0470e868 fffffa80`042e1978 : fffffa60`0014cc12 00000000`00000001 00000000`00008000 fffff880`08b05140 : 0xbfaea000
fffffa60`0470e870 fffffa60`0014cc12 : 00000000`00000001 00000000`00008000 fffff880`08b05140 fffffa60`01bbf000 : 0xfffffa80`042e1978
fffffa60`0470e878 00000000`00000001 : 00000000`00008000 fffff880`08b05140 fffffa60`01bbf000 fffffa80`042dd148 : 0xfffffa60`0014cc12
fffffa60`0470e880 00000000`00008000 : fffff880`08b05140 fffffa60`01bbf000 fffffa80`042dd148 fffffa80`081de040 : 0x1
fffffa60`0470e888 fffff880`08b05140 : fffffa60`01bbf000 fffffa80`042dd148 fffffa80`081de040 00000000`00000000 : 0x8000
fffffa60`0470e890 fffffa60`01bbf000 : fffffa80`042dd148 fffffa80`081de040 00000000`00000000 fffffa80`04274060 : 0xfffff880`08b05140
fffffa60`0470e898 fffffa80`042dd148 : fffffa80`081de040 00000000`00000000 fffffa80`04274060 fffffa80`03c25010 : 0xfffffa60`01bbf000
fffffa60`0470e8a0 fffffa80`081de040 : 00000000`00000000 fffffa80`04274060 fffffa80`03c25010 fffffa60`09cc5000 : 0xfffffa80`042dd148
fffffa60`0470e8a8 00000000`00000000 : fffffa80`04274060 fffffa80`03c25010 fffffa60`09cc5000 fffffa80`05618c80 : 0xfffffa80`081de040
-
- Volunteer
- Posts: 1064
- Joined: 10. May 2007, 10:27
- Primary OS: MS Windows Vista
- VBox Version: PUEL
- Guest OSses: Windows, Linux, Solaris
Re: 9F blue screen error caused by virtual box
Same for you: please create a ticket and attach the minidump. We have symbol info here, so windbg will show us the right call stack. Thanks.
-
- Posts: 5
- Joined: 9. Nov 2009, 18:27
- Primary OS: MS Windows Vista
- VBox Version: PUEL
- Guest OSses: Ubuntu 9.10
Re: 9F blue screen error caused by virtual box
Posted bug, ticket #5706, sorry for the delay.