BSOD - Driver Power State Failure

schniederzero

New member
Local time
11:08 PM
Messages
2
Hey Everyone,

If anyone could take a look at this and see why I got the BSOD for Driver Power State Failure, I would greatly appreciate it.

There are a few .dmp files in the attachment, but the only one I am concerned about would be the most recent one and may be the one before, since they are both related to Driver Power State Failure.

Thanks in advance.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom
OS
Windows 7 Professional x64
CPU
Intel i5 750 @ 3.1ghz
Motherboard
Asus P7P55D-E LX
Memory
16 gb (8x2) DDR3
Graphics Card(s)
Nvidia 660 Asus
Hard Drives
128GB SSD, 2TB
Antivirus
AVG
Browser
Chrome
Welcome to the forum.

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\schniederzero\SF_13-01-2014\011314-25708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Mon Jan 13 07:54:00.000 2014 (UTC + 6:00)
System Uptime: 0 days 6:48:39.771
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800c7ec4d0, fffff8000437c518, fffffa802b34e540}

*** WARNING: Unable to verify timestamp for VBoxNetAdp.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetAdp.sys
Probably caused by : VBoxNetAdp.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800c7ec4d0, Physical Device Object of the stack
Arg3: fffff8000437c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa802b34e540, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa800e161050

DRIVER_OBJECT: fffffa800e211e70

IMAGE_NAME:  VBoxNetAdp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52b1c9a9

MODULE_NAME: VBoxNetAdp

FAULTING_MODULE: fffff880044e6000 VBoxNetAdp

IRP_ADDRESS:  fffffa802b34e540

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80004382FB0

STACK_TEXT:  
fffff800`0437c4c8 fffff800`02cebe23 : 00000000`0000009f 00000000`00000003 fffffa80`0c7ec4d0 fffff800`0437c518 : nt!KeBugCheckEx
fffff800`0437c4d0 fffff800`02c88fa6 : fffff800`0437c600 fffff800`0437c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`0437c570 fffff800`02c88326 : fffff800`02e2b700 00000000`0017fbba 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`0437c5e0 fffff800`02c88e7e : 00000039`16ec2929 fffff800`0437cc58 00000000`0017fbba fffff800`02df99c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0437cc30 fffff800`02c88697 : 00000011`249513c1 00000011`0017fbba 00000011`2495132e 00000000`000000ba : nt!KiTimerExpiration+0x1be
fffff800`0437ccd0 fffff800`02c856fa : fffff800`02df5e80 fffff800`02e03c40 00000000`00000000 fffff880`010914c0 : nt!KiRetireDpcList+0x277
fffff800`0437cd80 00000000`00000000 : fffff800`0437d000 fffff800`04377000 fffff800`0437cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_VBoxNetAdp.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_VBoxNetAdp.sys

Followup: MachineOwner
---------

0: kd> lmvm VBoxNetAdp
start             end                 module name
fffff880`044e6000 fffff880`0450e000   VBoxNetAdp T (no symbols)           
    Loaded symbol image file: VBoxNetAdp.sys
    Image path: VBoxNetAdp.sys
    Image name: VBoxNetAdp.sys
    Timestamp:        Wed Dec 18 22:13:29 2013 (52B1C9A9)
    CheckSum:         0002ADD5
    ImageSize:        00028000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It seems that VirtualBox network driver causing the BSOD for you. Please remove it the software.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

AVG contributes to BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Keep us posted.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self assembled
OS
Windows 10 Home 64Bit
CPU
Intel Core i5 10400 @ 2.90GHz
Motherboard
Intel Corporation DG41WV (PROCESSOR)
Memory
8.00GB Single-Channel Unknown @ 1329MHz (16-20-20-38)
Sound Card
Realtek High Definition Audio
Monitor(s) Displays
DELL E170S
Screen Resolution
1280x1024 pixels
Hard Drives
931GB TOSHIBA DT01ACA100 (SATA)
238GB TEAM TM8PS7256G (SATA SSD)
Case
Nothing Fancy
Cooling
Fans
Keyboard
A4 Tech Co LTD
Mouse
A4 Tech Co Ltd/Logitech
Internet Speed
25 Mbps
Thank you very much for the response!

Interesting that virtual box did that.. since I just installed that a few days ago, it makes Me wonder what the previous BSODs were about..

I'll get a different virtual program and see how it performs, along with the other suggestions at the bottom.

You're amazing! Thank you.

Will update in the next few days.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom
OS
Windows 7 Professional x64
CPU
Intel i5 750 @ 3.1ghz
Motherboard
Asus P7P55D-E LX
Memory
16 gb (8x2) DDR3
Graphics Card(s)
Nvidia 660 Asus
Hard Drives
128GB SSD, 2TB
Antivirus
AVG
Browser
Chrome
Back
Top