DRIVER_POWER_STATE_FAILURE intermittent BSOD's

Hello all

I really need help I decided tocome here first before having to recover my Windows 7 back to factory settings. And I would hate to send it back to the socalled teck's at IBUYPOWER because they are really no help at all.

I have been getting occasionalBSOD's for a while now. Also I have been having a lot of issues with my internet. I don't know if one relates to the other. The BSOD is theDRIVER_POWER_STATE_FAILURE. The internet problems are usually when I have either a lot of IE's up at the same time it says something like "The default gateway is not available" when I run the troubleshooter and it fixes it, then 5 mins later again it has the exclamation mark over the internet access bars at the bottom left.

I added my default gateway IP to the network adapters IPv4 setting but still having the issues with the intermittent signals on internet. Again just adding this info in case one relates to the other.

I will attach the file that was created from the dm log collector file.

I thank you in advance for any help / suggestions that anyone can provide me.

Melissa M.

I wanted to add that I followed instructions on this link here for the internet issues Default Gateway Not Available - Intermittent Internet and it was not compatible with my system. Just incase. :)
Ibuypower CZ-17 Valkerie
64-bit OS
Interl 3630QM CPU 2.40 GHz
16GB ram

Nvidia 780M dedicated video card, latest driver is 344.60

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\debug-MelissaM-PC-\110514-111462-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00c90292?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`1af6e942?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`144e7362?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`1c59e3e2?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`1a433a02?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`19607772?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`15e80022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`2284e022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`1c5cac32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0364f000 PsLoadedModuleList = 0xfffff800`03892890
Debug session time: Thu Nov  6 07:09:52.024 2014 (UTC + 6:00)
System Uptime: 0 days 4:16:28.666
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800da4aa10, fffff80000b9c3d8, fffffa80158aa7d0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.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: fffffa800da4aa10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80158aa7d0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f57000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c388 fffff800`037348d2 : 00000000`0000009f 00000000`00000003 fffffa80`0da4aa10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`036cf85c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`036cf6f6 : fffffa80`1005ee60 fffffa80`1005ee60 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`036cf5de : 00000023`d45c39f9 fffff800`00b9cb18 00000000`000f0d4e fffff800`03842c48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`036cf3c7 : 00000008`60add6c2 00000008`000f0d4e 00000008`60add6b5 00000000`0000004e : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`036bc8ca : fffff800`0383fe80 fffff800`0384dcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

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

0: kd> !irp fffffa80158aa7d0
Irp is active with 4 stacks 3 is current (= 0xfffffa80158aa930)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 fffffa800da4aa10 00000000 fffff8800f827260-fffffa80107406a0    
	       \Driver\pci	nvlddmkm
			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa80115e83a0 00000000 00000000-00000000    pending
	       \Driver\nvlddmkm
			Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa801613b770    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f6d7000 fffff880`103b3000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Oct 16 18:31:28 2014 (543FBAA0)
    CheckSum:         00C97F5B
    ImageSize:        00CDC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

MSINFO32:

• Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter.
• Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
• Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

Code:

Start Menu\Programs\DAEMON Tools Pro	Public:Start Menu\Programs\DAEMON Tools Pro	Public

SPTD Removal:

• Uninstall the software using Add/Remove Programs.
• Reboot the system.
• Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
• DuplexSecure - Downloads

As an alternative, many people recommend the use of Total Mounter or Magic ISO


Remove Norton for testing purpose. It contributes to BSOD's.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Reinstall an older version of the drivers and see if that provides stability.

Drivers - Download NVIDIA Drivers


Sometimes drivers remain and do not get completely uninstalled.

Driver Removal Process:

• Download Driver Sweeper to the desired location.
• Extract the files from the zip.
• Uninstall the driver Program & Features - Control Panel.
• Run Driver Sweeper, check the drivers you want to uninstall or clean registry leftovers of.

Link to full tutorial: Drivers - Clean Left over Files after Uninstalling
Perform a Clean boot:

• Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Alright, good luck :)