Apparently this has happened to other people as well i've found....

Please tell me how after almost 2 years of fixes, the game still is so bugged it ruined my 1080Ti...

Game played fine for the first 10 hours or so, meanwhile in my haste to figure out what was causing it to suddenly constantly crash before starting or within a few minutes of gameplay, trying everything to remedy the problem I didn't stop to consider the game itself could gimp my GPU. I did a full uninstall with DDU and reinstall of the latest driver in case it somehow got corrupted, but it didn't help.

This is incredibly infuriating as now all of my other games crash within a minute or two of loading.. I JUST WANTED TO GIVE CYBERPUNK A CHANCE! I'm pissed because I don't have the means to replace the card right now.

I know most of you will say it's a coincidence.. but I am positive it isn't, I just don't know exactly how or if it's possible to proove. I remember on another PC years ago, a game that wasn't that graphics intensive had a weird bug in it that made either my CPU or GPU heat up incredibly. Also there is the whole New World game that crippled peoples hardware recently.

Has anyone else had this happen or heard of this happening?

I found this reddit thread others who got Cyberpunked:

reddit.com/r/cyberpunkgame/comments/kbe12p/cyberpunk_2077_literally_broke_my_pc

Are you overclocking your CPU and/or video card?

Have you tried using your GPU on another PC?

Windows 10 latest update
i7-4790K @4.00 (Overclocked to 4.4 and stable for years)
NVIDIA GeForce GTX 1080 Ti ASUS ROG (not overclocked) Updated to latest driver and used DDU to remove the old
16GB RAM

I can see about using it on another PC when i get the chance, but the concern is that it has an issue now caused by Cyberpunk.

In the crash logs from Cyberpunk it showed:
Message: Gpu Crash for unknown reasons! Callstack here is probably irrelevant. Check if Breadcrumbs or Aftermath logged anything useful.
File: e:\r6.release\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp

Windows event viewer for Cyberpunk showed: Exception code: 0x80000003
for Elden Ring it's now showing: Exception code: 0xc0000005 (granted Elden Ring would crash once in a rare while, it crashes a minute into the game now since the Cyberpunk issue.. the same with Wolfenstein)
Windows event viewer also shows "Display driver nvlddmkm stopped responding and has successfully recovered." right before crash.

Just tested Sea of Thieves, After it crashed I got the error message: "Video driver crashed and was reset"


I don't care about getting Cyberpunk to work anymore, I'm done with it.. I just want to be able to play all of my other games again :(

That's not a cyberpunk cause, that's an issue both nvidia and amd have had with their drivers going back to the mid 2000's.

EDIT: To clarify, you might be able to solve it by doing a complete uninstall of *every* piece of nvidia software on your pc and reinstalling your gpu drivers, but you need to use DDU and do it from safe mode. Google should have the exact steps if you're interested, because you yourself said other games have crashed before. You also said you recently updated nvidia drivers. Nvidia is notorious for leaving behind pieces of drivers even if you revert.

Thanks for the input, you probably didn't catch it in my wall of text but I did do the DDU thing in safe mode with no luck. At this point I think it somehow corrupted my DX12 files, which apparently you can't reinstall, only the 9 10 11 versions.. I am hoping once I reinstall windows that will fix the problem and Cyberpunk didn't somehow pull a New World (Amazon game debacle) on my GPU.

I apologize I completely missed that! Good luck and keep us posted. You'd think MS would have a DX 12 repair utility somewhere...

The first thing you should do is stress test the GPU. This will tell you if the issue stems from your hardware or if it is merely software corruption.

Download a temperature monitoring program (RealTemp, CPUID, etc. - your choice) and a stress testing program (3D Mark, Paessler, Heaven Unigen, Furmark, or MSI Kombustor).

Open your temperature monitor and watch the temperatures as you stress test the GPU. All modern hardware and GPU's have build in thermal throttles and fail safes that should shut down your computer if they get too hot, but you are welcome to stop the test yourself - a few minutes of stress testing is all you should need.

Pay attention to your average temperatures and note any oddities. All modern graphics cards can safely run up to 95+ degrees Celsius before they start hitting thermal limits. If your card dies or has an error before hitting 95 degrees, it would strongly suggest a fault with the card itself.

If you can run the stress test for 5-10 minutes and experience no instability or anomalies, it is almost certainly a software issue.


Since you've already tried a full driver uninstall with no success, I would suggest reformatting the entire computer. Back up all your important data and then press the Windows Key and "R" at the same time and run "cmd". Then extract your Windows license key by typing "wmic path SoftwareLicensingService get OA3xOriginalProductKey" into command prompt.

Write the license key down and then grab the official installation media for the operating systerm you have from Microsoft. (google "Create installation media for Windows" and pick the first result from Microsoft). During the installation, make sure to delete every partition from your hard drive. This will make sure that you start completely fresh. If there is any corruption of the OS, DX12, or any other driver this method will resolve it. When it asks you for your license key during the install, use the one you extracted in the step above.

Good luck!

tested on Heaven UNIGINE, temps didn't go above 85c.. However In the log for Heaven I get "Direct3D11 error: device hung" could this be caused by corrupted files?

If the hardware is now the problem, it was Cyberpunk that brought it to that point. I keep hearing of this having happened to other people as well, not as many as the amazon new world game fiasco to warrant as much attention though. :(