POE 2 Complete PC Freeze while loading screen

"

Intel users (specifically 13th and 14th gen users) suffering from this issue, I have the solution for probably a large portion of us. The windows version is completely irrelevant. I learned this in the dumbest way possible. I had a lot of friends begging me to attempt to play marvel rivals with them, upon downloading the game a large notification came up on the launcher that informed 13th and 14th gen users that if they are unable to load the shaders without their game crashing, they should download Intel Extreme Tuning Utility and set the Performance Core Ratio down from 55 to either 53 or 52.

I second this solved all my issues

"

RealMarsbar#1169 wrote:

Path of Exile 2 absolutely melts your cpu whenever you are loading into new areas

If PoE 2 melts your CPU you have to fix your cooling system. 100% CPU load doesn't melt anything if you didn;t mess up with your hardware / UEFI setup.

"

cursorTarget#1174 wrote:

"

RealMarsbar#1169 wrote:

Path of Exile 2 absolutely melts your cpu whenever you are loading into new areas

If PoE 2 melts your CPU you have to fix your cooling system. 100% CPU load doesn't melt anything if you didn;t mess up with your hardware / UEFI setup.

Not to be that guy — but for many Intel users, the board defaults are completely incorrect.

My MSI z690 board defaults my 13600K to:
- 288W TDP on a 181W chip
- insane draw power limits for long/short workloads: whatever the wattage max is (288). Intel default is 125/181.
- Massive voltage (line limit 18!!). My 13600K is stable at mode 5.

It’s like they’re trying to fry your chip.

For folks implying this is a windows thing: I’ve never been a windows user and aim to keep it that way. I can imagine there may be a separate issue there — but by and large it’s becoming more clear to me that Path of Exile 2 is exposing other issues potentially unrelated to the game. It is, after all, not GGG’s fault that MSI (and others) have lost their minds when it comes to picking sensible hardware defaults. It’s not exactly any developer’s fault that otherwise valid calls would be crashing on unstable hardware; implicit upstream dependencies.

For those that may be experiencing issues: go to Act 2, walk up to your stash and wait 15 minutes. Did you crash? Did your computer reboot? Congrats, you’ll likely have to verify your BIOS settings.

"

cursorTarget#1174 wrote:

I am (from 1999, atm working on time critical systems in AMTSS). I can't reproduce the bug on my end on three different Linux machines including several VMs with Windows + PCI Passthrough. There is/are definitely very specific condition(s) which trigger(s) the freeze. I have to install Windows on real machine and acquire debug symbols for the executable and sys, but NVIDIA doesn't provide the symbols for all their modules. Making workaround like proxy / shim DLL / SO is a bad approach and doesn't fix the problem.

I already told you, the roots lay WAY more deeper than you even can imagine. Working with just mdumps and some symbols will take WAY more time than working with complete environment having source code and PDBs available.

Of course. I wasn't quite aiming to fix the real problem (which is surely way deep into the Windows scheduler with internal locking/spinning during syscalls, somehow).

But people have reported that the problem completely disappears if the option for multithreading engine is disabled. That leads me to assume that serializing all Vulkan calls during loading would also avoid triggering the Windows bug. You would never get that kind of system freeze with user-land threads, so they are stuck in the kernel, in the syscalls behind Vulkan calls. So just allow one of them through at a time, a simple hack that would get the job done (ideally, only serializing a tiny subset of Vulkan calls, mostly related to buffer mapping/copying during area loading).

I have the same problem, Windows 11 pro, loading screen freezes entire PC and crashes it. Has there been some fix for windows yet?

when will they ever fix this shit ? Do we have to wait for microsoft's new windows update or the game devs ?

Just try this guys, this seems to be the best solution atm for me.

POEUncrasher
https://github.com/Kapps/PoEUncrasher/releases

I'm not sure it will be fixed but I played for 10 hours and it went smoothly.

"

kinglucifer#0490 wrote:

Just try this guys, this seems to be the best solution atm for me.

POEUncrasher
https://github.com/Kapps/PoEUncrasher/releases

I'm not sure it will be fixed but I played for 10 hours and it went smoothly.

This fixed it for me Running an older CPU and GPU on 24H2

Ryzen 5600x and 2060 Super

No temp problems here..

Resetting the Nvidia control panel settings to default values ​​(a separate preset for the game) solved the freezes in my case. Disabling multithreading in the game also solves the problem, but I don't like this option.
i3 12100/RTX4060/32Gb RAM/PCI-E SSD/Win11 24H2

Hello everyone. I have read over 50 pages of this discussion. I have 7700 + 4080 super. Of course, I also encountered freezes, and at first I thought about PBO and undervolt risen, until I came across this branch.

What is most surprising is that no one has ever written about consumption at the moment of freezing. And I think that's the reason. CPU consumption goes beyond the prescribed limits, which are prescribed in the motherboard. At the moment, I have 108vat. CPU consumption alone goes up for 115+. In any stress data, the parameter is strictly limited. But not in POE2.