Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\berka\AppData\Local\Temp\Rar$DIa2444.13441\041121-19437-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`56200000 PsLoadedModuleList = 0xfffff801`56e2a490
Debug session time: Sun Apr 11 22:56:58.365 2021 (UTC + 3:00)
System Uptime: 5 days 23:09:53.249
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..........................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`565f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`5a081160=000000000000001e
0: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8015c039283, The address that the exception occurred at
Arg3: fffff80156f27600, Parameter 0 of the exception
Arg4: fffff80156493270, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2999
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 17938
Key : Analysis.Init.CPU.mSec
Value: 500
Key : Analysis.Init.Elapsed.mSec
Value: 6029
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : Memory.System.Errors.ScrubErrors
Value: 1
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: 1e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff8015c039283
BUGCHECK_P3: fffff80156f27600
BUGCHECK_P4: fffff80156493270
EXCEPTION_PARAMETER1: fffff80156f27600
EXCEPTION_PARAMETER2: fffff80156493270
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
BAD_PAGES_DETECTED: 1
FAILED_INSTRUCTION_ADDRESS:
dxgmms2+9283
fffff801`5c039283 4885c0 test rax,rax
STACK_TEXT:
fffff801`5a081158 fffff801`566f507e : 00000000`0000001e ffffffff`c000001d fffff801`5c039283 fffff801`56f27600 : nt!KeBugCheckEx
fffff801`5a081160 fffff801`565feb0f : fffff801`566f505c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff801`5a0811a0 fffff801`5652bff7 : fffff801`5a081710 00000000`00000000 fffff801`5a06cd60 fffff801`565f97be : nt!RtlpExecuteHandlerForException+0xf
fffff801`5a0811d0 fffff801`5652abe6 : fffff801`5a06c208 fffff801`5a081e20 fffff801`5a06c208 ffffa20c`474802f0 : nt!RtlDispatchException+0x297
fffff801`5a0818f0 fffff801`565f6ae2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff801`5a081fb0 fffff801`565f6ab0 : fffff801`56607ca5 00000000`00000000 00000000`00000000 fffff801`5c072be0 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff801`5a06c0c8 fffff801`56607ca5 : 00000000`00000000 00000000`00000000 fffff801`5c072be0 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff801`5a06c0d0 fffff801`566021e9 : fffff801`5a06c338 00000000`00000008 fffff801`5a06c340 00000000`00000004 : nt!KiExceptionDispatch+0x125
fffff801`5a06c2b0 fffff801`5c039283 : ffffa20c`47435688 fffff801`5a06c540 ffffa20c`4a403bf0 ffffa20c`4a403bf0 : nt!KiInvalidOpcodeFault+0x329
fffff801`5a06c440 fffff801`5c036555 : ffffa20c`47480202 ffffa20c`46d326d0 00000000`00000001 fffff801`00000000 : dxgmms2+0x9283
fffff801`5a06c5a0 fffff801`5b213c72 : fffff801`5a06c699 00000000`00000000 fffff801`5a06cc20 0000b2ac`fdba729c : dxgmms2+0x6555
fffff801`5a06c650 fffff801`5e509bff : ffffa20c`46064030 00000000`00000000 ffffa20c`46064030 ffffa20c`464b4000 : dxgkrnl!DxgNotifyDpcCB+0x92
fffff801`5a06c700 ffffa20c`46064030 : 00000000`00000000 ffffa20c`46064030 ffffa20c`464b4000 fffff801`5e509b92 : nvlddmkm+0x79bff
fffff801`5a06c708 00000000`00000000 : ffffa20c`46064030 ffffa20c`464b4000 fffff801`5e509b92 ffffa20c`464b4000 : 0xffffa20c`46064030
SYMBOL_NAME: PAGE_NOT_ZERO
MODULE_NAME: hardware
IMAGE_NAME: hardware_ram
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x1E_c000001d
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a8d76156-cccb-e9c5-9ef7-e7392de4d97f}
Followup: MachineOwner
---------
*** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption.
