Hogwarts Legacy Crashing Fix: Startup, Shader and HAGS Crashes

Hogwarts Legacy crashes on PC usually come from a stale shader cache, an outdated driver or Windows install, an overclock, damaged game files or antivirus interference — and the first fix is to delete C:\ProgramData\Hogwarts Legacy so the game rebuilds its shaders. That folder fix is Warner Bros. Games’ own first step for launch hangs, and Intel gives the same fix for the DXGI_ERROR_DRIVER_INTERNAL_ERROR crash. Match your crash in the table, then work only that section.

Match your crash to the fix

When Hogwarts Legacy crashes	Most likely cause	Fix first
Hangs on a blank screen “preparing shaders”, or crashes at launch	Stale or corrupt shader cache	Fix 1
DXGI_ERROR_DRIVER_INTERNAL_ERROR at launch (Intel Arc)	Old shaders after driver updates	Fix 1
Epic: “components required… Microsoft C++ Runtime”	Missing Visual C++ runtime	Fix 2
Random crashes mid-game on an RTX 40/50-class card	HAGS + frame-generation memory leak (patched 2024)	Fix 3
Crashes in many places, after a driver or Windows change	Driver, DirectX, overclock	Fix 4
Crashes on launch with no message	Damaged files, antivirus	Fix 5

Fix 1 — Delete the shader cache in ProgramData

Warner Bros. Games’ support article for launch hangs says to delete the shader cache folder C:\ProgramData\Hogwarts Legacy first. The game stores its compiled shaders there, and shaders built for an older driver can break after you update it.

1. Close Hogwarts Legacy and the launcher.
2. Open File Explorer, paste C:\ProgramData\Hogwarts Legacy into the address bar and press Enter. (ProgramData is hidden by default; typing the path works anyway.)
3. Delete everything inside the folder.
4. Launch the game and let it prepare shaders fully before you load a save — the first launch is slower.

Intel Arc users: Intel’s support article for the DXGI_ERROR_DRIVER_INTERNAL_ERROR launch crash on Arc A-Series cards gives exactly this fix — remove the files in C:\ProgramData\Hogwarts Legacy and run the game again so it compiles new shaders.

If the game still hangs while preparing shaders, WB’s next step is clearing your GPU driver’s shader cache too and restarting the PC. Our shader cache guide has the current folders for NVIDIA, AMD and Intel.

Fix 2 — Epic Games Store “Microsoft C++ Runtime” error

On the Epic Games Store version, WB lists a known issue where launch fails with “The following component(s) are required to run this program: Microsoft C++ Runtime”.

1. Download the Microsoft Visual C++ Redistributable (x64) from Microsoft’s own download page. (WB’s article links the 2015 package; Microsoft’s current Visual C++ v14 redistributable covers 2015 and later.)
2. Run the installer, then restart your PC.
3. Launch Hogwarts Legacy from Epic again.

If Windows instead reports a missing or broken DLL, see fixing DLL errors with DISM and SFC.

Fix 3 — Update the game and test HAGS off

WB’s PC hotfix of 24 July 2024 fixed critical crashes from memory leaks and invalid shared-pointer use on graphics cards that support frame generation when Hardware-Accelerated GPU Scheduling (HAGS) was enabled — the original report named NVIDIA RTX 40-series cards on Windows 11.

1. Make sure the game is fully updated in Steam, Epic or the Xbox app — a build older than that hotfix still has the bug.
2. If you still get random mid-game crashes on a frame-generation-capable card, turn HAGS off as a test: Settings → System → Display → Graphics → Change default graphics settings → Hardware-accelerated GPU scheduling → Off, then restart.
3. If the crashes stop, leave it off for this game session and re-test after the next driver update. Note that DLSS Frame Generation needs HAGS on — see HAGS on or off for the trade-off.

Fix 4 — Drivers, Windows Update and overclocks

WB’s PC troubleshooting article lists three system causes of crashes:

• Outdated or corrupted video and sound drivers. Install the latest driver from NVIDIA, AMD or Intel. If crashes started right after a driver update, do a clean install with DDU.
• Out-of-date DirectX. DirectX is updated through Windows Update — install every available update and restart.
• Overclocking or turbo-boosting components. WB strongly recommends resetting overclocked parts to manufacturer specifications. That includes GPU overclocks in MSI Afterburner, CPU overclocks and undervolts, and aggressive memory profiles while you test.

WB also recommends a lower in-game graphics preset if you’re crashing: higher settings increase the load on your hardware and can hurt stability even on PCs above the minimum spec. If the game hitches rather than crashes, that’s a different problem — see the Hogwarts Legacy stuttering fix and the best Hogwarts Legacy settings.

Fix 5 — Verify files and add an antivirus exception

• Verify the game files. In Steam: Library → right-click Hogwarts Legacy → Properties → Installed Files → Verify integrity of game files. On Epic: Library → ⋯ → Manage → Verify. WB’s next step after that is a full uninstall and reinstall.
• Antivirus. WB notes that antivirus software can quarantine game files and stop the game launching; add Hogwarts Legacy to your antivirus exceptions list.
• Background apps. Close as many other applications as you can before launching. As a test, WB suggests a Windows clean boot (Microsoft’s steps) to see whether a startup program is the cause — then reverse it afterwards.

If Hogwarts Legacy still crashes

• If the crash names an access violation, see 0xc0000005 access violation fix.
• If the GPU driver stops responding mid-game, see DXGI_ERROR_DEVICE_HUNG fix.
• If you run out of VRAM on high textures, see out of video memory error fix.
• If you use mods, disable them and test a clean game first.
• WB asks players to check its Hogwarts Legacy bug-reporting site for a matching report, vote on it and add details.

Related guides

• Hogwarts Legacy Stuttering Fix
• Best Hogwarts Legacy Settings for FPS
• Clear Shader Cache to Fix Stuttering
• Borderlands 4 Crashing Fix
• Unreal Engine D3D Device Lost Crash Fix

Most Hogwarts Legacy crashes clear with the ProgramData shader-cache delete, a current driver and Windows install, and stock clocks. Work the table top to bottom and change one thing at a time so you know which fix worked.