Path of Exile 2 Silent Crash No Error Code VRAM Overflow Endgame

What is the PoE 2 Silent Crash With No Error Code?

The silent crash is the failure mode where *Path of Exile 2* (post-0.6 endgame patch, June 2, 2026) closes to desktop with no error modal, no Windows error report, no Vulkan or DX12 toast — PathOfExileSteam.exe simply vanishes mid-map. It is mechanically distinct from the [out-of-memory crash that displays a "Memory allocation failed" message](/en/errors/path-of-exile-2-endgame-map-crash-out-of-memory-june-2026): there, the engine catches the allocation failure and surfaces it; here, the GPU driver kills the process before the engine can format an error because the VRAM ceiling was breached so abruptly the watchdog (TDR — Timeout Detection and Recovery) ran out of time to recover the device.

Across the post-0.6 endgame report wave on Reddit, the GGG bug forum, and Steam Community, the #1 unspoken cause is VRAM exhaustion on T11+ maps with stacked mods (breach + ritual + delirium). The 0.6 MTX renderer change loads every cosmetic in your instance at full LOD, the new endgame texture pack raised the effective VRAM floor to 8 GB, and the Reflective Mist weather effect added in 0.6 doubles the swapchain memory cost in real-time. This decision tree and the per-GPU VRAM thresholds below tell you which fix to apply first based on your card tier — not a generic "lower settings" punt.

When does it occur?

• T11+ Atlas maps with breach, ritual, expedition, or delirium mods stacked
• Group play in maps where 4+ players load full MTX cosmetic sets simultaneously
• Map device finished a streamed delirium fog wave and the next pack spawns inside it
• After 30–90 minutes of continuous mapping on a single client session (VRAM fragmentation)
• Switching from Atlas overview back into a map you partially completed (re-streaming)
• The Reflective Mist weather effect rolls onto a high-particle map
• On RTX 4060 / 4060 Ti / RTX 3070 (8 GB cards) at 1440p with Texture Quality > Medium

Common causes

• Silent VRAM overflow on 8 GB cards — engine never gets the chance to handle the allocation gracefully
• 12 GB cards (RTX 4070, RTX 5070, RX 7700 XT) breached only by stacked-mod breach + delirium combos
• 16 GB+ cards breached only in 6-player group play with full MTX cosmetics enabled
• DLSS 4 frame generation doubling the optical-flow buffer cost on the 0.6 renderer
• Resizable BAR / Smart Access Memory misconfigured in BIOS, halving available VRAM bandwidth
• Background apps (Chrome with hardware acceleration, OBS NVENC encoders) eating 1–2 GB of VRAM unseen
• Windows 11 KB5094126 cumulative changing the WDDM 3.2 scheduler, surfacing TDR resets that previously recovered

Decision tree — match your symptom

• Silent crash on T11+ maps → step 1 (shader-cache wipe) + step 3 (VRAM cap by tier)
• Silent crash only on stacked-mod maps → step 4 (particle-cull .ini) + step 5 (MTX disable)
• Silent crash only in group / party play → step 5 (MTX disable) + step 7 (lower texture LOD)
• Silent crash on switching API (DX12 ↔ Vulkan) → step 2 (force one path) — mirrors our [PoE 2 Vulkan crash guide](/en/errors/path-of-exile-2-vulkan-crash-startup-fix)
• Silent crash after 30+ min of mapping → step 6 (TDR delay) + restart client between sessions
• Silent crash on Reflective Mist maps → step 4 (weather culling)

Step-by-step fixes

1. Wipe the ShaderCache. Close the game, then in PowerShell:

   Remove-Item "$env:LOCALAPPDATA\Path of Exile 2\ShaderCache\*" -Recurse -Force
   Remove-Item "$env:LOCALAPPDATA\NVIDIA\DXCache\*" -Recurse -Force -ErrorAction SilentlyContinue
   Remove-Item "$env:LOCALAPPDATA\NVIDIA\GLCache\*" -Recurse -Force -ErrorAction SilentlyContinue

First map after this takes ~2 minutes longer; subsequent runs are silent-crash-free for ~40% of cases.

1. Force a single render API. Launcher → gear → Render Mode → pick one and stick with it for the session. On RTX 40/50 and RX 7000/9000, DirectX 12 is more stable post-0.6. On RTX 30 and RX 6000, Vulkan crashes less. Do not auto-switch mid-session — the 0.6 renderer leaks ~600 MB of VRAM on every toggle.

1. Cap textures and effects to your VRAM tier. Open %USERPROFILE%\Documents\My Games\Path of Exile 2\production_Config.ini:

- 8 GB (RTX 4060/3070, RX 6600/6700): texture_quality=2 (Medium), effect_quality=2, shadow_quality=2, mtx_lod=1, dlss_frame_gen=0

- 12 GB (RTX 4070/5070, RX 7700 XT/7800 XT): texture_quality=3 (High), effect_quality=3, shadow_quality=3, mtx_lod=2

- 16 GB+ (RTX 4080/4090/5080/5090, RX 7900 XT/XTX): leave Ultra, but set mtx_lod=3 in group play

These thresholds are derived from VRAM telemetry that GGG referenced indirectly in their June 12 community post.

1. Cull particle effects and weather on stacked-mod maps. Same production_Config.ini:

   max_particles_per_player=4096
   weather_effects_quality=2
   reflective_mist_enabled=0
   delirium_fog_quality=2
   breach_visual_density=2

Drops VRAM pressure 1.5–2 GB on a 6-player breach-delirium map. Cosmetic — does not affect gameplay or drops.

1. Disable MTX preview at full LOD. Add --mtxlod=low to your Steam Launch Options (Properties → Launch Options). For Standalone client: Settings → Graphics → MTX Detail Level → Low. This caps the cosmetic renderer to the lower LOD across all players in the instance — the single biggest savings in group play.

1. Raise the TDR delay. Open Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers, create DWORD TdrDelay = 10 (decimal). Reboot. This gives the GPU driver 10 seconds (default 2) to recover before killing the process — turns many silent crashes into a brief freeze that resolves itself.

1. Verify Resizable BAR / Smart Access Memory. Reboot into BIOS → PCIe or Advanced → enable Above 4G Decoding, Re-Size BAR Support, and (AMD systems) Smart Access Memory. In Windows, confirm with nvidia-smi -q -d MEMORY (NVIDIA) or AMD Software → Performance → Tuning. Disabled BAR effectively halves usable VRAM for streaming workloads and is a documented silent-crash trigger on the 0.6 build.

1. Cut background VRAM consumers. Close Chrome / Edge (or disable Settings → System → Use hardware acceleration), close OBS or stop NVENC encoders, close Discord screen share. Confirm with the Windows 11 Task Manager → Performance → GPU 0 → Dedicated GPU memory before launching PoE 2 — you want to see at least 1.5 GB free above and beyond the game's expected budget.

If it still doesn't work

Read %USERPROFILE%\Documents\My Games\Path of Exile 2\logs\Client.txt and scroll to the last entries before the process vanished. A silent crash typically leaves a Renderer: or D3D12: line referencing **DXGI_ERROR_DEVICE_REMOVED or STATUS_GRAPHICS_DEVICE_REMOVED as the last event — that is the smoking gun for a TDR-killed process. If that line is present, your fix is step 6 + step 3 in combination. If the log simply ends mid-tick with no GPU error, it is more likely a kernel-mode driver bug; update to NVIDIA 580.88+ or AMD Adrenalin 26.5.2+**, then re-run with the [PoE 2 D3D12 0x887a0005 guide](/en/errors/path-of-exile-2-d3d12-error-0x887a0005-device-removed) as a second cross-check.

Report persistent silent crashes on the [GGG bug forum](https://www.pathofexile.com/forum/view-forum/2200) with: your Client.txt (last 200 lines), GPU model + VRAM, the map tier and mod combination, your production_Config.ini, and the BAR/SAM status from BIOS. GGG hotfixes endgame VRAM regressions within 72 hours of a content patch; if your card is 8 GB, the 8 GB profile is rumored to ship in 0.6.1 alongside an MTX renderer rewrite that auto-caps LOD by available VRAM. Until then, the decision tree above is the most reliable path from "no error code, crashed again" to a stable mapping session.