Windows 8 BSOD caused by pci.sys need help fixing

Hi Smurf,
in order to help you we need to read the dump file created when your machine blue screened. The Dump files are found in a folder marked Minidump. This folder can be found in the main Windows folder. If you can't find it or no dump files are present then you probably need to change settings so they get created:
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click and apply to exit the dialogs, then reboot for the changes to take effect.

Once you have a few dump files then read this post and it will show you what we need and how to post it:
Link Removed

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 Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\mss*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\mss*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff801`c4881000 PsLoadedModuleList = 0xfffff801`c4b57370
Debug session time: Tue Dec 9 10:41:26.255 2014 (UTC - 8:00)
System Uptime: 1 days 18:37:06.966
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe001ddbf8060, ffffd00193d2a960, ffffe001ddbd9010}

Probably caused by : pci.sys

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

6: 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: ffffe001ddbf8060, Physical Device Object of the stack
Arg3: ffffd00193d2a960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001ddbd9010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4

MODULE_NAME: pci

FAULTING_MODULE: fffff8015b367000 pci

DEFAULT_BUCKET_ID: WIN8_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: FFFFD00193D31FB0

STACK_TEXT:
ffffd001`93d2a928 fffff801`c4a8736e : 00000000`0000009f 00000000`00000003 ffffe001`ddbf8060 ffffd001`93d2a960 : nt!KeBugCheckEx
ffffd001`93d2a930 fffff801`c4a8728e : ffffe001`ddbda678 00000000`00000008 ffffe001`ddbda6b0 fffff801`c4972c19 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`93d2a990 fffff801`c48f6e67 : 00000000`00000000 ffffd001`93d2aae0 ffffe001`ddbda6b8 ffffe001`00000002 : nt!PopIrpWatchdog+0x32
ffffd001`93d2a9e0 fffff801`c49d3cea : ffffd001`93d00180 ffffd001`93d00180 ffffd001`93d0c3c0 ffffe001`e19d4480 : nt!KiRetireDpcList+0x4f7
ffffd001`93d2ac60 00000000`00000000 : ffffd001`93d2b000 ffffd001`93d25000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.3.9600.17238

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_acpi_image_pci.sys

FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

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

6: kd> lmvm pci
start end module name
fffff801`5b367000 fffff801`5b3af000 pci (pdb symbols) c:\mss\pci.pdb\8AB2DB46BB1C48778F5A8E000B9ABA642\pci.pdb
Loaded symbol image file: pci.sys
Image path: \SystemRoot\System32\drivers\pci.sys
Image name: pci.sys
Timestamp: Thu Jul 24 04:45:24 2014 (53D0F1D4)
CheckSum: 000516FC
ImageSize: 00048000
File version: 6.3.9600.17238
Product version: 6.3.9600.17238
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.3.9600.17238
FileVersion: 6.3.9600.17238 (winblue_gdr.140723-2018)
FileDescription: NT Plug and Play PCI Enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.
6: kd> lmvm pci
start end module name
fffff801`5b367000 fffff801`5b3af000 pci (pdb symbols) c:\mss\pci.pdb\8AB2DB46BB1C48778F5A8E000B9ABA642\pci.pdb
Loaded symbol image file: pci.sys
Image path: \SystemRoot\System32\drivers\pci.sys
Image name: pci.sys
Timestamp: Thu Jul 24 04:45:24 2014 (53D0F1D4)
CheckSum: 000516FC
ImageSize: 00048000
File version: 6.3.9600.17238
Product version: 6.3.9600.17238
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.3.9600.17238
FileVersion: 6.3.9600.17238 (winblue_gdr.140723-2018)
FileDescription: NT Plug and Play PCI Enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.
6: 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: ffffe001ddbf8060, Physical Device Object of the stack
Arg3: ffffd00193d2a960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001ddbd9010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4

MODULE_NAME: pci

FAULTING_MODULE: fffff8015b367000 pci

DEFAULT_BUCKET_ID: WIN8_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: FFFFD00193D31FB0

STACK_TEXT:
ffffd001`93d2a928 fffff801`c4a8736e : 00000000`0000009f 00000000`00000003 ffffe001`ddbf8060 ffffd001`93d2a960 : nt!KeBugCheckEx
ffffd001`93d2a930 fffff801`c4a8728e : ffffe001`ddbda678 00000000`00000008 ffffe001`ddbda6b0 fffff801`c4972c19 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`93d2a990 fffff801`c48f6e67 : 00000000`00000000 ffffd001`93d2aae0 ffffe001`ddbda6b8 ffffe001`00000002 : nt!PopIrpWatchdog+0x32
ffffd001`93d2a9e0 fffff801`c49d3cea : ffffd001`93d00180 ffffd001`93d00180 ffffd001`93d0c3c0 ffffe001`e19d4480 : nt!KiRetireDpcList+0x4f7
ffffd001`93d2ac60 00000000`00000000 : ffffd001`93d2b000 ffffd001`93d25000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.3.9600.17238

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_acpi_image_pci.sys

FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

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

6: kd> lmvm pci
start end module name
fffff801`5b367000 fffff801`5b3af000 pci (pdb symbols) c:\mss\pci.pdb\8AB2DB46BB1C48778F5A8E000B9ABA642\pci.pdb
Loaded symbol image file: pci.sys
Image path: \SystemRoot\System32\drivers\pci.sys
Image name: pci.sys
Timestamp: Thu Jul 24 04:45:24 2014 (53D0F1D4)
CheckSum: 000516FC
ImageSize: 00048000
File version: 6.3.9600.17238
Product version: 6.3.9600.17238
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.3.9600.17238
FileVersion: 6.3.9600.17238 (winblue_gdr.140723-2018)
FileDescription: NT Plug and Play PCI Enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.

Smurf did you read the thread I posted above? We need to see the actual dump files so we can debug them. You need to zip them up although if they are memory dumps they will be massive in size and so won't post to the forum. You need to follow my post exactly.

here is a link to the file do to the file Link Removed

I'm currently downloading the dump file but I'll ask again as I mentioned this is a memory dump. In my instructions it said change to a mini dump:

Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click and apply to exit the dialogs, then reboot for the changes to take effect.

The reason we ask to see the other types of dump file is down to speed and file size. Please don't post any further memory dumps.

I am curious to the process you used to figure out it was those drivers?

Also i should be running the newest version of bit defender just got it and auto updates

adobesmurf said:

I am curious to the process you used to figure out it was those drivers?

Click to expand...

How to read dump files:
http://support.microsoft.com/kb/315263/en-gb

Checking through your driver stack we can see that all drivers are dated 2013/2014 apart from the drivers I highlighted. Windows 8 and 8.1 dislikes older drivers and one should always upgrade to the latest version.

It's possible that even after updating the above drivers the issue continues. If that proves to be the case then we'll delve a little deeper but at present the drivers presented seems the most obvious choice.

well it worked for about a week here is the new file link

Hi,
when viewing the call stack, I can see av3.sys listed which probably means that was the cause. (A call stack is a kind list of the activity of certain subroutines just before the bsod event and will at times list the culprit).
avc3.sys Thu Sep 11 10:28:29 2014: BitDefender Active Virus Control filter driver

Bitdefender may have become corrupted and just needs re-installing but whatever the reason try removing and see if the BSOD stops. Looking through the dump file I can't see anything else that's listed that could have tripped the blue screen. I did notice Chrome was active at the time, is it updated to the latest version?

You also have another 'possible cause' although i think it's doubtful:
AiCharger.sys Fri Sep 23 03:04:40 2011: Asus Charger Driver can be a bsod cause but I saw no mention of it in the dump file unlike the above. If you desperately don't want to uninstall Bitdefender then try removing this first. If there isn't any change then you know what to try next.

Use MSE as a replacement as it's ultra stable:
http://windows.microsoft.com/en-GB/windows/security-essentials-download

Post any new dump files.

chrome is updated to the newest version. bit defender is new to the computer but a bsod had happened before i had installed it, i will try and re install it soon.

Don't forget about the other option I gave as well as that charger driver is known for causing bsod's.

sigh well still happened again i had just uninstalled the ai asus charger, but hadn't restarted the computer

Hi,
same again unfortunately.

AiCharger.sys Fri Sep 23 03:04:40 2011: Asus Charger Driver update or remove: (I know you said you removed it but just in case)
http://www.asus.com/Notebooks_Ultrabooks/G551JM/HelpDesk_Download/

ASMMAP64.sys Thu Jul 02 10:13:26 2009 :ATK0101 ACPI UTILITY please update. Found under 'ATK':
http://www.asus.com/Notebooks_Ultrabooks/G551JM/HelpDesk_Download/

In fact I notice there are several driver versions on the support page which are later than you have on the machine. It's probably a good idea to go through each section and apply the updates accordingly. (this includes the drivers found under 'Utilities' and other such sections)

If the machine still bsod's after applying the new drivers then find command prompt, right click on it and run as admin. Type:
sfc /scannow
Press enter and await results.

I will do what you said but i had this happen to me again before i read this, i believe this one may have been caused by a different source

HD-Hypervisor-amd64.sys: Hypervisor for amd64 from BlueStack Systems

My suggestions remain the same as above.... Update your drivers ....Please.

thought i had updated most of the drivers... went about a whole week without a bsod see attached also ran scannow in cmd and this came up

Hi,
still the same bugcheck I'm afraid. You also still need to update the drivers highlighted below. I've checked the support page and 2014 updates are available:

ASMMAP64.sys Thu Jul 02 10:13:26 2009: Asus ATK Hotkey ATK0101 ACPI UTILITY please update:
http://www.asus.com/Notebooks_Ultrabooks/G551JM/HelpDesk_Download/
Look under ATK.

As for the corruption found in the sfc scan try running this scan as will download files to repair corrupt ones:
Similar to the System File Checker is the DISM Tool. This will, if possible, download files to repair missing or corrupt data. Opn the admin command prompt and type:
DISM /Online /Cleanup-Image /RestoreHealth
Press enter and await results.
Be patient as it can take some time before it looks like anything is happening.

If you still get bsod after the above then it might be worth running the Driver verifier but in order to run the driver verifier you must create a system repair disk or USB drive. This is because the driver verifier will at the start of windows go through each driver and 'stress test' it which usually leads to a bsod if a driver is faulty or in need of changing. If this occurs then because of the bsod you cannot get into windows. To get round this you boot into safe mode but the trouble with 8.1 is that pressing F8 when booting will not get you into safe mode. Why they changed it I'm unsure but anyway using a recovery disk or USB drive will allow you access to the advanced boot options and eventually safe mode. Once in safe mode you can then turn off the verifier and hopefully the offending driver will have been caught in the dump files.
Here are some links to help you:

Create a system repair disk or USB drive:
http://www.howtogeek.com/131907/how...ery-drive-or-system-repair-disc-in-windows-8/
Note: You will need to change the boot order of your machine in order to use either the disk or USB drive.

This guide shows you how to turn the verifier on and off. As mentioned above, hopefully the offending driver should turn up in the dump file. If it doesn't we'll then go on to do some general testing of your components.
http://www.reviversoft.com/blog/2013/09/using-driver-verifier-to-fix-a-blue-screen-of-death/

Any problems post back.

thanks for the help but I have to ask is there a certain update process for the ATK driver i should follow i know i have updates it before?