POE2 Win11 24H2 Crashes - Constant crashing, >100% CPU usage, and more

same here.. 7800x3d and 3060, on w11 24h2.. when the game arrives to 100% cpu (idk why) the pc freezes completely and i should reset with the button

"

tsamolotoff#0248 wrote:

Personally I have not encountered this issue (but I also have a beefy custom loop water cooling system and extensively tested my CPU for stability), but I've noticed that temperature shots up quite high for a game (80+ ish Celsius peak temps) while starting the game or on loading shaders /assets. Probably the people who have crashes and freezes need to check up their system stability with prime95/linpack etc, repaste their CPUs and do other checkups.

It's not system stability. My system (7800X3D / 64GB 6400MT / 4090 / Win11 24H2) on open loop water cooling survives a 24 hour Prime95/Furmark loop (max temps 75C CPU and 65 GPU) and it crashed several times a night playing PoE2.

This is not a system stability issue. This is not a Windows issue.

The way PoE2 crashes, the workarounds that somewhat works, and the dxdiags imply that the issue is improper usage of system APIs by the PoE2.

PoE2 has a command in its code that tries to use something that it should not be using.

This not a Version problem. 23h2 does not work. Random people are not crashing anymore when downgrading but this has to be because of something else underlying because for the majority this does not work.

"

WolfeAndedare#6437 wrote:

This not a Version problem. 23h2 does not work. Random people are not crashing anymore when downgrading but this has to be because of something else underlying because for the majority this does not work.

False. If it was a majority, this thread would be a lot bigger. Also my problem immediately fixed after I went back to 23H2 and then came back immediately when updating to 24H2. If you are still having issues on 23H2, it's likely because you are overclocking, or your CPU is configured incorrectly.

"

SmugJay#5477 wrote:

"

WolfeAndedare#6437 wrote:

This not a Version problem. 23h2 does not work. Random people are not crashing anymore when downgrading but this has to be because of something else underlying because for the majority this does not work.

False. If it was a majority, this thread would be a lot bigger. Also my problem immediately fixed after I went back to 23H2 and then came back immediately when updating to 24H2.

False. There are reports from every kind of Windows versions here, we all crash.

"

Cainrith#2807 wrote:

"

SmugJay#5477 wrote:

"

WolfeAndedare#6437 wrote:

This not a Version problem. 23h2 does not work. Random people are not crashing anymore when downgrading but this has to be because of something else underlying because for the majority this does not work.

False. If it was a majority, this thread would be a lot bigger. Also my problem immediately fixed after I went back to 23H2 and then came back immediately when updating to 24H2.

False. There are reports from every kind of Windows versions here, we all crash.

This happens in PoE1 as well and only on 24H2. 24H2 also broke a ton of other games outside of PoE. It is a problem with the update. If you are crashing on 23H2, change your voltage or stop overclocking.

"

SmugJay#5477 wrote:

This happens in PoE1 as well and only on 24H2. 24H2 also broke a ton of other games outside of PoE. It is a problem with the update. If you are crashing on 23H2, change your voltage or stop overclocking.

This is not a system stability issue. This is not a Windows issue.

The way PoE2 crashes, the workarounds that somewhat works, and the dxdiags imply that the issue is improper usage of system APIs by the PoE2.

PoE2 has a command in its code that tries to use something that it should not be using.

You should see the two threads with >3.5k replies in this forums. We tried everything there. It is a PoE issue.

Btw linux also crashes:

"

a1902g#4000 wrote:

This problem occurs not only on Windows.
I tried to install Linux Mint 22, the game started and the computer froze.
I can only assume that the problem is related to the processor

- 5700x
- 3070
- 32 Gb
(Linux mint 22(NV driver 550 )/Windows 11 (23H2/24H2, nv driver 566.36))

This is a Linux-Win11-23H2:

"

Ranguvar#5016 wrote:

Same issue here on 23H2. I have a pretty crazy setup with virtualized Windows 11 stripped down / spyware removed, running on top of a Linux host, with an RTX 3090 GPU, an NVMe SSD, and a USB controller passed directly to the VM.

I'm using a 5950X with 6 cores from one of the two 8-core CCDs directly passed to the VM, so 12 virtual cores.

The game freezes, then the cursor and all of Windows, every few hours.
I hard reset the VM to get it back, sometimes a few times to get the GPU to reset properly from its bugged state, and then it's good for a few hours again.

Nothing in the client log.
This did not happen in either closed beta phase I participated in that I recall.
Testing Vulkan instead of DX12 now, might try removing Steam Overlay also.

Hope this gets high priority.

Please keep this thread alive. All the years I've been playing this game, I've never had this issue so prevalent.

GGG, please respond. The game isn't enjoyable to play with the constant freezing.

EDIT: POE1 and POE2 both constantly freeze.

@GGG
Please consider adding an option to disable multithreading before loading zones. Disabling multithreading is the only workaround that solves the problem entirely, but remembering to do it or accepting the FPS loss is annoying.

For me the workaround has been the following:

1. Disable multithreading in the options before switching zones. Have never crashed so far when this is disabled

2.Limiting affinity in task manager
Task manager->Details->Right Click PathOfExile.exe->Set Affinity
For me disabling 4 of the 16 virtual cores I have makes it so my PC does not completely freeze. You can also use a program called "Process Lasso" to automate setting the affinity for you

Additional details:
CPU: Ryzen 5 9800X3D
GPU: NVidia 3080
Windows 11 24H2
I crash randomly when loading any place, but for whatever reason Clearfell is a common culprit. Second most common is right after a crash the loading screen when starting up will crash too.