BSOD DRIVER_POWER_STATE_FAILURE (9f) - Windows 7 Pro

Hi,

Periodically (every day or so) my machine crashes with DRIVER_POWER_STATE_FAILURE (9f)
Below is information gathered from the dump file using WinDbg.
Any idea as to which driver could cause the problem? What could 'atapi.sys' mean?

Note: the crash also produced a 206 KB XML file with a list of all drivers on the machine. 
         Unfortunately, I can't attach this file to this message.

Thanks,
Roy.


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: 86212330, Physical Device Object of the stack
Arg3: 82b69ae0, Functional Device Object of the stack
Arg4: 8894fde0, The blocked IRP


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

DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  8894fde0
DEVICE_OBJECT: 86212330
DRIVER_OBJECT: 861f9f38
IMAGE_NAME:  atapi.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf13
MODULE_NAME: atapi
FAULTING_MODULE: 8b9d7000 atapi
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from 82b08ecf to 82b20e9c

STACK_TEXT:  
82b69a94 82b08ecf 0000009f 00000003 86212330 nt!KeBugCheckEx+0x1e
82b69b00 82b08f48 82b69bac 00000000 82b76380 nt!PopCheckIrpWatchdog+0x1f5
82b69b38 82abc019 82b846e0 00000000 2ded41b9 nt!PopCheckForIdleness+0x73
82b69b7c 82abbfbd 82b6cd20 82b69ca8 00000002 nt!KiProcessTimerDpcTable+0x50
82b69c68 82abbe7a 82b6cd20 82b69ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82b69cdc 82aba00e 01b35e58 856a3c30 82b76380 nt!KiTimerExpiration+0x25c
82b69d20 82ab9e38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82b69d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  0x9F_IMAGE_atapi.sys
BUCKET_ID:  0x9F_IMAGE_atapi.sys



 

Question Info


Last updated February 28, 2018 Views 166 Applies to:
Answer
Answer

You should only have one anti-virus programme. I counted at least four. Dump all except one.

You will need the Norton removal tool to uninstall Norton. I do recommend you remove Norton as it can cause all sorts of issues.
https://www-secure.symantec.com/norton-support/jsp/help-solutions.jsp?docid=20080710133834EN&product=home&pvid=f-home&version=1&lg=english&ct=us

I have not completed examining your dumpfile and will need to finish the task later. However, rationalising your computer security arrangements could go a long way towards solving your problems.

 

Gerry
Stourport-on-Severn, Worcestershire, England
Enquire Plan Execute

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Answer
Answer

Hi,

Results verified by WinDBG, DumpCHK, and BlueScreenView.

The Bug_Check was 9F CAUSE atapi.sys which is a Windows component.

Unfortunately the analysis did not reveal any other data than that found in
your report of the minidump and the !irp command.

As you noted BlueScreenView suggests this driver is involved in the issue.
(Pink mean involved in the issue - to toggle between ALL Drivers and Only
Driver found in the stack use OPTIONS - Lower Pane Mode OR toggle
back and forth with F6 and F7 - of course the minidump has to be highlighted
in the top part of BlueScreenView.)

pynwflt.sys dated 7/7/2010 Pylon GigE Vision Protocol Stack driver.

8dbd3000 8dbdd980   pynwflt    (deferred)            
    Image path: \SystemRoot\system32\DRIVERS\pynwflt.sys
    Image name: pynwflt.sys
    Timestamp:        Wed Jul 07 13:11:43 2010 (4C34DF7F)

1. Check with its maker's support and for updated versions. If no newer exist then
re-install the same one. Also you may need to uninstall it as a check to see if
it really is involved in the issue. It is not unusual for more than on driver to be
involved in a fault such that both (or more) need to be active for the fault to
occur.

----------

2. Use ALL the methods in the previously posted troubleshooters such as
MSCONFIG and you can add trying an elimination process with the Clean
Boot method.


A. Start - type in Search box - MSCONFIG  find at top - Right Click - RUN
AS ADMIN

General Tab - check Diagnostic Start  - APPLY / OK  -  REBOOT

Try it now. If it still blue screens think Video Driver. If not think NIC, Wifi,
Sound, or...... (and it still could be video interacting with something else).
See troubleshooter link above for my generic driver update methods.

B. How to troubleshoot a problem by performing a clean boot in Windows
Vista or Windows 7
http://support.microsoft.com/kb/929135

------------

3. Update BIOS, low level chipset drivers, and the major on-board and separate
device drivers.

BiosVersion = 4.6.3
BiosReleaseDate = 10/31/2011 <- check for updates to the BIOS, low level chipset
drivers, and the major on-board and separate device drivers.

Also run DriverView - set VIEW to Hide Microsoft drivers - update those without
Dump in their names (see driver update methods in the previously posted trouble-
shooter).

Check with Nexcom/NISE for updates to the BIOS, low level chipset drivers, and
the major on-board device drivers.

--------------

4. Remove ALL power - reseat the cards, memory, and cables (on both ends when
possible) - actually remove and replace - do not just snug.

---------------

5. Be sure to read the FaultWire link in the previously posted troubleshooter.

BCCode: 9F  0x0000009F  <-- read this link
http://www.faultwire.com/solutions-fatal_error/DRIVER-POWER-STATE-FAILURE-0x0000009F-*1167.html?order=date

----------------

6. Run DriverVerifier to see it it creates a minidump - see methods in the
previously posted troubleshooter.


Hope this helps.


Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!



 

Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.