So it has to do with your display driver and the system thinking that your pc hung. Refer to this article
https://learn.microsoft.com/en-us/w.../debugger/bug-check-0x116---video-tdr-failure
I used windbg and analyzed the file and found this
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe70412418460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff807a4fb3d00, 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.
thats how I know what it is.
Have you overclocked at all?
Is windows up to date?