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

[#1KanekiHater]

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?

[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

[Ih8myjob]

Originally posted by 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?

If you're on a 13 or 14 gen intel and haven't updated your bios to one with the 0x125 or newer microcode I've got some bad news for you. Your cpu is probably damaged.

You can still update it, and I'd suggest doing that, then I'd suggest immediately rmaing it because it's been overvolted, even if you've manually undervolted it.

Even if updating resolves the issue, please still rma it, because it is likely damaged and its longevity is at best uncertain and at worst already going downhill.

[BreakTheLaw]

yeah it happened to me for one of cutscenes after a boss fight
tried everything but nothing worked except skipping the cutscene

[#1KanekiHater]

Yep, certainly do have a 13th gen. Thanks for the info, will update the bios and hope mine isn't ruined already

[Saru]

Originally posted by BreakTheLaw:

yeah it happened to me for one of cutscenes after a boss fight
tried everything but nothing worked except skipping the cutscene

If it's the one after typhon then I'm having the same issue.

[dlux]

Originally posted by Edgewater:

Yep, certainly do have a 13th gen. Thanks for the info, will update the bios and hope mine isn't ruined already

If that doesn't help, then the CPU is already damaged and it is permanent. Underclocking might help though.

[Kaziedell]

Originally posted by Kaziedell:

also if anyone has the "The GPU will not respond to more commands" issue
i think i just found the cause. I got it after upping my gpu clock to +100 on firestorm / asus gpu tweak/ afterburner
seems to be tied to overclock configurations

I think i just found out the cause of this specific issue

[Kaziedell]

ran the game for around 18 hours without this problem and got it after rising gpu clock +100 on zotac firestorm

[#1KanekiHater]

That seemed to be the fix! Updated bios, haven't had a single crash since. Thanks for the help y'all

Just gotta hope mine wasn't horribly damaged x.x

[Ih8myjob]

Originally posted by Edgewater:

That seemed to be the fix! Updated bios, haven't had a single crash since. Thanks for the help y'all

Just gotta hope mine wasn't horribly damaged x.x

Since you ran on a bios with the bad microcode, rma your cpu.

Intel is being pretty cool with rmas. If you purchased a prebuilt contact the mfg, they should do it too. It's very likely your cpu, even though it seems like it's ok, is in fact damaged.

Do not wait, do not give it the ole "well it's fine now so why bother", get it replaced. It should cost you nothing, and that cpu is more likely than not damaged and already on its way to a premature death, whether you can tell or not.

Some people are even getting upgrades (for free) if intel doesn't have their cpu in stock.

I had to rma 3, 2 were showing signs of damage (what you described is a sign), 1 seemed fine, but was still replaced since it had ran on a bios that didn't have the INSANELY IMPORTANT microcode update.

[Red Hefner]

Originally posted by Ih8myjob:

Originally posted by 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?

If you're on a 13 or 14 gen intel and haven't updated your bios to one with the 0x125 or newer microcode I've got some bad news for you. Your cpu is probably damaged.

You can still update it, and I'd suggest doing that, then I'd suggest immediately rmaing it because it's been overvolted, even if you've manually undervolted it.

Even if updating resolves the issue, please still rma it, because it is likely damaged and its longevity is at best uncertain and at worst already going downhill.

Let's not get crazy.

Let them update the BIOS, if it works then no reason to panic.

I've been running my 13900k with various different BIOS versions and a 1-1.2 UV since day one, no issues.

Do intel even have a policy of accepting returns on these CPU's?

[Ih8myjob]

Originally posted by Red Hefner:

Originally posted by Ih8myjob:

If you're on a 13 or 14 gen intel and haven't updated your bios to one with the 0x125 or newer microcode I've got some bad news for you. Your cpu is probably damaged.

You can still update it, and I'd suggest doing that, then I'd suggest immediately rmaing it because it's been overvolted, even if you've manually undervolted it.

Even if updating resolves the issue, please still rma it, because it is likely damaged and its longevity is at best uncertain and at worst already going downhill.

Let's not get crazy.

Let them update the BIOS, if it works then no reason to panic.

I've been running my 13900k with various different BIOS versions and a 1-1.2 UV since day one, no issues.

Do intel even have a policy of accepting returns on these CPU's?

Panic no, and rmaing a cpu that they released in a crap state isn't crazy, it's common sense. It's VERY likely it's damaged, and BEST case it's severely degraded, and its life span has been shortened significantly.

Yes intel has a policy and is accepting rmas for just about all of them, because its a HUGE issue.

Google it. You should do the same and rma yourself.

Even manually undervolted, the cpu was pulling way more voltage than it's rated for prior to x125. No matter what you did, what configs you set,it was happening. Its not a secret. It's not hidden. They know it. They've admitted it, and they're making it right as long as the consumer takes action (rma).

The simple fact you responded the way you have shows you dont pay attention to your voltages, and def don't keep an eye on the happenings of cpus, which is fine, but you shouldn't be giving any advice on something you arent familiar with.

[Red Hefner]

Originally posted by Ih8myjob:

Originally posted by Red Hefner:

Let's not get crazy.

Let them update the BIOS, if it works then no reason to panic.

I've been running my 13900k with various different BIOS versions and a 1-1.2 UV since day one, no issues.

Do intel even have a policy of accepting returns on these CPU's?

Panic no, but odds are its damaged.

Yes intel has a policy and is accepting rmas for just about all of them, because its a HUGE issue.

Google it. You should do the same and rma yourself.

Even manually undervolted, the cpu was pulling way more voltage than it's rated for prior to x125. No matter what you did, what configs you set,it was happening. Its not a secret. It's not hidden. They know it. They've admitted it, and they're making it right as long as the consumer takes action (rma).

The simple fact you responded the way you have shows you dont pay attention to your voltages, and def don't keep an eye on the happenings of cpus, which is fine, but you shouldn't be giving any advice.

There's no need to be so blunt, i simply stated that the users CPU may be fine, we don't know their daily use or how often they were pulling too much voltage or what programs they were running or how often they were using it.

Admittedly i don't know every single detail regarding the issues with 13th and 14th gen CPU's, but i knew about the voltage issues, knew about the various BIOS updates and knew that Intel decided against a recall but i didn't know they were accepting RMA's.

It's good that they are but i have no intention of going through a lengthy RMA process to fix something that doesn't appear to need fixing at this point and i'm confident that my 13900k will last until i need to upgrade or build a new PC in years to come.

And i do keep an eye on my CPU and what it's doing, since i built my PC last year i've had an undervolt applied, multi-core enhancement off, Windows is always set to balanced power plan and had my fans set accordingly, temps are always healthy and i've had no reason to be concerned with the performance or stability of my CPU, i get next to zero crashes (the only crashes i've ever had related to the CPU have been benchmarking to get a stable undervolt) and i keep all my drivers up to date.

Think my point is it's not a black and white issue, not everyone who's ran an old BIOS version on these CPU's is going to have a guaranteed hardware failure, it depends on daily use and the users ability to maintain their own PC effectively.

[Ih8myjob]

Originally posted by Red Hefner:

Originally posted by Ih8myjob:

Panic no, but odds are its damaged.

Yes intel has a policy and is accepting rmas for just about all of them, because its a HUGE issue.

Google it. You should do the same and rma yourself.

Even manually undervolted, the cpu was pulling way more voltage than it's rated for prior to x125. No matter what you did, what configs you set,it was happening. Its not a secret. It's not hidden. They know it. They've admitted it, and they're making it right as long as the consumer takes action (rma).

The simple fact you responded the way you have shows you dont pay attention to your voltages, and def don't keep an eye on the happenings of cpus, which is fine, but you shouldn't be giving any advice.

There's no need to be so blunt, i simply stated that the users CPU may be fine, we don't know their daily use or how often they were pulling too much voltage or what programs they were running or how often they were using it.

Admittedly i don't know every single detail regarding the issues with 13th and 14th gen CPU's, but i knew about the voltage issues, knew about the various BIOS updates and knew that Intel decided against a recall but i didn't know they were accepting RMA's.

It's good that they are but i have no intention of going through a lengthy RMA process to fix something that doesn't appear to need fixing at this point and i'm confident that my 13900k will last until i need to upgrade or build a new PC in years to come.

And i do keep an eye on my CPU and what it's doing, since i built my PC last year i've had an undervolt applied, multi-core enhancement off, Windows is always set to balanced power plan and had my fans set accordingly, temps are always healthy and i've had no reason to be concerned with the performance or stability of my CPU, i get next to zero crashes (the only crashes i've ever had related to the CPU have been benchmarking to get a stable undervolt) and i keep all my drivers up to date.

Think my point is it's not a black and white issue, not everyone who's ran an old BIOS version on these CPU's is going to have a guaranteed hardware failure, it depends on daily use and the users ability to maintain their own PC effectively.

Its very much a black or white issue. If you'd take a few minutes to do a little research you'd know that.

Did you run on a pre 0x125 mc bios? rma because the cpu has been run under conditions that will cause it harm, at the MINIMUM shortening it's lifespan noticeably, and they will accept the rma.

If you didnt, you're good.

Can't get more black or white than that.


Even if the Cpu seems fine now, the likelihood of it actually being fine is almost 0. You can't test to see if the lifespan has been degraded,or if it will lose stability in 12 months. These are the things that WILL happen if it was run, even under minimal conditions pre 125.

If you want to be the one who says it's fine, screw it, cool, but don't tell others not to worry about it. It is a problem, and odds are they won't accept rmas with open arms for a super long period of time.

[Zero_Blazer]

Originally posted by Saru:

Originally posted by BreakTheLaw:

yeah it happened to me for one of cutscenes after a boss fight
tried everything but nothing worked except skipping the cutscene

If it's the one after typhon then I'm having the same issue.

Exact same problem, only for this specific boss. It's so dumb, I don't know what to do

Edit:Its working good, just get the github fix, newest driver which should be the 24.10 one and also edit the github int file for frame generation during cutscenes to be false.