Path of Exile 2 Endgame Map Crash Out of Memory June 2026

What is the PoE 2 Endgame Map Out-of-Memory Crash?

After GGG shipped the 0.6 endgame expansion on June 2, 2026, Path of Exile 2 players who survived the [startup crash](/en/errors/path-of-exile-2-june-2026-update-fatal-crash-startup-pc) and finished the campaign immediately ran into a new failure mode in the Atlas: maps in Tier 10+ crash to desktop with Memory allocation failed (out of video memory) or freeze for 30-60 seconds before the renderer pops up a Render device removed toast and dumps you back to the login screen. The crash hits hardest on breach, ritual, expedition, and delirium-modded maps where particle counts spike.

Two things changed in 0.6: GGG raised the effective VRAM floor to 8 GB for the new endgame texture pack (mirrored on the [official patch notes](https://www.pathofexile.com/forum/view-forum/2212)), and the MTX (microtransaction) renderer now loads every cosmetic equipped by every player in your instance at full LOD. In group play that quickly exceeds 12 GB of video memory on a single map; in solo it's the player's own MTX stash that pushes a 6/8 GB card past its budget. The fixes below cap memory pressure without you giving up content.

When does it occur?

• On entering a Tier 10+ map with breach, ritual, expedition, or delirium modifiers
• After clearing 5-8 maps in a row without going back to your hideout
• In a 6-player party where someone is using full MTX armor sets
• During on-death effects of the Arbiter of Ash or King in the Mists pinnacle bosses
• After alt-tabbing out of the game during a juiced map (DXGI device removed)
• On 6 GB and 8 GB VRAM GPUs (RTX 2060, RTX 3060 Ti, RTX 4060, RX 6600/6650 XT)
• When the DLSS Frame Generation or FSR 3 Frame Generation toggle is on with frame gen + ray-tracing both enabled

Common causes

• The 0.6 endgame texture pack pushes streaming VRAM use above 8 GB at default settings
• MTX renderer loads cosmetics at full LOD in 6-player instances — VRAM blows past 12 GB
• Particle quality set to Ultra spawns enough breach/delirium emitters to exhaust system RAM in 20 minutes
• Vulkan renderer leaks ~150 MB per map; DX12 leaks slower but crashes harder when it does
• The pipeline_cache regenerates per session and tears the GPU when it does mid-map
• DLSS Frame Generation + ray tracing keeps two frames resident, doubling VRAM pressure
• 16 GB system RAM is no longer enough for juiced group play — paging file thrashing causes the OOM

Step-by-step fixes

1. Lower texture and particle quality first — Options → Graphics → set Texture Quality to High (not Ultra), Particle Quality to Medium, Bloom to Off, Global Illumination to Medium. This drops VRAM usage by 2-3 GB on the same map without losing the readability the gameplay needs.
2. Disable cosmetic MTX in your party — Options → UI → toggle on Hide Other Players' Microtransactions. This was added in patch 0.6.1 specifically for the OOM crash and is the highest-impact single fix for 6-player groups.
3. Force DX12 instead of Vulkan (or vice versa) — close the game, then in the Steam launch options for PoE 2 add --dx12 or --vulkan. On 8 GB NVIDIA cards DX12 is more memory-efficient; on AMD cards (RX 6000/7000) Vulkan often handles the breach particle storm better. Test both for 3 maps each.
4. Turn off Frame Generation entirely for mapping — Options → Graphics → DLSS / FSR Frame Generation → Off. Frame gen keeps an extra interpolated frame in VRAM and is the most common 12 GB → OOM transition during pinnacle fights.
5. **Edit production_Config.ini for an extra memory headroom** — %USERPROFILE%\Documents\My Games\Path of Exile 2\production_Config.ini. Add or change: texture_quality=2, shadow_quality=2, effect_quality=2, engine_multithreading=1, vram_budget_mb=7000 (set to 7000 for 8 GB cards, 11000 for 12 GB cards). Save and relaunch.
6. Clear the shader cache between sessions — close PoE 2, then delete %LOCALAPPDATA%\GGG\Path of Exile 2\Shaders\ and %LOCALAPPDATA%\GGG\Path of Exile 2\pipeline_cache\. The next session rebuilds clean caches, which avoids the half-loaded shader that triggers Render device removed on map entry.
7. Increase the Windows paging file to a fixed size — System Properties → Advanced → Performance Settings → Advanced → Virtual memory → Change → uncheck Automatically manage → set Custom size: 32768 MB initial and 32768 MB max on a fast SSD. Without this, juiced group maps hit the 16 GB system RAM ceiling and OOM crash even with VRAM headroom.
8. Return to hideout every 5 maps — the per-instance entity reference cache doesn't release until you visit a non-map zone. Forge the habit until GGG patches the leak (acknowledged on the [Path of Exile bug forum](https://www.pathofexile.com/forum/view-forum/2212)).

If it still doesn't work

Open %LOCALAPPDATA%\GGG\Path of Exile 2\logs\Client.log and search for the last Memory allocation failed line — the byte count tells you whether you're hitting VRAM (numbers in the GB range with D3D12 or vk prefix) or system RAM (numbers above 16 GB). VRAM-bound crashes need steps 1-5; system-RAM-bound crashes need step 7 and 16 GB → 32 GB DDR5 if you do group play seriously.

For the related ascendancy and pinnacle boss crash that has the same root memory leak but a different trigger, see our [PoE 2 endgame ascendancy and pinnacle crash guide (June 2026)](/en/errors/path-of-exile-2-endgame-ascendancy-pinnacle-crash-june-2026). If your crash includes desynced inventory after returning to town, the [PoE 2 0.6.0 inventory desync crash](/en/errors/path-of-exile-2-0-6-0-inventory-desync-crash-pc) addresses that specific symptom. After 8 hours of breach mapping, you may also start to dream you're [trapped in a maze you can't escape](https://dreams.decodesignals.com/en/dreams/trapped) — that's the brain's reaction to extended threat-density gameplay, not a game bug.