How to Fix Path of Exile 2 Crashing on Loading Screen?

Path of Exile 2 can complete login and character selection normally, then fail as soon as the next area begins loading. The same cogwheel screen may end with the game closing to the desktop or, in the more serious version, with Windows no longer responding at all.

The crash appears here because this is when the client reads assets for the next area and prepares renderer and shader data. If an asset is damaged or the graphics driver cannot complete that work, the menu can run normally while the transition fails. Grinding Gear Games tracks a complete Windows lockup separately from a game-only DirectX 12 device-lost crash, so the behavior outside the game matters as much as the screen where it stopped.

1. Update the Game and GPU Driver, Then Test Another Renderer

The renderer is the most useful first test when the game itself closes or produces a device-lost error. Updating the game and graphics driver first matters because an older client and a newer driver, or the reverse, can leave DirectX 12 or Vulkan failing during shader preparation.

For NVIDIA systems, driver 610.88 specifically fixed intermittent long pauses in Path of Exile 2’s DirectX 12 mode. Install NVIDIA 610.88 or a newer stable driver rather than downgrading to an arbitrary launch-era version.

1. Let Steam or the Epic Games Launcher finish every pending Path of Exile 2 update.
2. Install the current stable driver for your GPU. If several driver versions have been installed over one another, use this clean graphics-driver update guide.
3. Open Options > Graphics in Path of Exile 2 and note the current Renderer.
4. Test DirectX 12 if Vulkan is selected, or test Vulkan if DirectX 12 is selected. Restart the game after changing it.
5. If the game crashes before the menu, open %USERPROFILE%\Documents\My Games\Path of Exile 2\poe2_production_Config.ini in Notepad and change renderer_type to DirectX12 or Vulkan. Save the file, then launch the game again.

Test at least two area transitions after the change. A renderer that reaches the menu but still crashes in the same location points more strongly to damaged game data, which Method 2 checks.

2. Verify the Game Package

Verification is especially important when the crash repeats in the same town, map, or character load. That pattern can mean the client reaches one damaged asset each time rather than failing under general graphics load.

1. On Steam, open Library, right-click Path of Exile 2, and select Properties > Installed Files > Verify integrity of game files.
   
2. On Epic Games Launcher, open Library, select the three dots beside the game, choose Manage, and click Verify.
3. For the standalone client, close the game and launcher, then run PackCheck.exe from the Path of Exile 2 installation folder.
4. Let the repair finish before launching the game. Do not interrupt it if the progress appears slow.

This game-file verification guide shows the launcher paths in more detail. If verification repairs files, test the same area before changing any graphics setting so you know whether the package was the cause.

3. Close Graphics Hooks and Force the Dedicated GPU

Discord’s overlay, RivaTuner, MSI Afterburner, ReShade, capture tools, and hardware-monitoring overlays can attach to the renderer as a loading screen begins. Close them for one test. On a laptop or hybrid desktop, also confirm that Windows is not starting the game on integrated graphics.

1. Exit Path of Exile 2 and its launcher.
2. Close overlays and monitoring tools completely from the system tray or Task Manager.
3. Right-click the Windows desktop and open Display settings.

4. Open Graphics under the display settings.

5. Add PathOfExileSteam.exe or the executable used by your installation.

6. Open its Options, choose High performance, and save the preference.

7. Launch the game and test the same loading screen again.

If the crash stops, restore closed programs one at a time. That identifies the conflicting overlay without leaving useful software disabled permanently.

4. Rebuild the Renderer Cache and Local Graphics Configuration

A renderer switch or interrupted update can leave the local configuration pointing to data the current client can no longer use. Rebuilding these files is safer than reinstalling the whole game because launcher verification does not normally replace per-user settings and shader caches.

1. Close Path of Exile 2 and exit Steam, Epic Games Launcher, or the standalone launcher.
2. Open %USERPROFILE%\Documents\My Games\Path of Exile 2.
3. Rename poe2_production_Config.ini to poe2_production_Config.old. For a full local reset, rename the entire Path of Exile 2 folder after preserving loot filters.

4. Open %APPDATA%\Path of Exile 2 and, if present, rename the folders beginning with ShaderCache. You may have separate DirectX 12, DirectX 11, or Vulkan cache folders.
5. Launch the game and allow it to create a clean configuration and rebuild its shader data. The first load may take longer or stutter while this happens.

If Windows also stops responding, repeated game-file reinstalls are unlikely to address the immediate failure. Grinding Gear Games has deployed fixes for this full-system freeze and asks affected players to keep reporting current cases separately from DirectX 12 device-lost crashes.

1. Open Options > Graphics and turn Engine Multithreading off.
2. Remove CPU or GPU overclocks and aggressive undervolts for the test.
3. Restart Windows, launch the game, and test one or two area transitions.

Disabling Engine Multithreading can reduce frame rate substantially, so use it as a temporary safety workaround and diagnostic, not an ideal permanent setting. If it prevents the hard lock, add that result to the official Path of Exile 2 full-PC-freeze thread.