Path of Exile 2 June 2026 Update Fatal Crash on Startup (PC)
Fix Path of Exile 2 fatal crash on startup after the June 2026 0.6 update. Clear shader cache, switch DX12/Vulkan, disable MTX cosmetics, and fix ultrawide crashes.
What is the Path of Exile 2 June 2026 Update Crash?
Path of Exile 2 — currently Steam's fastest-growing game with a +873% player surge going into June 2026 — pushed its 0.6 content update on June 2, 2026, and like every PoE 2 patch before it, it kicked off a wave of Fatal Error and Memory Allocation Error crashes at startup. The crash signature varies: a Windows error dialog citing PathOfExileSteam.exe, a black window that closes after 5 seconds, or an instant Vulkan device lost message.
GGG patches the Direct3D 12 renderer, the Vulkan render path, and the shader pipeline in nearly every major update, which invalidates the **ShaderCache directory** for almost everyone. Couple that with new MTX cosmetics shipped on patch day and the long-standing 16:10 ultrawide handling regression, and you get the four-headed crash pattern below. Treat them in the diagnostic order shown — the shader-cache wipe alone solves 60% of cases.
When does it occur?
- Immediately after pressing Play on the 0.6 patched client
- A few seconds into the GGG splash, then a
Fatal Errormodal - During the character-select screen as MTX cosmetics load
- On 16:10 / ultrawide / 32:9 resolutions at the very first frame
- After the launcher updates only the executable but a previous Vulkan crash left a partial
ShaderCache - For Standalone client users, after Steam users get the patch first
Common causes
- Corrupted/stale
ShaderCacheafter the 0.6 renderer changes - Vulkan path crashing on RTX 50-series and RX 9000-series (same pattern as our [PoE 2 Vulkan crash guide](/en/errors/path-of-exile-2-vulkan-crash-startup-fix))
- DX12 path failing on RTX 30-series with older 561.x drivers
- MTX cosmetics (specifically the new 0.6 stash decorations and pet effects) triggering a load-time exception
- 16:10 and ultrawide resolutions hitting a swapchain init crash GGG hasn't backported the 0.5.1 fix for
- Out-of-VRAM crash at startup on 8 GB cards with Texture Quality set to Ultra
- Build system data desync from a previous session (related to our [PoE 2 0.5.0 build system crash](/en/errors/path-of-exile-2-0-5-0-build-system-crash))
Step-by-step fixes
- Delete the ShaderCache (the #1 fix) — close the game completely, press Win+R, paste
%LOCALAPPDATA%\Path of Exile 2\ShaderCacheand press Enter, then delete every file in the folder. Relaunch — first launch will take 2-5 minutes rebuilding shaders. This alone resolves the majority of "fatal error on startup after 0.6" reports. - Switch the render API — at the launcher screen click the gear icon → Render Mode → if you're on DirectX 12, switch to Vulkan. If you're on Vulkan, switch to DirectX 12. The 0.6 patch broke one path per GPU vendor; toggling exposes which one. Standalone client users find the same toggle under Options → Graphics.
- Update GPU drivers to the June 2026 branch — NVIDIA 580.88 or newer (it carries the PoE 2 0.6 game-ready profile), AMD Adrenalin 26.5.2 or newer. Use a clean install (NVIDIA: "Perform clean installation", AMD: "Factory Reset"). Reboot afterward.
- Disable MTX cosmetics on the character select — launch with
--noasyncadded to your launcher's Command line (Steam: Properties → Launch Options → enter--noasync). This serializes the cosmetic load and bypasses the 0.6 MTX preview crash on character select. - Fix the 16:10 / ultrawide startup crash — open
%USERPROFILE%\Documents\My Games\Path of Exile 2\production_Config.iniand setdisplay_width=1920,display_height=1080,fullscreen_mode=2(windowed). Launch, get into the menu, then change resolution back to your native 16:10 or ultrawide inside the game options. - Force lower texture quality on the first launch — same
production_Config.inifile, settexture_quality=2(Medium). VRAM-saturated startup is a known 0.6 regression on RTX 3060 / RX 6600 cards. You can raise it back inside the game once you reach the hideout. - Verify game files — Steam: right-click Path of Exile 2 → Properties → Installed Files → Verify integrity. Standalone: launcher → Repair. The 0.6 patch shipped as multiple staged downloads and partial installs are a common cause of
MissingAssetExceptioncrashes. - Disable overlays — Steam Overlay (game Properties → uncheck "Enable Steam Overlay while in-game"), Discord overlay (User Settings → Game Overlay → toggle off), and NVIDIA App overlay (NVIDIA App → Settings → In-Game Overlay → off). The NVIDIA App overlay introduced in the 580.x driver branch is the newest culprit on PoE 2.
If it still doesn't work
Open %USERPROFILE%\Documents\My Games\Path of Exile 2\logs\Client.txt and read the last 50 lines after a crash — GGG's client log is unusually detailed and will name the failing module (Renderer_Vulkan.dll, MicroTransactions.dll, BuildSystem.dll). The module tells you which of our cluster guides to follow: the [PoE 2 Vulkan crash on startup](/en/errors/path-of-exile-2-vulkan-crash-startup-fix), the [PoE 2 0.5.0 build system crash](/en/errors/path-of-exile-2-0-5-0-build-system-crash), the [Dawn of the Hunt crash](/en/errors/path-of-exile-2-dawn-of-the-hunt-crash), or the [Settlers act 4 boss desync](/en/errors/path-of-exile-2-settlers-act-4-boss-desync-crash).
If the game still crashes after wiping the shader cache and switching render APIs, report on the [GGG bug forum](https://www.pathofexile.com/forum/view-forum/2200) with Client.txt, a DxDiag, and the exact patch build number from %LOCALAPPDATA%\Path of Exile 2\version.txt. GGG hotfixes PoE 2 crash regressions within 48-72 hours of a content patch — they're typically fixed before the first weekend after release.
Frequently Asked Questions
Why does Path of Exile 2 crash on startup after the June 2026 update?
The 0.6 patch invalidated old shader caches and changed how the engine initializes DX12. A stale shader cache, outdated GPU driver, or corrupted MTX cosmetic cache are the three most common triggers for the fatal error at launch.
How do I clear the PoE 2 shader cache?
Delete the ShaderCache folders in the Path of Exile 2 installation directory (and %LocalAppData% for the standalone client), then also clear your GPU driver's own cache (NVIDIA: DXCache/GLCache in %LocalAppData%). The game rebuilds them on next launch — the first load will be slower, which is normal.
Should I use DX12 or Vulkan to stop the crashes?
If the game crashes on DX12 after the update, switching the renderer to Vulkan in the launcher options (or via the client config) bypasses the crash for most players. Vulkan can be slightly slower on some NVIDIA cards but is significantly more stable on this patch.
PoE 2 crashes with no error message at all — is that the same bug?
A silent crash with no fatal error dialog usually points to VRAM overflow in endgame maps rather than the startup bug. Lower texture quality one notch and cap your FPS; if crashes happen only in juiced maps, it's the VRAM issue, not the 0.6 startup crash.
Related errors
Fix Path of Exile 2 Vulkan crashes on startup and in-game. Switch renderer to DX12, clear shader cache, update GPU drivers, and resolve Dawn of the Hunt crash triggers.
Fix Path of Exile 2 0.5.0 crashes from the new build-saving system. Clear corrupted build files, apply May 30 hotfix, verify integrity, and rollback steps.
Fix Path of Exile 2 crashes after the Dawn of the Hunt 0.2.0 update. Covers unknown object errors, zone crashes, NVIDIA device removed, and shader fixes.
Fix Path of Exile 2 Settlers of Kalguur Act 4 boss desync, disconnects, and crashes. Region pinning, predictive mode toggle, and GGG's known-issue workarounds for 2026.