KMODE_EXCEPTION_NOT_HANDLED

Evet bu hatayı bir sürü bilgisayarcı gezdim. Eskiden farklı kodlarda bir sürü mavi ekran hatası sıklıkla alıyordum ancak bir bilgisayarcı HDD değişimi yaptıktan sonra geçeceğini söyledi ve değiştirdik. Sonrasında hata hala veriyor ancak tek bir hata olarak veriyor. KMODE_EXCEPTION_NOT_HANDLED ayrıca ilgilenebilecekler için.

Minidump:Minidump - Google Drive
C:\Windows\system32>sfc /scannow



Beginning system scan. This process will take some time.



Beginning verification phase of system scan.

Verification 100% complete.



Windows Resource Protection found corrupt files and successfully repaired them.

For online repairs, details are included in the CBS log file located at

windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline

repairs, details are included in the log file provided by the /OFFLOGFILE flag.

1.Minidump:
nt!KeBugCheckEx:
fffff803`2c7fc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff870e`d6900060=000000000000001e
3: 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: fffffc8deb4763a6, 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: 4733

Key : Analysis.Elapsed.mSec
Value: 6221

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 546

Key : Analysis.Init.Elapsed.mSec
Value: 3577

Key : Analysis.Memory.CommitPeak.Mb
Value: 92

Key : Bugcheck.Code.LegacyAPI
Value: 0x1e

Key : Failure.Bucket
Value: AV_R_win32kbase!NtDCompositionBeginFrame

Key : Failure.Hash
Value: {05267455-18cd-2ae4-0687-d1c2a6d58788}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffffc8deb4763a6

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB: 071923-5328-01.dmp

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: fffff8032d0fb390: 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: dwm.exe

STACK_TEXT:
ffff870e`d6900058 fffff803`2c860d23 : 00000000`0000001e ffffffff`c0000005 fffffc8d`eb4763a6 00000000`00000000 : nt!KeBugCheckEx
ffff870e`d6900060 fffff803`2c81026c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1793a3
ffff870e`d6900720 fffff803`2c80b85a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffff870e`d6900900 fffffc8d`eb4763a6 : 00000000`00000000 ffffc002`17e830b0 ffffffff`fd050f80 00000000`00000000 : nt!KiGeneralProtectionFault+0x31a
ffff870e`d6900a98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!NtDCompositionBeginFrame+0x26


SYMBOL_NAME: win32kbase!NtDCompositionBeginFrame+26

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

IMAGE_VERSION: 10.0.19041.3205

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 26

FAILURE_BUCKET_ID: AV_R_win32kbase!NtDCompositionBeginFrame

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {05267455-18cd-2ae4-0687-d1c2a6d58788}

Followup: MachineOwner
---------

2.Minidump:
nt!KeBugCheckEx:
fffff801`0effc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`11a89160=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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80113533f87, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: ffff8f829b53abf0, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: 6468

Key : Analysis.Elapsed.mSec
Value: 21872

Key : Analysis.IO.Other.Mb
Value: 1

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 2

Key : Analysis.Init.CPU.mSec
Value: 562

Key : Analysis.Init.Elapsed.mSec
Value: 4704

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Bugcheck.Code.LegacyAPI
Value: 0x1e

Key : Failure.Bucket
Value: AV_W_dxgmms2!VidSchiReferenceDisplayingAllocationsForThisEntry

Key : Failure.Hash
Value: {9ed796b4-3c4f-02eb-4424-b5de0202fa45}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80113533f87

BUGCHECK_P3: 1

BUGCHECK_P4: ffff8f829b53abf0

FILE_IN_CAB: 071923-5453-01.dmp

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: ffff8f829b53abf0

WRITE_ADDRESS: fffff8010f8fb390: 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
ffff8f829b53abf0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff801`11a89158 fffff801`0f0f917e : 00000000`0000001e ffffffff`c0000005 fffff801`13533f87 00000000`00000001 : nt!KeBugCheckEx
fffff801`11a89160 fffff801`0f0067b2 : fffff801`0f0f915c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff801`11a891a0 fffff801`0eee5b37 : fffff801`11a89710 00000000`00000000 fffff801`11a74c60 fffff801`0f0009be : nt!RtlpExecuteHandlerForException+0x12
fffff801`11a891d0 fffff801`0eee7b06 : fffff801`11a73f68 fffff801`11a89e20 fffff801`11a73f68 00000000`00000000 : nt!RtlDispatchException+0x297
fffff801`11a898f0 fffff801`0effd1d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff801`11a89fb0 fffff801`0effd1a0 : fffff801`0f010265 ffff8f82`9b53abf0 fffff801`11a73f30 00000000`00000004 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff801`11a73e28 fffff801`0f010265 : ffff8f82`9b53abf0 fffff801`11a73f30 00000000`00000004 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff801`11a73e30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125


SYMBOL_NAME: dxgmms2!VidSchiReferenceDisplayingAllocationsForThisEntry+167

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.3205

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 167

FAILURE_BUCKET_ID: AV_W_dxgmms2!VidSchiReferenceDisplayingAllocationsForThisEntry

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9ed796b4-3c4f-02eb-4424-b5de0202fa45}

Followup: MachineOwner
---------

3.Minidump:
nt!KeBugCheckEx:
fffff800`5f1fc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8088`22c5be50=000000000000007e
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff8005f021cac, The address that the exception occurred at
Arg3: ffff808822c5ce48, Exception Record Address
Arg4: ffff808822c5c680, Context Record Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 3437

Key : Analysis.Elapsed.mSec
Value: 27003

Key : Analysis.IO.Other.Mb
Value: 9

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 11

Key : Analysis.Init.CPU.mSec
Value: 467

Key : Analysis.Init.Elapsed.mSec
Value: 1820

Key : Analysis.Memory.CommitPeak.Mb
Value: 102

Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007e

Key : Failure.Bucket
Value: AV_dxgkrnl!unknown_function

Key : Failure.Hash
Value: {fa21b66f-fc18-71cb-000b-eb2b0bb02607}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8005f021cac

BUGCHECK_P3: ffff808822c5ce48

BUGCHECK_P4: ffff808822c5c680

FILE_IN_CAB: 071923-5625-01.dmp

EXCEPTION_RECORD: ffff808822c5ce48 -- (.exr 0xffff808822c5ce48)
ExceptionAddress: fffff8005f021cac (nt!ExAcquireResourceExclusiveLite+0x000000000000001c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffff8387324ac3aa
Attempt to read from address ffff8387324ac3aa

CONTEXT: ffff808822c5c680 -- (.cxr 0xffff808822c5c680)
rax=ffff8387c1571080 rbx=ffff8387324ac390 rcx=ffff8387324ac302
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffdd0ff1e85470
rip=fffff8005f021cac rsp=ffff808822c5d080 rbp=ffff808822c5d210
r8=00000000ffffffff r9=7fffdd0ff179beb0 r10=fffff8005f021c90
r11=ffff808822c5d738 r12=ffffdd0ff1f4c2a0 r13=ffffdd0ff179bde0
r14=0000000000000000 r15=ffffffffffffffff
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!ExAcquireResourceExclusiveLite+0x1c:
fffff800`5f021cac 0fb7431a movzx eax,word ptr [rbx+1Ah] ds:002b:ffff8387`324ac3aa=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

READ_ADDRESS: fffff8005fafb390: 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
ffff8387324ac3aa

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: 0000000000000000

EXCEPTION_PARAMETER2: ffff8387324ac3aa

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff8088`22c5d080 fffff800`65539dc4 : ffffdd0f`f1e85470 ffff8387`00000000 ffff8387`00000000 ffff8387`c21df050 : nt!ExAcquireResourceExclusiveLite+0x1c
ffff8088`22c5d110 ffffdd0f`f1e85470 : ffff8387`00000000 ffff8387`00000000 ffff8387`c21df050 00000000`00000000 : dxgkrnl+0xe9dc4
ffff8088`22c5d118 ffff8387`00000000 : ffff8387`00000000 ffff8387`c21df050 00000000`00000000 ffff8387`c24ac3f0 : 0xffffdd0f`f1e85470
ffff8088`22c5d120 ffff8387`00000000 : ffff8387`c21df050 00000000`00000000 ffff8387`c24ac3f0 00000000`00000000 : 0xffff8387`00000000
ffff8088`22c5d128 ffff8387`c21df050 : 00000000`00000000 ffff8387`c24ac3f0 00000000`00000000 ffff8088`22c5d840 : 0xffff8387`00000000
ffff8088`22c5d130 00000000`00000000 : ffff8387`c24ac3f0 00000000`00000000 ffff8088`22c5d840 ffff8088`00000001 : 0xffff8387`c21df050


SYMBOL_NAME: dxgkrnl+e9dc4

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

STACK_COMMAND: .cxr 0xffff808822c5c680 ; kb

BUCKET_ID_FUNC_OFFSET: e9dc4

FAILURE_BUCKET_ID: AV_dxgkrnl!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fa21b66f-fc18-71cb-000b-eb2b0bb02607}

Followup: MachineOwner
---------

4.Minidump:
nt!KeBugCheckEx:
fffff802`34dfc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa88b`e09584e0=0000000000000050
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff802a4edf518, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80239da3d53, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 3280

Key : Analysis.Elapsed.mSec
Value: 5178

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 452

Key : Analysis.Init.Elapsed.mSec
Value: 2026

Key : Analysis.Memory.CommitPeak.Mb
Value: 83

Key : Bugcheck.Code.LegacyAPI
Value: 0x50

Key : Failure.Bucket
Value: AV_R_(null)_dxgkrnl!unknown_function

Key : Failure.Hash
Value: {749b1d99-0328-14d4-1b07-ac069c133952}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 50

BUGCHECK_P1: fffff802a4edf518

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80239da3d53

BUGCHECK_P4: 0

FILE_IN_CAB: 071923-5765-01.dmp

READ_ADDRESS: fffff802356fb390: 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
fffff802a4edf518

MM_INTERNAL_CODE: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

TRAP_FRAME: ffffa88be0958780 -- (.trap 0xffffa88be0958780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc70d7d4ffb90 rbx=0000000000000000 rcx=ffffc70d7d9ee000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80239da3d53 rsp=ffffa88be0958910 rbp=ffffa88be09589d0
r8=fffff802a4edf4d0 r9=ffffa88be0958ad0 r10=fffff80234cff7e0
r11=ffffa88be09589d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
dxgkrnl+0x3d53:
fffff802`39da3d53 498b4048 mov rax,qword ptr [r8+48h] ds:fffff802`a4edf518=????????????????
Resetting default scope

STACK_TEXT:
ffffa88b`e09584d8 fffff802`34e4b2f5 : 00000000`00000050 fffff802`a4edf518 00000000`00000000 ffffa88b`e0958780 : nt!KeBugCheckEx
ffffa88b`e09584e0 fffff802`34c6e7b0 : 00000000`00010100 00000000`00000000 ffffa88b`e0958800 00000000`00000000 : nt!MiSystemFault+0x1b2905
ffffa88b`e09585e0 fffff802`34e0bbd8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
ffffa88b`e0958780 fffff802`39da3d53 : 00000000`0000139b fffff802`39da616f ffffa88b`e0958970 ffffc70d`7db36008 : nt!KiPageFault+0x358
ffffa88b`e0958910 00000000`0000139b : fffff802`39da616f ffffa88b`e0958970 ffffc70d`7db36008 00000000`00000000 : dxgkrnl+0x3d53
ffffa88b`e0958918 fffff802`39da616f : ffffa88b`e0958970 ffffc70d`7db36008 00000000`00000000 fffff802`00000000 : 0x139b
ffffa88b`e0958920 ffffa88b`e0958970 : ffffc70d`7db36008 00000000`00000000 fffff802`00000000 ffffc70d`7d118b20 : dxgkrnl+0x616f
ffffa88b`e0958928 ffffc70d`7db36008 : 00000000`00000000 fffff802`00000000 ffffc70d`7d118b20 fffff802`39efd1b0 : 0xffffa88b`e0958970
ffffa88b`e0958930 00000000`00000000 : fffff802`00000000 ffffc70d`7d118b20 fffff802`39efd1b0 00000000`0000139b : 0xffffc70d`7db36008


SYMBOL_NAME: dxgkrnl+3d53

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 3d53

FAILURE_BUCKET_ID: AV_R_(null)_dxgkrnl!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {749b1d99-0328-14d4-1b07-ac069c133952}

Followup: MachineOwner
---------

5.Minidump:

nt!KeBugCheckEx:
fffff803`21dfc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff838d`991bde90=000000000000003b
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the BugCheck
Arg2: fffff80321c40582, Address of the instruction which caused the BugCheck
Arg3: ffff838d991be790, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3577

Key : Analysis.Elapsed.mSec
Value: 11160

Key : Analysis.IO.Other.Mb
Value: 3

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 5

Key : Analysis.Init.CPU.mSec
Value: 546

Key : Analysis.Init.Elapsed.mSec
Value: 7393

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Failure.Bucket
Value: 0x3B_C000001D_nt!FsRtlReleaseEofLock

Key : Failure.Hash
Value: {c2d3f7b3-3e06-a982-52d1-8424e2330dd7}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80321c40582

BUGCHECK_P3: ffff838d991be790

BUGCHECK_P4: 0

FILE_IN_CAB: 071923-5781-01.dmp

CONTEXT: ffff838d991be790 -- (.cxr 0xffff838d991be790)
rax=000000000000003c rbx=ffffde0344be2080 rcx=0000000000000001
rdx=000000000000003e rsi=ffffde0348cc32a8 rdi=ffffa709c47961d8
rip=fffff80321c40582 rsp=ffff838d991bf190 rbp=ffffde0344be2730
r8=0000000000000000 r9=0000000000000000 r10=fffff80321c404d0
r11=ffff838d991bf218 r12=0000000000000000 r13=ffff838d991bf5d0
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nt!FsRtlReleaseEofLock+0xb2:
fffff803`21c40582 0f84dc031f00 je nt!FsRtlReleaseEofLock+0x1f0494 (fffff803`21e30964) [br=0]
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MsMpEng.exe

STACK_TEXT:
ffff838d`991bf190 fffff803`2618b15e : ffff838d`00000000 ffffa709`c4796200 ffffde03`00000001 fffff803`00000000 : nt!FsRtlReleaseEofLock+0xb2
ffff838d`991bf220 fffff803`2618ace4 : 00000000`00000000 fffff803`00000001 ffff838d`991bf530 fffff803`2618a932 : Ntfs!NtfsCleanupIrpContext+0x33e
ffff838d`991bf280 fffff803`2626e80e : ffff838d`991bf530 00000000`00000000 ffffde03`462d2010 00000000`00000000 : Ntfs!NtfsExtendedCompleteRequestInternal+0x134
ffff838d`991bf2e0 fffff803`2626cf16 : ffff838d`991bf530 ffffde03`462d2010 00000000`00000001 00000000`00000001 : Ntfs!NtfsCommonQueryInformation+0xcfe
ffff838d`991bf3e0 fffff803`2626cda0 : ffff838d`991bf530 ffffde03`462d2010 ffffde03`462d2010 00000000`00000000 : Ntfs!NtfsFsdDispatchSwitch+0x156
ffff838d`991bf510 fffff803`21c113a5 : ffffde03`462d2010 ffff838d`991bf880 00000000`00000000 fffff803`20225021 : Ntfs!NtfsFsdDispatchWait+0x40
ffff838d`991bf7b0 fffff803`2022710f : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000020 : nt!IofCallDriver+0x55
ffff838d`991bf7f0 fffff803`20224a43 : ffff838d`991bf880 00000064`e637bd01 00000000`0000000a 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffff838d`991bf860 fffff803`21c113a5 : ffffde03`462d2010 00000000`00000208 00000000`0000003e fffff803`00000000 : FLTMGR!FltpDispatch+0xa3
ffff838d`991bf8c0 fffff803`21c0a920 : 00000064`e637bda0 00000000`0000003e 00000000`00000000 00000000`00000016 : nt!IofCallDriver+0x55
ffff838d`991bf900 fffff803`21ffbece : ffff838d`991bfb80 ffffde03`462d2010 00000000`0000003e 00000000`00000000 : nt!IopCallDriverReference+0xd0
ffff838d`991bf970 fffff803`21e0f8f8 : 00000000`00000000 00000064`e637bda0 00000064`e637bdb8 ffffde03`0000003e : nt!NtQueryInformationFile+0x7de
ffff838d`991bfa90 00007ff8`0bf0d204 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000064`e637bd58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`0bf0d204


SYMBOL_NAME: nt!FsRtlReleaseEofLock+b2

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3208

STACK_COMMAND: .cxr 0xffff838d991be790 ; kb

BUCKET_ID_FUNC_OFFSET: b2

FAILURE_BUCKET_ID: 0x3B_C000001D_nt!FsRtlReleaseEofLock

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c2d3f7b3-3e06-a982-52d1-8424e2330dd7}

Followup: MachineOwner
---------