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: fffff80378027c82, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2765 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 18993 Key : Analysis.Init.CPU.mSec Value: 624 Key : Analysis.Init.Elapsed.mSec Value: 24010 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: 080322-11453-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: a BUGCHECK_P1: 0 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff80378027c82 READ_ADDRESS: fffff80378afb390: 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: 800000021d208788 TRAP_FRAME: ffff810e001868f0 -- (.trap 0xffff810e001868f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=ffff810e001865a8 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80378027c82 rsp=ffff810e00186a80 rbp=ffffdd018b19d180 r8=0000000000000000 r9=ffffdd018b1c0000 r10=fffff80378a59000 r11=ffff9f84f9c7a000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po cy nt!KeSetEvent 0x92: fffff803`78027c82 498b4500 mov rax,qword ptr [r13] ds:00000000`00000000=???????????????? Resetting default scope STACK_TEXT: ffff810e`001867a8 fffff803`7820a569 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffff810e`001867b0 fffff803`78206869 : 00000001`ffffffff fffff803`78081595 ffff9f85`03c07c40 00000000`00000000 : nt!KiBugCheckDispatch 0x69 ffff810e`001868f0 fffff803`78027c82 : ffff810e`001865a8 00000000`00000000 3d37f364`d74e0682 3d37f364`d74e0682 : nt!KiPageFault 0x469 ffff810e`00186a80 fffff803`780273b9 : 00000000`00000000 ffff810e`00186c50 00000001`00000000 ffff8d07`650c0000 : nt!KeSetEvent 0x92 ffff810e`00186b10 fffff803`78039d20 : 80000002`1d208800 ffff9f84`00000000 ffff9f84`f66dd500 ffff9f84`f1196080 : nt!IopCompleteRequest 0x389 ffff810e`00186bd0 fffff803`781fc8f0 : 00000000`00000000 00000000`00000000 9f84f561`00000000 00000000`00000000 : nt!KiDeliverApc 0x1b0 ffff810e`00186c80 fffff803`780cf4a1 : 00000000`00000114 00000000`00000000 ffff8d07`650c0000 00000000`00000000 : nt!KiApcInterrupt 0x2f0 ffff810e`00186e10 fffff803`7808a9eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault 0x231 ffff810e`00186fb0 fffff803`780b6e85 : 00000000`00000000 00000000`00000000 ffff810e`001871f0 ffff810e`001871d4 : nt!MmCheckCachedPageStates 0x17eb ffff810e`00187180 fffff803`780b5e0a : ffff9f84`f5a6fd90 00000000`14bea6d8 ffff810e`00187378 ffff9f84`00000000 : nt!CcMapAndCopyInToCache 0x605 ffff810e`00187320 fffff803`7bdc63b7 : 00000000`00000000 ffff810e`00187600 ffff9f84`f5fbbd68 00000000`00000000 : nt!CcCopyWriteEx 0xea ffff810e`001873a0 fffff803`7bdc2063 : ffff9f84`f5fbbd68 ffff9f85`03d91a20 ffff810e`00187640 00000000`00000000 : Ntfs!NtfsCommonWrite 0x3ee7 ffff810e`001875d0 fffff803`78030d45 : ffff9f84`f1506420 ffff9f85`03d91a20 ffff9f85`03d91a20 ffff9f84`ec4d8da0 : Ntfs!NtfsFsdWrite 0x1d3 ffff810e`001876a0 fffff803`750970cf : ffff810e`00180008 00000000`00000000 ffff9f85`03d91a20 fffff803`750970cf : nt!IofCallDriver 0x55 ffff810e`001876e0 fffff803`75094a03 : ffff810e`00187770 00000000`00000000 00000000`00000000 fffff803`7803334e : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted 0x28f ffff810e`00187750 fffff803`78030d45 : ffff9f85`03d91a20 00000000`00000204 ffff9f84`f576c790 fffff803`78030d45 : FLTMGR!FltpDispatch 0xa3 ffff810e`001877b0 fffff803`783f4118 : 00000000`00000001 ffff9f84`f576d5a0 00000000`00000001 ffff9f85`03d91e50 : nt!IofCallDriver 0x55 ffff810e`001877f0 fffff803`783e2f9f : ffff9f84`00000000 ffff810e`00187a80 00000000`1172e13c ffff810e`00187a80 : nt!IopSynchronousServiceTail 0x1a8 ffff810e`00187890 fffff803`78209fb5 : ffff9f84`f1196080 00000000`000011fc 00000000`00000000 00000000`13f4bd9c : nt!NtWriteFile 0x66f ffff810e`00187990 00000000`77181cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd 0x25 00000000`04d4eee8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77181cfc 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 --------- 求问这是怎么回事!!经常蓝屏

你好泽宇保罗,来帮助你解决你的问题的。minidump文件没有命名任何驱动程序。它只表示一个系统内核驱动程序“ntkrnlmp.exe”。由于它是一个系统文件,这意味着其他东西导致它出现故障。它可以是硬件、软件或驱动程序。需要做进一步的分析。如果您有其他小型转储文件,您可以上传吗?1.打开Windows文件资源管理器2.转到C:\Windows\Minidump3.压缩这些文件4.将zip文件上传到云端(OneDriveDropBox.等)。5.然后在这里分享链接。谢谢。此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


你好Paul,Minidump文件链接:https://1drv.ms/u/s!Asay3ElbiOcYiw4kV-FuUxbK7N5S此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


你好,minidump文件仍然指向“ntkrnlmp.exe”。我建议您运行驱动程序验证程序来查找任何行为不端、损坏或过时的驱动程序。按照本文中的说明进行操作。https://www.tenforums.com/tutorials/5470-enable.提醒:=>48小时后或收到BSOD后禁用驱动程序验证程序。=>在运行驱动程序验证程序之前创建一个还原点。收到BSOD错误后共享minidump文件。


点赞(89) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部