Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\090322-9484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`71800000 PsLoadedModuleList = 0xfffff801`7242a250
Debug session time: Sat Sep 3 17:01:08.566 2022 (UTC + 8:00)
System Uptime: 0 days 0:42:25.357
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`71bf88c0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff9f86`3fcf4790=000000000000000a
15: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000000013e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80171a4a486, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1890
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3125
Key : Analysis.Init.CPU.mSec
Value: 452
Key : Analysis.Init.Elapsed.mSec
Value: 7514
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : Bugcheck.Code.DumpHeader
Value: 0xa
Key : Bugcheck.Code.Register
Value: 0xa
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 090322-9484-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: a
BUGCHECK_P1: 13e
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80171a4a486
READ_ADDRESS: fffff801724fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
000000000000013e
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: msedge.exe
DPC_STACK_BASE: FFFF9F863FCF4FB0
TRAP_FRAME: ffff9f863fcf48d0 -- (.trap 0xffff9f863fcf48d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80171a4a486 rsp=ffff9f863fcf4a60 rbp=ffffd380f2b36180
r8=0000000000000000 r9=0000000000000029 r10=0000000000000022
r11=000000000000000f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!PpmPerfSnapDeliveredPerformance+0x196:
fffff801`71a4a486 8b893c010000 mov ecx,dword ptr [rcx+13Ch] ds:00000000`0000013e=????????
Resetting default scope
STACK_TEXT:
ffff9f86`3fcf4788 fffff801`71c0a869 : 00000000`0000000a 00000000`0000013e 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff9f86`3fcf4790 fffff801`71c06b69 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9f86`3fcf48d0 fffff801`71a4a486 : 000006b6`84c91031 ffffd380`f2b36180 ffff9f86`3fcf4cb0 fffff801`71a55117 : nt!KiPageFault+0x469
ffff9f86`3fcf4a60 ffffd380`f2b3e290 : ffff8adf`d2ab56ab 00000000`00000001 00000000`00000001 fffff801`71a4a2be : nt!PpmPerfSnapDeliveredPerformance+0x196
ffff9f86`3fcf4b60 ffff8adf`d2ab56ab : 00000000`00000001 00000000`00000001 fffff801`71a4a2be 00000000`00000000 : 0xffffd380`f2b3e290
ffff9f86`3fcf4b68 00000000`00000001 : 00000000`00000001 fffff801`71a4a2be 00000000`00000000 ffff9f86`3fcf4e70 : 0xffff8adf`d2ab56ab
ffff9f86`3fcf4b70 00000000`00000001 : fffff801`71a4a2be 00000000`00000000 ffff9f86`3fcf4e70 ffffd380`f2b36180 : 0x1
ffff9f86`3fcf4b78 fffff801`71a4a2be : 00000000`00000000 ffff9f86`3fcf4e70 ffffd380`f2b36180 000006b6`84c91031 : 0x1
ffff9f86`3fcf4b80 fffff801`71a67f9e : ffffd380`f2b39240 ffffbe8d`d29f0000 00000000`00000000 ffff9f86`00000002 : nt!PpmPerfAction+0x6e
ffff9f86`3fcf4bb0 fffff801`71a67284 : ffffd380`f2b36180 fc8b49a4`00000000 00000000`00000008 00000000`00017a68 : nt!KiExecuteAllDpcs+0x30e
ffff9f86`3fcf4d20 fffff801`71bff935 : d04d89ff`0047503f ffffd380`f2b36180 00000000`00000000 00000000`00000161 : nt!KiRetireDpcList+0x1f4
ffff9f86`3fcf4fb0 fffff801`71bff720 : 00000038`1c7fd6d0 000001c5`2905fa01 ffff98e1`00000000 ffffa98c`259b0010 : nt!KxRetireDpcList+0x5
ffff9f86`47ccaad0 fffff801`71bfedee : 000001c5`3df2cc03 ffffbe8d`eaaa33e0 00000000`00000000 ffffbe8d`00000000 : nt!KiDispatchInterruptContinue
ffff9f86`47ccab00 00007ffd`4e85e2a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee
00000038`1c7fd048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`4e85e2a2
SYMBOL_NAME: nt!PpmPerfSnapDeliveredPerformance+196
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1889
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 196
FAILURE_BUCKET_ID: AV_nt!PpmPerfSnapDeliveredPerformance
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {4b2e0fc5-0fbb-ea75-827e-432f1a67615e}
Followup: MachineOwner
---------
今日产生的dump文件共享
https://1drv.ms/u/s!AqLj9akJCjFZgSKeWjFKIzONO0d_?e=aS5mY2 你好您的小型转储文件仅表明内存(RAM)损坏未列出特定驱动程序1等待看看您的系统是否稳定,如果没有,最好的选择是下载广泛可用的免费实用程序MemTest86,然后运行完整的4遍扫描以测试您的RAM是否存在物理错误2如果没有发现RAM错误,要尝试强制Windows10显示任何有故障的驱动程序,最好的选择是打开驱动程序验证程序,让你的电脑崩溃3次,然后你必须关闭驱动程序验证程序,最后,上传任何新的创建小型转储文件___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
你好,我尝试使用驱动程序验证程序管理器无法生成dump文件,关闭自动重启,进度卡在0%以下是近期产生的dump文件共享https://1drv.ms/u/s!AqLj9akJCjFZgSj0K5V9wfmfFxgF?e=j0Q3rD此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。