Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ali\Downloads\Minidump\122121-65921-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`3e800000 PsLoadedModuleList = 0xfffff806`3f42a1b0
Debug session time: Tue Dec 21 21:55:32.410 2021 (UTC + 3:00)
System Uptime: 1 days 10:48:51.281
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
......................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`3ebf70d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa387`8e415690=000000000000007e
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8065a75a660, The address that the exception occurred at
Arg3: ffffa3878e416688, Exception Record Address
Arg4: ffffa3878e415ec0, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 5890
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 95740
Key : Analysis.Init.CPU.mSec
Value: 609
Key : Analysis.Init.Elapsed.mSec
Value: 3195
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
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: 122121-65921-01.dmp
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8065a75a660
BUGCHECK_P3: ffffa3878e416688
BUGCHECK_P4: ffffa3878e415ec0
EXCEPTION_RECORD: ffffa3878e416688 -- (.exr 0xffffa3878e416688)
ExceptionAddress: fffff8065a75a660 (nvlddmkm+0x00000000003ea660)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 00000000000003c1
Attempt to write to address 00000000000003c1
CONTEXT: ffffa3878e415ec0 -- (.cxr 0xffffa3878e415ec0)
rax=ffffbc86ebac95e0 rbx=ffffbc86eea7c000 rcx=0000000000000020
rdx=ffffa3878e416878 rsi=ffffbc86d7cbfdc0 rdi=ffffbc86ee9ce000
rip=fffff8065a75a660 rsp=ffffa3878e4168c0 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000020 r10=ffffa3878e416e20
r11=0000000000000001 r12=0000000000000004 r13=ffffbc86ed5157d0
r14=0000000000000000 r15=ffffbc86ee9d4010
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0x3ea660:
fffff806`5a75a660 664183a6c103000000 and word ptr [r14+3C1h],0 ds:002b:00000000`000003c1=????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
WRITE_ADDRESS: fffff8063f4fb390: 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
00000000000003c1
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 00000000000003c1
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffa387`8e4168c0 ffffbc86`eea7c000 : 00000000`07980000 80000000`00002000 00000000`00000000 00000000`d1755e00 : nvlddmkm+0x3ea660
ffffa387`8e4168c8 00000000`07980000 : 80000000`00002000 00000000`00000000 00000000`d1755e00 ffffbc86`eea7c008 : 0xffffbc86`eea7c000
ffffa387`8e4168d0 80000000`00002000 : 00000000`00000000 00000000`d1755e00 ffffbc86`eea7c008 00000000`00000025 : 0x7980000
ffffa387`8e4168d8 00000000`00000000 : 00000000`d1755e00 ffffbc86`eea7c008 00000000`00000025 00000000`00000036 : 0x80000000`00002000
SYMBOL_NAME: nvlddmkm+3ea660
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xffffa3878e415ec0 ; kb
BUCKET_ID_FUNC_OFFSET: 3ea660
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
Followup: MachineOwner