Shader compilation STILL shuts my PC off

[Sixstrings114]

I know that UE5 and intel dont get along. I have intel I7 14700, 4060TI, 32gb ram. On release, the game ran fine, no crashes, i just turned the graphics down a bit because NVidia wanted to run the game on spaceship mode, put everything to medium-high and i was getting great frames. After first patch is when I started having issues with the Shader compilation just turning off my PC. Not providing an error, not just crashing the game, but causing my CPU to go into danger mode, even though the damn thing has an overbuilt radiator. The Compilation doesn't even hang up, it moves pretty quickly then boop, reboot. I STILL can't play it unless I crash the game while it compiles and reload for the workaround. It's ♥♥♥♥♥♥♥ outrageous that because I have 9 hours in the game, I can't get a refund. I spent money for the ultimate edition on a game I can no longer play.

Like I said, I know Intel 13/14gens dont get along with UE5, but there are plenty of games that have figured it out that I don't have this issue with.

[GlowWorm]

If your machine is rebooting during shader compilation, my first reaction is that your graphics card is pulling too much power from your power supply.

But when you say "causing my CPU to go into danger mode", what do you actually mean by that? Are you watching CPU temperatures or do you see something in particular, or are you just making a guess?

[Whargoul]

Okay, if your PC is just turning off then it's not the game. There are multiple reasons why this could be happening. Some main ones I can think of would be you are either overclocking something or under volting something and your system is unstable. Another would be that your PSU is going bad or you're overdrawing power. Do a google search and research - there are tons of videos to help you. I would try removing any over clocks and reset your bios to default settings to start

[Ernasty]

there's something seriously wrong with your rig.. take a look at the windows event viewer to try and narrow down what part of your system is failing..

[sunflower]

First shader compilation puts 100% load on all your CPU cores. This is like mini stress test. Something is wrong with your PC. There was another topic here, dude had blue screens during shader compilation. He didn't believe he had overheating problem, but after some investigation this was confirmed.

[Crispy™]

Try downloading Core Temp then running it before launching the game. You can turn on Logging in Core Temp (F4 I believe) then check the log after. I think you can even still check the log after the computer shuts itself down or restarts.

If your processor is reaching its T-Junction Max temperature during the shader compilation, then the unit is shutting itself down to protect itself.

[GatorBait]

Yeah, check your event viewer for errors. Mine did this when under stress when my PSU was going bad. System would shut down to protect the CPU.

[Dr.Abscondus]

Read this https://www.pcgamer.com/hardware/processors/intel-cpu-crashes-what-you-need-to-knowmicrocode-to-blame-but-fix-incoming-this-month-alongside-two-year-extended-warranty/ Good luck.

[NoSh0w]

It may not even be an Intel problem. I have AMD, 7900x3d, and occasionally my PC randomly reboots while shader compilation for stalker 2. Terrible bug.

My temps are good, 74c under load. Benchmarks good, plays other games perfectly fine. But I have trouble with UE5 games crashing for whatever reason

[76561197961275394]

Originally posted by GlowWorm:

If your machine is rebooting during shader compilation, my first reaction is that your graphics card is pulling too much power from your power supply.

But when you say "causing my CPU to go into danger mode", what do you actually mean by that? Are you watching CPU temperatures or do you see something in particular, or are you just making a guess?

[Sixstrings114]

It's not actually a hardware or over heating issue. there's nothing "wrong" with my machine. My temps are fine, benchamarks fine. Temps hold in the low 70s C under 100% load. It's not a Power supply issue. It's not a power supply issue, because I would be able to replicate it either on other games that are more demanding or on any benchmarking tool. It's just this game. everything holds even when benchmarking 100% load for both CPU/GPU. The only time it happens is with this game

[WhiteSnake76]

Originally posted by GlowWorm:

If your machine is rebooting during shader compilation, my first reaction is that your graphics card is pulling too much power from your power supply.

Thats my first thought also, underpowered or cheap powersuply.

Originally posted by Sixstrings114:

It's not actually a hardware or over heating issue. there's nothing "wrong" with my machine. My temps are fine, benchamarks fine. Temps hold in the low 70s C under 100% load. It's not a Power supply issue. It's not a power supply issue, because I would be able to replicate it either on other games that are more demanding or on any benchmarking tool. It's just this game. everything holds even when benchmarking 100% load for both CPU/GPU. The only time it happens is with this game

At first you say: "causing my CPU to go into danger mode, even though the damn thing has an overbuilt radiator"
And now you say: "Temps hold in the low 70s C under 100% load"

I sugest you run Prime95 with high memory load and furmark at the same time if you want to see maximum load on your system.

You might want to try one at a time first, if something is wrong with the CPU or your RAM, Prime95 wil not pass the tests at one piont.

Most Benchmarks test one thing maxed out at a time, and dont max out CPU and GPU at the same time.

I never seen Compiling Shaders cause a system crash and reboot, usualy it just hangs, and i takes a while for the system to notice its not doing anything.
Worst thing is what i have seen is that you could not close the game window, or Alt + Tab your way out, and being forced to shut down the system.

[GlowWorm]

Originally posted by WhiteSnake76:

Worst thing is what i have seen is that you could not close the game window, or Alt + Tab your way out, and being forced to shut down the system.

If a game is running in full-screen exclusive mode and becomes "non-response", you might not be able to alt-tab out of it.

But what you CAN do is to set the option in Task Manager (ctrl-shift-esc) for Always on top, and then (if you set the option BEFORE the game hangs) when the game hangs you can bring up Task Manager (ctrl-shift-esc) and find the task in Task Manager and kill it.

(If you don't set Always on top in Task Manager first, you have the same problem as alt-tab - you can launch Task Manager (ctrl-shift-esc) when the game is hung, but you can't SWITCH to Task Manager because the game is hung in full-screen exclusive mode.)

[Consolgamer]

Why people don't maintain their systems is a mystery to me.

[Crispy™]

op, clearly this game is stressing your system beyond what other games are, and you are justified in being frustrated about it.

However, you have to keep in mind that if it truly were a global problem, no one would be able to play or complete the game.

It sucks to have to admit defeat, but maybe the best course of action for you is to get some professional assistance with your rig. If you have a competent computer repair shop in your area, especially one that is gamer-friendly, they'll likely offer the service to isolate the problem for free, or maybe at a reasonable price. As a repair shop, they're going to have access to things like replacement RAM, a bench test power supply, different GPUs, all on-hand, ready to test with.

You either take advantage of this kind of thing or finally isolate the problem on your own, which can get very expensive. Either that or just stop playing the game or wait. It's up to you.

[bkbraptor]

Shader loading is mostly all cpu intensive...if you are overclocked...bump up your core voltage...I had blue screens on shader loading until i bumped up my core voltage a notch.

Hope it helps.

Also...make sure your psu is up to the job.