17 R5, persistent BSOD issues

probably time for a fresh install of windows

Update: DDU'd again. Got some stable uptime out of it. Trying to export something light from Resolve resulted in another BSOD. Upon startup, Reliability Monitor showed no issue, but I finally was able to get a Minidump:

VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffb6854fdbb010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff805a3816af0, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data. Debugging Details: ------------------ Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvdmsi.inf_amd64_32750443fd131dd6\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2687 Key : Analysis.Elapsed.mSec Value: 18696 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 25 Key : Analysis.Init.CPU.mSec Value: 984 Key : Analysis.Init.Elapsed.mSec Value: 33206 Key : Analysis.Memory.CommitPeak.Mb Value: 109 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0x116 Key : Bugcheck.Code.TargetModel Value: 0x116 Key : Failure.Bucket Value: 0x116_IMAGE_nvlddmkm.sys Key : Failure.Exception.IP.Address Value: 0xfffff805a3816af0 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0x1986af0 Key : Failure.Hash Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 116 BUGCHECK_P1: ffffb6854fdbb010 BUGCHECK_P2: fffff805a3816af0 BUGCHECK_P3: ffffffffc000009a BUGCHECK_P4: 4 FILE_IN_CAB: 060225-14890-01.dmp FAULTING_THREAD: ffffb6853f102080 VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffb6854fdbb010 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: 0000000000000004 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffff810559aaf918 fffff805899c686e : 0000000000000116 ffffb6854fdbb010 fffff805a3816af0 ffffffffc000009a : nt!KeBugCheckEx ffff810559aaf920 fffff80589976ef4 : fffff805a3816af0 ffffb6854ae766e0 0000000000002000 ffffb6854ae767a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffff810559aaf960 fffff8058996fa2c : ffffb6854ae64000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174 ffff810559aaf990 fffff805899c5f95 : 0000000000000100 ffffb6854ae64a70 000000003baa1a20 fffff80571d25440 : dxgkrnl!DXGADAPTER::Reset+0x4dc ffff810559aafa10 fffff805899c6107 : fffff80571d25440 0000000000000000 0000000000000000 0000000000000100 : dxgkrnl!TdrResetFromTimeout+0x15 ffff810559aafa40 fffff805712489d5 : ffffb6853f102080 fffff805899c60e0 ffffb6853baa1a20 ffffb68500000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27 ffff810559aafa70 fffff805713347d5 : ffffb6853f102080 0000000000000080 ffffb6853bb02080 0034002300300030 : nt!ExpWorkerThread+0x105 ffff810559aafb10 fffff80571406ff8 : ffffcb00d7a5c180 ffffb6853f102080 fffff80571334780 006300330061002d : nt!PspSystemThreadStartup+0x55 ffff810559aafb60 0000000000000000 : ffff810559ab0000 ffff810559aa9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: nvlddmkm+1986af0 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffb6853bb02080; .thread 0xffffb6853f102080 ; kb FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd} Followup: MachineOwner

@HedgeFundManager​ Do you think? I'm starting to think this might be hardware related.

You could try F12 when you boot and try the diagnostics but I am suspecting a mangled windows setup