Yeah, you are getting a video TDR problem.
Given you've already taken the appropriate steps with the power supply and the driver.
I'm going to have to side with the card being the source of the issue here.
The only thing I can think to try software side, is running driver sweeper (the latest version it's no longer supported on guru3d.)
Phyxion.net - Driver Sweeper
and install the previous version of the nvidia driver. As the software debug does show that the nvidia kernel is what's crashing.
This could of course just be because it's sending instructions to the card and getting the wrong answers too.
Code:
Probably caused by : nvlddmkm.sys ( nvlddmkm+e1140 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009f9b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88008156140, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+e1140
fffff880`08156140 803d51b4970000 cmp byte ptr [nvlddmkm+0xa5c598 (fffff880`08ad1598)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`045f0988 fffff880`06ecc000 : 00000000`00000116 fffffa80`09f9b4e0 fffff880`08156140 00000000`00000000 : nt!KeBugCheckEx
fffff880`045f0990 fffff880`06ecbd0a : fffff880`08156140 fffffa80`09f9b4e0 fffffa80`09d36d50 fffffa80`09d2a010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`045f09d0 fffff880`08b52f07 : fffffa80`09f9b4e0 00000000`00000000 fffffa80`09d36d50 fffffa80`09d2a010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`045f0a00 fffff880`08b7cb75 : 00000000`ffffffff 00000000`00018e91 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`045f0ae0 fffff880`08b7b2bb : 00000000`00000102 00000000`00000000 00000000`00018e91 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`045f0b10 fffff880`08b4e2c6 : ffffffff`ff676980 fffffa80`09d2a010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`045f0bb0 fffff880`08b7ae7a : 00000000`00000000 fffffa80`06eb1010 00000000`00000080 fffffa80`09d2a010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`045f0cc0 fffff800`02d68bc6 : 00000000`fffffc32 fffffa80`09b21b60 fffffa80`06712040 fffffa80`09b21b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`045f0d00 fffff800`02aa3bc6 : fffff800`02c3fe80 fffffa80`09b21b60 fffff800`02c4dc40 fffff880`01418bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`045f0d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+e1140
fffff880`08156140 803d51b4970000 cmp byte ptr [nvlddmkm+0xa5c598 (fffff880`08ad1598)],0
SYMBOL_NAME: nvlddmkm+e1140
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5ce19c
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------