Stop error 0x0000009f


 I've been having a stop error DRIVER_POWER_STATE_FAILURE.

From looking in the mskb I've found out that it is a driver problem. I've reinstalled all my drivers, done every save for a reinstall of the entire OS.  I am unsure what to do at this point, so I started debugging.  I've been doing system administration for about 6 years, but I've never had to interpret this stuff before, does anyone think they could lead me in the correct direction?  Here is the debugging output:

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

Loading Dump File [C:\WINNT\MEMORY.DMP]
Kernel Dump File: Full address space is available

Symbol search path is: c:\winnt\symbols\
Executable search path is:
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Product: WinNt
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e1b8
Debug session time: Tue Nov 18 22:54:51 2003
System Uptime: 0 days 0:04:29.530
Loading Kernel Symbols
Loading unloaded module list
Loading User Symbols
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {100, 81fe1e50, 81fe1e50, 8204f230}

*** WARNING: symbols timestamp is wrong 0x3f16dae6 0x3ed6e418 for winlogon.exe
Probably caused by : ntoskrnl.exe ( nt!IoBuildPoDeviceNotifyList+27c )

Followup: MachineOwner

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

A driver is causing an inconsistent power state.
Arg1: 00000100, SubCode
Arg2: 81fe1e50
Arg3: 81fe1e50
Arg4: 8204f230

Debugging Details:


DRIVER_OBJECT:  8204f230

DEVICE_OBJECT:  81fe1e50



LAST_CONTROL_TRANSFER:  from 8048d447 to 804875da

eb5dfae4 8048d447 ff32374c 00000001 00000000 nt!IoBuildPoDeviceNotifyList+0x27c
eb5dfb04 8048cfc9 00000000 eb5dfbf4 eb5dfc78 nt!PopSetDevicesSystemState+0x85
eb5dfbe0 80465691 00000005 00000004 c0000004 nt!NtSetSystemPowerState+0x329
eb5dfbe0 80401555 00000005 00000004 c0000004 nt!KiSystemService+0xc4
eb5dfc64 8048cd13 00000005 00000004 c0000004 nt!ZwSetSystemPowerState+0xb
eb5dfd48 804c446f 00000005 00000004 c0000004 nt!NtSetSystemPowerState+0x70
eb5dfd58 80465691 00000001 00000000 00000000 nt!NtShutdownSystem+0x2e
eb5dfd58 77f9b3f7 00000001 00000000 00000000 nt!KiSystemService+0xc4
0006fe94 0100b15e 00000001 00000000 00076a10 ntdll!NtShutdownSystem+0xb
0006feac 0100b414 000005b8 0000000b 0000000b winlogon!`string'+0x6
00000600 00000000 00000000 00000000 00000000 winlogon!`string'+0xc

804875da 8b55ec           mov     edx,[ebp-0x14]

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!IoBuildPoDeviceNotifyList+27c


IMAGE_NAME:  ntoskrnl.exe



BUCKET_ID:  0x9F_nt!IoBuildPoDeviceNotifyList+27c

Followup: MachineOwner


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You may receive a "STOP 0x0000009F DRIVER_POWER_STATE_FAILURE" error message in Windows.
This behavior occurs when drivers do not handle power state transition requests properly. The error message most often occurs during one of the following actions:
Shutting down
Suspending or resuming from Standby mode
Suspending or resuming from Hibernate mode
To prevent the error message from occurring, update or remove the offending driver. This behavior is not limited to device drivers; it can also occur with file system filter drivers (for example, drivers installed by an anti-virus, Remote Control, or backup program). To isolate the driver that is causing the problem, use the following steps:
Check to be sure your computer and all devices are on the Hardware Compatibility List (HCL) and have WHQL signed and certified drivers. You can use Sigverif.exe to check for unsigned drivers.
Check for driver updates that may be available for your hardware.
Update software that uses filter drivers (for example, anti-virus, remote control, and backup software).
Uninstall any non-critical devices and software to help isolate the device/software that may be causing the problem.
Install Windows in a new folder. Add drivers and restart as you proceed to isolate the driver that is causing the problem.

Also disable - Allow the computer to turn device off to save power, and wake up device using device manager.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.