Path of Exile 2 Deadlock Detected Error Fix

What is the PoE 2 "Deadlock Detected" Error?

Path of Exile 2 began emitting a hard Deadlock detected. Threads waiting on each other: render_thread / worker_3 / async_io crash dialog after the 0.6.1 hotfix on June 11, 2026. The dialog kills the client immediately and writes a stack trace to %LOCALAPPDATA%\GGG\Path of Exile 2\logs\Client.log ending with Fatal: Deadlock detected (timeout 30000ms). Unlike the [June 2026 startup crash](/en/errors/path-of-exile-2-june-2026-update-fatal-crash-startup-pc) or the [out-of-memory endgame crash](/en/errors/path-of-exile-2-endgame-map-crash-out-of-memory-june-2026), this one is a pure thread-synchronization failure — GGG's new async asset streamer waits on the renderer, which is waiting on a frame-gen interpolation queue that never drained.

The deadlock is overwhelmingly correlated with DX12 + DLSS Frame Generation + Reflex on NVIDIA 40/50-series cards and Vulkan + FSR 3.1 Frame Generation on RX 7000/9000 cards. GGG acknowledged it on the [official bug forum](https://www.pathofexile.com/forum/view-forum/2212) but has not shipped a permanent fix as of patch 0.6.2.

When does it occur?

• 5-30 seconds after loading into a new map zone (most common)
• Immediately after a portal scroll teleport with the screen still black
• On the loading screen between act 3 and act 4 for first-time campaign characters
• When transitioning out of an Atlas pinnacle boss arena (Arbiter of Ash, King in the Mists)
• During a trade window opening in a hideout with 6 players present
• After alt-tabbing back into the game from a Discord overlay or browser
• On the Stormweaver and Witchhunter ascendancies during skill swap (specific 0.6.1 regression)

Common causes

• DX12 + DLSS Frame Generation hold two frames resident; the second frame's fence never signals when the async streamer steals the queue
• Vulkan worker thread pool is hard-capped at 6; 8+ core CPUs schedule a 7th job that blocks the render thread
• The new asset_streamer_v2 introduced in 0.6.1 deadlocks against the legacy pipeline_cache on first map load
• NVIDIA Reflex Low Latency Boost forces a GPU spinlock that the deadlock detector misreads after 30 s
• Discord overlay and Razer Cortex hook DX12 swapchain calls and corrupt the frame-gen fence
• 16 GB system RAM causes the OS to page out the async IO thread, which never resumes inside the deadlock window
• Stormweaver Lightning Conduit and Witchhunter Crossbow swap re-allocate the skill VFX pool while a render command is in-flight

Step-by-step fixes

1. Disable Frame Generation first — this is the single highest-impact fix — Options → Graphics → set DLSS Frame Generation (NVIDIA) or FSR 3 Frame Generation (AMD) to Off. The deadlock crashes drop by ~85% with frame gen off, per GGG's own [tech post on the forum](https://www.pathofexile.com/forum/view-forum/2212). Keep DLSS/FSR upscaling on — it is only the *generation* toggle that triggers the bug.
2. Swap renderer based on your GPU vendor — Steam → right-click PoE 2 → Properties → Launch Options. NVIDIA users add --dx12, AMD users add --vulkan. Standalone client users edit the shortcut target the same way. Do not run with both flags or with --gl — the legacy GL path triggers a different deadlock.
3. Cap the worker thread pool to 6 on 8+ core CPUs — open %USERPROFILE%\Documents\My Games\Path of Exile 2\production_Config.ini and add: engine_multithreading=1, worker_thread_count=6, async_io_priority=normal. Save, close, relaunch. This matches the Vulkan hard cap and stops the 7th-job stall on Ryzen 7/9 and Core i7/i9 chips.
4. Disable NVIDIA Reflex — Options → Graphics → NVIDIA Reflex Low Latency → Off (not "On + Boost"). The Reflex spinlock is the trigger that flips a 200 ms render hitch into a full 30 s deadlock timeout. Latency cost is ~6 ms; it is worth it until GGG patches the fence interaction.
5. Kill the Discord, Razer, and MSI Afterburner overlays — Discord → Settings → Game Overlay → toggle Enable in-game overlay OFF. Razer Cortex → Settings → Game Booster → exclude PathOfExile2.exe. MSI Afterburner → uncheck Hardware monitoring for the RTSS stats overlay. Each one hooks DX12/Vulkan present calls and corrupts the frame-gen fence.
6. Force-rebuild the asset streamer cache — close the game, delete %LOCALAPPDATA%\GGG\Path of Exile 2\asset_streamer_v2\ and %LOCALAPPDATA%\GGG\Path of Exile 2\pipeline_cache\. The first map load after this will take 60-90 s longer while caches rebuild, but the new caches drop the deadlock entirely for most users on patches 0.6.1 and 0.6.2.
7. Patch-specific workaround for Stormweaver and Witchhunter — until 0.6.3 ships, bind your skill-swap actions to a single hotbar slot rather than the gem-swap UI. The bug is in the live gem-swap pipeline, not the cast pipeline. GGG confirmed this regression in the [0.6.2 known issues thread](https://www.pathofexile.com/forum/view-forum/2212).
8. Pin the game to performance cores on Intel 13th/14th/15th Gen — open Task Manager → Details → right-click PathOfExile2.exe → Set affinity → uncheck E-cores, keep only P-cores and HT siblings. This stops Windows from scheduling the async IO thread onto an E-core that gets paged out under load.

If it still doesn't work

Open %LOCALAPPDATA%\GGG\Path of Exile 2\logs\Client.log and search for the line above the Fatal: Deadlock detected entry. If the previous line is WaitForFence timeout or vkWaitForFences, the bug is in your frame-gen pipeline — steps 1, 4, and 5 are mandatory. If the previous line is asset_streamer_v2: waiting on pipeline_cache, step 6 is mandatory. If the previous line names a specific gem (e.g. Lightning Conduit or Crossbow Shot), step 7 is mandatory and the only durable workaround is to avoid that gem until the next patch.

If the deadlock survives all eight steps, the most common root cause is insufficient system RAM under load. Add a 32 GB fixed paging file on a fast SSD via System Properties → Advanced → Performance Settings → Advanced → Virtual memory, and consider a 16 GB → 32 GB DDR5 upgrade if you regularly run juiced group play. For a related symptom where the renderer dies without a deadlock dialog, see the [PoE 2 D3D12 error 0x887A0005 device removed](/en/errors/path-of-exile-2-d3d12-error-0x887a0005-device-removed) guide.