Unable to start up 3D acceleration, then crashes

Support Technical Support
1

Hi there!

Trying to play Classic tonight, I didn’t touch any of the settings, just went to log in and after the queue the game crashed saying it “Failed to start up 3D acceleration”, I quickly tried to log back in hopes of it being a one time error and not having to queue again, but this time I had a blue screen and had to restart.

So I loaded it up again and tried to change the settings to see if perhaps vertical sync or something was being funny, and when I went to apply the changes, the game crashed, I then went to the WoW.exe in the classic folder and disabled “Full Screen Enhancements” and when I booted the game up, my system instantly restarted, which was a bit of a worry.

Drivers should all be up to date, have had no issues with any other games or programs as of late.

Any advice on how to get the game running would be appreciated.

Edit: I should add that I have no problem running BoA, it’s never given me any trouble. Also, tried to add my DxDiag, but it say it’s too many characters?

2

Hi Sylestria

If you have any overlays running you would want to disable. Discord is a common one. Check this sticky for some further steps:

3

Thanks Tratt! I should have added that the first thing I did was disable the Discord overlay, and I already had the GeForce experience one disabled too. I’ve not been able to log back in, since i’m still in queue, to see if it’s resolved the issue. I’m also now trying the game with the -windowed command, and default settings.

Would someone be able to give me a brief explanation on how to use the code button to input my Dx Diag? Whenever I try, it’s just a big mess, instead of the neat little window I see some people are able to do. I imagine it’s very straight forward and i’m just being dumb. I’ve tried hitting the button, and pasting the DxDiag info into there, and using < and /> at the start and end, and neither seemed to work, though very likely I did something wrong. Thanks again!

edit: Also disabled the Blizzard Streaming in the Battle .net launcher

4

Paste the DXDiag on pastebin.com - easier to read there anyhow. We just need the end code of the URL link to it.

Provide the code from the pastebin link - the green bold portion of this example:

https://pastebin.com/**Qk28Ed1P**

5

Ahh, a great idea. The code for the pastebin link is YBHSU3HR

edit: Just logged in, and still had the game crash with all of the overlays disabled and with the -windowed command. Have more information since I didn’t blue screen or need to reboot right away.

This time I got a window pop up saying:

"This application has encountered a critical error:
Error#132 (0x85100084) Fatal Exception!
program: installation dir
ProcessID: 14800
Exception: ACCESS_VIOLATION

the instruction at “0x00007ff73127b4c7” referenced memort at “0x00000222a667cde0”
the memory could not be “written”.

Press Ok to terminate the application.

6

We are seeing video related bluescreen errors on the DXDiag report. Let’s take a look at what Asus has for downloads there. Can you provide the exact model of the notebook.

FX 705 - GD GE or GM (should be on a sticker somewhere)

7

The complete model number should be 705GD DH71-CA

8

Let’s update the Intel driver first then test. You will need to use the dropdowns to select the model then Windows 10 64bit OS. After that open the VGA section

This driver:

Version V25.20.100.6374
2019/05/28 358.46 MBytes
Intel Graphics Driver

9

I just saw your edit regarding the 132 game error. Would be good to take a look at that. Navigate to the main Wow folder - Classic folder. Look for a folder called Errors. The crash reports should be inside. Open the most recent with notepad.

Paste the entire error on Pastebin.

10

Will give that an install and check, i’m quite sure I did install all the updates off that page (laptop is only a few weeks old), but I did have to do a rollback due to some issues with the Microsoft Store and the Xbox Game Pass PC Beta.

The pastebin for the last crash is bWY5q8ce

Thank you kindly for all this assistance.

Edit: I did already have those Intel drivers installed, as well as 436.02 for Nvidia.

11

What I was looking at there is many notebooks don’t take kindly to the generic drivers provided by Intel or Nvidia. Notebook manufacturers like to tweek the drivers then release them. It is usually best to use manufacturer drivers even if they are somewhat dated.

If BfA plays just fine this is likely some sort of bug that the Devs need to find. We have hit on the usual solutions for this 3D error. I took a look through the forum posts looking for anything else. The only other thing I found was Vertical Sync causing issue. Do you have that enabled in game by chance.

I would get a ticket open on this:

https://us.battle.net/support/en/help/product/wow/158/164/channels

12

I did come across the other post recommending turning V-sync off, I have tried it with it on and off and I still get the same crash, unfortunately.

13

Have you experimented with the various DirectX modes. DX11 - DX11 Legacy and DX 12?

It can’t hurt to try a Selective Startup as well:

14

No, how do I do that with Classic, or is at an option outside of the program? I know in BFA I have the option to select which version of DX to use, but the option doesn’t seem to be there in Classic.

I did also try running Classic after a fresh reboot with no programs running in the background (minimized or otherwise), which unfortunately didn’t seem to help.

15

Well that I’m not sure about - Classic troubleshooting is all new to me. It looks like you are on DirectX 11 which would likely be the best mode. I suspect there isn’t a setting. I’m going to be creating a character there later this morning to have a look at the controls.

16

This has me curious - open the Classic folder - look for the Logs folder. Inside open the “gx” file with notepad. Paste the contents.

17

Here you are:

8/27 02:09:27.781 LogOpen
8/27 02:09:27.822 ConsoleDetectDetectHardware():
8/27 02:09:27.822 cpuIdx: 1
8/27 02:09:27.845 ConsoleDeviceInitialize(): hwDetect = 0, hwChanged = 0
8/27 02:09:27.861 D3d11 Device Create
8/27 02:09:27.874 Format 1920 x 1080 Fullscreen, ArgbX888, vsync 1
8/27 02:09:27.888 Taking Adapter 0 by name: Vendor Id 0x10de, Device Id 0x1c8d - Sysmem = 0
8/27 02:09:27.888 NVIDIA GeForce GTX 1050
8/27 02:09:27.907 Detected NvAPI and checking if it’s valid…
8/27 02:09:27.973 Reduce Input Lag: D3DDevice = 0x000002178f0db178, IDXGIDevice1 = 0x000002178f0da988, hr = 0x0
8/27 02:09:27.985 AFR detection
8/27 02:09:27.997 AFR found with 1 devices(s)
8/27 02:09:28.007 Caps:
8/27 02:09:28.007 Vendor ID: 10de
8/27 02:09:28.030 Device ID: 1c8d
8/27 02:09:28.041 AFR Groups: 1/1
8/27 02:09:28.041 Feature Level: DX=3, GL=0, MTL=0
8/27 02:09:28.074 D3d11 Device Create Successful
8/27 02:09:28.093 CPU Processor Detection: 12 H/W threads
8/27 02:09:28.093 Memory Detection: 8433463296 bytes of physical memory available
8/27 02:09:28.109 Detected Graphics Defaults: 6 (CPU = 6, GPU = 6, MEM = 6)
8/27 02:09:28.123 Resample::CreateResources
8/27 02:09:28.221 RenderSettings::NotifyChanged
8/27 02:09:28.269 Liquid::CreateProceduralTextures
8/27 02:09:29.297 PortraitDeviceCreate
8/27 02:09:29.409 VolumeFog::DestroyResources
8/27 02:09:29.508 VolumeFog::UpdateResources
8/27 02:09:29.508 VolumeFog::DestroyResources

18

Hmm - it is using the Nvidia, however I see something else. Did you try this - it was in a link I first posted.

  1. Open the Blizzard Battle.net Desktop App and select the WoW tab
  2. Click Options and select Game Settings from the dropdown menu
  3. In Game Settings under Classic Wow activate the option Additional command line arguments . Type in the following:

-windowed

(include the hypen)

19

I did, after disabling all the overlays it’s what I tried next and sadly it didn’t help. Was getting the same error once I hit ‘Enter World’ even with the game in a window (regardless of vertical sync on or off, or using the command from the additional command lines, or selected in the menu)

20

Double check that - the log seems to indicate you are in Fullscreen. There are two places you can do it Wow Classic and BfA. It needs the hyphen before windowed.

It seems to me changing it in settings doesn’t work - needs to be the command line.