PC Random Crashes

[uShifty]

 

• OS - Windows 10 Pro (x64) build 19043, reinstalled 1-3 weeks ago 
• Age of system (hardware) Mixed as I upgrade my pc instead of getting new builds 
• Age of OS installation - have you re-installed the OS? ive reinstall it 
• CPU model - AMD Ryzen 5 3600xt 
• Video Card model - Nvidia GeForce GTX 1080
• MotherBoard - (if NOT a laptop) Asus Prime B550M-A
• Power Supply - brand & wattage (if laptop, skip this) Corsair RM 650
• Laptop or Desktop? - Desktop
• Memory - G-Skill 16GB (2xx8gb)

 

Description of the problem - 

When gaming I am running into an issue as of late where my PC freezes then a second or two later both monitors display a random solid color before restarting. This issue happens on titles like Destiny 2, New World, Battlefield 2042 Beta. Their are times I can game out for hours without this problem happening but some times it can happen multiple times within an hour.

 

What I have tried -

I tried monitoring temperatures and everything seems fairly normal GPU @ 65-75c cpu @ 38-46c. I have tried driver versions 457.51, 471.96, and 472.12. I also tried using windows troubleshooters, and a few benchmark/stress-test tools to no avail. 

 

I will attach my event viewer incase that can be of any help as I dont know what any of it means. If their is any other information that you need that would help me out I will try to supply it 

 

eventviewerlogs.evtx

[MingLee420]

8 minutes ago, uShifty said:

 

• OS - Windows 10 Pro (x64) build 19043, reinstalled 1-3 weeks ago 
• Age of system (hardware) Mixed as I upgrade my pc instead of getting new builds 
• Age of OS installation - have you re-installed the OS? ive reinstall it 
• CPU model - AMD Ryzen 5 3600xt 
• Video Card model - Nvidia GeForce GTX 1080
• MotherBoard - (if NOT a laptop) Asus Prime B550M-A
• Power Supply - brand & wattage (if laptop, skip this) Corsair RM 650
• Laptop or Desktop? - Desktop
• Memory - G-Skill 16GB (2xx8gb)

 

Description of the problem - 

When gaming I am running into an issue as of late where my PC freezes then a second or two later both monitors display a random solid color before restarting. This issue happens on titles like Destiny 2, New World, Battlefield 2042 Beta. Their are times I can game out for hours without this problem happening but some times it can happen multiple times within an hour.

 

What I have tried -

I tried monitoring temperatures and everything seems fairly normal GPU @ 65-75c cpu @ 38-46c. I have tried driver versions 457.51, 471.96, and 472.12. I also tried using windows troubleshooters, and a few benchmark/stress-test tools to no avail. 

 

I will attach my event viewer incase that can be of any help as I dont know what any of it means. If their is any other information that you need that would help me out I will try to supply it 

 

eventviewerlogs.evtx 5.07 MB · 0 downloads

have you done anything in bios if so try revert it to normal if it continues to crash try clearing the cmos by either taking out the flat circle battery or a screwdriver and bridge two pins of the moobo but im not sure what its called or where it is and is different on different mobos

[uShifty]

8 minutes ago, MingLee420 said:

have you done anything in bios if so try revert it to normal if it continues to crash try clearing the cmos by either taking out the flat circle battery or a screwdriver and bridge two pins of the moobo but im not sure what its called or where it is and is different on different mobos

I have updated my bios to the latest version and reset to the default settings. I will try clearing the CMOS next time my pc crashes to see if any changes take place on next boot

[leclod]

I guess your psu should be powerfull enough (I didn't check) but maybe it isn't.

Do you daisy chain your 2 gpu power plugs ? do you have other to try ?

Once I fixed my build by simply switching my 2 gpu power plugs

I'd reinstall that gpu to be sure it fits well in it's slot, same with Ram.

Then I'd replug all my connectors...

 

 

[uShifty]

23 minutes ago, leclod said:

I guess your psu should be powerfull enough (I didn't check) but maybe it isn't.

Do you daisy chain your 2 gpu power plugs ? do you have other to try ?

Once I fixed my build by simply switching my 2 gpu power plugs

I'd reinstall that gpu to be sure it fits well in it's slot, same with Ram.

Then I'd replug all my connectors...

 

 

I am not using a daisy chain I use a single 8pin header for my GPU. I can try reseating my GPU when I clear my CMOS. I never really had an issue with my PSU especially on destiny 2 unless maybe my PSU is dying and not delivering enough power at certain times?  

[MingLee420]

16 minutes ago, uShifty said:

I am not using a daisy chain I use a single 8pin header for my GPU. I can try reseating my GPU when I clear my CMOS. I never really had an issue with my PSU especially on destiny 2 unless maybe my PSU is dying and not delivering enough power at certain times?  

 Id highly doubt it because a 1080 is 70w tdp less than the ti and the ti could go up to 250 but can go to 290 close to a 3080 but you could run it off a 650w so id say reseat the ram is like the other guy said and download ddu it uninstalls all gpu drivers from the pc, you will have to boot into safe mode in order to do it but do it first to make sure its not a physical issue or is

[uShifty]

I just cleared my CMOS by removing the battery for 5 minutes, reseated the ram and GPU. I will see if that resolves anything. Was their anything useful in the event viewer log I provided? Or was that just useless information I am not too sure how event viewer works 

[uShifty]

After reseating everything and using a air compressor to clean everything out I am still encountering this problem. Is their any software I can use to test the integrity of my PSU/GPU all tools ive tried to use work/run flawlessly 

[uShifty]

UPDATE: I used a tool called BlueScreenView and I noticed that I may have been having a BSOD issue the entire time. and the crash for all the times that it happened were the same. Here is some of the information that I gathered from the tool that may be helpful I will look into this some more but just in case someone from here knows what any of that means that would be great! 

Bug Check Code: 0x00000116

Driver: dxgkrnl.sys    

Caused By Address: dxgkrnl.sys+2409ba

Crash Address: ntoskrnl.exe+1c1220 

 

EDIT: Added the html log of all crashes from today whilst playing new world 

report.html

[uShifty]

After downloading the Windows SDK and running the crash dump in WinDBG I got a little more information that correlates to the information provided yesterday. That may be helpful but if I get any more information I will update the thread as I could really use some pointers on what can be the issue still learning how to debug everything. 
 

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe40136877460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff801949c08b8, 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.

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5292bbfbf575e2d2\nvlddmkm.sys, Win32 error 0n2

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe40136877460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

SYMBOL_NAME:  nvlddmkm+da08b8
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
STACK_COMMAND:  .thread ; .cxr ; kb
FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
OS_VERSION:  10.0.18362.1
BUILDLAB_STR:  19h1_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

 

[kudzu]

Getting a similar daily 116/TDR BSOD myself. Found this thread when I googled the following string from a windb !analyze -v

 

nvlddmkm+da08b8

My particular issue was due in part to update KB5006670. After uninstalling that update, my BSODs went away.

 

Today, the bloody thing re-installed itself because I wasn't fast enough with "wushowhide.diagcab" to disable the pending update. So, unfortunately, it re-installed itself as of today.

 

I'm trying one more process of elimination step and that is to update vmware workstation to 6.1.2. I was at 6.1.1. Vmware does some 3d graphics sharing and sometimes I've noticed that my desktop UI will occasionally slow to a crawl for around 30sec to a min. I'm guessing that timeout detection and/or driver reset behavior could have changed in the windows update and the occasional vmware related slowdowns are now causing the bug check.

 

Do you have vmware or other virtualization solution installed and running when your crashes occur??  Do you have KB5006670 installed?

 

Here's my full BSOD desc for comparison:

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe18b8c7f7460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff800952508b8, 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\nv_dispi.inf_amd64_5292bbfbf575e2d2\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4077

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 8546

    Key  : Analysis.Init.CPU.mSec
    Value: 2265

    Key  : Analysis.Init.Elapsed.mSec
    Value: 24729

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 86

    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.1


BUGCHECK_CODE:  116

BUGCHECK_P1: ffffe18b8c7f7460

BUGCHECK_P2: fffff800952508b8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe18b8c7f7460
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:  
ffff8684`819e1a18 fffff800`9026665e     : 00000000`00000116 ffffe18b`8c7f7460 fffff800`952508b8 ffffffff`c000009a : nt!KeBugCheckEx
ffff8684`819e1a20 fffff800`90216e44     : fffff800`952508b8 ffffe18b`772d6890 00000000`00002000 ffffe18b`772d6950 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8684`819e1a60 fffff800`9020f97c     : ffffe18b`772ce000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff8684`819e1a90 fffff800`90265d85     : 00000000`00000100 ffffe18b`772cea70 00000000`4d0fa710 fffff800`828cf40c : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff8684`819e1b10 fffff800`90265ef7     : fffff800`83325440 ffffe18b`8e1239f0 00000000`00000000 00000000`00000200 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8684`819e1b40 fffff800`828b8515     : ffffe18b`766bc040 fffff800`90265ed0 ffffe18b`3c0d2c20 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8684`819e1b70 fffff800`82955855     : ffffe18b`766bc040 00000000`00000080 ffffe18b`3c0d7080 fffafafa`00000001 : nt!ExpWorkerThread+0x105
ffff8684`819e1c10 fffff800`829fe808     : ffffa681`8b8c0180 ffffe18b`766bc040 fffff800`82955800 fffafafa`fffafafa : nt!PspSystemThreadStartup+0x55
ffff8684`819e1c60 00000000`00000000     : ffff8684`819e2000 ffff8684`819dc000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+da08b8

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; 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