终止代码: irql_not_less_or_equal导致的蓝屏

      想麻烦大佬帮看一下，最近笔记本经常蓝屏，用WinDBG查了dump文件提示ntkrnlmp.exe导致的问题，想请大佬帮分析一下应该怎么解决蓝屏问题。下面是dump文件的信息： Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64                     Copyright           (版权)                   (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\speedwagon\Desktop\072922-10984-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name:                     Kernel           (内核)                   base = 0xfffff800`7fe00000 PsLoadedModuleList = 0xfffff800`80a2a230                     Debug           (调试)                   session time: Fri Jul 29 16:57:12.706 2022 (UTC + 8:00) System Uptime: 0 days 0:34:18.490 Loading                     Kernel           (内核)                   Symbols ............................................................... ................................................................ ................................................................ .................................... Loading User Symbols Loading                     unloaded           (卸载)                                       module           (模块)                   list ............... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`801f8590 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff90c`bc9e67b0=000000000000000a 1: 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: fffff80080027c82, address which referenced memory                      Debugging           (调试)                   Details: ------------------   KEY_VALUES_STRING: 1      Key  : Analysis.CPU.mSec     Value: 4030      Key  : Analysis.DebugAnalysisManager     Value: Create      Key  : Analysis.Elapsed.mSec     Value: 43653      Key  : Analysis.Init.CPU.mSec     Value: 1311      Key  : Analysis.Init.Elapsed.mSec     Value: 34151      Key  : Analysis.Memory.CommitPeak.Mb     Value: 100      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:  072922-10984-01.dmp  BUGCHECK_CODE:  a  BUGCHECK_P1: 0  BUGCHECK_P2: 2  BUGCHECK_P3: 0  BUGCHECK_P4: fffff80080027c82  READ_ADDRESS: fffff80080afb390: 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: 80000002c039c788  TRAP_FRAME:  fffff90cbc9e68f0 -- (.trap 0xfffff90cbc9e68f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or                     incorrect           (错误)                  . rax=0000000000000000 rbx=0000000000000000 rcx=fffff90cbc9e65a8 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80080027c82 rsp=fffff90cbc9e6a80 rbp=ffffe080acded180  r8=0000000000000000  r9=ffffe080ad000000 r10=fffff80080a59000 r11=ffff9c8a8b1bbd80 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei pl nz na po cy nt!KeSetEvent+0x92: fffff800`80027c82 498b4500        mov     rax,qword ptr [r13] ds:00000000`00000000=???????????????? Resetting                     default           (默认)                   scope  STACK_TEXT:   fffff90c`bc9e67a8 fffff800`8020a569     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff90c`bc9e67b0 fffff800`80206869     : 00000001`ffffffff fffff800`80081595 ffff9c8a`8934f910 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff90c`bc9e68f0 fffff800`80027c82     : fffff90c`bc9e65a8 00000000`00000000 3d37f364`d74e0682 3d37f364`d74e0682 : nt!KiPageFault+0x469 fffff90c`bc9e6a80 fffff800`800273b9     : 00000000`00000000 fffff90c`bc9e6c50 00000001`00000000 ffffb400`45700000 : nt!KeSetEvent+0x92 fffff90c`bc9e6b10 fffff800`80039d20     : 80000002`c039c800 ffff9c8a`00000000 ffff9c8a`85f9b500 ffff9c8a`82e85080 : nt!IopCompleteRequest+0x389 fffff90c`bc9e6bd0 fffff800`801fc8f0     : 00000000`00000000 00000000`00000000 9c8aab58`00000000 00000000`00000000 : nt!KiDeliverApc+0x1b0 fffff90c`bc9e6c80 fffff800`800cf4a1     : 00000000`00000114 00000000`00000000 ffffb400`45700000 00000000`00000000 : nt!KiApcInterrupt+0x2f0 fffff90c`bc9e6e10 fffff800`8008a9eb     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x231 fffff90c`bc9e6fb0 fffff800`800b6e85     : 00000000`00000000 00000000`00000000 fffff90c`bc9e71f0 fffff90c`bc9e71d4 : nt!MmCheckCachedPageStates+0x17eb fffff90c`bc9e7180 fffff800`800b5e0a     : ffff9c8a`8ab4d980 00000000`1b311470 fffff90c`bc9e7378 ffff9c8a`00000000 : nt!CcMapAndCopyInToCache+0x605 fffff90c`bc9e7320 fffff800`82fb63b7     : 00000000`00000000 fffff90c`bc9e7600 ffff9c8a`8adeed28 00000000`00000000 : nt!CcCopyWriteEx+0xea fffff90c`bc9e73a0 fffff800`82fb2063     : ffff9c8a`8adeed28 ffff9c8a`8739c010 fffff90c`bc9e7640 00000000`00000000 : Ntfs!NtfsCommonWrite+0x3ee7 fffff90c`bc9e75d0 fffff800`80030d45     : ffff9c8a`89f48010 ffff9c8a`8739c010 ffff9c8a`8739c010 ffff9c8a`78c89d80 : Ntfs!NtfsFsdWrite+0x1d3 fffff90c`bc9e76a0 fffff800`7c2870cf     : fffff90c`bc9e0007 00000000`00000000 ffff9c8a`8739c010 fffff800`7c2870cf : nt!IofCallDriver+0x55 fffff90c`bc9e76e0 fffff800`7c284a03     : fffff90c`bc9e7770 00000000`00000000 00000000`00000000 fffff800`8003334e : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f fffff90c`bc9e7750 fffff800`80030d45     : ffff9c8a`8739c010 00000000`00000204 ffff9c8a`8d33b580 fffff800`80030d45 : FLTMGR!FltpDispatch+0xa3 fffff90c`bc9e77b0 fffff800`803f4118     : 00000000`00000001 ffff9c8a`8d33d650 00000000`00000001 ffff9c8a`8739c4d0 : nt!IofCallDriver+0x55 fffff90c`bc9e77f0 fffff800`803e2f9f     : ffff9c8a`00000000 fffff90c`bc9e7a80 00000000`0517de90 fffff90c`bc9e7a80 : nt!IopSynchronousServiceTail+0x1a8 fffff90c`bc9e7890 fffff800`80209fb5     : ffff9c8a`82e85080 00000000`000003a0 00000000`00000000 00000000`082aa84c : nt!NtWriteFile+0x66f fffff90c`bc9e7990 00000000`76ff1cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 00000000`0507ec38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ff1cfc   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  OS_VERSION:  10.0.19041.1  BUILDLAB_STR:  vb_release  OSPLATFORM_TYPE:  x64  OSNAME:  Windows 10  FAILURE_ID_HASH:  {c42bf4ac-5ef0-4bd6-418f-0d54b7c20876}  Followup:     MachineOwner ---------      欢迎咨询本站！。建议卸载微信。然后正常使用1-2天，看下是否恢复正常。若是恢复正常了，可以全新安装一下微信，若是全新安装后又出现了蓝屏，建议考虑该应用本身的问题。
        您好，我卸载微信后没有再蓝屏，但是重装之后再次蓝屏了，不知道是不是新版微信对于DELL电脑的不适配，请问这种情况是否有解决的办法？因为出现蓝屏也就是今年6月份才开始的，之前电脑里也安装了微信，却并没有出问题。此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。