我的win10系统这两天一直蓝屏，我将dmp文件放入WINDbg查看显示如下 Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\072122-61812-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff807`5cc00000 PsLoadedModuleList = 0xfffff807`5d82a230 Debug session time: Thu Jul 21 18:02:02.278 2022 (UTC 8:00) System Uptime: 0 days 3:27:33.191 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 -v nt!KeBugCheckEx: fffff807`5cff8590 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffff8502`a63e68b0=000000000000000a 4: 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: 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: fffff8075ce27c82, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 15202 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 28888 Key : Analysis.Init.CPU.mSec Value: 2405 Key : Analysis.Init.Elapsed.mSec Value: 194983 Key : Analysis.Memory.CommitPeak.Mb Value: 100 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: 072122-61812-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: a BUGCHECK_P1: 0 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8075ce27c82 READ_ADDRESS: fffff8075d8fb390: 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 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: WeChat.exe IRP_ADDRESS: 800000021760d788 TRAP_FRAME: ffff8502a63e69f0 -- (.trap 0xffff8502a63e69f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=ffff8502a63e66a8 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8075ce27c82 rsp=ffff8502a63e6b80 rbp=ffffa200a2d84180 r8=0000000000000000 r9=ffffa200a2dc0000 r10=fffff8075d859000 r11=ffff920c3a3f6c60 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po cy nt!KeSetEvent 0x92: fffff807`5ce27c82 498b4500 mov rax,qword ptr [r13] ds:00000000`00000000=???????????????? Resetting default scope STACK_TEXT: ffff8502`a63e68a8 fffff807`5d00a569 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffff8502`a63e68b0 fffff807`5d006869 : 00000001`ffffffff fffff807`5ce81595 ffff920c`382543f8 00000000`00000000 : nt!KiBugCheckDispatch 0x69 ffff8502`a63e69f0 fffff807`5ce27c82 : ffff8502`a63e66a8 00000000`00000000 3d37f364`d74e0682 3d37f364`d74e0682 : nt!KiPageFault 0x469 ffff8502`a63e6b80 fffff807`5ce273b9 : 00000000`00000000 ffff8502`a63e6d50 00000001`00000000 ffffd480`a6040000 : nt!KeSetEvent 0x92 ffff8502`a63e6c10 fffff807`5ce39d20 : 80000002`1760d800 ffff920c`00000000 ffff920c`39d68000 ffff920c`39ef0080 : nt!IopCompleteRequest 0x389 ffff8502`a63e6cd0 fffff807`5cffc8f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc 0x1b0 ffff8502`a63e6d80 fffff807`5cecf4a1 : 00000000`00000114 00000000`00000000 ffffd480`a6040000 00000000`00000000 : nt!KiApcInterrupt 0x2f0 ffff8502`a63e6f10 fffff807`5ce8a9eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault 0x231 ffff8502`a63e70b0 fffff807`5ceb6e85 : 00000000`00000000 00000000`00000000 ffff8502`a63e72f0 ffff8502`a63e72d4 : nt!MmCheckCachedPageStates 0x17eb ffff8502`a63e7280 fffff807`5ceb5e0a : ffff920c`38543c70 00000000`15b65198 ffff8502`a63e7478 ffff920c`00000000 : nt!CcMapAndCopyInToCache 0x605 ffff8502`a63e7420 fffff807`5f5d63b7 : 00000000`00000000 ffff8502`a63e7700 ffff920c`34e4a738 00000000`00000000 : nt!CcCopyWriteEx 0xea ffff8502`a63e74a0 fffff807`5f5d2063 : ffff920c`34e4a738 ffff920c`39ac7010 ffff8502`a63e7740 00000000`00000000 : Ntfs!NtfsCommonWrite 0x3ee7 ffff8502`a63e76d0 fffff807`5ce30d45 : ffff920c`3af9fa20 ffff920c`39ac7010 ffff920c`39ac7010 ffff920c`2f5c5520 : Ntfs!NtfsFsdWrite 0x1d3 ffff8502`a63e77a0 fffff807`591b70cf : ffff8502`a63e0007 00000000`00000000 ffff920c`39ac7010 fffff807`591b70cf : nt!IofCallDriver 0x55 ffff8502`a63e77e0 fffff807`591b4a03 : ffff8502`a63e7870 00000000`00000000 00000000`00000000 fffff807`5ce3334e : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted 0x28f ffff8502`a63e7850 fffff807`5ce30d45 : ffff920c`39ac7010 00000000`00000204 ffff920c`3661aa10 fffff807`5ce30d45 : FLTMGR!FltpDispatch 0xa3 ffff8502`a63e78b0 fffff807`5d1f4118 : 00000000`00000001 ffff920c`3661ad30 00000000`00000001 ffff920c`39ac7488 : nt!IofCallDriver 0x55 ffff8502`a63e78f0 fffff807`5d1e2f9f : ffff920c`00000000 ffff8502`a63e7b80 00000000`0d65dff8 ffff8502`a63e7b80 : nt!IopSynchronousServiceTail 0x1a8 ffff8502`a63e7990 fffff807`5d009fb8 : ffff920c`39ef0080 00000000`000007b8 00000000`00000000 00000000`156c0c3c : nt!NtWriteFile 0x66f ffff8502`a63e7a90 00000000`76f81cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd 0x28 00000000`0bcaed68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f81cfc SYMBOL_NAME: nt!KeSetEvent 92 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1826 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 92 FAILURE_BUCKET_ID: AV_nt!KeSetEvent OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {c42bf4ac-5ef0-4bd6-418f-0d54b7c20876} Followup: MachineOwner 希望有朋友能帮我解答一下，十分感谢
欢迎咨询本站！。建议卸载一下微信。（正常使用1-2天）看下是否恢复正常。若是恢复正常，可以再次安装一下该应用，若是全新安装后有出现了蓝屏，建议考虑该应用本身的问题。
