Got past login. Made a character. When logging into the character, the bar fills up on the loading screen and everything crashes with “Error 109”. Anyone else getting this?
1 Like
I was able to play for a few hours, but after swapping from DX12 back to DX11 I now get this error when trying to login across all my Forever characters. I even get it when making a new character. I tried re-installing, changing settings, messing with Faugus (I’m on Linux) etc. but nothing works. What’s worse is even after clean installs I still get the issue. Hopefully it will be patched or updated soon.
I did some testing with this error myself, and as long as I avoided Secondary Lighting being on ‘High’ I could scale everything else up. I started on 1 to get in and slowly adjusted settings until I found the crash. I can load in and play at 10 as long as Secondary Lighting is at ‘Good’ or lower. I recently had to lower it to ‘Fair’ based on where I had logged out, ‘Good’ still crashed it in Ironforge. Hope this helps.
Linux Mint, Lutris, Geforce 5070 TI, AMD Ryzen 9 7900
1 Like
This worked for me. Also on Linux Mint using Lutris. Geforce 2080TI.
Edit: Worked for a few, then I started having the same problem again. I found that I have to set the Secondary Lighting setting to Fair and then I have no problems.
I have secondary lighting turned down, still getting the error. Something is causing a GPU hang, and after several failures in the run, it triggered the error. I’m using Proton 10.0-4; will attempt to back up to Proton 9 to see if that resolves it.
From gx.log:
9/22 09:20:06.338 [0] Periodic Gpu Status Report: Mem Budget: 0.5GB / 7.0GB (7.6%)
9/22 09:20:13.725 [0] Render Settings Changed
9/22 09:20:20.410 [0] Render Settings Changed
9/22 09:20:30.900 [0] Failure in WaitForFence
9/22 09:20:30.900 [0] Device Removed Reason: GPU Hung. Timeout when waiting for queue: Graphics (0x80070102) count:1
9/22 09:20:30.939 [0] Device context was lost. Attempting recovery. Occurrence: 1
9/22 09:20:30.944 [0] Doing GxRestart. Reason:DeviceRecovery
9/22 09:20:30.944 [0] Dx11 Device Destroy
9/22 09:20:40.945 [0] Failure in WaitForFence
9/22 09:20:50.945 [0] Failure in WaitForFence
9/22 09:21:00.945 [0] Failure in WaitForFence
9/22 09:21:00.945 [0] Notify responders to DeviceDestroy event
9/22 09:21:21.970 Mapping “WatchdogThread” (ID 1384) as 1
9/22 09:21:21.970 [1] Crash Summary: ERROR #109 (0x8510006d) A thread has become unresponsive. Freeze Detected: thread 1660 has been frozen for 20 seconds
(DBG-OPTIONS DBG-ADDR<00007fffff8fc985>(“dxgi.dll”) ← DBG-ADDR<0000000143ea9c02>(“WowB.exe”) ← DBG-ADDR<0000000143e07b5d>(“WowB.exe”) DBG-OPTIONS<>)
For reference: I was using Proton 10.0-4 because retail worked with it.
I tested with Proton 9.0-4, Battle.net didn’t like that runner.
Tried Proton 11.0-2. I still get the same crash, same entries in gx.log.
I will look at other options, including Proton Experimental. I may have to download different runners to see if they’ll work.
I’m using Proton 9-23 (system 76 -gazelle / pop os) which works for all other versions of the game. Looking at everyone’s replies it seems we’re all? on Linux.
After a few days I tried again without switching runners or anything like that, and I was able to log in. There is a weird delay when running, but it seems Blizzard did something in the meantime.
The Error 109 is only Linux users. There’s a similar thread on EU with more responses and suggestions. I just had to lower a few more shadow and lighting effects on log in though I had no issues an hour ago. Hopefully they continue to improve through beta.
I was able to get both Battle.net and Forever running with no issues with Proton 11-3. I haven’t tried it with retail yet, but it would be nice if I had one that worked for both.
For any Steam users, it only has the base versions of Proton (11.0, 10.0, etc). You’ll need to download a different runner to get Forever to work.