BSOD 0x9F pci.sys

athanasecalydon

Reputable
Apr 1, 2015
1
0
4,510
0
Hello everyone,
I have left win 8.1 for win 7 on my computer recently and I have got BSOD right now after updated my win7 and some drivers.

It happens when I try to shutdown and even when I'm working on it.
I have search for examples and I found on this forum a similar problem but the cause isn't the same :
http://www.tomshardware.co.uk/answers/id-2158985/driver-power-state-failure-win7.html

Here is the scan I've got from windows debug tool :


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


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03298890
Debug session time: Wed Apr 1 18:49:52.547 2015 (UTC + 2:00)
System Uptime: 0 days 2:55:12.499
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004c27a10, fffff80000b9a3d8, fffffa8009fe2550}

*** ERROR: Symbol file could not be found. Defaulted to export symbols 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.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8004c27a10, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8009fe2550, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f8e000 pci

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE: FFFFF80000BA0FB0

STACK_TEXT:
fffff800`00b9a388 fffff800`03139b92 : 00000000`0000009f 00000000`00000003 fffffa80`04c27a10 fffff800`00b9a3d8 : nt!KeBugCheckEx
fffff800`00b9a390 fffff800`030d4cfc : fffff800`00b9a4d8 fffff800`00b9a4d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9a430 fffff800`030d4b96 : fffff880`06bf2990 fffff880`06bf2990 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a4a0 fffff800`030d4a7e : 00000018`79f03116 fffff800`00b9ab18 00000000`000a4851 fffff800`03248ca8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9aaf0 fffff800`030d4867 : 00000006`336499c6 00000006`000a4851 00000006`336499a3 00000000`00000051 : nt!KiTimerExpiration+0x1be
fffff800`00b9ab90 fffff800`030c0bca : fffff800`03245e80 fffff800`03253cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9ac40 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ac00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.1.7601.17514

FAILURE_BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_3_acpi_image_pci.sys

FAILURE_ID_HASH: {f949ba98-ee69-8040-f9fe-7209de5e5499}

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

I don't want to add a .sys file without being certain this is the one for my problem.
Any help is welcomed. :)
 
-I would update the BIOS or reset the BIOS to defaults and see if you can get another bugcheck.
-I would also turn off any CPU or GPU overclocking.
- change your memory dump type to kernel, reboot and when you get another bugcheck provide the kernel memory dump, it will contain more debug data to help figure out the problem. (be sure to update the BIOS or reset it to defaults first as it is a more likely cause of the problem
 
-I would update the BIOS or reset the BIOS to defaults and see if you can get another bugcheck.
-I would also turn off any CPU or GPU overclocking.
- change your memory dump type to kernel, reboot and when you get another bugcheck provide the kernel memory dump, it will contain more debug data to help figure out the problem. (be sure to update the BIOS or reset it to defaults first as it is a more likely cause of the problem
 

ASK THE COMMUNITY

TRENDING THREADS