Unable to Start 3D Acceleration after patch

Dredlok-atiesh · March 11, 2020, 1:47am

Battle.net patched the client up to 1.13.4.xxxx today and now I can’t play the game (classic) anymore.

I get the error in the thread title. Wasn’t happening before the patch.
My config.wtf used to have “D3D11” in there somewhere but I can’t even find that line anymore.

Am I the only one with this issue? What was so important in this update that the devs had to tweak the way the client operates on a graphical level?

Windows 10 Home, DirectX 12, I have Intel Integrated HD Graphics 3000 and a mobile Nvidia card (it’s a laptop). Thanks

Jambrix · March 11, 2020, 1:51am

Hey Dredlok,

I’m not aware of any changes today that would cause this for WoW Classic. There was a Battle.net app patch but that should not have affected WoW.

Can you try resetting the game settings through the Battle.net app to see if that helps?

If not, go ahead and post your DXDIAG.

DXDIAG:

Press Windows Key + R.
In the Run window type dxdiag and press Enter.
In the DirectX window, click Save All Information.
Name the file “dxdiag” and save it to your Desktop. Open the new dxdiag file with Notepad.
In the posting section here hit the </> button for “Preformatted text” then paste (Ctrl+V) the DXDIAG contents. That’ll make the information much more readable.

If you are unable to post this due to the length of the DXDIAG, please feel free to use pastebin.com and share the link with us instead. Use the </> button as well in order to share the link.

Dredlok-atiesh · March 11, 2020, 2:04am

Did you update the client yesterday then? it definitely updated the client because it wouldn’t let me login to any servers. I had to open battle.net and hit “update” button, after which I couldn’t even start the client without the 3d acceleration error. I tried rebooting as well. Basically the update bricked it.

Pastbin is: https://pastebin.com/TiteX6us

Jambrix · March 11, 2020, 2:14am

Thanks for the DXDIAG.

Actually there was a patch for WoW Classic today, patch 1.13.4, but the patch didn’t have any mention of changes to graphics or any pre-known bugs that would cause the error you’re getting. It’s always possible something was missed of course, but yours is the first report I’m seeing of this since the patch.

The DXDIAG looks good at first glance.

Can you post the contents of your gx log from the Logs folder inside the _classic_folder? I’m curious to see if the game is maybe trying to launch using your Intel HD Graphics 3000 instead of the Nvidia Geforce 540M.

Dredlok-atiesh · March 11, 2020, 2:22am

Thanks for the help. It’s not using intel card, I’ve definitely made sure my nvidia control panel/windows 10 knows to use nvidia as the default card.

Also I noticed in the windows error section at the end of dxdiag:

Problem signature:
P1: WowClassic.exe
P2: 1.13.4.33598
P3: 5e613ff1
P4: unknown
P5: unknown
P6: unknown
P7: unknown
P8: 
P9: 
P10:

Don’t know what that means though. Here’s what you asked for from
the gx log file:

3/10 22:20:23.223  LogOpen
3/10 22:20:23.310  ConsoleDetectDetectHardware():
3/10 22:20:23.339  	cpuIdx: 1
3/10 22:20:23.386  ConsoleDeviceInitialize(): hwDetect = 0, hwChanged = 0
3/10 22:20:23.446  D3d11 Device Create
3/10 22:20:23.466  	Format 1366 x 768 Fullscreen, ArgbX888, vsync 0
3/10 22:20:23.506  Found Adapter 0: Vendor Id 0x8086, Device Id 0x0116 - Sysmem = 0
3/10 22:20:23.532  Monitor 0 attached to adapter 0
3/10 22:20:23.563  Found Adapter 1: Vendor Id 0x10de, Device Id 0x0df4 - Sysmem = 0
3/10 22:20:23.587  Skipping Software VendorID Adapter 2: Vendor Id 0x1414, Device Id 0x008c - Sysmem = 0
3/10 22:20:23.617  Choosing adapter 1
3/10 22:20:23.643  Detected NvAPI and checking if it's valid...
3/10 22:20:23.738  AFR detection
3/10 22:20:23.765  AFR found with 1 devices(s)
3/10 22:20:23.795  Caps:
3/10 22:20:23.821  	Vendor ID: 10de
3/10 22:20:23.850  	Device ID: df4
3/10 22:20:23.876  	AFR Groups: 1/1
3/10 22:20:23.906  Feature Level: DX=3, GL=0, MTL=0
3/10 22:20:23.950  D3d11 Device Create Successful
3/10 22:20:24.074  D3d11 Device Destroy
3/10 22:20:24.129  D3d11 Device Destroyed
3/10 22:20:24.150  D3d11 Device Create
3/10 22:20:24.176  	Format 1366 x 768 Fullscreen, ArgbX888, vsync 0
3/10 22:20:24.218  Found Adapter 0: Vendor Id 0x8086, Device Id 0x0116 - Sysmem = 0
3/10 22:20:24.243  Monitor 0 attached to adapter 0
3/10 22:20:24.273  Found Adapter 1: Vendor Id 0x10de, Device Id 0x0df4 - Sysmem = 0
3/10 22:20:24.298  Skipping Software VendorID Adapter 2: Vendor Id 0x1414, Device Id 0x008c - Sysmem = 0
3/10 22:20:24.328  Choosing adapter 1
3/10 22:20:24.354  Detected NvAPI and checking if it's valid...
3/10 22:20:24.409  AFR detection
3/10 22:20:24.432  AFR found with 1 devices(s)
3/10 22:20:24.461  Caps:
3/10 22:20:24.499  	Vendor ID: 10de
3/10 22:20:24.539  	Device ID: df4
3/10 22:20:24.565  	AFR Groups: 1/1
3/10 22:20:24.595  Feature Level: DX=3, GL=0, MTL=0
3/10 22:20:24.638  D3d11 Device Create Successful
3/10 22:20:24.698  D3d11 Device Destroy
3/10 22:20:24.735  D3d11 Device Destroyed
3/10 22:20:24.761  D3d11 Device Create
3/10 22:20:24.788  	Format: 1366 x 768 Window, vsync 0
3/10 22:20:24.825  Found Adapter 0: Vendor Id 0x8086, Device Id 0x0116 - Sysmem = 0
3/10 22:20:24.854  Monitor 0 attached to adapter 0
3/10 22:20:24.885  Found Adapter 1: Vendor Id 0x10de, Device Id 0x0df4 - Sysmem = 0
3/10 22:20:24.910  Skipping Software VendorID Adapter 2: Vendor Id 0x1414, Device Id 0x008c - Sysmem = 0
3/10 22:20:24.953  Choosing adapter 1
3/10 22:20:24.988  Detected NvAPI and checking if it's valid...
3/10 22:20:25.044  AFR detection
3/10 22:20:25.065  AFR found with 1 devices(s)
3/10 22:20:25.095  Caps:
3/10 22:20:25.121  	Vendor ID: 10de
3/10 22:20:25.150  	Device ID: df4
3/10 22:20:25.177  	AFR Groups: 1/1
3/10 22:20:25.206  Feature Level: DX=3, GL=0, MTL=0
3/10 22:20:25.252  D3d11 Device Create Successful
3/10 22:20:25.352  D3d11 Device Destroy
3/10 22:20:25.399  D3d11 Device Destroyed
3/10 22:20:25.422  ReportDeviceCreationFailure(): no output device available!

Jambrix · March 11, 2020, 2:37am

Thanks,

It is indeed using the Nvidia card, so we are good there. The vendor ID and device ID match the 540M.

3/10 22:20:23.563 Found Adapter 1: Vendor Id 0x10de, Device Id 0x0df4 - Sysmem = 0
3/10 22:20:23.617 Choosing adapter 1

I noticed the WoWClassic.exe errors in the Windows Error Logs section, but unfortunately that only shows that the game is crashing/hanging and doesn’t tell us why. It was also happening with the previous version 1.13.3:

Problem signature:

P1: WowClassic.exe

P2: 1.13.3.33302

At this point I’m thinking two things may help here.

Lets try a full reset UI to set the UI back to defaults, in case you have any addons installed that may be conflicting with the patch we want to rule this out.
Try wiping the Nvidia drivers with Display Driver Uninstaller and then reinstall version 391.35, basically to “re-initialize” the drivers and make sure that WoW is hooking into them properly.

Download DDU here

Click on the first link under “Announcements” titled Display Driver Uninstaller (DDU). Then click the “Official Download Here” link to start the download.

Run the .exe file and extract the contents to the default location. Open the new folder and run the Display Driver Uninstaller.

You will get a pop-up saying it is recommended to reboot in Safe Mode, feel free to ignore this if you are not familiar with how to get into Safe Mode. To start the removal process, click on “Clean and restart”

Once the PC restarts, go ahead and download the 391.35 drivers here: https://www.geforce.com/drivers/results/132841

Run the driver installer and use the default/recommended install steps.

Test the game again and let us know how it goes.

Dredlok-atiesh · March 11, 2020, 3:35am

Hey Jambrix, thank you for your assistance with this.

The UI reset did not resolve the issue but after using DDU as per your instructions, and then manually reinstalling the Nvidia drivers, it appears that I can now run WoW successfully without the error!

The successful gx log:

3/10 23:23:12.273  LogOpen
3/10 23:23:12.404  ConsoleDetectDetectHardware():
3/10 23:23:12.438  	cpuIdx: 1
3/10 23:23:12.489  ConsoleDeviceInitialize(): hwDetect = 0, hwChanged = 0
3/10 23:23:12.538  D3d11 Device Create
3/10 23:23:12.567  	Format 1366 x 768 Fullscreen, ArgbX888, vsync 0
3/10 23:23:12.599  Found Adapter 0: Vendor Id 0x8086, Device Id 0x0116 - Sysmem = 0
3/10 23:23:12.621  Monitor 0 attached to adapter 0
3/10 23:23:12.650  Found Adapter 1: Vendor Id 0x10de, Device Id 0x0df4 - Sysmem = 0
3/10 23:23:12.677  Skipping Software Renderer 2: Vendor Id 0x1414, Device Id 0x008c - Sysmem = 0
3/10 23:23:12.704  Choosing adapter 1
3/10 23:23:12.732  Detected NvAPI and checking if it's valid...
3/10 23:23:12.825  AFR detection
3/10 23:23:12.854  AFR found with 1 devices(s)
3/10 23:23:12.882  Caps:
3/10 23:23:12.910  	Vendor ID: 10de
3/10 23:23:12.938  	Device ID: df4
3/10 23:23:12.966  	AFR Groups: 1/1
3/10 23:23:12.994  Feature Level: DX=3, GL=0, MTL=0
3/10 23:23:13.036  D3d11 Device Create Successful
3/10 23:23:13.101  CPU Processor Detection: 4 H/W threads
3/10 23:23:13.159  Memory Detection: 8496287744 bytes of physical memory available
3/10 23:23:13.187  Detected Graphics Defaults: 2 (CPU = 6, GPU = 2, MEM = 6)
3/10 23:23:13.219  Resample::CreateResources
3/10 23:23:13.371  RenderSettings::NotifyChanged
3/10 23:23:13.457  Liquid::CreateProceduralTextures
3/10 23:23:15.328  PortraitDeviceCreate
3/10 23:23:15.569  VolumeFog::DestroyResources
3/10 23:23:15.698  VolumeFog::UpdateResources
3/10 23:23:15.744  VolumeFog::DestroyResources
3/10 23:23:36.417  PortraitDeviceDestroy
3/10 23:23:36.487  PortraitDeviceCreate
3/10 23:28:54.678  PortraitDeviceDestroy
3/10 23:28:54.756  PortraitDeviceDestroy
3/10 23:28:55.184  VolumeFog::DestroyResources
3/10 23:28:55.223  Liquid::DestroyProceduralTextures
3/10 23:28:55.337  Resample::DestroyResources
3/10 23:28:55.359  D3d11 Device Destroy
3/10 23:28:55.637  D3d11 Device Destroyed

Hopefully I am the only one encountering this “change” but if not it seems like doing a clean install of the nvidia drivers will solve the issue.

Chloroplast-netherwind · March 11, 2020, 2:22pm

The same unable to start up 3D accelerator error was happening to me too. This only occurred after the patch update as I was playing wow just fine for months prior to patch 1.13.4. I also have the nvidia gt540 card in addition to intel 3000 on my laptop. I have done the same manual setting of the Nvidia card as default. Also did a reinstall and update of my graphics drivers. No luck yet. Tonight I will try to follow the instructions above exactly to see if that fixes this error.

Mod note: If you still have an issue, please create your own thread and include the steps you have taken and a DxDiag.