Hard crashing PC locks up

Whew! This morning I woke up from a nightmare where my computer literally caught on fire and started spewing smoke while playing PoE2. That was a real dream. I'm not just saying that to be funny or whatever. It's really sad considering where my priorities are, but hey, at least my system is still functioning.

"

interbeing#5112 wrote:

Whew! This morning I woke up from a nightmare where my computer literally caught on fire and started spewing smoke while playing PoE2. That was a real dream. I'm not just saying that to be funny or whatever. It's really sad considering where my priorities are, but hey, at least my system is still functioning.

100% CPU load, can work non stop for months. How is it possible without melting down?

"

I have had some good success with an app called Process Lasso. You can use this to specifically set a rule for the PoE2 process to drop to IDLE priority and unassign 2 cores if the CPU usage rises above 95% for a second, and then remain at IDLE for say, 10 seconds. And then resume normal processes.

Find the tool here: https://bitsum.com/

To do this:

* Open Options, CPU Limiter
* New CPU Limit Rule:
Process match: pathofexilesteam.exe
When CPU use is: 85%
For a period of: 1 seconds
Reduce by this many cores: 2
For a period of: 10 seconds.

I also use ProBalance settings:
Advanced/
Leave all settings except:

Lower to idle priority instead of below normal: Ticked
Ignore all foreground processes: Unticked
Change affinity during restraint: Ticked
CPUs: 2-15 (or how many cores you have, just ensure you start at core 2)

This has immediately solved the issue for me - and it even decreases load time dramatically as well. Any tool that can reduce the CPU priority and remove cores will probably work, but this can be done on a rule basis per running process.

Of course, I cannot say if this is guaranteed to work for everyone. But I can say I've had hardlocking constantly, and I've now been able to play for 5 hours continuously. Except for one REALLY off bug that may be a server issue (says my controller is unplugged then dumps me back to the login screen).

This seems to have worked for me. Loading screens are notably smoother and quicker without the suspenseful hitching that would come before the crash.

I'm going to try re-enabling dx12 and turning my settings back up since I turned them all the way down. My CPU was running at about 45-50% load and GPU at 65% load while playing but I was still crashing every 1.5 hours give or take 30 mins.

It almost felt like it was a certain number of zone changes but I wasn't counting. Also seemed to occur when I would be heading back out from camp.

"

zumocano#9039 wrote:

"

I have had some good success with an app called Process Lasso. You can use this to specifically set a rule for the PoE2 process to drop to IDLE priority and unassign 2 cores if the CPU usage rises above 95% for a second, and then remain at IDLE for say, 10 seconds. And then resume normal processes.

Find the tool here: https://bitsum.com/

To do this:

* Open Options, CPU Limiter
* New CPU Limit Rule:
Process match: pathofexilesteam.exe
When CPU use is: 85%
For a period of: 1 seconds
Reduce by this many cores: 2
For a period of: 10 seconds.

I also use ProBalance settings:
Advanced/
Leave all settings except:

Lower to idle priority instead of below normal: Ticked
Ignore all foreground processes: Unticked
Change affinity during restraint: Ticked
CPUs: 2-15 (or how many cores you have, just ensure you start at core 2)

This has immediately solved the issue for me - and it even decreases load time dramatically as well. Any tool that can reduce the CPU priority and remove cores will probably work, but this can be done on a rule basis per running process.

Of course, I cannot say if this is guaranteed to work for everyone. But I can say I've had hardlocking constantly, and I've now been able to play for 5 hours continuously. Except for one REALLY off bug that may be a server issue (says my controller is unplugged then dumps me back to the login screen).

This seems to have worked for me. Loading screens are notably smoother and quicker without the suspenseful hitching that would come before the crash.

I'm going to try re-enabling dx12 and turning my settings back up since I turned them all the way down. My CPU was running at about 45-50% load and GPU at 65% load while playing but I was still crashing every 1.5 hours give or take 30 mins.

It almost felt like it was a certain number of zone changes but I wasn't counting. Also seemed to occur when I would be heading back out from camp.

this does liter1ally nothing for me on my 7800X3D and 4090. still hard freezes. except now, it freezes 100% of the time i try to leave camp. i can no longer play this until proper fix is patched. i'm not hard resetting my hardware a few thousand times more until it's fixed. unless GGG is paying me for a entire new setup. which i kinda doubt.

and if this issue is as wide spread as it seems, how was this not addressed earlier in development? the game is advertised as "early access", not a Beta. a "beta", i could understand a few big things like this to crop up. not in EA. EA implies that we are playing the game before all the content is there, but what IS there is playable and working.

and i just got to act 3 on my witch, which makes it more annoying!

"

cursorTarget#1174 wrote:

"

MightoBoy#0452 wrote:

you can also wait and not risk your processor

There is no risk to your processor unless you're using shitty components and have bad cooling. Processors are designed to work at 100% load.

Why are you still spreading misinformation here?

"Processors are designed to work at 100% load" oversimplifies the design and operational philosophy of processors. Modern processors are engineered to handle full utilization of their computational resources for periods without failure, as long as the system's cooling, power delivery, and thermal management are adequate. BUT the part you are not telling is that sustained operation at 100% load is not ideal because processors are not intended to operate at 100% load continuously. "Sustained Operation" and "for periods" here are Short-Duration Full Load situations, which is at most a few minutes. This still causes shortened component lifespan even with ideal conditions, especially if the burst periods are extended/back-to-back or the situation exceeds the short-duration timeframe.

Specialized systems can handle thermal problems as long as one designed/built their PC well. Laptops, budget PCs, or general public PCs DO NOT satisfy this condition. A server-grade processor/server processor with good thermal design can work for days in 100% state. But household PCs are not in this category.

A regular PC with decent components is not built to handle its processor to work at 100% load.

The processors that are not specialized for 100% load will suffer from shortened component lifespan when run at 100% beyond short-bursts with adequate time in between them.

You keep coming here to degrade people with your half-baked semi-applicable knowledge. Please stop this behaviour. There are people in this world that cannot afford to replace their components if they break, and misleading people into believing a risky situation is not, is malicious.

To anyone who is still trying to play the game with regular crashes: Please know that you are risking your PC. While the probability is low, it can happen. So do not play the game until a fix is made if you cannot afford to replace the parts that get broken.

"

dethsight#7519 wrote:

"

zumocano#9039 wrote:

"

I have had some good success with an app called Process Lasso. You can use this to specifically set a rule for the PoE2 process to drop to IDLE priority and unassign 2 cores if the CPU usage rises above 95% for a second, and then remain at IDLE for say, 10 seconds. And then resume normal processes.

Find the tool here: https://bitsum.com/

To do this:

* Open Options, CPU Limiter
* New CPU Limit Rule:
Process match: pathofexilesteam.exe
When CPU use is: 85%
For a period of: 1 seconds
Reduce by this many cores: 2
For a period of: 10 seconds.

I also use ProBalance settings:
Advanced/
Leave all settings except:

Lower to idle priority instead of below normal: Ticked
Ignore all foreground processes: Unticked
Change affinity during restraint: Ticked
CPUs: 2-15 (or how many cores you have, just ensure you start at core 2)

This has immediately solved the issue for me - and it even decreases load time dramatically as well. Any tool that can reduce the CPU priority and remove cores will probably work, but this can be done on a rule basis per running process.

Of course, I cannot say if this is guaranteed to work for everyone. But I can say I've had hardlocking constantly, and I've now been able to play for 5 hours continuously. Except for one REALLY off bug that may be a server issue (says my controller is unplugged then dumps me back to the login screen).

This seems to have worked for me. Loading screens are notably smoother and quicker without the suspenseful hitching that would come before the crash.

I'm going to try re-enabling dx12 and turning my settings back up since I turned them all the way down. My CPU was running at about 45-50% load and GPU at 65% load while playing but I was still crashing every 1.5 hours give or take 30 mins.

It almost felt like it was a certain number of zone changes but I wasn't counting. Also seemed to occur when I would be heading back out from camp.

this does liter1ally nothing for me on my 7800X3D and 4090. still hard freezes. except now, it freezes 100% of the time i try to leave camp. i can no longer play this until proper fix is patched. i'm not hard resetting my hardware a few thousand times more until it's fixed. unless GGG is paying me for a entire new setup. which i kinda doubt.

and if this issue is as wide spread as it seems, how was this not addressed earlier in development? the game is advertised as "early access", not a Beta. a "beta", i could understand a few big things like this to crop up. not in EA. EA implies that we are playing the game before all the content is there, but what IS there is playable and working.

and i just got to act 3 on my witch, which makes it more annoying!

With Lasso or Shirase you should be able to avoid the hard freeze since there will be processors available for the system itself. The game would freeze, but since your system still has resources that the game cannot use (because you blocked PoE2 from accessing them) you should be able to Ctrl+Alt+Del and kill PoE2.

(If you are playing in a window setting that stops windows from rendering on top of the game, switch out of it for the remainder of this crash problem, it might be stopping you from accessing the Task Manager.)

"

Cainrith#2807 wrote:

because processors are not intended to operate at 100% load continuously.

Prove it with official datasbeets from official websites (intel, amd, etc). Everything else is considered your personal fantasies.

"

Cainrith#2807 wrote:

A regular PC with decent components is not built to handle its processor to work at 100% load.

OMG what a bullshit statement here.

You're just accepting the fact it's ok for you to buy trash components and this is sort of "normal" when some of the fail. Dis thread is full of disinformation from people like you. Whey...

"

Daldonie#5305 wrote:

Dis thread is full of disinformation from people like you.

He's right in terms of probability if some component will fail. So there is a reason to use server hardware for better sustain. But in general we have a lot of PCs working at 95-100% load without issues in the envelope defined by the official data sheets. Back in the days it was a standard to stress test the new PC hardware at full 100% load for 2-4 weeks without restart. But in our specific case some users complain their CPU can't handle even 1-3 minutes of 100% load. So it's way far from what can and what can't be done with normal PCs.

PS please relax, you're talking to troll.

POE2 is hoarding all CPU sources that it bricks the whole PC INCLUDING the tool that is observing its behavior.

Imagine saying that people should feel okay stress testing their pc for nothing. Completely unhinged