TBC Classic doesn't work, Classic and Shadowlands work fine

Support Technical Support
1

Heyo.

I’ve got an issue here where TBC Classic launches with sound and the armor cursor, but there’s no video. Launching with “Windowed” is just a white screen, then I get an Error 132: Access Violation. Adding command line argument of “-d3d11” or “-d3d11legacy” or “-d3d9” or “-opengl” do nothing.

These errors do NOT happen with WoW Classic, or Shadowlands, they open and run just fine. Only Burning Crusade Classic is unable to start up.

Any ideas?

2

A white screen sounds like a firewall/security app is blocking files for that version of the game. We could help more if you post info for us to work from, like the error log in the wow folder, or your DxDiag/MSInfo.

3

I am having the exact same problem. I even tried uninstalling and reinstalling the game but nothing changed. Any help on how to fix it would be greatly appreciated.

4

Just as I mentioned in my reply above, I cannot suggest definite fixes without some data/error logs to work with.

5

Are you on a system that has a dedicated and integrated GPU? (nvidia optimus)

If so, you might need to locate the wow tbc exe, right click, run with whatever nvidia gpu you have. If the drivers aren’t new enough, the setting in the NVCP won’t stick sometimes and it will still try to run with the IGPU instead of the dedicated one, so you’ll have to do the right click run with trick every time you boot it up.

6

This is what my gx log looks like.

Why would WoW Classic and Shadowlands work, but Burning Crusade Classic not work? Does not make much sense.

5/28 01:48:36.217 LogOpen
5/28 01:48:36.217 World of Warcraft Retail x86_64 2.5.1.38757
5/28 01:48:36.217 Windows 10 (10.0.19042) x86_64
5/28 01:48:36.217 AMD Ryzen Threadripper 3970X 32-Core Processor | Sockets:1 Cores:32 Threads:64
5/28 01:48:36.217 63.9 GB System Memory
5/28 01:48:36.217 On AC Power - Battery Not Present
5/28 01:48:36.217 Force API D3D11_LEGACY
5/28 01:48:36.493 Adapter 0: “NVIDIA GeForce RTX 3090” family:Turing type:Discrete vendor:0x10de device:0x2204 driver(0x1b0015000e19f7) location:76 dx11:true dx12:false
5/28 01:48:36.493 Monitor 0 “Generic PnP Monitor” Size(2560x1440) Pos(0, 0)
5/28 01:48:36.900 Adapter 1: “NVIDIA GeForce GTX 1050 Ti” family:Pascal type:Discrete vendor:0x10de device:0x1c82 driver(0x1b0015000e19f7) location:1 dx11:true dx12:false
5/28 01:48:36.900 Monitor 0 “ZOWIE XL LCD (DisplayPort)” Size(2560x1440) Pos(2560, 0)
5/28 01:48:36.900 Monitor 1 “Generic PnP Monitor” Size(1920x1080) Pos(0, -1080)
5/28 01:48:36.900 Monitor 2 “DELL S2340M(Digital)” Size(1920x1080) Pos(-1920, 255)
5/28 01:48:36.900 Monitor 3 “Generic PnP Monitor” Size(1920x1080) Pos(-1920, -1080)
5/28 01:48:37.200 Adapter 3: “NVIDIA GeForce GTX 1050 Ti” family:Pascal type:External vendor:0x10de device:0x1c82 driver(0x1b0015000e19f7) location:0 dx11:true dx12:false
5/28 01:48:37.200 Unable to load “d3d12.dll”
5/28 01:48:37.200 Nvidia driver version: r466_41
5/28 01:48:37.216 Choosing headless egpu: “NVIDIA GeForce GTX 1050 Ti [1]”
5/28 01:48:37.216 D3d11 Legacy Device Create
5/28 01:48:37.482 Created 11.0 Device
5/28 01:48:37.482 SetMaximumFrameLatency set: 3
5/28 01:48:37.482 AFR detection
5/28 01:48:37.482 AFR found with 1 devices(s)
5/28 01:48:38.516 Deferred Mode = 0
5/28 01:48:38.530 NotifyOnDeviceCreate
5/28 01:48:38.530 D3d11 Legacy Device Create Successful
5/28 01:48:38.787 No
5/28 01:48:38.787 Detected Graphics Defaults: 7 (CPU = 7, GPU = 7, MEM = 7)
5/28 01:48:38.868 Render Settings Changed. New Render Size: 2560x1440
5/28 01:48:39.603 Error DeviceRemoved: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
5/28 01:48:39.603 Device Removed Reason: An internal issue prevented the driver from carrying out the specified operation. The driver’s state is probably suspect,
and the application should not continue. (0x887A0020).
5/28 01:48:39.621 Device context was lost. Attempting recovery. Occurrence: 1
5/28 01:48:39.636 GxRestart
5/28 01:48:57.777 Device Removed Reason: An internal issue prevented the driver from carrying out the specified operation. The driver’s state is probably suspect,
and the application should not continue. (0x887A0020).
5/28 01:48:57.777 Device context was lost. Attempting recovery. Occurrence: 24
5/28 01:48:57.794 GxRestart
5/28 01:48:57.794 D3d11 Device Destroy
5/28 01:48:57.794 NotifyOnDeviceDestroy
5/28 01:48:57.915 D3d11 Device Destroyed
5/28 01:48:57.917 Choosing headless egpu: “NVIDIA GeForce GTX 1050 Ti [1]”
5/28 01:48:57.917 D3d11 Legacy Device Create
5/28 01:48:58.144 Created 11.0 Device
5/28 01:48:58.144 SetMaximumFrameLatency set: 3
5/28 01:48:58.144 AFR detection
5/28 01:48:58.144 AFR found with 1 devices(s)
5/28 01:48:58.144 Deferred Mode = 0
5/28 01:48:58.152 NotifyOnDeviceCreate
5/28 01:48:58.333 D3d11 Legacy Device Create Successful
5/28 01:48:58.333 No
5/28 01:48:58.333 Render Settings Changed
5/28 01:48:58.495 Error DeviceRemoved: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
5/28 01:48:58.495 Device Removed Reason: An internal issue prevented the driver from carrying out the specified operation. The driver’s state is probably suspect,
and the application should not continue. (0x887A0020).
5/28 01:48:58.495 Device context was lost. Attempting recovery. Occurrence: 25
5/28 01:48:58.512 GxRestart
5/28 01:48:58.512 D3d11 Device Destroy
5/28 01:48:58.512 NotifyOnDeviceDestroy
5/28 01:48:58.628 D3d11 Device Destroyed
5/28 01:48:58.628 Choosing headless egpu: “NVIDIA GeForce GTX 1050 Ti [1]”
5/28 01:48:58.628 D3d11 Legacy Device Create
5/28 01:48:58.858 Created 11.0 Device
5/28 01:48:58.858 SetMaximumFrameLatency set: 3
5/28 01:48:58.858 AFR detection
5/28 01:48:58.858 AFR found with 1 devices(s)
5/28 01:48:58.858 Deferred Mode = 0
5/28 01:48:58.858 NotifyOnDeviceCreate
5/28 01:48:59.049 D3d11 Legacy Device Create Successful
5/28 01:48:59.049 No
5/28 01:48:59.049 Render Settings Changed
5/28 01:48:59.210 Error DeviceRemoved: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
5/28 01:48:59.210 Device Removed Reason: An internal issue prevented the driver from carrying out the specified operation. The driver’s state is probably suspect,
and the application should not continue. (0x887A0020).
5/28 01:48:59.210 Device context was lost. Attempting recovery. Occurrence: 26
5/28 01:48:59.227 GxRestart
5/28 01:48:59.227 D3d11 Device Destroy
5/28 01:48:59.227 NotifyOnDeviceDestroy
5/28 01:48:59.352 D3d11 Device Destroyed
5/28 01:48:59.353 Choosing headless egpu: “NVIDIA GeForce GTX 1050 Ti [1]”
5/28 01:48:59.353 D3d11 Legacy Device Create
5/28 01:48:59.588 Created 11.0 Device
5/28 01:48:59.588 SetMaximumFrameLatency set: 3
5/28 01:48:59.588 AFR detection
5/28 01:48:59.588 AFR found with 1 devices(s)
5/28 01:48:59.588 Deferred Mode = 0
5/28 01:48:59.588 NotifyOnDeviceCreate
5/28 01:48:59.777 D3d11 Legacy Device Create Successful
5/28 01:48:59.777 No
5/28 01:48:59.777 Render Settings Changed
5/28 01:48:59.962 Error DeviceRemoved: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
5/28 01:48:59.962 Device Removed Reason: An internal issue prevented the driver from carrying out the specified operation. The driver’s state is probably suspect,
and the application should not continue. (0x887A0020).
5/28 01:48:59.964 Device context was lost. Attempting recovery. Occurrence: 27
5/28 01:48:59.979 GxRestart
5/28 01:48:59.979 D3d11 Device Destroy
5/28 01:48:59.979 NotifyOnDeviceDestroy
5/28 01:49:00.100 D3d11 Device Destroyed
5/28 01:49:00.100 Choosing headless egpu: “NVIDIA GeForce GTX 1050 Ti [1]”
5/28 01:49:00.100 D3d11 Legacy Device Create
5/28 01:49:00.334 Created 11.0 Device
5/28 01:49:00.334 SetMaximumFrameLatency set: 3
5/28 01:49:00.334 AFR detection
5/28 01:49:00.334 AFR found with 1 devices(s)
5/28 01:49:00.334 Deferred Mode = 0
5/28 01:49:00.343 NotifyOnDeviceCreate
5/28 01:49:00.533 D3d11 Legacy Device Create Successful
5/28 01:49:00.533 No
5/28 01:49:00.533 Render Settings Changed
5/28 01:49:00.701 Error DeviceRemoved: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
5/28 01:49:00.701 Device Removed Reason: An internal issue prevented the driver from carrying out the specified operation. The driver’s state is probably suspect,
and the application should not continue. (0x887A0020).
5/28 01:49:00.701 Device context was lost. Attempting recovery. Occurrence: 28
5/28 01:49:00.718 GxRestart
5/28 01:49:00.718 D3d11 Device Destroy
5/28 01:49:00.718 NotifyOnDeviceDestroy
5/28 01:49:00.841 D3d11 Device Destroyed
5/28 01:49:00.841 Choosing headless egpu: “NVIDIA GeForce GTX 1050 Ti [1]”
5/28 01:49:00.841 D3d11 Legacy Device Create
5/28 01:49:01.089 Created 11.0 Device
5/28 01:49:01.089 SetMaximumFrameLatency set: 3
5/28 01:49:01.089 AFR detection
5/28 01:49:01.089 AFR found with 1 devices(s)
5/28 01:49:01.089 Deferred Mode = 0
5/28 01:49:01.089 NotifyOnDeviceCreate
5/28 01:49:01.285 D3d11 Legacy Device Create Successful
5/28 01:49:01.285 No
5/28 01:49:01.285 Render Settings Changed
5/28 01:49:01.441 Error DeviceRemoved: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
5/28 01:49:01.441 Device Removed Reason: An internal issue prevented the driver from carrying out the specified operation. The driver’s state is probably suspect,
and the application should not continue. (0x887A0020).
5/28 01:49:02.197 D3d11 Device Destroy
5/28 01:49:02.197 NotifyOnDeviceDestroy
5/28 01:49:02.328 D3d11 Device Destroyed
5/28 01:49:02.328 GxShutdown

7

You might want to try disabling your second GPU in the device manager:

  1. Start key+X
  2. Device manager
  3. Display adapters
  4. Select which GPU you DON’T use for WoW
  5. Right click+disable device
  6. Shut the PC all the way down because sometimes motherboard stuff doesn’t fully reset properly on a restart
  7. Power on
  8. Try WoW again

If that didn’t fix it, you can repeat the same steps to renable the device. It’s possible you have bad/old drivers for the motherboard that might be messing with the PCIE systems. That or your BIOS might be old or incorrectly set up.

8

It’s something wrong with the way Burning Crusade Classic is launching. It’s attempting to launch on a GPU that is not my main monitor. Even if I open it up and tell it to launch on my RTX 3090 after disabling my 1050 ti, it still attempts to launch on the 1050ti, even after setting the 3090 as the GPU in the Advanced settings section of the Burning Crusade Classic settings menu.

Not an issue with my computer. WoW Classic and Shadowlands work 100% no issues.

EDIT: I found the solution myself. The game was generating an improper hardware config.wtf.

Steps are:

  1. Delete all logs in \World of Warcraft\_classic_\Logs
  2. Launch game, and then close after encountering error.
  3. Open gxLog located in \World of Warcraft\_classic_\Logs
  4. Get name of GPU you wish to use. In my case it was "Adapter 0: “NVIDIA GeForce RTX 3090”.
  5. Open up Config.wtf located in \World of Warcraft\_classic_\WTF with Notepad, or Notepad++ in my case.
  6. Find the line that says SET hwDetect "1" and change it to SET hwDetect "0". If it is already SET hwDetect "0", do not change it.
  7. Add a line beneath it that says SET gxAdapter "INSERT YOUR GPU NAME HERE", so in my case it was SET gxAdapter "NVIDIA GeForce RTX 3090".
  8. Save the file.
  9. Launching the game should work now.
9

Yeah that’s what I was slowly working toward explaining if the fix I suggested didn’t work. Didn’t want to get into the nitty gritty editing unless I had to. Glad you found a fix though!

10

I attempted to try your solution, but I guess because I uninstalled and reinstalled the game first, I do not have a config.WTF file at all in my classic folder.
I was hoping Blizzard would fix the issue in a patch but no luck so far.
I even tried to find a phone number so I could talk to someone at Blizzard to help me but I can’t even find a support number.
It feels like I’m screwed until they patch and fix the issue.

If you need it I am on a Dell Laptop, pretty old, and Intel® HD Graphics 4000 is my gx adapter.

11

Yep. Same problem here and unfortunately that fix didn’t help. Hope they fix this soon.

Aced aspire v15 with NVIDIA GeForce GTX 950M on my end