windbg dmp文件

Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\999\技术支持\jj\072524-12328-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`2ce00000 PsLoadedModuleList = 0xfffff806`2da2a360
Debug session time: Wed Jul 24 21:04:00.490 2024 (UTC + 8:00)
System Uptime: 0 days 12:01:52.660
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffff9909ea1c5c80, ffff8785b2e4f150, ffff9909c925d990}

Implicit thread is now ffff9909`b8c90080
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

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

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

Implicit thread is now ffff9909`b8c90080

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  Precision 7560

SYSTEM_SKU:  0A69

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  1.8.0

BIOS_DATE:  01/07/2022

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  0G01WF

BASEBOARD_VERSION:  A01

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: ffff9909ea1c5c80

BUGCHECK_P3: ffff8785b2e4f150

BUGCHECK_P4: ffff9909c925d990

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  b8c90080

CPU_COUNT: 10

CPU_MHZ: 9c0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8d

CPU_STEPPING: 1

CPU_MICROCODE: 6,8d,1,0 (F,M,S,R)  SIG: 3E'00000000 (cache) 3E'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  LAPTOP-RQ246RBE

ANALYSIS_SESSION_TIME:  07-25-2024 19:45:10.0398

ANALYSIS_VERSION: 10.0.15063.468 x86fre

LAST_CONTROL_TRANSFER:  from fffff8062d038a30 to fffff8062d206146

STACK_TEXT:  
ffff8785`b95367c0 fffff806`2d038a30 : ffffa980`82de8180 00000000`ffffffff ffff2d5a`b2acc258 00000000`00000000 : nt!KiSwapContext+0x76
ffff8785`b9536900 fffff806`2d037f5f : 20004001`00000001 ffff9909`0000000f ffff8785`b9536ac0 ffff9909`00000000 : nt!KiSwapThread+0x500
ffff8785`b95369b0 fffff806`2d037803 : ffff9909`00000018 00000000`00000000 00000000`00000000 ffff9909`b8c901c0 : nt!KiCommitThreadWait+0x14f
ffff8785`b9536a50 fffff806`64c2fba3 : ffff9909`ce5ec700 ffff9909`00000000 fffff806`64c5ed00 000066f6`10146500 : nt!KeWaitForSingleObject+0x233
ffff8785`b9536b40 fffff806`64c185e2 : ffff9909`ce5ec0d0 ffff8785`b9536c29 00000000`00000005 ffffffff`dc3cba00 : UsbHub3!HUBMISC_WaitForSignal+0xff
ffff8785`b9536bb0 fffff806`2e7c8bff : 00000000`00000000 ffff9909`eda517f8 00000000`00000005 ffff9909`efeb9a30 : UsbHub3!HUBPDO_EvtDeviceD0Exit+0x322
ffff8785`b9536c90 fffff806`2e7c0a31 : ffff9909`eda517f8 ffff8785`b9536db0 00000000`00000000 00000000`00000001 : Wdf01000!FxPnpDeviceD0Exit::InvokeClient+0x2f [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 285]
ffff8785`b9536cf0 fffff806`2e7cc4f5 : 00000000`00000000 00000000`00000000 00000000`00000005 ffff9909`eda51280 : Wdf01000!FxPrePostCallback::InvokeStateless+0x2d [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 408]
ffff8785`b9536d20 fffff806`2e7c119b : 00000000`00000000 ffff8785`b9536ec0 00000000`00000380 00000000`00000000 : Wdf01000!FxPkgPnp::PowerGotoDxIoStoppedCommon+0x169 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3100]
ffff8785`b9536d90 fffff806`2e7c2546 : 00000000`0000031c 00000000`00000b20 ffff9909`eda51280 00000000`00000359 : Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0xb [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 2842]
ffff8785`b9536dc0 fffff806`2e7c22fa : 00000000`00000000 ffff9909`eda51280 ffff9909`eda51280 ffff9909`97102060 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x156 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699]
ffff8785`b9536f20 fffff806`2e7c1741 : ffff9909`eda51280 00000000`00000000 00000000`00000002 fffff806`2e7c0f00 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xea [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1615]
ffff8785`b9536fa0 fffff806`2e7c0001 : 00000000`00000000 ffff9909`eda51280 00000000`00000001 ffff9909`efeb9ba0 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d1 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1394]
ffff8785`b9537030 fffff806`2e7bfeb5 : ffff9909`eda51280 ffff9909`efeb9a30 00000000`00000004 00000000`00000000 : Wdf01000!FxPkgPdo::DispatchDeviceSetPower+0x51 [minkernel\wdf\framework\shared\irphandlers\pnp\pdopower.cpp @ 208]
ffff8785`b9537080 fffff806`2e7bcd00 : ffff9909`eda51280 ffff9909`efeb9a30 ffff9909`970e5640 fffff806`2d19898e : Wdf01000!FxPkgPdo::_DispatchSetPower+0x25 [minkernel\wdf\framework\shared\irphandlers\pnp\pdopower.cpp @ 89]
ffff8785`b95370b0 fffff806`2e7c3674 : ffff9909`c925d990 ffff9909`efeb9ba0 00000000`00000005 ffff9909`c925dd30 : Wdf01000!FxPkgPnp::Dispatch+0xb0 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
ffff8785`b9537120 fffff806`2e7c3604 : ffff9909`c925d990 ffff9909`efeb9ba0 ffff9909`efeb9a30 fffff806`64c01c30 : Wdf01000!DispatchWorker+0x54 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1592]
ffff8785`b9537150 fffff806`2e7c3785 : ffff9909`a0be4de0 ffff9909`ce5ec0d0 ffff9909`c925d990 00000000`00000000 : Wdf01000!FxDevice::DispatchPreprocessedIrp+0x88 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1654]
ffff8785`b9537190 fffff806`64c1660d : ffff9909`efeb9a30 ffff9909`c925d990 000066f6`101465c8 fffff806`2d17cbf2 : Wdf01000!imp_WdfDeviceWdmDispatchPreprocessedIrp+0x65 [minkernel\wdf\framework\shared\core\km\fxdeviceapikm.cpp @ 258]
ffff8785`b95371d0 fffff806`2e7baa17 : ffff9909`c925d990 00000000`00000016 ffff9909`efeb9a30 ffff9909`ef796410 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPnPPowerPreprocess+0x42d
ffff8785`b9537220 fffff806`2d1986cf : fffff806`4c8d8008 ffff9909`eb6c50a0 00000000`00000016 ffff9909`c925d990 : Wdf01000!FxDevice::DispatchWithLock+0x267 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffff8785`b9537280 fffff806`2d02d40d : 00000000`00000000 00000000`00000000 fffff806`4c8d1918 ffff9909`eb6c51f0 : nt!IopPoHandleIrp+0x3b
ffff8785`b95372b0 fffff806`2d19a959 : fffff806`4c8d8008 fffff806`4c8b4ebe 00000000`00000016 ffff9909`eb6c50a0 : nt!IofCallDriver+0x6d
ffff8785`b95372f0 fffff806`65022a8b : ffff9909`c925d990 00000000`00000002 ffff9909`eb6c51f0 00000000`00000004 : nt!IoCallDriver+0x9
ffff8785`b9537320 fffff806`4c8b443d : ffff9909`eb6c5210 ffff9909`eb6c51f0 ffff9909`c925ddc0 ffff9909`c925d990 : hidusb!HumPower+0xab
ffff8785`b9537360 fffff806`4c8b26c6 : ffff9909`eb6c51f0 00000000`00000000 00000000`00000016 fffff806`2d19cda6 : HIDCLASS!HidpFdoPower+0x4bd
ffff8785`b95373e0 fffff806`2d19cb79 : ffff8785`b95374f0 ffff9909`b8c90080 ffff9909`c925d990 ffff9909`00000001 : HIDCLASS!HidpMajorHandler+0x206
ffff8785`b9537470 fffff806`2d148da5 : ffffffff`fa0a1f00 fffff806`2d19c9a0 ffff9909`a931d2f0 00000000`000000dd : nt!PopIrpWorker+0x1d9
ffff8785`b9537510 fffff806`2d206b58 : ffffa980`83152180 ffff9909`b8c90080 fffff806`2d148d50 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8785`b9537560 00000000`00000000 : ffff8785`b9538000 ffff8785`b9531000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


STACK_COMMAND:  .thread 0xffff9909b8c90080 ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Wdf01000
    fffff8062e7ba7fb-fffff8062e7ba7fc  2 bytes - Wdf01000!FxDevice::DispatchWithLock+4b
    [ 48 ff:4c 8b ]
    fffff8062e7ba802-fffff8062e7ba806  5 bytes - Wdf01000!FxDevice::DispatchWithLock+52 (+0x07)
    [ 0f 1f 44 00 00:e8 b9 73 90 fe ]
    fffff8062e7ba85f-fffff8062e7ba860  2 bytes - Wdf01000!FxDevice::DispatchWithLock+af (+0x5d)
    [ 48 ff:4c 8b ]
    fffff8062e7ba866-fffff8062e7ba86a  5 bytes - Wdf01000!FxDevice::DispatchWithLock+b6 (+0x07)
    [ 0f 1f 44 00 00:e8 45 ba 98 fe ]
14 errors : !Wdf01000 (fffff8062e7ba7fb-fffff8062e7ba86a)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2024-07-24T13:04:00.000Z

OSBUILD:  19041

OSSERVICEPACK:  4522

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  191206-1406

BUILDLAB_STR:  vb_release

BUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406

ANALYSIS_SESSION_ELAPSED_TIME:  2bba

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corr

1. WinDbg：WinDbg 是一个强大的调试工具，用于分析和调试 Windows 操作系统和应用程序。你可以下载并安装 WindDbg，然后打开 .dmp 文件进行分析。

2. 打开 .dmp 文件：使用 WinDbg 打开 .dmp 文件，通过 File -> Open Crash Dump 或者通过命令行 windbg.exe -z <path-to-dmp-file> 打开 .dmp 文件。

3. 执行符号加载：在 WinDbg 中执行符号加载，以确保能够正确解析和显示调试信息。你可以使用以下命令进行符号加载：

   |

4. .symfix ; 尝试从 Microsoft 符号服务器加载符号
   .reload ; 重新加载所有模块的符号
   

5. 分析堆栈信息：在 WinDbg 中使用 !analyze -v 命令，以自动分析堆栈信息并生成相应的调试报告。这将帮助你了解异常发生的位置、调用栈和相关模块的信息。

6. 手动分析：如果自动分析无法提供足够的信息，你可以手动分析堆栈和内存信息。通过以下命令来查看堆栈：

   |

7. k ; 查看当前堆栈
   u <address> ; 查看特定地址的代码信息
   

8. 查找内存损坏点：根据堆栈信息和代码分析，可以尝试定位到可能的内存损坏点。这可能涉及到对代码的仔细审查，查找可能的内存越界访问、空指针解引用或者内存泄漏等问题。

9. 修复问题：一旦定位到内存损坏的点，你可以对代码进行修复。这可能包括修复程序中的越界访问、内存释放问题或者修复其他引发内存损坏的原因。

uption
---------