WoW Forever Crashing Fix: Launch Crashes, Error 134 & DX12
Published
On this page
WoW Forever crashes are usually fixed by one of four changes: switch the Graphics API to DirectX 11, pick your real graphics card instead of auto-detect, add an antivirus exclusion for the whole World of Warcraft folder, or end stray WoW processes that cause Error #134. Those four come from WoW: Forever beta threads on Blizzard’s own forums (September–October 2026), where they fixed most reported launch, login and loading-screen crashes. WoW Forever launches on 4 November 2026, and launch builds may fix some of these, so work through the steps in order and stop when the crash stops.
Blizzard doesn’t offer technical support for the beta, and its support articles sit behind a Battle.net login, so the fixes below are the ones players confirmed on Blizzard’s forums. They’re labelled as player-reported where that’s all they are.
Match your crash to the fix
| What happens | Likely cause | Fix |
|---|---|---|
| Game closes 1–2 seconds after Play, no window | Antivirus blocking the client, or a locked cache | Antivirus exclusion, then clear the cache |
ERROR #134 (0x85100086) Fatal condition at launch | Another WoW or Agent.exe process locking the game data | End stray processes |
Crash or freeze loading into the world, missing terrain, Fatal Error | DirectX 12 shader loading | Switch to DirectX 11 |
| Crash right after picking a character | Lighting/shadow settings | Lower Secondary Lighting |
| Low FPS and crashes on a laptop | Game running on the integrated GPU | Pick your graphics card |
| FPS sinks over 30 minutes, no crash | Client memory leak | Memory-leak fix |
1. Add an antivirus exclusion for the whole WoW folder
If WoW Forever disappears a second or two after you press Play, with no window and nothing in the Errors folder that helps, antivirus is the first suspect. On Blizzard’s forum thread about the BEX64 / dbghelp.dll / 0xC0000005 launch crash, the fix that worked for several players was adding an exclusion for the entire World of Warcraft folder, even though the antivirus never reported blocking anything.
In Windows Security: Virus & threat protection → Manage settings → Exclusions → Add or remove exclusions → Add an exclusion → Folder, then pick your World of Warcraft install folder (not just the WoW Forever sub-folder). Third-party antivirus has its own exclusion list. For the general 0xc0000005 crash, see our access violation crash fix.
2. Fix Error #134 by ending stray WoW processes
ERROR #134 (0x85100086) Fatal condition with a crash report that says the CAS system “was unable to initialize” and the container is locked means another process holds the game data. Beta players traced it to a background World of Warcraft client or Battle.net’s Agent.exe.
- Close the Battle.net app.
- Open Task Manager (Ctrl + Shift + Esc).
- End every World of Warcraft process and Agent.exe.
- Reopen Battle.net. Let any pending WoW Forever update finish, then press Play.
If the Error #134 report talks about failing to download version data instead of a locked container, it’s a connection or patching problem. Wait for Battle.net to finish updating, or run Scan and Repair from the gear menu next to Play.
3. Switch the Graphics API to DirectX 11
WoW Forever uses DirectX 12 by default. On the beta forums, crashes where the world loads without terrain, freezes, black-screens the monitor and ends in Fatal Error were fixed by switching to DirectX 11; one poster blamed shader loading in DX12. Change it in the game’s System → Advanced graphics options (Graphics API: DirectX 11), then restart the game.
If you can’t reach the settings because the game crashes first, close it and edit WTF\Config.wtf in the WoW Forever folder: set the line SET gxApi "D3D11" (add it if it isn’t there). WoW reads this setting at startup. Delete the line later to go back to the default.
DX11 isn’t a universal fix. One player using an external GPU dock crashed only on DX11 and fixed it by updating a 2017-era NVIDIA driver, so update your driver too (step 7).
4. Clear the Cache folder
A corrupted cache can stop the client from starting. With the game and Battle.net closed, open the WoW Forever folder inside your World of Warcraft install (_classic_beta_ during the beta) and delete the Cache folder. The game rebuilds it on the next launch. One beta player also deleted a leftover WowB_Loader.dll from that folder; others reported it didn’t help, and one had to reinstall afterwards. Delete only Cache first, and use Scan and Repair rather than deleting game files by hand.
5. Lower Secondary Lighting and shadows from character select
For crashes to desktop right after you choose a character, open Menu on the character-select screen and set Secondary Lighting to Fair. Warcraft Tavern reported this fix on 18 September 2026 from its readers. Results in its comments were mixed: some players fixed the same crash by lowering Shadow Quality to its lowest setting, others needed DirectX 11. Changing these at character select means the world never loads at the old settings.
6. Pick your real graphics card
On laptops and desktops with integrated graphics, WoW Forever can run on the integrated GPU. A beta player went from crashing to 100+ FPS at max settings by changing Graphics → Advanced → Graphics Card from auto-detect to their actual GPU. You can also set it in Windows: Settings → System → Display → Graphics, add the WoW Forever executable and choose High performance.
7. Update or clean-install your GPU driver
Old drivers came up again and again in the beta threads, including a 2017 driver on an external GPU dock that only worked after a manual update from NVIDIA. Install the current driver from NVIDIA, AMD or Intel rather than the laptop maker’s older one. If crashes started after a driver update, do a clean install with DDU.
If the crash message names video memory, follow the out of video memory fix. If it’s a DXGI_ERROR_DEVICE_HUNG or device-removed error, see the DXGI device hung fix.
8. Remove GPU overclocks and turn off overlays
This is our general guidance, not something Blizzard published for WoW Forever. Reset any GPU overclock or undervolt to stock, and close overlays and monitoring tools (MSI Afterburner, RivaTuner, recording overlays) while you test. A tuning profile that is stable in one game can crash another engine. Re-enable them one at a time once the game runs.
Crashes the beta players couldn’t fix
Some beta crashes had no player fix. A detailed thread for build 69913 logged repeatable null-read crashes in WowB.exe and a “Security Crash” in WowB_loader.dll across several PCs, and nothing the poster tried on Windows stopped them. If your crash report matches, it’s a client bug: send it with the in-game bug report tool or post it in Blizzard’s WoW Forever forum, and check whether a launch-day patch fixes it.
Fix WoW Forever performance, not just crashes
Once the game runs, set it up with the best WoW Forever settings for FPS. If FPS sinks the longer you play, that’s the client memory leak, and logging out to character select resets it. For the Windows side (power plan, background apps, timer resolution), Tier1Suite applies the common fixes in one place.
The short version
- Add an antivirus exclusion for the whole World of Warcraft folder.
- For Error #134, end every WoW process and Agent.exe, then relaunch.
- Switch the Graphics API to DirectX 11 if the world crashes while loading.
- Delete the
Cachefolder and run Scan and Repair. - Set Secondary Lighting to Fair from character select.
- Pick your real GPU instead of auto-detect.
- Update or clean-install your GPU driver.
Related guides
Frequently asked questions
Why does WoW Forever keep crashing?
During the WoW Forever beta the most common crash reports on Blizzard's forums traced back to four things: DirectX 12 shader loading on some GPUs, the game auto-picking an integrated GPU instead of the graphics card, antivirus blocking the client at launch, and a leftover WoW process locking the game data (Error #134). Switching the Graphics API to DirectX 11, choosing your real GPU in the Advanced graphics settings, adding an antivirus exclusion for the whole World of Warcraft folder and ending stray WoW processes fixed most reported cases.
How do I fix WoW Forever Error #134 (0x85100086) Fatal Condition?
Error #134 with 'container locked' in the crash report means another process is holding the game's data. Close Battle.net, open Task Manager, end every World of Warcraft and Agent.exe process, then reopen Battle.net and press Play. If the error mentions downloading version data instead, let Battle.net finish updating or run Scan and Repair from the game's options menu.
Should I use DirectX 11 or DirectX 12 for WoW Forever?
Use DirectX 12 by default and switch to DirectX 11 if the game crashes or freezes while loading into the world, or shows missing terrain with a Fatal Error. Several beta players fixed exactly that crash with DX11. The opposite also happened: one player with an old external-GPU driver crashed only on DX11, and updating the GPU driver fixed it, so update your driver before deciding.
Why does WoW Forever crash when I log into my character?
Crashes right after character select were most often fixed by lowering Secondary Lighting to Fair or Shadow Quality to its lowest, or by switching the Graphics API to DirectX 11. Change these from the Menu on the character-select screen so the game never has to load the world at the old settings.
Is a WoW Forever crash the same as the FPS drop over time?
No. A crash closes the game or shows a Fatal Error. The FPS drop that builds over 15 to 30 minutes is a memory leak in the client, and logging out to character select and back in resets it. If the game only gets slower and never closes, use the memory-leak fix instead of the crash steps.