Author Topic: Analyzing a dump file - Solved (Read 13162 times)

JohnCoool · « **on:** December 28, 2020, 12:02:39 pm »

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 · « **Reply #1 on:** December 28, 2020, 03:11:08 pm »

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 · « **Reply #2 on:** December 29, 2020, 04:22:33 am »

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 · « **Reply #3 on:** December 29, 2020, 09:51:34 am »

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 · « **Reply #4 on:** December 29, 2020, 01:45:33 pm »

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...

JohnCoool · « **Reply #5 on:** December 29, 2020, 01:46:54 pm »

I wish there was a way to ignore certain errors.

Boggin · « **Reply #6 on:** December 29, 2020, 02:14:29 pm »

You can't really ignore BSODs.

Probably best to leave the scanning until you have finished.

Is InstallGuard the only antivirus program you have installed ?

JohnCoool · « **Reply #7 on:** December 29, 2020, 02:53:40 pm »

There is nothing to do now but wait to see if there are any changes after the rollback.
InstallGuard is not an Antivirus. It is just an Administrator security program.

I have been using the same thing for over 4 years with the scanning and music and what not. That is not new at all. The only new thing is the new virtual drivers.

More information is required at this point.

What does the Tweaking.com repair program do?

Boggin · « **Reply #8 on:** December 29, 2020, 03:04:43 pm »

There is a Repair Drive Associatior but I don't know what it does or if it would resolve your problem.

BSODs are usually caused by a driver malfunction but whatever you are scanning with - it doesn't seem to like virtual drivers.

JohnCoool · « **Reply #9 on:** December 29, 2020, 03:13:58 pm »

Is there a way to use a 3rd party event viewer so that it can do better monitoring of the problem to try and pin point it?

I have 3 dump files and does not show much when I check on the internet.

Boggin · « **Reply #10 on:** December 29, 2020, 03:22:17 pm »

While I've never tried them, this article has some alternatives to the built in Event Viewer - https://windowsreport.com/best-windows-10-event-log-viewers/

The Event Log Explorer looks interesting.

JohnCoool · « **Reply #11 on:** December 29, 2020, 03:25:00 pm »

Ok Thanks. I will check it out tomorrow.

For now I want to test a game that have downloaded.

Boggin · « **Reply #12 on:** December 29, 2020, 03:28:17 pm »

Okay - I'm off to roost anyway.

Boggin · « **Reply #13 on:** December 30, 2020, 04:22:51 am »

Have you considered upgrading your Win 8.1 to Win 10 ?

I believe you can still upgrade for free by clicking on the Update now button at - https://www.microsoft.com/en-gb/software-download/windows10

You can also create Win 10 install media at the same site after reading the instructions.

JohnCoool · « **Reply #14 on:** December 30, 2020, 04:24:01 am »

Here are the current updates. In the past three days it only crashed on Monday at 6 AM and there was no scan at the time going on.

I will use the event viewer that you provided and will keep it up till next Thursday. If nothing happens by then, I will close the thread.

JohnCoool · « **Reply #15 on:** December 30, 2020, 04:26:08 am »

I know that it could be upgraded the same why I did the other one but I am not interested in Upgrading it.

I have no interest in avoiding problems.

I like to over analyze everything.

Boggin · « **Reply #16 on:** December 30, 2020, 04:30:43 am »

I've always preferred the easy way out

JohnCoool · « **Reply #17 on:** December 30, 2020, 04:33:54 am »

Ok, Please keep the easy suggestion to yourself. Last time it just annoyed me.

I will update once I have some new information.

Boggin · « **Reply #18 on:** December 30, 2020, 04:42:48 am »

Well it strikes me that if the virtual drivers are crashing in Win 8.1 but in Win 10 then the obvious solution would be to upgrade or find other drivers.

Why else have you posted on the forum if it wasn't to find a solution to your BSOD problems.

JohnCoool · « **Reply #19 on:** December 30, 2020, 04:59:57 am »

Close the thread.

I am fed up with this.

I think that you are smart and yet very very dumb.

Delete my profile too.

JohnCoool · « **Reply #20 on:** December 30, 2020, 05:14:10 am »

Delete this thread too you dummy.

Tim_Tweaking · « **Reply #21 on:** December 30, 2020, 05:35:27 am »

The next time you ask for help, we recommend you listen. All Boggin did was try and help you, but you want an answer you're happy with. It doesn't work that way. Otherwise, if you don't need help, don't ask. Windows 8.1 is right there with Vista. It's garbage, should be upgraded to Windows 10. There isn't a gamer left that would use Windows 8.

I'll be glad to delete your account so Boggin can continue to help people who WANT help.

Quote from: JohnCoool on December 30, 2020, 04:33:54 am

Ok, Please keep the easy suggestion to yourself. Last time it just annoyed me.

I will update once I have some new information.

Boggin · « **Reply #22 on:** December 30, 2020, 02:30:23 pm »

Thanks for the support, Tim.

Tim_Tweaking · « **Reply #23 on:** December 30, 2020, 05:22:22 pm »

All you do is help. If they don't want it... then what can you do. Thanks, Boggins!

Boggin · « **Reply #24 on:** December 31, 2020, 01:23:35 am »

Well I do what I can and know it is appreciated by others.

As for the OP - if he can't see that the easiest solution to this would be to upgrade to Win 10, then he's the Dummy.