Constant 0xC0000005 crash in PathOfExileSteam.exe+0x10DBD8 on Ryzen 3900X + RTX 3070 Ti
|
Hi,
I have a persistent crash that I can reproduce in 1–10 minutes of mapping. Exception is always 0xC0000005 in PathOfExileSteam.exe with the same offset. Hardware: 1) CPU: Ryzen 9 3900X 2) GPU: Nvidia RTX 3070 Ti 3) RAM: 32 GB (tested with MemTest86 and OCCT), also tested with a different 16 GB 2133 MHz kit – same result 4) SSD: Samsung 970 EVO Plus 1 TB (Samsung NVMe driver installed on Windows) What I tried: 1) Fresh install of Windows 10 and Windows 11 (from official Media Creation Tool) 2) Fresh Linux Mint install + Steam + Proton 9 (game also crashes there) 3) Different Nvidia drivers (clean install) 4) Steam client and standalone PoE client 5) DX11 / DX12 / Vulkan, with and without multithreading, --nosound 6) No overlays, no overclock, SMT on/off, XMP off, different power plans 7) RAM stress tests (MemTest86, OCCT) and GPU stress tests – no errors Crash details (Windows): 1) Exception code: 0xC0000005 (Access Violation) 2) Faulting module: PathOfExileSteam.exe 3) Fault offset: 0x000000000010DBD8 WinDbg shows: ExceptionAddress: 00007ff73737dbd8 (PathOfExileSteam+0x000000000010dbd8) ExceptionCode: c0000005 (Access violation) Attempt to read from address 0000000000000028 PathOfExileSteam+0x10dbd8: mov rax, qword ptr [rdi+28h] rdi = 0 So it looks like a null pointer dereference inside the client. Important: 1) In this league (3.27) the game initially worked for ~20 hours on this exact hardware without crashes. 2) After the first OS reinstall, the crashes started and now are reproducible on: 2.1) clean Win10, 2.2) clean Win11, 2.3) clean Linux Mint + Proton 9. This suggests it’s not a broken Windows install or RAM, but a client-side bug that triggers very reliably on this hardware/config. How to reproduce (for me): 1) Launch the game (Steam client, DX11/DX12/Vulkan – doesn’t matter). 2) Run maps with normal gameplay (monsters, skills, effects). 3) Within 1–10 minutes the client crashes with 0xC0000005 and the offset above. If I can provide additional info (full dump, Client.txt, dxdiag, etc.) – please tell me exactly where/how to send it. Thanks. Last bumped on Dec 14, 2025, 8:45:17 AM
|
|
|
You appear to have ruled out the RAM - did you rule out the CPU in any way?
While I wouldn't rule it out, you might be a touch hasty when asserting that a client crash which is readily reproducible for you in ten minutes or less is caused by a game bug in context of how relatively few other reports of crashes to the desktop are being posted. It isn't likely you'll receive a response in relation to your query about forwarding additional debugging information - GGG hasn't provided Technical Support for close to ten years now. GGG do not offer first-party Technical Support.
Free Technical Support guides are available here: https://www.poecommunity.help No ads, trackers, or other weird stuff. |
|
|
I’ve also ruled out the CPU. I ran stress tests and memory exchanges, and the CPU behaves stably under load in all other applications.
|
|
|
Have you checked the log for any accompanying nvlddmkm.sys errors? If so, disable your GPU OC profile and set it to default, then try again, assuming you have one enabled.
[3.27] Poor Man's Ward Loop: https://youtu.be/p5NA_Rf2TJU
[3.27] Cheeto Chasers: https://youtu.be/f4feauaRxAk [3.26] Shaper Beam Totems: https://youtu.be/soG0-Y2pDDo [3.26] Gorilla Pop: https://youtu.be/JYGmntfn1ho [3.25] Lazy Susie: https://youtu.be/VlcH6tIBzkg |
|
|
No nvlddmkm.sys errors. But I also tried with my GPU OC profile and with default. Same problem.
|
|
|
Do you have a multi monitor setup? What happens if you play on one display with others disabled?
What happens when you play the game in windowed mode? It's weird that you're able to reproduce this exact issue on all platforms. Is 8gb card really not enough for this game? *shrug* |
|


























