Main Forum > General Computer Support

Analyzing a dump file - Solved

(1/5) > >>

JohnCoool:
My system crashes sometimes when Idle. I got the tools to extract the information that is created by the BSOD but I don't understand any of it. I only understood the part of the installguard which is a program that I have had for many years.

Please check and help me understand the below details.
--------------------------------------------------------------------------

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

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5a7f3138

MODULE_NAME: pci

FAULTING_MODULE: fffff800b4c00000 pci

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  InstallGuard.e

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFD001CE146FB0

STACK_TEXT: 
ffffd001`ce146c78 fffff802`4b5fd45e : 00000000`0000009f 00000000`00000003 ffffe001`38b4a880 ffffd001`ce146cb0 : nt!KeBugCheckEx
ffffd001`ce146c80 fffff802`4b5fd37e : ffffe001`3cd97510 00000000`00000000 0000006f`0aa46f3f fffff802`4b43c70d : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`ce146ce0 fffff802`4b439a18 : 00000000`00000000 ffffd001`ce146e30 00000000`00000001 00000000`00000001 : nt!PopIrpWatchdog+0x32
ffffd001`ce146d30 fffff802`4b54c5b5 : 00000000`00000000 ffffd001`ce108180 ffffe001`374e32d0 00000000`7719311c : nt!KiRetireDpcList+0x4f8
ffffd001`ce146fb0 fffff802`4b54c3b9 : 00000000`736fed00 00000000`00010070 00000000`00000000 00000000`7eb8c000 : nt!KxRetireDpcList+0x5
ffffd000`3732bac0 fffff802`4b54ee05 : 00000000`77e51b10 fffff802`4b54aeef ffffe001`4c655080 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffd000`3732baf0 fffff802`4b54aeef : ffffe001`4c655080 00000000`00000000 00000000`00000000 ffffe001`489e6710 : nt!KiDpcInterruptBypass+0x25
ffffd000`3732bb00 00000000`77105731 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xaf
00000000`003ae4d4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77105731


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.18939

FAILURE_BUCKET_ID:  0x9F_3_igdkmd64_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_igdkmd64_IMAGE_pci.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_igdkmd64_image_pci.sys

FAILURE_ID_HASH:  {286c55ea-1207-29ac-12e0-be8aeff9a0fd}

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

1: kd> lmvm pci
start             end                 module name
fffff800`b4c00000 fffff800`b4c46000   pci        (pdb symbols)          c:\symcache\pci.pdb\50827B16BC1C47809178F1C43FFBE2E12\pci.pdb
    Loaded symbol image file: pci.sys
    Image path: \SystemRoot\System32\drivers\pci.sys
    Image name: pci.sys
    Timestamp:        Sat Feb 10 19:51:52 2018 (5A7F3138)
    CheckSum:         000490F6
    ImageSize:        00046000
    File version:     6.3.9600.18939
    Product version:  6.3.9600.18939
    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.18939
    FileVersion:      6.3.9600.18939 (winblue_ltsb.180210-0600)
    FileDescription:  NT Plug and Play PCI Enumerator
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
1: kd> lmvm pci

Boggin:
I've always used Blue Screen View to get to the nitty gritty - https://www.nirsoft.net/utils/blue_screen_view.html

The download links are at the bottom of the article,

JohnCoool:
Seems like it is a better tool than the official one provided by Microsoft.

It lead me to a program called driver verifier which puts stress on drivers until the system crashes to single it out.

I think it is my virtual Audio driver.

I will update if I know more.

Boggin:
Has it been subject to a recent driver update or can you check to see if it will update.

Could your InstallGuard have conflicted with an Audio driver update ?

Sometimes an uninstall/reinstall of programs can resolve problems.

Could you try that with InstallGuard and the Audio driver to see if that resolves the BSODs.

JohnCoool:
A few weeks ago I was having BSOD with a virtual graphics driver that allows to share display wirelessly with other machines and that was resolved after I rolled back the graphics driver.

Recently it seems that the Audio virtual driver is causing the issue. This one is being using to control a 3rbarty software that is for controlling loud and low sounds to make them more leveled. They needed to be controlled via another driver.

So you can say there too many indigents in the pot plus the software is old. It was designed for Win7. So it most probably had compatibility issues.

I also rolled back the driver on my Audio card. Lets see if it comes back.

It usually happens late at night while scanning for viruses and I usually have music playing too.

If it does not get resolved then I will have to remove it.

On WIn 10 PC that uses Realtech card it installed normally but on Win8.1 (the one that crashes) that uses Conexant card it crashes during configuration every-time and has a safemode option to bypass that problem.

It does not happen every day. It is occasional. So let's see...

Navigation

[0] Message Index

[#] Next page