Windows 10: BSOD Crash Dump Debugger Report

A few days ago i change my ssd and did a clean windows 10 installation with usb tool from microsoft. Since then i have random freezes and bsod while gaming ac valhalla, ac black flag, RDR2. The ssd is a WD blue 500gb m.2 and the previous one was a WD green 240Gb m.2.


Windows 10 is installed there along with the games. Before changing the ssd i had no issues whatsoever with the current nvidia driver. But what is different appart from the ssd was the windows version i had, it wasnt the latest 10.0.19041.1. I dont remember wich one was, but it was a version where you could see if windows was activated trough "this pc - properties".


Here is the dump that was generated. It points to "nvlddmkm". Nvidia driver. But that's odd, forgot to mention i had clean installed windows 3 times since the first BSOD, and with each new installation the same issue. As i mentioned, the only thing different is the ssd which i analized with tools and no damage there and the new windows 10 version i installed. So could be a combination of the new windows and the driver? Or in fact a faulty ssd? which i doubt because it only crashes when im gaming, i can use windows for hours otherwise


Thanks in advance to whoever take a look into this! :

******************************************************************************** ** 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: fffff8014e140e36, The address that the exception occurred atArg3: fffff4029d258ef8, Exception Record AddressArg4: fffff4029d258730, Context Record AddressDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 5546 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-SQU8CAL Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 70777 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff8014e140e36BUGCHECK_P3: fffff4029d258ef8BUGCHECK_P4: fffff4029d258730EXCEPTION_RECORD: fffff4029d258ef8 -- .exr 0xfffff4029d258ef8ExceptionAddress: fffff8014e140e36 nvlddmkm+0x00000000007c0e36 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000048Attempt to read from address 0000000000000048CONTEXT: fffff4029d258730 -- .cxr 0xfffff4029d258730rax=0000000000000000 rbx=0000000000000000 rcx=ffffe381724dc1d8rdx=0000000000000000 rsi=ffffbb8bb076611a rdi=ffffe38172446000rip=fffff8014e140e36 rsp=fffff4029d259130 rbp=ffffe38172467f20 r8=0000000000000006 r9=0000000000000000 r10=0000000000000000r11=ffffbb8bb0766186 r12=0000000000000000 r13=0000000000000000r14=0000000000000002 r15=ffffe38172446180iopl=0 nv up ei ng nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286nvlddmkm+0x7c0e36:fffff801`4e140e36 ff5048 call qword ptr [rax+48h] ds:002b:00000000`00000048=????????????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff801436fa390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8014360f330: Unable to get Flags value from nt!KdVersionBlockfffff8014360f330: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 0000000000000048 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: c0000005EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: 0000000000000048EXCEPTION_STR: 0xc0000005STACK_TEXT: fffff402`9d259130 00000000`00000000 : fffff801`4dae9543 00000000`00000001 fffff801`42dd3608 00000000`000000ff : nvlddmkm+0x7c0e36SYMBOL_NAME: nvlddmkm+7c0e36MODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .cxr 0xfffff4029d258730 ; kbBUCKET_ID_FUNC_OFFSET: 7c0e36FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_functionOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}Followup: MachineOwner---------

:)

 

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

I have been getting a BSOD almost every day now for some reason, because of that I created a dmp file, but I am not familiar with this process to figure out what any of this means. Would anyone be willing to take a look at the dmp file? I'd greatly appreciate
it.