WoW Forever crashing? Fixes for startup, loading screen and driver crashes
Short answer: 💥 Most WoW Forever beta crashes happened right as the loading screen finished. The fix players reported again and again was setting Secondary Lighting to Fair before entering the world. If that doesn't help, work through Blizzard's official crash steps below. (player reports, Blizzard Support)
| When it crashes | Most likely fix | Source |
|---|---|---|
| ⏳ End of the loading screen | 💡 Secondary Lighting to Fair before logging in | ⚠️ Player reports |
| 🖥️ AMD driver timeout / black screen | 💡 Secondary Lighting to Fair, then try windowed mode | ⚠️ Player reports |
| 🍎 Mac freezes on entering the world | 💡 Secondary Lighting to Fair at character select | ⚠️ Player reports |
| 🧊 Error #109 (thread unresponsive) | 💡 Lowest preset, then raise settings in-game | ⚠️ Player reports |
| 💀 Error #132 (fatal exception) | 🔧 Drivers, reset UI, close apps | ✅ Blizzard Support |
| ⬛ Black screen, music still plays | 🪟 Launch with -Windowed |
✅ Blizzard Support |
| 🔵 Blue screen / PC restarts | 🌡️ Hardware checks (heat, RAM, overclock) | ✅ Blizzard Support |
💡 The loading screen crash and the Secondary Lighting fix
During the beta, many players could reach character select but crashed the moment the world finished loading. Some got a black screen with sound still playing. Others lost the graphics driver or had their whole PC lock up. (AMD thread, Mac thread)
Players on Windows, Mac and Linux narrowed it to the Secondary Lighting setting. On Good, High or Ultra the game hung; on Fair it loaded normally. (9070 XT thread, bug report)
| Step | What to do |
|---|---|
| 1️⃣ | Log in to character select. Don't enter the world yet |
| 2️⃣ | Open Options > Graphics and set Secondary Lighting to Fair (the lowest option) |
| 3️⃣ | Also drop shadows low if you're on a Mac or an older GPU |
| 4️⃣ | Enter the world |
| 5️⃣ | Once you're in, raise other settings one at a time. Leave Secondary Lighting on Fair if it crashed before |
⚠️ Status: this is a player workaround, not a Blizzard fix. Blizzard's Known Issues thread doesn't list this crash, and we haven't found an official note saying it's fixed for launch. [Unconfirmed] One player said the hang stopped for them after a later beta build. (bug report)
The menu path above comes from the beta client. [Unconfirmed] for the launch client. For the separate Secondary Lighting frame rate bug that Blizzard did fix, see our graphics page.
🖥️ AMD driver crashes and black screens
AMD Radeon owners (RX 7000 and RX 9000 cards) reported the most driver timeouts. Some came back after a 15 Oct beta patch. (AMD driver thread) Not every AMD player had trouble, so treat this as "common", not "every card".
| Try | What players said | Source |
|---|---|---|
| 💡 Secondary Lighting on Fair | Fixed it for most | AMD thread |
| 🪟 Windowed mode | Smooth again for one 9070 XT owner | AMD driver thread |
| 🧱 DX11 instead of DX12 | Avoided the crash but caused stutter | AMD thread |
🗑️ Delete the Cache folder, enter at lowest settings |
Worked for one player (two changes at once) | AMD driver thread |
| ⚙️ Turn off Optional GPU Features | Suggested by players for AMD cards | 9070 XT thread |
🧊 Error #109: "A thread has become unresponsive"
This error appears when the game freezes for about 20 seconds. In the beta it usually followed the same GPU hang on world load. (error #109 thread, bug report)
| Player fix | Notes |
|---|---|
| 1️⃣ Secondary Lighting to Fair | Start here |
| 2️⃣ Graphics quality to 1 at character select, then raise it in-game | Some found it worked in one zone and failed in the next |
| 3️⃣ Turn off Optional GPU Features | Several Linux players said this alone fixed it |
| 4️⃣ Turn off Multithreaded Rendering | Less clear; one player could leave it on |
💀 Error #132 and other crash codes
Error #132 is a generic crash code, so it isn't Forever-specific. Blizzard Support says it can come from out-of-date addons, corrupted files, drivers or hardware. (Error 132) Search Blizzard Support for your exact code first; many codes have their own article. (Technical Troubleshooting)
| Code | What Blizzard says to try |
|---|---|
| 💀 #132 Fatal exception | Update drivers and OS, reset your UI, close other apps, allow Blizzard in your security software, check for overheating (Blizzard) |
| 🧩 ACCESS_VIOLATION (C0000005) | Same driver and security steps, then reinstall and repair disk permissions (Blizzard) |
| 🧊 #109 | No Forever-specific Blizzard article found. Use the player fixes above ⏳ |
🧩 Addons: resetting your UI means moving your addons and settings aside to test. Our addons troubleshooting page shows where those folders live.
🔧 Blizzard's official crash checklist
These steps are from Blizzard Support's World of Warcraft troubleshooting article. They're written for all WoW versions, and Forever uses the same Battle.net app. (Technical Troubleshooting)
| # | Step |
|---|---|
| 🔍 1 | Search Blizzard Support for your exact error message or code |
| 🔄 2 | Update your graphics drivers and operating system |
| 🛠️ 3 | Run Scan and Repair in the Battle.net app to fix damaged files |
| 🖥️ 4 | Check you meet the system requirements. Playing below the minimum often causes instability |
| ⚙️ 5 | Reset graphics to defaults (Blizzard's path: Main Menu > System > Graphics > Defaults). [Unconfirmed] in the Forever client |
| 🗑️ 6 | If all else fails, uninstall and reinstall the game |
Black screen with music still playing? Blizzard's fix is to start in windowed mode: in the Battle.net app open Game Settings, tick Additional command line arguments under World of Warcraft, and type -Windowed. (Black Screen)
Blue screen, or your PC restarts? Blizzard says that's a system problem, not the game. Check for overheating, test your RAM, turn off overclocking (including factory overclocks) and update drivers. (Blue Screen Crashes)
🍎 Mac and 🐧 Linux / Steam Deck
- 🍎 Mac: Apple Silicon players (M2 Pro, M4, M5) reported full freezes on entering the world. The same Secondary Lighting fix worked. (Mac thread) Mac-only bugs and the Rosetta fix for Battle.net are on our Mac page.
- 🐧 Linux / Steam Deck: not supported by Blizzard. Players found the same Secondary Lighting hang under Proton. See Steam Deck.
📋 Related pages
| Page | For |
|---|---|
| Graphics settings and FPS | Low FPS, settings resetting |
| Addons not working | Lua errors, outdated addons |
| Download and install | Install problems, install size |
| Server status | Can't connect, realms down |
FAQ
Why does WoW Forever crash on the loading screen?
In the beta, most reports traced it to the Secondary Lighting setting. Setting it to Fair before entering the world stopped it for many players.
Has Blizzard fixed the loading screen crash?
Unconfirmed. Blizzard hasn't listed it on its Known Issues thread, and we found no official fix note for launch.
Why does my AMD driver time out in WoW Forever?
Players with RX 7000 and 9000 cards reported it in the beta. Secondary Lighting on Fair, windowed mode or DX11 helped some. Update your driver too.
What is error #109 in WoW Forever?
It means a game thread froze for 20 seconds. Beta players saw it after a GPU hang on world load. Try the Secondary Lighting fix first.
What is error #132?
A generic crash. Blizzard says it can be addons, corrupted files, drivers or hardware. Update drivers, reset your UI and close other apps.
WoW Forever crashes on Mac. What do I do?
Set Secondary Lighting to Fair at character select, before you log in. See our Mac page for more Mac-only fixes.
Will reinstalling fix crashes?
Sometimes, but it's Blizzard's last step. Try Scan and Repair, driver updates and lower settings first.
Sources
- Blizzard Support: World of Warcraft Technical Troubleshooting (Crashing section)
- Blizzard Support: Error 132
- Blizzard Support: Unhandled Exception: Access_Violation (C0000005)
- Blizzard Support: Black Screen - World of Warcraft
- Blizzard Support: Blue Screen Crashes in Blizzard Games
- Blizzard forums (player reports): GPU hang after world load, build 69913, Secondary Lighting workaround
- Blizzard forums (player reports): WoW Forever crash on loading (AMD)
- Blizzard forums (player reports): 9070XT crashing on loading into game
- Blizzard forums (player reports): ERROR #109 A thread has become unresponsive
- Blizzard forums (player reports): Hard crashes on loading screen, M5 Apple Silicon Mac
- Blizzard forums (player reports): AMD driver crash after latest patch (17 Oct)
- Blizzard forums: WoW Forever Beta Known Issues thread (Kaivax), via Blue Tracker