Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\hazar\AppData\Local\Temp\7zO46D78681\020121-31531-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:
Unable to load image WDFLDR, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WDFLDR
Debugger can not determine kernel base address
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff806`12600000 PsLoadedModuleList = 0xfffff806`12a461b0
Debug session time: Mon Feb 1 15:40:34.654 2021 (UTC + 3:00)
System Uptime: 0 days 4:31:00.380
Unable to load image WDFLDR, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WDFLDR
Debugger can not determine kernel base address
Loading Kernel Symbols
...Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
For analysis of this file, run !analyze -v
fffff806`127c3b20 ?? ???
11: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 46
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 54
Key : Analysis.Init.CPU.mSec
Value: 218
Key : Analysis.Init.Elapsed.mSec
Value: 14209
Key : Analysis.Memory.CommitPeak.Mb
Value: 45
Key : WER.CorruptModuleList
Value: 1
BUGCHECK_CODE: 139
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
TRAP_FRAME: 0000000000000000 -- (.trap 0x0)
EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffff8604`3eeb5758 fffff806`127cc55b : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff806`127c3b20
ffff8604`3eeb5760 00000000`00000139 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff806`127cc55b
ffff8604`3eeb5768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`23bca863 : 0x139
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x139
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {bec1bc00-1c8a-a417-55b2-9f8b67cbb1c5}
Followup: MachineOwner
---------
