DRIVE_POWER_STATE_FAILURE on shut down

[younggrr]

Hangs on shut down for 5 - 10, then gives me the BSOD. Details below.

· OS - Windows 7 Non-OEM - Re-imaged with Zenworks 6 months ago. Original OS was Win 7 OEM.
· x64
· Age of system (hardware) - 4 years

· CPU - Intel Core i7-3770
· Video Card - AMD Radeon HD 7470
· MotherBoard - Dell 0KRC95 Version A00
· Power Supply - Unkown

· System Manufacturer - Dell
· Exact model number - Optiplex 7010

· Desktop

 

[Xer]

Hi Younggrr,

This is likely being caused by your VirtualBox network adapter.

0: kd> !irp fffffa801445ae10
Irp is active with 3 stacks 2 is current (= 0xfffffa801445af28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_QUERY_POWER(3)]
            0 e1 fffffa8010ad9050 00000000 fffff800030cf210-fffffa800cad2350 Success Error Cancel pending
           [COLOR=#ff0000]\Driver\VBoxNetAdp    nt!PopSystemIrpCompletion[/COLOR]
            Args: 00016600 00000000 00000006 00000005
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-fffffa800cad2350    


            Args: 00000000 00000000 00000000 00000000

0: kd> lmvm vboxnetadp6
Browse full module list
start             end                 module name
fffff880`01c00000 fffff880`01c2f000   VBoxNetAdp6 T (no symbols)           
    Loaded symbol image file: VBoxNetAdp6.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys
    Image name: VBoxNetAdp6.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Nov 21 11:44:34 2016 (58332472)
    CheckSum:         00020DEF
    ImageSize:        0002F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You can try either disabling the virtual adapter from Device Manager (or Network Connections), and if that doesn't work, try uninstalling VirtualBox. If that corrects the issue and you still need the software, try doing a fresh installation of the most up-to-date version of VirtualBox. Presumably if you put the computer into sleep mode, the same issue would occur.

 

[younggrr]

Initial tests disabling the VirtualBox network adapter seems to resolve the issue. Thank you! I'll keep on eye on it for a few days and if all seems well I'll check back in to mark this resolved.

Hi Younggrr,

This is likely being caused by your VirtualBox network adapter.

0: kd> !irp fffffa801445ae10
Irp is active with 3 stacks 2 is current (= 0xfffffa801445af28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_QUERY_POWER(3)]
            0 e1 fffffa8010ad9050 00000000 fffff800030cf210-fffffa800cad2350 Success Error Cancel pending
           [COLOR=#ff0000]\Driver\VBoxNetAdp    nt!PopSystemIrpCompletion[/COLOR]
            Args: 00016600 00000000 00000006 00000005
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-fffffa800cad2350    


            Args: 00000000 00000000 00000000 00000000

0: kd> lmvm vboxnetadp6
Browse full module list
start             end                 module name
fffff880`01c00000 fffff880`01c2f000   VBoxNetAdp6 T (no symbols)           
    Loaded symbol image file: VBoxNetAdp6.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys
    Image name: VBoxNetAdp6.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Nov 21 11:44:34 2016 (58332472)
    CheckSum:         00020DEF
    ImageSize:        0002F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You can try either disabling the virtual adapter from Device Manager (or Network Connections), and if that doesn't work, try uninstalling VirtualBox. If that corrects the issue and you still need the software, try doing a fresh installation of the most up-to-date version of VirtualBox. Presumably if you put the computer into sleep mode, the same issue would occur.