Constant crashing - "The gpu will not respond to more commands"

[Edgewater]

I keep randomly crashing, be it in cutscenes or out of them. I get that error a lot, or I get "The gpu device instance has been suspended"

Currently using a 4090, and I have the most recent graphics driver installed. I tried installing an earlier version, but it didn't work. I've also validated the game files, but nothing.

Anyone else running into this or have a fix?

[Kaziedell]

and I also found out it happens with certain overclock configs, not all
I was able to overclock my 4060 to 3000 mhz but if I do 2950 or 3050 the game crashes with the same error

same with my R5 3600 if I run it stock 4.0 GHz or default overclock setting at 4.2 the game runs but any other clock speed makes it crash

[javimegar]

When does the AMD Software: Adrenaline Edition update to version 24.10.1 arrive? Today I received the update to version 24.9.1, but we need version 24.10.1 to fix the bug.

[Tr0w]

Originally posted by Just Fkin Ryan:

i remember this happening to asmon on stream when he was playing wukong on a 13th/14th gen cpu, could be that, try updating your bios if you have one of those CPUs

Happened to me 3 or 4 times and i'm using a 5800X3D with the latest bios for my mobo

[DiscoZombie]

I'm getting this crash and I don't have an Intel processor, so it's not the BIOS issue, I've got an AMD Ryzen 7800 and video card is GeForce RTX 4070. It happens infrequently enough that I was able to finish the main game after plenty of frustrating crashes, but frequently enough that I can't get through Kairos Gate since there are no checkpoints. I'm about to give up.

[painkiller1607]

I have played 30 Hours without any Problems, but now after i beat the Bahamut in the big Bossfight the Games Freezes/Crush very often.
Most time it freeze when i use Fast-Travel on the Map, so i click on the location i want to Fast-Travel an then Freeze the Game on the Loading-Screen and i must use Task-Manager to kill the Game.

I have an Ryzen 7 7600X, RTX 4070Ti, 32GB RAM and the Game on a 2 TB KC3000 SSD

[javimegar]

painkiller1607, be careful with spoilers, I recommend that you edit your post.

[Ten'nō Yamato]

I have the same problem, also on the 4090. The processor is Intel, 14700k, but I tend to assume that the problem is not in it. 1) Crashes only in this game. 2) I had crashes only and exclusively during cutscenes. In addition to this, in the error message I do not have any code by which I could determine what exactly the problem is.

In some old topics I came across the fact that this error occurs due to high video card frequencies, sometimes due to a memory leak (24 GB is not enough lol), but I did not find any confirmation of this either. So perhaps the problem is in the drivers or in the game itself. By the way, all mentions of this problem were with the 40th series of video cards (at least I did not come across others).

[aweigh]

since you mentioned it happens during cutscenes have you tried using the cutscene FPS unlocker fix mod? maybe it might fix something related to what's happening.

[Ten'nō Yamato]

Actually, I think it's because of this problem. But since it's not that critical (although I would like more checkpoints between cutscenes), I didn't change anything.
I use this fix github com/Lyall/FFXVIFix
Without this fix it's really painful for me to play FF16.

[Ten'nō Yamato]

In general, I did something. Switched the game to fullscreen mode. In the ini file of the mod for FPS in cutscenes, I put the following data in the last lines. Over the last 4 hours of the game, I have not had a single crash yet.

[Remove 30FPS Cap]
; Set "Enabled" to true to disable 30FPS cap in cutscenes/photo mode.
; Alternatively, set "Enabled" to false and enter a desired framerate to limit cutscene framerate.
; Remember that this framerate value is set before frame generation so set half of your desired framerate if using cutscene frame generation.
Enabled = true
Framerate = 110

[Cutscene Frame Generation]
; Set "Enabled" to true to permit frame generation during real-time cutscenes.
Enabled = true

Data from the FFXVIFix.ini file (this is at the very end).
[Disable Graphics Debugger Check]
; Set "Enabled" to true to disable graphics debugger check.
; Can help with performance issues on Linux machines.
Enabled = false
Maybe this will help someone.

[iameatingjam]

You might have a degraded cpu. A bios update MIGHT help if you caught it early enough. But you might have to do rma if it doesn't help. Good news is rma is pretty easy since intel knows there's been problems. They are overloaded, thats for sure, but you will get a replacement. There's been a cross-ship program, but it'll cost you $25.

I also got the 'suspended gpu' error when I was undervolting my gpu and went too far, so if are undervolting or overclocking your gpu, stop it, or at least, turn it down a little.

[Ten'nō Yamato]

Originally posted by iameatingjam:

You might have a degraded cpu. A bios update MIGHT help if you caught it early enough. But you might have to do rma if it doesn't help. Good news is rma is pretty easy since intel knows there's been problems. They are overloaded, thats for sure, but you will get a replacement. There's been a cross-ship program, but it'll cost you $25.

I also got the 'suspended gpu' error when I was undervolting my gpu and went too far, so if are undervolting or overclocking your gpu, stop it, or at least, turn it down a little.

Perhaps, before writing a reply, it was worth reading the messages above :)

[beussta]

i played fine 60 hours FF16 without no error and today suddenly i have this message error, i had this 3 times in 30 min

nothing changed on my pc, it happens only on this game

wtf

[Ten'nō Yamato]

Just forget it, it's a problem with this game that, apparently, will never be fixed. Stories about it being due to "degradation" of Intel processors, etc. are nonsense.

[Ih8myjob]

Originally posted by Ten'nō Yamato:

Just forget it, it's a problem with this game that, apparently, will never be fixed. Stories about it being due to "degradation" of Intel processors, etc. are nonsense.

no, they arent. I have 3 13900k systems, each, after updating the bios after the microcode update was pushed and RMA'ing them, it works fine.

Neat right?