Windows 7: BSOD Power State Failure - Please help

CurtisHelp · 23 Nov 2010

Hello,

Every since I had Telus Internet installed, my computer keeps giving me a BSOD when it goes to sleep. It's a Driver_Power_State_Failure ... 0x0000009F.

I don't get this with Shaw internet, only with Telus (I also have Optik TV on the same network). I still have both providers, and the computer is stable with shaw, but not with Telus.

I can eliminate the error by switching the Power Options so the hard drives "Never" turn off ... but I'm not sure what affect this has on the computer.

Please help, I don't understand mini-dumps and I've spent about 10 hrs on the phone.

My computer was orginally Vista, but my Hard drive crashed so I installed the full version of Windows 7 on the computer. Its 32 bit, on a 2-3 year old computer (Intel Core 2 Quad CPU Q9450).

I appreciate the help!

CarlTR6 · 23 Nov 2010

Hi, Curtis. Sorry you are having problems. Your dumps are blaming e1e6232.sys, which is a LAN driver (network adapter) for the crashes. This driver is up to date and something else may be interfering with it.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c1b000 PsLoadedModuleList = 0x82d63810
Debug session time: Mon Nov 22 21:55:01.429 2010 (GMT-5)
System Uptime: 0 days 0:54:38.224
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 85e6db60, 82d41ae0, 85995328}

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

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 85e6db60, Physical Device Object of the stack
Arg3: 82d41ae0, Functional Device Object of the stack
Arg4: 85995328, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  85995328

DEVICE_OBJECT: 86bb2028

DRIVER_OBJECT: 863f7e30

IMAGE_NAME:  e1e6232.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bac6cac

MODULE_NAME: e1e6232

FAULTING_MODULE: 91bb6000 e1e6232

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82c57054 to 82cf7d10

STACK_TEXT:  
82d41a94 82c57054 0000009f 00000003 85e6db60 nt!KeBugCheckEx+0x1e
82d41b00 82c568e8 82d41ba0 00000000 82d4e280 nt!PopCheckIrpWatchdog+0x1f5
82d41b38 82c8504d 82d5ca20 00000000 d26f7440 nt!PopCheckForIdleness+0x73
82d41b7c 82c84ff1 82d44d20 82d41ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82d41c68 82c84eae 82d44d20 82d41ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82d41cdc 82c8320e 000334dd 88026030 82d4e280 nt!KiTimerExpiration+0x25c
82d41d20 82c83038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82d41d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_e1e6232.sys

BUCKET_ID:  0x9F_IMAGE_e1e6232.sys

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

Many times this kind of error is caused by a third party antivirus or third party firewall. I recommend that you uninstall Vipre antivirus. Many third party antivirus programs cause BSOD's on some Win Win 7 systems. Download, install and use Revo Uninstaller (free) to remove Vipre. Once your system is stable, you can try Vipre again; but I do not recommend doing so. Download and install Microsoft Security Essentials in its place.

Outdated drivers can and do cause BSOD's. I find the following outdated drivers on your system. Both are way obsolete and are not going to run on a Win 7 system. Update the drivers or uninstall the software with which they are associated.

Quote:

000.fcl Fri Sep 26 09:11:12 2008 - CyberLink FCL Driver, http://www.gocyberlink.com. Update CyberLink or uninstall it.

PxHelp20.sys Wed Oct 17 14:24:26 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs) http://www.carrona.org/pxhelp20.html
Go to C:\Windows\System32\drivers and rename PxHelp20.sys to PXHelp20.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

Uninstall Vipre and take care of the above drivers. Reboot and see how your system runs. Update us and let us know. If you get another BSOD after taking the steps above, please upload it and we will go from there.

CurtisHelp · 23 Nov 2010

Thanks so much for the help. I very much appreciate it.

Jonathan_King · 23 Nov 2010

Looks like your Intel Ethernet drivers are the cause.

Code:

Timestamp:        Fri Mar 26 04:13:32 2010 (4BAC6CAC)

Install these updated ones: http://downloadcenter.intel.com/Deta...=2775&lang=eng

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_BSOD reports.zip\Windows_NT6_BSOD_jcgriff2\112110-14570-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82d68ad4?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c42000 PsLoadedModuleList = 0x82d8a810
Debug session time: Sun Nov 21 11:16:35.324 2010 (UTC - 5:00)
System Uptime: 0 days 1:11:53.119
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 85e60b60, Physical Device Object of the stack
Arg3: 82d68ae0, Functional Device Object of the stack
Arg4: 85b3af00, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf14

MODULE_NAME: pci

FAULTING_MODULE: 8b904000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
82d68a94 82c7e054 0000009f 00000003 85e60b60 nt!KeBugCheckEx+0x1e
82d68b00 82c7d8e8 82d68ba0 00000000 82d75280 nt!PopCheckIrpWatchdog+0x1f5
82d68b38 82cac04d 82d83a20 00000000 77ce09ff nt!PopCheckForIdleness+0x73
82d68b7c 82cabff1 82d6bd20 82d68ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82d68c68 82cabeae 82d6bd20 82d68ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82d68cdc 82caa20e 00043800 85708270 82d75280 nt!KiTimerExpiration+0x25c
82d68d20 82caa038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82d68d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_e1e6232_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_e1e6232_IMAGE_pci.sys

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

0: kd> lmvm e1e6232
start    end        module name
91e00000 91e39000   e1e6232    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\e1e6232.sys
    Image name: e1e6232.sys
    Timestamp:        Fri Mar 26 04:13:32 2010 (4BAC6CAC)
    CheckSum:         000431D0
    ImageSize:        00039000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

CarlTR6 · 23 Nov 2010

Quote: Originally Posted by CurtisHelp

Thanks so much for the help. I very much appreciate it.

You are very welcome. I hope your problem is a simple fix.

CurtisHelp · 23 Nov 2010

Thanks for everything, I've done exactly what you instructed. Now to see if it works.

CarlTR6 · 23 Nov 2010

You are welcome. Here's hoping!!

CurtisHelp · 24 Nov 2010

It worked! My error is gone. I installed Microsoft Essentials, and everything is good (microsoft essentials even found a virus ... win32/PowerRegScheduler). I might re-install Vipre on the weekend.

Is microsoft essentials good enough?

Thanks again for your help, I really do appreciate it.

Jonathan_King · 24 Nov 2010

MSE is good enough, although the best security option is using good judgment about the sites you visit, the programs you install, etc.

Glad to hear the BSODs have stopped. Let us know if you need anything else!

CarlTR6 · 24 Nov 2010

You are welcome, Curtis; and Jonathan is spot on.

Windows 7: BSOD Power State Failure - Please help

BSOD Power State Failure - Please help problems?