Windows 10: Crash Dump Debugger Report

I have a crash dump file that I have used the Windows Debugger to analyze. I am not familiar enough with this process to actually read the information and interpret it. Will someone take a look at them and let me know what caused them? Much appreciated.

Here is the link for the dump file:

https://1drv.ms/u/s!AjL3rwOFDoOMg8NRrk7FHJEf2X882w?e=4xjyRt


3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003. This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG. This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG. This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff803768d0e36, The address that the exception occurred atArg3: fffff48ed9185df8, Exception Record AddressArg4: fffff48ed9185630, Context Record AddressDebugging Details:------------------KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2921 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on WTZ-MASTER Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 5701 Key : Analysis.Memory.CommitPeak.Mb Value: 77 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff803768d0e36BUGCHECK_P3: fffff48ed9185df8BUGCHECK_P4: fffff48ed9185630EXCEPTION_RECORD: fffff48ed9185df8 -- .exr 0xfffff48ed9185df8ExceptionAddress: fffff803768d0e36 nvlddmkm+0x00000000007c0e36 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000048Attempt to read from address 0000000000000048CONTEXT: fffff48ed9185630 -- .cxr 0xfffff48ed9185630rax=0000000000000000 rbx=0000000000000000 rcx=ffffa806cd4dc1d8rdx=0000000000000000 rsi=ffff95834917490d rdi=ffffa806cd446000rip=fffff803768d0e36 rsp=fffff48ed9186030 rbp=ffffa806cd467f20 r8=0000000000000009 r9=0000000000000000 r10=0000000000000000r11=ffff958349174979 r12=0000000000000000 r13=0000000000000000r14=0000000000000002 r15=ffffa806cd446180iopl=0 nv up ei ng nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286nvlddmkm+0x7c0e36:fffff803`768d0e36 ff5048 call qword ptr [rax+48h] ds:002b:00000000`00000048=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff8035d2fa390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8035d20f330: Unable to get Flags value from nt!KdVersionBlockfffff8035d20f330: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 0000000000000048 ERROR_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_CODE_STR: c0000005EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: 0000000000000048EXCEPTION_STR: 0xc0000005STACK_TEXT: fffff48e`d9186030 ffffa806`ce752080 : fffff803`5cb19946 00000000`00000001 fffff803`5c9d3608 00000000`000000ff : nvlddmkm+0x7c0e36fffff48e`d9186038 fffff803`5cb19946 : 00000000`00000001 fffff803`5c9d3608 00000000`000000ff ffff9583`49173b05 : 0xffffa806`ce752080fffff48e`d9186040 ffffa806`cd311010 : ffff8281`00000004 ffff9583`491739f1 00000000`00000000 ffffa806`cd446180 : nt!KiHeteroChooseTargetProcessor+0x426fffff48e`d9186110 ffff8281`00000004 : ffff9583`491739f1 00000000`00000000 ffffa806`cd446180 fffff48e`d9186190 : 0xffffa806`cd311010fffff48e`d9186118 ffff9583`491739f1 : 00000000`00000000 ffffa806`cd446180 fffff48e`d9186190 ffff9583`49112419 : 0xffff8281`00000004fffff48e`d9186120 00000000`00000000 : ffffa806`cd446180 fffff48e`d9186190 ffff9583`49112419 00000008`ccf84000 : 0xffff9583`491739f1SYMBOL_NAME: nvlddmkm+7c0e36MODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .cxr 0xfffff48ed9185630 ; kbBUCKET_ID_FUNC_OFFSET: 7c0e36FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_functionOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}Followup: MachineOwner---------

Thanks!

:)

 

Crash Dump Debugger Report - BSOD

Please remove old dumps and share new ones if bsod repeats.

 

Crash Dump Debugger Report - BSOD

Hi,

clean graphic adaptor's cooling system. check system files with sfc /scannow command. Reinstall graphic driver.

If problem persists please share memory dumps to OneDrive.

Palmer's message is a scam.

 

Crash Dump Debugger Report - BSOD

Hello Igor,

Thanks a lot for your reply and pointing out that Palmer's message is fake.

I just cleaned out my the cooling system for my graphics adaptor and also checked the system files, which only repaired a file relating to One Drive. The PC hasn't crashed as of yet

This is the link for all of the dmp files from today

Memory Dumps

I appreciate the help!