• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
Locked

‎09-01-2022 03:04 AM

HP Recommended
Product: HP Pavilion Gaming - 15-ec1007ax
Operating System: Microsoft Windows 11

this is my computer dump document analyse .I want to know what happened to my computer

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


Loading Dump File [C:\Windows\Minidump\090122-11265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`5aa00000 PsLoadedModuleList = 0xfffff801`5b6297b0
Debug session time: Thu Sep  1 15:41:02.341 2022 (UTC + 8:00)
System Uptime: 0 days 0:21:21.228
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff801`5ae1acf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8a89`f2ea77a0=000000000000009f
10: 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: ffffe384489d3de0, Physical Device Object of the stack
Arg3: ffff8a89f2ea77d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe384472384e0, The blocked IRP

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

*** WARNING: Unable to verify timestamp for amdhdaudbus.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1890

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 24107

    Key  : Analysis.Init.CPU.mSec
    Value: 1108

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2341966

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 99

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9f

    Key  : Bugcheck.Code.Register
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  090122-11265-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe384489d3de0

BUGCHECK_P3: ffff8a89f2ea77d0

BUGCHECK_P4: ffffe384472384e0

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  amdhdaudbus.sys

MODULE_NAME: amdhdaudbus

FAULTING_MODULE: fffff801a9d00000 amdhdaudbus

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff8a89`f2ea7798 fffff801`5afc2677     : 00000000`0000009f 00000000`00000003 ffffe384`489d3de0 ffff8a89`f2ea77d0 : nt!KeBugCheckEx
ffff8a89`f2ea77a0 fffff801`5afc2591     : ffffe384`4b921208 00000000`00000080 ffff8a89`f2ea7af8 ffff8a89`f2ea7af0 : nt!PopIrpWatchdogBugcheck+0xdf
ffff8a89`f2ea7810 fffff801`5acc8a94     : 00000000`00000000 00000000`00000001 ffff8a89`00000000 00000000`00000002 : nt!PopIrpWatchdog+0x31
ffff8a89`f2ea7860 fffff801`5acc7084     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`57496fc8 : nt!KiProcessExpiredTimerList+0x204
ffff8a89`f2ea7990 fffff801`5ae1ec6e     : 00000000`00000000 ffffbd01`8a5c0180 ffffbd01`8a5cc340 ffffe384`4f794080 : nt!KiRetireDpcList+0x714
ffff8a89`f2ea7c40 00000000`00000000     : ffff8a89`f2ea8000 ffff8a89`f2ea2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_RTKVHD64_IMAGE_amdhdaudbus.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {49ab50af-1e2d-ff74-9889-03389f4d62ca}

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

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1734

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1738

    Key  : Analysis.Init.CPU.mSec
    Value: 3014

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2698100

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 99

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9f

    Key  : Bugcheck.Code.Register
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  090122-11265-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe384489d3de0

BUGCHECK_P3: ffff8a89f2ea77d0

BUGCHECK_P4: ffffe384472384e0

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  amdhdaudbus.sys

MODULE_NAME: amdhdaudbus

FAULTING_MODULE: fffff801a9d00000 amdhdaudbus

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff8a89`f2ea7798 fffff801`5afc2677     : 00000000`0000009f 00000000`00000003 ffffe384`489d3de0 ffff8a89`f2ea77d0 : nt!KeBugCheckEx
ffff8a89`f2ea77a0 fffff801`5afc2591     : ffffe384`4b921208 00000000`00000080 ffff8a89`f2ea7af8 ffff8a89`f2ea7af0 : nt!PopIrpWatchdogBugcheck+0xdf
ffff8a89`f2ea7810 fffff801`5acc8a94     : 00000000`00000000 00000000`00000001 ffff8a89`00000000 00000000`00000002 : nt!PopIrpWatchdog+0x31
ffff8a89`f2ea7860 fffff801`5acc7084     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`57496fc8 : nt!KiProcessExpiredTimerList+0x204
ffff8a89`f2ea7990 fffff801`5ae1ec6e     : 00000000`00000000 ffffbd01`8a5c0180 ffffbd01`8a5cc340 ffffe384`4f794080 : nt!KiRetireDpcList+0x714
ffff8a89`f2ea7c40 00000000`00000000     : ffff8a89`f2ea8000 ffff8a89`f2ea2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_RTKVHD64_IMAGE_amdhdaudbus.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {49ab50af-1e2d-ff74-9889-03389f4d62ca}

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

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

 

3 REPLIES 3

‎09-01-2022 08:20 AM - edited ‎09-01-2022 08:27 AM

HP Recommended

Crash dumps can be best analyzed by Microsoft engineers.  Note the following discussion mirrors your "natvis" 

https://docs.microsoft.com/en-us/answers/questions/626325/windows-10-crash.html

If you ask over at Microsoft I suspect "answers.microsoft" is not the best place.  I recall they have a tech site were the engineers can answer.

 

What happened that caused you to want to do a crash dump?

For me, the Event Viewer would be more useful.  Frequently the events just before the crash as as important as the crash fault.

One should also correlate the time of the app fault with events in  "system" to get a better understanding of the problem.

 

During playing a game?

At startup of game?

Running a app such as Visual Studio, Edge, 

Are your win11 updates current?  There as a big release for my win11 yesterday (8-31-2022)

Do you have the latest Visual Studio runtime dll's?

Some older games and apps need a specific VS runtime and not the latest

Thank you for using HP products and posting to the community.
I am a community volunteer and do not work for HP. If you find
this post useful click the Yes button. If I helped solve your
problem please mark this as a solution so others can find it
1 person found this reply helpful
Was this reply helpful? Yes No

‎09-01-2022 10:02 AM

HP Recommended

thank your reply

Was this reply helpful? Yes No

‎09-01-2022 12:16 PM

HP Recommended

Hello @当代硬汉贾宝玉 

 

The error dump is caused by <AMD hd audio> module.

 

(1) Download and Install

AMD High-Definition Graphics Driver

27.20.21030.11000 Rev.H735.8 MBNov 18, 2021Download

 

(2) [ Optional ] 

Realtek High-Definition (HD) Audio Driver - Renior

6.0.9198.1 Rev.G79.5 MBSep 10, 2021Download

 

(3) Reboot and test

(4) Please report your results

Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.