Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Wang\Desktop\101622-14015-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 Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`33200000 PsLoadedModuleList = 0xfffff805`33e2a290 Debug session time: Sun Oct 16 02:51:15.894 2022 (UTC 8:00) System Uptime: 0 days 3:59:12.713 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ......................... Loading User Symbols Loading unloaded module list ............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805`335f8fa0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffbf0e`ae6df530=000000000000000a 14: 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: 0000000000000000, memory referenced Arg2: 00000000000000ff, IRQL Arg3: 000000000000003d, 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: fffff8053360c268, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2530 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 14817 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 546 Key : Analysis.Init.Elapsed.mSec Value: 3163 Key : Analysis.Memory.CommitPeak.Mb Value: 98 Key : Bugcheck.Code.DumpHeader Value: 0xa Key : Bugcheck.Code.Register Value: 0xa Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: 101622-14015-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: a BUGCHECK_P1: 0 BUGCHECK_P2: ff BUGCHECK_P3: 3d BUGCHECK_P4: fffff8053360c268 WRITE_ADDRESS: fffff80533efb390: 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 0000000000000000 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: ffffbf0eae6df670 -- (.trap 0xffffbf0eae6df670) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=fffff80533f25440 rdx=fffff80533f23380 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8053360c268 rsp=ffffbf0eae6df800 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000001 r11=fffff80533f23380 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl zr na po nc nt!memset 0xe8: fffff805`3360c268 c3 ret Resetting default scope STACK_TEXT: ffffbf0e`ae6df528 fffff805`3360af69 : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`0000003d : nt!KeBugCheckEx ffffbf0e`ae6df530 fffff805`33607269 : 00000000`00000000 00000000`00000000 fffff7a5`8001cd30 fffff805`3358c6db : nt!KiBugCheckDispatch 0x69 ffffbf0e`ae6df670 fffff805`3360c268 : ffffd58f`48887560 ffffbf0e`ae6dfb34 ffffbf0e`ae6dfb38 ffffbf0e`ae6dfb31 : nt!KiPageFault 0x469 ffffbf0e`ae6df800 ffffd58f`48887560 : ffffbf0e`ae6dfb34 ffffbf0e`ae6dfb38 ffffbf0e`ae6dfb31 ffffbf0e`ae6dfb60 : nt!memset 0xe8 ffffbf0e`ae6df808 ffffbf0e`ae6dfb34 : ffffbf0e`ae6dfb38 ffffbf0e`ae6dfb31 ffffbf0e`ae6dfb60 00000000`00000000 : 0xffffd58f`48887560 ffffbf0e`ae6df810 ffffbf0e`ae6dfb38 : ffffbf0e`ae6dfb31 ffffbf0e`ae6dfb60 00000000`00000000 00000000`00000000 : 0xffffbf0e`ae6dfb34 ffffbf0e`ae6df818 ffffbf0e`ae6dfb31 : ffffbf0e`ae6dfb60 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffbf0e`ae6dfb38 ffffbf0e`ae6df820 ffffbf0e`ae6dfb60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffbf0e`ae6dfb31 ffffbf0e`ae6df828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffbf0e`ae6dfb60 SYMBOL_NAME: nt!KiPageFault 469 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.2006 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 469 FAILURE_BUCKET_ID: AV_nt!KiPageFault OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ec3e2762-48ae-ffe9-5b16-fbcb853e8320} Followup: MachineOwner --------- 已持续将近一个月，各种手段用尽，均无法排除
你好，感谢联系本站！没有看到具体的错误驱动等。若是有超频，降压等，建议恢复正常，xmp也关闭。然后到电脑品牌的官网更新一下bios，覆盖安装一下所有的驱动，请勿使用第三方的驱动安装程序。完成后在Windows中执行干净启动，看下是否有好转。
