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

@chillingreen#3361 Wrong.

- Permanent fix: switch back to 22h2/23h2 and block 24h2
- or disable 2 real cores (must be real cores, disable SMT) with Process Lasso PLUS disable SMT in bios (this way PC wont freeze just POE2, and you can restart), this way FPS wont tank much maybe just 10FPS
Last edited by mkdr#2100 on Dec 13, 2024, 2:36:48 PM
Same. Crash on game loading/zone loading most.
CPU goes prrrrrrrr prrrrrrrrr and Pewwwwwwwww game crashes.
windows 10/i5 5800h
issue started last 2-3 days
Same problem with 24h2 in loading screen
Can we get a response from GGG on how far they are from a potential fix?

If they can't because it's a MS issue then fine... i'll reinstall windows 11 23H2.
Same issue here. On Windows 11 24H2 Home, running an i5-13400F, 32GB RAM, RTX4060. Happens very, very frequently when loading between zones. It's bad enough I don't want to play the game for fear of damaging my system.
I can confirm the same issue on Win 11 24H2. Game just freezes in loading screens at random, and when it does the entire PC freezes, forcing me to force close my PC.
If you're like and your game crashes loading shaders (usually in zone transitions), you can try this.

1. Delete shader cache from %appdata%\Path of Exile 2\ShaderCache(your render engine). This step may not be necessary, but it's what I did.

2. Go to your nvidia control panel, go to 'Manage 3d Settings'. In the global settings, increase the shader cache to 100GB (you may be able to go less, I havent tested).

After this, your game will probably be still crashing while the shaders are recompiled and cached. After some time, you will be able to play the game just like normal again.

One other thing, you can disable engine multithreading to severely limit the crash potential at a steep performance cost. If you do this in zone transitions, and then turn it back when you are in the zone, this also works.
Whoops, didn't see this thread when I posted mine, so I'll just repost what I put in my thread in case this one is getting monitored:


I've had other crashes, but this one is happening several times per play session, almost always on a loading screen. The entire system becomes unresponsive and must be manually restarted.

My system:
OS: Windows 11 Pro 64-bit (10.0, build 26100) (24H2)
Mobo: Gigabyte AORUS ELITE AX
CPU: AMD Ryzen 7 7800X3D
RAM: Corsair Vengeance 32GB (2x16GB) DDR5 6000
SSD: Samsung 990 PRO 2TB PCIe Gen 4x4 NVMe
GFX: EVGA nVIDIA RTX 2080 SUPER

I've noticed nothing showing up in Windows Event Viewer after a freeze, or any indication when a freeze may be about to happen. The game is running fantastic (120+FPS), then I load into an area and the system locks up, seemingly at random. Happens both solo and in party play.

The last debug entries from my last crash today (spam of "No collision callback set! MoveTo was not called before setting up line sweeper. Metadata/Characters/Int/IntFour" precedes this):

"

2024/12/13 18:59:02 7315906 4228e34f [DEBUG Client 17124] [ENTITY] Destroy static entities
2024/12/13 18:59:02 7315906 992412d1 [DEBUG Client 17124] [SCENE] Height Map Texture: 670 x 330
2024/12/13 18:59:02 7315921 4228e280 [DEBUG Client 17124] [ENTITY] Finalize static entities
2024/12/13 18:59:05 7319500 4228e34f [DEBUG Client 17124] [ENTITY] Destroy static entities
2024/12/13 18:59:05 7319500 4228e280 [DEBUG Client 17124] [ENTITY] Finalize static entities
2024/12/13 18:59:05 7319500 4228e34f [DEBUG Client 17124] [ENTITY] Destroy static entities
2024/12/13 18:59:05 7319515 992412d1 [DEBUG Client 17124] [SCENE] Height Map Texture: 540 x 480
2024/12/13 18:59:05 7319515 4228e280 [DEBUG Client 17124] [ENTITY] Finalize static entities
2024/12/13 18:59:07 7321046 2d8e8abd [DEBUG Client 17124] Got Instance Details from login server
2024/12/13 18:59:07 7321046 403248f7 [INFO Client 17124] [SHADER] Delay: OFF
2024/12/13 18:59:07 7321046 91c6da6 [INFO Client 17124] Connecting to instance server at 170.106.113.80:21360
2024/12/13 18:59:07 7321093 91c69aa [DEBUG Client 17124] Connect time to instance server was 32ms
2024/12/13 18:59:07 7321125 91c4c6b [DEBUG Client 17124] Client-Safe Instance ID = 1115021170
2024/12/13 18:59:07 7321125 2caa1679 [DEBUG Client 17124] Generating level 53 area "C_G2_3a" with seed 775663143
2024/12/13 18:59:07 7321421 f0c29e12 [INFO Client 17124] Tile hash: 4024287929
2024/12/13 18:59:07 7321421 f0c29e11 [INFO Client 17124] Doodad hash: 3155793838
2024/12/13 18:59:07 7321453 4228e34f [DEBUG Client 17124] [ENTITY] Destroy static entities
2024/12/13 18:59:07 7321453 4228e280 [DEBUG Client 17124] [ENTITY] Finalize static entities
2024/12/13 18:59:07 7321453 4228e34f [DEBUG Client 17124] [ENTITY] Destroy static entities
2024/12/13 18:59:07 7321484 992412d1 [DEBUG Client 17124] [SCENE] Height Map Texture: 450 x 510
2024/12/13 18:59:07 7321500 4228e280 [DEBUG Client 17124] [ENTITY] Finalize static entities
2024/12/13 18:59:08 7322265 1a61ea26 [DEBUG Client 17124] InstanceClientSetSelfPartyInvitationSecurityCode = 0
2024/12/13 18:59:09 7322796 403248f7 [INFO Client 17124] [SHADER] Delay: ON
2024/12/13 18:59:26 7340156 2d8e8abd [DEBUG Client 17124] Got Instance Details from login server
2024/12/13 18:59:26 7340156 403248f7 [INFO Client 17124] [SHADER] Delay: OFF
2024/12/13 18:59:26 7340171 91c6da6 [INFO Client 17124] Connecting to instance server at 172.240.69.41:21360
2024/12/13 18:59:26 7340187 91c69aa [DEBUG Client 17124] Connect time to instance server was 16ms
2024/12/13 18:59:26 7340218 91c4c6b [DEBUG Client 17124] Client-Safe Instance ID = 3088740917
2024/12/13 18:59:26 7340218 2caa1679 [DEBUG Client 17124] Generating level 57 area "C_G2_town" with seed 1
2024/12/13 18:59:28 7341781 f0c29e12 [INFO Client 17124] Tile hash: 1414081272
2024/12/13 18:59:28 7341781 f0c29e11 [INFO Client 17124] Doodad hash: 1797091165


I really hope this somehow helps, it's really my only major technical issue I'm experiencing.
Selection bias occurs when the sample studied is not representative of the broader population, leading to skewed results. In our example, the issue arises because the sample primarily consists of systems updated to the latest version. If most of the observed issues are in those updated systems, it might lead to the conclusion that the update is the cause of the problem, even though other possible explanations (e.g., older systems being underreported or not included in the analysis) have not been considered.

In this case, it is not unlikely that people have auto updates on, on their newly built/bought computer that they installed the lastest OS with. Those people (including me) will then have 24H2
Last edited by godimpulse#1516 on Dec 13, 2024, 11:14:52 PM
have constant crashes on 23h2)))
nothing helps

and the only thing matters - my 4080

changing it to 3080 leads to no ussues

Report Forum Post

Report Account:

Report Type

Additional Info