Path of Exile 2 Crashing: Causes, Checks and Fixes (2026)

Path of Exile 2 runs on Grinding Gear Games’ in-house engine, which compiles shaders aggressively on its own thread, offers a choice between DirectX 12 and Vulkan, and pushes CPUs harder than most action RPGs. Those three traits explain most of its crashes. A crash during the loading screen or the first time a new skill effect appears is usually a shader cache problem or a renderer that your driver does not like. A hard crash to desktop in a dense map fight, sometimes preceded by “The game encountered an unrecoverable error,” is frequently memory or an unstable CPU; this game became well known for exposing marginal processors that survive everything else. A crash that comes with “Failed to create D3D12 device” or a device-removed message is the graphics driver. Everything the client knows about a crash is written to Client.txt in the game’s logs folder, and your settings are in a plain text file at %USERPROFILE%\Documents\My Games\Path of Exile 2\production_Config.ini. With those two files open, the fixes below are mostly a matter of matching the symptom in 2026.

Likely Causes

Fix 1: Switch the renderer

How to check

Open Options, Graphics, and look at Renderer. The game defaults to DirectX 12. Check the last lines of Client.txt after a crash; a D3D12 or Vulkan error string tells you which path failed.

What to do

Select the other renderer and restart the client. Vulkan often sidesteps DirectX 12 device-removal crashes on certain driver versions, and DirectX 12 is the fallback when Vulkan validation errors appear. Play a few maps before judging. Note that switching renderer triggers a full shader recompile, so expect stutter for a while.

How to undo it

Select the previous renderer and restart.

Fix 2: Delete the shader cache

How to check

If the crash began after a patch or driver update and hits at loading or the first time a new effect renders, the cached shaders may be stale or corrupt.

What to do

Close the game. In %USERPROFILE%\Documents\My Games\Path of Exile 2, delete the shader cache folder for your renderer (it is named for DirectX 12 or Vulkan). Steam users also delete Steam\steamapps\shadercache\2694490. Clear %LOCALAPPDATA%\NVIDIA\DXCache or %LOCALAPPDATA%\AMD\DxCache. Relaunch and let the in-game shader precompilation finish at the login screen before entering a map.

How to undo it

Nothing to revert; caches rebuild automatically.

Fix 3: Disable overlays

How to check

Overlays inject into the render pipeline and are a frequent cause of silent exits in this engine. If Client.txt ends without an error line, suspect one.

What to do

Turn off the Discord in-game overlay, the Steam overlay for the game (Properties), RivaTuner Statistics Server, the NVIDIA App or GeForce Experience overlay, and Xbox Game Bar. Test several maps, then re-enable one at a time.

How to undo it

Reverse each toggle.

Fix 4: Clean-install the GPU driver

How to check

Open Event Viewer, Windows Logs, System, and look for a nvlddmkm or amdkmdag warning at the crash time. “Failed to create D3D12 device” or a device-removed line in Client.txt also implicates the driver.

What to do

Install the current driver from NVIDIA, AMD or Intel with the clean installation option and reboot. If the newest driver introduced the crash, install the previous release; this engine has hit driver regressions before. Repeat Fix 2 afterward.

How to undo it

Roll back through Device Manager or install the older package.

Fix 5: Toggle Engine Multithreading and Dynamic Culling

How to check

In Options, Graphics, find Engine Multithreading and Dynamic Culling. Both change how work is split across CPU threads. On some processors, particularly hybrid Intel parts and CPUs with aggressive boost behavior, one of them correlates with crashes in dense fights.

What to do

Turn Engine Multithreading off and play several maps. If the crashes stop, leave it off; performance drops slightly but stability improves. If not, turn it back on and try Dynamic Culling off instead.

How to undo it

Return both toggles to their previous state.

Fix 6: Increase the page file

How to check

Watch Committed memory in Task Manager during a long mapping session. The client’s footprint grows over time, and on 16 GB systems with a small page file a crash after an hour or two is common.

What to do

Set a fixed page file of at least 16384 MB through System Properties, Advanced, Performance Settings, Advanced, Virtual Memory, then reboot. Lower Texture Quality one step if VRAM is also at the limit.

How to undo it

Re-enable automatic page file management and reboot.

Fix 7: Verify game files

How to check

Crashes tied to a specific area, boss or skill effect can indicate a damaged asset.

What to do

Steam users right-click the game, Properties, Installed Files, Verify integrity. Standalone client users run PackCheck.exe from the install folder, which validates the content packs and redownloads damaged ones. Epic users use the Verify option in the library.

How to undo it

Not applicable.

Fix 8: Stabilize the CPU

How to check

Path of Exile 2 gained a reputation for crashing on Intel 13th and 14th generation processors that had degraded under earlier motherboard power settings, and it also exposes marginal manual overclocks and undervolts. If crashes cluster in heavy fights and other CPU-bound games occasionally fail too, the processor is a serious suspect.

What to do

Update your motherboard BIOS to a version that applies Intel’s current default power limits and microcode, then load those defaults. Disable manual CPU overclocks, curve optimizer offsets and XMP/EXPO for testing. If the crashes stop only at stock, reintroduce memory profiles first, then CPU tuning, one step at a time. If an Intel CPU remains unstable at stock on a current BIOS, it may be degraded and eligible for warranty replacement.

How to undo it

Reload your saved BIOS profile.

Fix 9: Reset production_Config.ini

How to check

If the client crashes before the login screen and nothing above helped, a stale display or graphics value in the config may be the cause.

What to do

Close the game. Rename %USERPROFILE%\Documents\My Games\Path of Exile 2\production_Config.ini to .bak. Launch to regenerate defaults, then rebuild your settings. Keybinds are stored here, so keep the backup for reference.

How to undo it

Delete the regenerated file and restore the backup.

If Nothing Works

Copy the last hundred lines of Client.txt and the Application error from Event Viewer, which names the faulting module. Grinding Gear Games’ support and the official bug report forum ask for both. Test a fresh Windows user account and a session with no third-party software. Run a CPU stress test that exercises AVX workloads for at least half an hour; instability there confirms a hardware fault. If the crash arrived with a patch and many players report it, the fix is on the developer’s side, and hotfixes for this game tend to follow quickly.

FAQ

Is Vulkan or DirectX 12 more stable in Path of Exile 2?

It varies by driver. Vulkan often avoids DX12 device-removal crashes; DX12 is the fallback if Vulkan shows validation errors. Test both.

Why does the game crash only during big fights?

Dense effects push the CPU and memory hardest. That pattern points at CPU stability, page file size or Engine Multithreading rather than the GPU.

Does deleting the shader cache lose progress?

No. Progress is server-side. You only lose precompiled shaders, which rebuild on the next launch.

Could my Intel CPU really be the problem when other games work?

Yes. This engine’s workload exposed degraded 13th and 14th generation chips that ran other games fine. A BIOS with current Intel defaults is the first step; stock instability after that suggests a warranty claim.