POE 2 Complete PC Freeze while loading screen

"
mkdr#2100 wrote:
I already wrote a week ago on here, the total pc lock-up issue during loading screens is mostly related to Windows 11 24h2 and the new CPU scheduler which came with 24h2. The new schedulder was back ported to 23h2 with this optional update, so everyone who installed it on 23h2 mostly also has the same issue. read about that optional update here. If youre on 23h2 and have total lock-ups of your PC during loading screens, see if you have installed kb5041587 and remove it. though it could also be true, the optional update was already implemen

https://www.reddit.com/r/pcmasterrace/comments/1f383k8/you_dont_need_24h2_for_the_amd_update_it_has_been/

https://arstechnica.com/gadgets/2024/08/ryzen-speed-boosts-get-backported-to-windows-11-23h2-with-optional-update/

https://support.microsoft.com/en-us/topic/august-27-2024-kb5041587-os-builds-22621-4112-and-22631-4112-preview-9706ea0e-6f72-430e-b08a-878963dafe08

People laughed at me and said at that time I was spreading false information, where at that time it was already clear, the issue has nothing to do with POE2. POE2 seems just to be a catalyst for the issue to occur. A friend of mine had the same lock-up issue on 24h2 with Eve Online when he used 6 instances of the game (multiboxing). Going back to 23h2 with no optional updates totally fixed the issue for him.

Then there is the problem, that people seem to mix different issues all into one cup.

- 24h2 cpu scheduler total pc lock-up issue (can be resolved by going back to 23h2 with no optional updates), can be mitigated by setting CPU affinity -2, which will prevent total pc lock-up, POE2 freezes might still occur, which can be unstuck though with the trick setting process to realtime for a moment (PoEUncrasher does that automatically in the best case)

- other PC instabilities, like overclock, undervolt, voltage issues, driver issues etc, game crashes or BSOD might occur

- dx12 instabilities, changing to Vulkan might fix crashes, no total PC lockup

- other game bugs which lead to game crashes, no total PC lockup

Anyway, I have written to a developer working at Microsoft to look into the issue with the 24h2 CPU scheduler, and he was kind to open a bug report at MS for it. So it might be looked into it, yet just in the new year after the holidays.

GGG should also get in contact with Microsoft, and maybe send them some code example from the loading mechanic of the game, so MS can identify, whats wrong with the CPU scheduler causing the total PC lock-up issue under this specific work load.


People laughed at you because there's people on linux with the same issue. The latest one I read was having it on Nobara distro.
@Elenher No proof of that so far. Mostly something totally different. If that was the case, it would indicate a fundamental problem with (some) Ryzen CPUs which I dont believe is true. Fact is, the CPU scheduler has a bug in Windows 11 24h2, either in combination with some Ryzen CPUs, or some other so far unknown relationship. A game shouldnt be able to lock-up the entire OS even if it crashes or is stuck in a 100% cpu use loop. The kernel/CPU scheduler should prevent total PC lockup => bug in Windows which needs to be addressed anyway.
Last edited by mkdr#2100 on Dec 21, 2024, 9:33:31 PM
For 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 originally ignored this, attempted to download the shaders, and the game crashed. Afterwards, I attempted one final time and my screen froze up exactly as it did after loading instances in POE 2 maps. I immediately downloaded the Intel tool, changed my performance core ratio to 52, and the game ran as smooth as butter. The next day, I figured I could try POE 2 again and boom. It's running perfectly smooth on max graphics. I have minimized, opened up other applications, and streamed the game without a single crash for the last two days.

I wish I understood more about computers because Path of Exile 2 absolutely melts your cpu whenever you are loading into new areas (albeit for maybe two seconds). Please if you are an Intel user try this and see if it works. You may have to reopen the tool every time you turn on your PC but once it is on, you should have no issues.
Last edited by RealMarsbar#1169 on Dec 21, 2024, 9:42:05 PM
"
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
"
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.
"
"
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.
Last edited by hesham8#4339 on Dec 22, 2024, 12:56:29 AM
"
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.

Report Forum Post

Report Account:

Report Type

Additional Info