EVGA 1080 Ti crashing in games. Should I RMA?

[Rex4748]

I built my computer in early June and up until a few weeks ago, I've had no issues with it. Suddenly, all my games started crashing and I get this error in the event logs: "Display driver nvlddmkm stopped responding and has successfully recovered."

I looked up possible solutions, and I believe I've tried them all:

• Uninstalled GeForce driver -> Ran DDU -> clean install
• Reformatted and re-installed Windows
• Underclocked GPU
• Changed power settings to "maximum performance", etc. Tried tweaking voltages as well.
• Ran MemTest. RAM is all clear.
• Stress tested CPU. All clear. Tried reverting to stock settings as well.
• Cleaned dust out of computer (there wasn't much) and reseated GPU.
• Tried a different PCIe slot.
• Tried a different PSU, as well as different cables.
• Tried a different monitor and different cables.
• Detached all peripherals and clean booted Windows.
• Tried disabling G-Sync, and tested just about every Nvidia setting
• Tried playing games in Windowed mode

 

The airflow in my case is fine as well, and my temperatures are at reasonable levels at all times (under 70°C). I've tried this with several games and they all crash within half an hour or so (average is about 5-10 minutes). Like I said, I've had no issues running these exact same games for the past 4 months. This just started out of nowhere; I hadn't updated or changed anything. I'm really confused as to why the card would just start doing this months later if it was defective, rather than right away.

Anyway, I can't think of anything I haven't tried, and at this point it seems like my only option is to RMA the card.
Just wanted to make sure I wasn't missing anything before I go ahead with it. Any thoughts or suggestions are appreciated!

Specs:
ASRock Z370 Taichi
i7-8700K
EVGA 1080 Ti SC Black
32GB RAM (G.Skill)
Samsung 860 EVO SSD
Corsair RM650i
Windows 10 Enterprise (64-bit)

[Brooksie359]

I have had this issue before. It's usually software related. 

[Crunchy Dragon]

Tried an older driver?

[Brooksie359]

There is a way to edit your registry keys to allow more time for the driver to recover. If you do that and it still fails then I am unsure. 

[Daniel644]

5 minutes ago, Crunchy Dragon said:

Tried an older driver?

this, have you tried this????

[Rex4748]

3 minutes ago, Brooksie359 said:

I have had this issue before. It's usually software related. 

Based on what I've read, that seems to be the case, but it doesn't really make a lot of sense. I did a complete re-format and clean install of the driver and it didn't fix it. Also, it just started happening after several months even though I had changed nothing software-wise.

 

3 minutes ago, Crunchy Dragon said:

Tried an older driver?

The one I was on was fine for months and I never updated it until after this issue started showing up. I could try though. Any you would recommend, or should I just try a few random ones?

[Brooksie359]

2 minutes ago, Rex4748 said:

Based on what I've read, that seems to be the case, but it doesn't really make a lot of sense. I did a complete re-format and clean install of the driver and it didn't fix it. Also, it just started happening after several months even though I had changed nothing software-wise.

 

The one I was on was fine for months and I never updated it until after this issue started showing up. I could try though. Any you would recommend, or should I just try a few random ones?

https://windowsreport.com/driver-stopped-responding-recovered-windows-10/

Try the part where they edit the registry. I had this issue with my 1070 awhile back and that fixed it for me. No harm in trying. 

[Rex4748]

7 hours ago, Brooksie359 said:

https://windowsreport.com/driver-stopped-responding-recovered-windows-10/

Try the part where they edit the registry. I had this issue with my 1070 awhile back and that fixed it for me. No harm in trying. 

Tried it, but still crashed.

 

7 hours ago, Daniel644 said:

this, have you tried this????

Tried another clean install of an older driver (v388.13) and crashed again.

[Daniel644]

2 hours ago, Rex4748 said:

Tried it, but still crashed.

 

Tried another clean install of an older driver (v388.13) and crashed again.

then sounds like you've tried everything, sounds like time to RMA to me.