Question 3080 Crushing consistently in any game

[KivAle]

Started getting crushes often, now it happens every time when i try to launch a game.

I have a 3080 from MSI, only a few years old.

I've tried:

1. Fresh driver install
2. Reinstalling windows
3. Downgrading driver
4. Memtest
5. Increase TDR Timeout
6. resitting GPU
7. Setting a fan in front of PC (temps seem absolutely fine)
8. Limiting power to 90%, -100 core clock via afterburner
9. updating all other PC drivers

Sharing my minidump, hopefully someone can help:

*******************************************************************************

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1359

Key : Analysis.Elapsed.mSec
Value: 1953

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x116

Key : Bugcheck.Code.TargetModel
Value: 0x116

Key : Dump.Attributes.AsUlong
Value: 21008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x116_IMAGE_nvlddmkm.sys

Key : Failure.Hash
Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}


BUGCHECK_CODE: 116

BUGCHECK_P1: ffff968cce180010

BUGCHECK_P2: fffff80369030a40

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: 020525-49031-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump

FAULTING_THREAD: ffff968ccb502080

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff968cce180010
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:
fffffb8f`7d107888 fffff803`594515ad : 00000000`00000116 ffff968c`ce180010 fffff803`69030a40 ffffffff`c000009a : nt!KeBugCheckEx
fffffb8f`7d107890 fffff803`596dc61e : fffff803`69030a40 ffff968c`bf6b5010 00000000`00002000 ffff968c`bf6b50d0 : dxgkrnl!TdrBugcheckOnTimeout+0x101
fffffb8f`7d1078d0 fffff803`5946049d : ffff968c`bf6b2000 00000000`00000000 00000000`00000004 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a
fffffb8f`7d107900 fffff803`59496a55 : ffffa780`ba080180 ffff968c`cb502080 ffff968c`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x589
fffffb8f`7d107990 fffff803`59496bb2 : ffff968c`b65a4260 ffff968c`ad6a4fb0 00000000`00000000 ffff968c`b64a7400 : dxgkrnl!TdrResetFromTimeout+0x15
fffffb8f`7d1079c0 fffff803`c77704b2 : ffff968c`cb502080 ffff968c`ad77ebf0 ffff968c`ad77eb00 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
fffffb8f`7d107a00 fffff803`c785594a : ffff968c`cb502080 ffff968c`cb502080 fffff803`c7770300 ffff968c`ad77ebf0 : nt!ExpWorkerThread+0x1b2
fffffb8f`7d107bb0 fffff803`c7a79fb4 : ffffa780`ba451180 ffff968c`cb502080 fffff803`c78558f0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffffb8f`7d107c00 00000000`00000000 : fffffb8f`7d108000 fffffb8f`7d101000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nvlddmkm+1700a40

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffff968cad6bf040; .thread 0xffff968ccb502080 ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
---------
Any help/ideas will be appreciated, thank you all in advance!

 

[Brillis Wuce]

Ah bummer, always a stressful situation.
You said the temps look fine, what what temps are you looking at? HWINFO will show memory, core, and hotspot temps. The core temp isn't the whole shebang.
2nd thought, what is your PSU brand and model? This could be a failing PSU. especially if the crashing happens while launching a game which triggers power usage spikes.
3rd, are you using separate power cables connected to the 3080, or are you splitting a single cable into 2?

Started getting crushes often, now it happens every time when i try to launch a game.
I've never developed a crush on someone from gaming. Sounds like a good thing 😉

 

[KivAle]

Ah bummer, always a stressful situation.
You said the temps look fine, what what temps are you looking at? HWINFO will show memory, core, and hotspot temps. The core temp isn't the whole shebang.
2nd thought, what is your PSU brand and model? This could be a failing PSU. especially if the crashing happens while launching a game which triggers power usage spikes.
3rd, are you using separate power cables connected to the 3080, or are you splitting a single cable into 2?

Started getting crushes often, now it happens every time when i try to launch a game.
I've never developed a crush on someone from gaming. Sounds like a good thing 😉

1. Here's a snapshot right before the crush from HWINFO, didn't find additional GPU temp data, but on the graphs i've never seen it rise higher than 83

/nvidiagpu/0/power/0	/nvidiagpu/0/throughput/0	/nvidiagpu/0/throughput/1	/hdd/0/temperature/0
GPU Power	GPU PCIE Rx	GPU PCIE Tx	Temperature

[td]

106.001​

[/td][td]

16.60156​

[/td][td]

1.416016​

[/td][td]

59​

[/td]​

2. Its a Corsair 850 Gold + certified one, im not sure about the model, im working with an ITX case and its complicated to take it out, I hope you're right, that's the first thing ill be replacing..

3. its not split but its in one braid, looks like two cables. It has worked perfectly for the past 3-4 years.

Got the PC around the same time I found my current SO so I guess crushes are a feature )

Thank you for the help!

 

[Brillis Wuce]

One braided cabled that has 2 power connectors is a split. 2 individual power cables to each connector is ideal, in terms of power delivery and performance. I know its a pain, but a quick search on YouTube will show you why.
Install HWMonitor and keep an eye on it. That's by far the easiest solution right now since you have an ITX setup. I'd wager your PSU is going bad, or something on your 3080 is overheating, but that's the easiest and most effective solution right now.
Let me know how it goes!