Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081022-9062-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 = 0xfffff804`46e00000 PsLoadedModuleList = 0xfffff804`47a2a230
Debug session time: Wed Aug 10 13:05:51.129 2022 (UTC + 8:00)
System Uptime: 0 days 0:50:58.920
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`471f8590 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc001`c0ad2110=000000000000001e
14: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8044720b822, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3968
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 237245
Key : Analysis.Init.CPU.mSec
Value: 483
Key : Analysis.Init.Elapsed.mSec
Value: 83148
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
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: 081022-9062-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8044720b822
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff80447afb390: 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
ffffffffffffffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffc001`c0ad2108 fffff804`47235843 : 00000000`0000001e ffffffff`c0000005 fffff804`4720b822 00000000`00000000 : nt!KeBugCheckEx
ffffc001`c0ad2110 fffff804`4720a6ac : ffffc001`c0a80180 ffff800e`ae056dad 00000000`00000200 00000000`00000008 : nt!KiDispatchException+0x1df613
ffffc001`c0ad27d0 fffff804`472063e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffc001`c0ad29b0 fffff804`4720b822 : 00000000`00000000 fffff804`4717354a fffff7d5`400139c0 00000000`000000a5 : nt!KiGeneralProtectionFault+0x320
ffffc001`c0ad2b40 00000000`00000000 : fffff804`4717354a fffff7d5`400139c0 00000000`000000a5 ffff800e`ae05617d : nt!memset+0xa2
SYMBOL_NAME: nt!KiDispatchException+1df613
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1826
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1df613
FAILURE_BUCKET_ID: AV_R_nt!KiDispatchException
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {36796e09-312c-3519-a508-ce00ff2df497}
Followup: MachineOwner
---------
14: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8044720b822, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 302540
Key : Analysis.Init.CPU.mSec
Value: 6514
Key : Analysis.Init.Elapsed.mSec
Value: 322457
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
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: 081022-9062-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8044720b822
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffc001`c0ad2108 fffff804`47235843 : 00000000`0000001e ffffffff`c0000005 fffff804`4720b822 00000000`00000000 : nt!KeBugCheckEx
ffffc001`c0ad2110 fffff804`4720a6ac : ffffc001`c0a80180 ffff800e`ae056dad 00000000`00000200 00000000`00000008 : nt!KiDispatchException+0x1df613
ffffc001`c0ad27d0 fffff804`472063e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffc001`c0ad29b0 fffff804`4720b822 : 00000000`00000000 fffff804`4717354a fffff7d5`400139c0 00000000`000000a5 : nt!KiGeneralProtectionFault+0x320
ffffc001`c0ad2b40 00000000`00000000 : fffff804`4717354a fffff7d5`400139c0 00000000`000000a5 ffff800e`ae05617d : nt!memset+0xa2
SYMBOL_NAME: nt!KiDispatchException+1df613
MODULE_NAME: nt<365>
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1826
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1df613
FAILURE_BUCKET_ID: AV_R_nt!KiDispatchException
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {36796e09-312c-3519-a508-ce00ff2df497}
Followup: MachineOwner
--------- HiALMARK,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards你好，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，
Dyari你好，这是onedrive的共享文件https://1drv.ms/u/s!AqLj9akJCjFZgQSaoFPZH895w9fz此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
onedirve共享连接https://1drv.ms/u/s!AqLj9akJCjFZgQW6PAZllBJFX3eC?e=jG8mBTMicrosoft(R)WindowsDebuggerVersion10.0.25136.1001AMD64Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile
这是dump的共享链接https://1drv.ms/u/s!AqLj9akJCjFZgQS7UjR-s_5gdtkF此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
你好，感谢联系本站！没有看到具体错误的驱动等。建议到电脑品牌的官网更新一下bios，覆盖安装一下所有的驱动，请勿使用第三方的驱动安装程序。完成后在Windows中执行干净启动(microsoft.com)然后鼠标右键单击开始按钮（图标的按钮）→"WindowsPowerShell(I)（管理员)(A）”→输入：sfc/SCANNOW（按下Enter键）Dism/Online/Cleanup-Image/ScanHealth（按下Enter键）Dism/Online/Cleanup-Image/CheckHealth（按下Enter键）DISM/Online/Cleanup-image/RestoreHealth（按下Enter键）完成后重启电脑，再次输入：sfc/SCANNOW（按下Enter键）看下是否有好转。
微信小程序
微信扫一扫体验
投稿
微信公众账号
微信扫一扫加关注
评论 返回
顶部