Failed to decompress

I have been having this issue for a while now too and reached out multiple times but getting no where.

Link
I made a forum post documenting all my crash reports it might be worth a look
Spoiler
https://www.pathofexile.com/forum/view-thread/3431280
+1 Also having this issue. Game is not playable.
I've run verify integrity of game files multiple times, and always successful.
Deleted the directory as well and reinstalled.
I'm having the same issue.
Going through the available help and support steps does not resolve it, I could be wrong, but from what I have been reading it seems like its related to 13th gen processors.
13900
4090
64gb ddr5
hi, got same problem to and got 13th gen proc too.
However it now concern others proc and the problem exists from 3.21.2 !

At this moment there is still no answer from GGG except an answer from henry_ggg telling they know this issue.

Fine, but actually we can't play more 30min in a row. since yesterday, i just can't connet myself at all.

end league for me and if GGG han't solved it next league, probably end of poe for me.
same issue on my i79700k 16gigs 2070 setup,

ive damn near given up on playing the league as i cant be bothered battling through the loop of crashing -> relaunch -> crash on town load -> relaunch -> crash on atlas load -> reload enter map. its just too much when you crash 30 times an hour
i9 14900k
RTX 4090
64GB DDR5

get any time error "failed to decompress (corrupted data)"

unplayable
Last edited by Autcs on Feb 7, 2024, 7:18:42 PM
So guys, just a heads-up. I was having this issue in a new pc (a mid to high-end pc) and I was very bugged out by this. I went looking into more thoroughly, and I found out that this was being caused by a hardware problem! One of my RAM sticks was defective (it was a 5200mgh 16gb). The moment I removed the faulty RAM, the game worked like a charm.

I know this might not be the case for everyone, but try running some tests on the RAM of the pcs. This may be the issue.
Disabling the TURBO MODE from the BIOS worked for me. Looks like it's a common issue for the 13th and 14th generation of Intel core processors.

Mine is 13th Gen Intel(R) Core(TM) i7-13700KF.

Report Forum Post

Report Account:

Report Type

Additional Info