DRIVER_POWER_STATE_FAILURE (9f) Pci.sys file causes BSOD

Original title: PSI system crash

 

Greetings,


I seen a similar question posted on this but a different file I believe. So first I apologize for any redundancy in questions. I have been having some system crashes. I installed WinDbg and got the info that will follow. I believe if I did it correctly that the problem is in my NT Plug and Play PCI Enumerator. I opened device manager and in the 'system devices' I found 'Plug and Play Software Enumerator'. So I did an update to the driver and the Window popped up saying that Windows determined that the driver was up to date. So am I doing something wrong or did I look at the incorrect driver? Thanks in advance for any help as I would like to keep my PC from the crashes. It has crashed each night while sleeping the last 2 nights. I had some earlier issues to which I researched the WinDbg but it was pretty crash free for a week or 2. Again thanks.

Justin

FROM WinDbg:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff801`d4e7d000 PsLoadedModuleList = 0xfffff801`d5149a20
Debug session time: Mon Jul 22 04:00:11.729 2013 (UTC - 5:00)
System Uptime: 0 days 14:51:19.500
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80041c7060, fffff801d4cda930, fffffa800773ac20}

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: fffffa80041c7060, Physical Device Object of the stack
Arg3: fffff801d4cda930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800773ac20, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ab1f

MODULE_NAME: pci

FAULTING_MODULE: fffff8800100a000 pci

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF801D4CE0FB0

STACK_TEXT:  
fffff801`d4cda8f8 fffff801`d5013722 : 00000000`0000009f 00000000`00000003 fffffa80`041c7060 fffff801`d4cda930 : nt!KeBugCheckEx
fffff801`d4cda900 fffff801`d5013755 : fffffa80`085ea070 fffff801`d4cdaa79 00000000`00000001 fffff801`d4fa10a0 : nt!PopIrpWatchdogBugcheck+0xe2
fffff801`d4cda960 fffff801`d4f001ea : fffffa80`085ea0a8 fffff801`d4cdaa79 00000000`00000001 fffff801`d4e2de3b : nt!PopIrpWatchdog+0x32
fffff801`d4cda9b0 fffff801`d4efe655 : fffff801`d5177f00 fffff801`d4effcff fffff801`d4cdabf0 fffff801`d51786a0 : nt!KiProcessExpiredTimerList+0x22a
fffff801`d4cdaae0 fffff801`d4f00668 : fffff801`d5175180 fffff801`d5177f80 00000000`00000001 00000000`001f2111 : nt!KiExpireTimerTable+0xa9
fffff801`d4cdab80 fffff801`d4effa06 : fffffa80`05e19010 fffff801`d5175180 0000001d`2f05fe66 fffff801`d4cdac8c : nt!KiTimerExpiration+0xc8
fffff801`d4cdac30 fffff801`d4f009ba : fffff801`d5175180 fffff801`d5175180 00000000`00183de0 fffff801`d51cf880 : nt!KiRetireDpcList+0x1f6
fffff801`d4cdada0 00000000`00000000 : fffff801`d4cdb000 fffff801`d4cd5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_nvmf6264_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_nvmf6264_IMAGE_pci.sys

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

0: kd> lmvm pci
start             end                 module name
fffff880`0100a000 fffff880`01047000   pci        (private pdb symbols)  c:\cache\pci.pdb\429548BF135649C9A87C6617D1481B962\pci.pdb
    Loaded symbol image file: pci.sys
    Image path: \SystemRoot\System32\drivers\pci.sys
    Image name: pci.sys
    Timestamp:        Wed Jul 25 21:27:43 2012 (5010AB1F)
    CheckSum:         00044B6F
    ImageSize:        0003D000
    File version:     6.2.9200.16384
    Product version:  6.2.9200.16384
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     pci.sys
    OriginalFilename: pci.sys
    ProductVersion:   6.2.9200.16384
    FileVersion:      6.2.9200.16384 (win8_rtm.120725-1247)
    FileDescription:  NT Plug and Play PCI Enumerator
    LegalCopyright:   © Microsoft Corporation. All rights reserved.


|

Hi Justin,

 

Thank you providing the detailed error report.

 

From the error report, it appears that the pci.sys file is causing the error "Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE"

 

This bug check indicates that the driver is in an inconsistent or invalid power state.

 

I would have you run the Verifier to check if there is an unsigned driver that could be causing this issue.

 

- In the Search charms, type Command Prompt, right click on it and select Run as Administrator.

- In the command prompt, type Verifier and hit enter.

- Click on Create Standard Settings and click on Next.

- Then select the drivers to be verified.  Try the 4 options provided. First for the unsigned drivers and then for the signed drivers. Also try to verify the PCI.SYS driver using the last option and check.

 

 For more info: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329(v=vs.85).aspx

 

 

Visit the computer manufacturer websites and download/install the chipset drivers, update the BIOS and the other major on-board and separate device drivers. Installing the updated drivers might help you fix this BSOD errors.

 

Hope this information is helpful. If you have any concerns, please do let us know.

 

Microsoft Desktop Support Engineer

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

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

How satisfied are you with this reply?

Thanks for your feedback.

Also, the error points to the nvmf6264.sys:

 

BUCKET_ID:  0x9F_3_nvmf6264_IMAGE_pci.sys

 

The nvmf6264.sys is the NVIDIA NIC driver.

 

This error is also sometimes caused by third party firewall drivers.

 

Are you able to provide a couple of minidump files via Windows Live SkyDrive or similar site?

 

 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

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

How satisfied are you with this reply?

Thanks for your feedback.

Thanks you two for the replies. Sorry for the delay of responding but with class and work been a hectic week. I am starting on what Kevin posted. As for the minidump I have not don that or done anything with Windows Live SkyDrive or a similar site. I would be willing to give it a go.

JP

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

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

How satisfied are you with this reply?

Thanks for your feedback.

As for the minidump I have not don that or done anything with Windows Live SkyDrive or a similar site. I would be willing to give it a go.

Here are some steps for providing the minidump files:


First create a folder on the Desktop and call it Minidumps

 

Then open the C:\Windows\Minidump folder and do the following:

 

Home > Select all > Home > Copy to > Choose location > Minidumps > Copy

 

Then right-click the Minidumps folder > Send to > Compressed (zipped) folder.

 

Then upload the newly created compressed (zipped) folder to Windows Live SkyDrive or similar site and then provide a link here.

 

If you are using Windows Live SkyDrive make sure the minidump files are in a "public folder" "shared with everyone":

 

Right-click the folder with the minidump files > Sharing > Get a link > Make Public

 

Then copy and paste the link here.



Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

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

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated June 28, 2020 Views 7,589 Applies to: