Microsoft (R) Windows Debugger Version 10.0.22621.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081422-13000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`0fc00000 PsLoadedModuleList = 0xfffff803`108296b0
Debug session time: Sun Aug 14 10:41:04.284 2022 (UTC - 5:00)
System Uptime: 0 days 1:29:49.004
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
0: 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: fffff80337099d8d, The address that the exception occurred at
Arg3: ffffc20e4b1467e8, Exception Record Address
Arg4: ffffc20e4b146000, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 7734

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19639

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

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

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


FILE_IN_CAB:  081422-13000-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80337099d8d

BUGCHECK_P3: ffffc20e4b1467e8

BUGCHECK_P4: ffffc20e4b146000

EXCEPTION_RECORD:  ffffc20e4b1467e8 -- (.exr 0xffffc20e4b1467e8)
ExceptionAddress: fffff80337099d8d (nvlddmkm+0x0000000000349d8d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000010000
Attempt to read from address 0000000000010000

CONTEXT:  ffffc20e4b146000 -- (.cxr 0xffffc20e4b146000)
rax=0000000000180002 rbx=fffff803375a9be0 rcx=0000000000180002
rdx=0000000000180001 rsi=0000000000010000 rdi=ffff9d872c1de220
rip=fffff80337099d8d rsp=ffffc20e4b146a20 rbp=ffffc20e4b146a80
 r8=0000000000000001  r9=0000000000000020 r10=fffff8030fc00000
r11=ffffc20e4b146001 r12=ffff9d8725a582c8 r13=ffff9d87281593d8
r14=ffff9d872c1de220 r15=ffff9d872e9f5a08
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+0x349d8d:
fffff803`37099d8d ff16            call    qword ptr [rsi] ds:002b:00000000`00010000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

READ_ADDRESS: fffff80310905450: 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
 0000000000010000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%p hace referencia a la memoria en 0x%p. La memoria no se pudo %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000010000

EXCEPTION_STR:  0xc0000005

STACK_TEXT:  
ffffc20e`4b146a20 ffffc20e`4b146b30     : fffff803`36def0e7 ffffc20e`4b146b58 fffff803`36edd377 ffff9d87`281595a8 : nvlddmkm+0x349d8d
ffffc20e`4b146a28 fffff803`36def0e7     : ffffc20e`4b146b58 fffff803`36edd377 ffff9d87`281595a8 00000000`00000000 : 0xffffc20e`4b146b30
ffffc20e`4b146a30 ffffc20e`4b146b58     : fffff803`36edd377 ffff9d87`281595a8 00000000`00000000 fffff803`36edd377 : nvlddmkm+0x9f0e7
ffffc20e`4b146a38 fffff803`36edd377     : ffff9d87`281595a8 00000000`00000000 fffff803`36edd377 fffff803`36deecfd : 0xffffc20e`4b146b58
ffffc20e`4b146a40 ffff9d87`281595a8     : 00000000`00000000 fffff803`36edd377 fffff803`36deecfd ffff9d87`1db08a30 : nvlddmkm+0x18d377
ffffc20e`4b146a48 00000000`00000000     : fffff803`36edd377 fffff803`36deecfd ffff9d87`1db08a30 ffffc20e`00000020 : 0xffff9d87`281595a8


SYMBOL_NAME:  nvlddmkm+349d8d

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xffffc20e4b146000 ; kb

BUCKET_ID_FUNC_OFFSET:  349d8d

FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}

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