Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\31828\Desktop\082021-12125-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`42e00000 PsLoadedModuleList = 0xfffff801`43a2a190
Debug session time: Fri Aug 20 19:33:13.178 2021 (UTC + 8:00)
System Uptime: 2 days 3:50:51.636
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`431f71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff950b`7473f670=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: 0000000000000058, 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: fffff801430db5f2, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5250
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 282057
Key : Analysis.Init.CPU.mSec
Value: 1093
Key : Analysis.Init.Elapsed.mSec
Value: 503072
Key : Analysis.Memory.CommitPeak.Mb
Value: 89
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
BUGCHECK_CODE: a
BUGCHECK_P1: 58
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff801430db5f2
READ_ADDRESS: fffff80143afa390: 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
0000000000000058
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffff950b7473f7b0 -- (.trap 0xffff950b7473f7b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffffffffffffff80
rdx=0000000000000370 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801430db5f2 rsp=ffff950b7473f940 rbp=0000000000000000
r8=ffffcd059e500ba0 r9=0000000000000000 r10=ffffcd057d002160
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!RtlpHpSegContextCompact+0x72:
fffff801`430db5f2 f6431801 test byte ptr [rbx+18h],1 ds:00000000`00000018=??
Resetting default scope
STACK_TEXT:
ffff950b`7473f668 fffff801`43209169 : 00000000`0000000a 00000000`00000058 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff950b`7473f670 fffff801`43205469 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff950b`7473f7b0 fffff801`430db5f2 : ffffcd05`84800760 00000000`00000062 ffffcd05`84800760 ffffcd05`7d002340 : nt!KiPageFault+0x469
ffff950b`7473f940 fffff801`430db558 : ffffcd05`7d002000 ffffcd05`7d002000 ffffcd05`7d002280 ffffcd05`7d002280 : nt!RtlpHpSegContextCompact+0x72
ffff950b`7473f9b0 fffff801`43053777 : 00000000`00000001 ffffcd05`7d002000 ffffcd05`7d002000 ffffcd05`8b66e260 : nt!RtlpHpHeapCompact+0x84
ffff950b`7473f9e0 fffff801`430b8505 : 00000000`00000001 fffff801`0000003f ffffcd05`00000000 00000000`00000000 : nt!ExpHpCompactionRoutine+0x207
ffff950b`7473fa70 fffff801`43155845 : ffffcd05`abde8040 00000000`00000080 ffffcd05`7d6bc180 00000000`00000001 : nt!ExpWorkerThread+0x105
ffff950b`7473fb10 fffff801`431fe828 : ffffbd01`a518e180 ffffcd05`abde8040 fffff801`431557f0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff950b`7473fb60 00000000`00000000 : ffff950b`74740000 ffff950b`74739000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!RtlpHpSegContextCompact+72
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1165
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 72
FAILURE_BUCKET_ID: AV_nt!RtlpHpSegContextCompact
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3ed2d1f7-0e0e-b0bc-b6ae-ea2c9c8be089}
Followup: MachineOwner
--------- HiIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,Icannotdownloadfrompan.baidu,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
https://1drv.ms/u/s!AuIMPaz4pacRj3cejMF_P9E4gzkC?e=Lh****此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
你好,关于dump文件的共享链接发给你了,可能是防火墙问题,我无法访问这条共享链接,所以我不知道你是否可以访问并下载文件此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
Yourminidumpfilejustindicatesmemory(RAM)corruptionnospecificdriverislistedGotothesupportpageforyourPCorMotherboardonthemanufacturerswebsite,thenfromthere,downloadandinstalltheversionofChipsetdriverstheyrecommendandwhilethere,checkforanyBIOSupdatethatmayneedtobeinstalledWaittoseeifyoursystemstabilizes,ifnot,thebestoptionistodownloadthewidelyavailablefreeutilityMemTest86,thenrunafull4passscanwiththattotestyourRAMforphysicalerrors此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。