Unable to start up 3D acceleration, then crashes

I have tried a myriad of other options and combinations of settings since, including resetting to default settings, which I imagine is why the log is reflecting that, but I will try it again.

Ahh - that could be it. I’m going to test that myself right now - see what my log shows.

Here is my most recent log which I ran with the -windowed command, which unfortunately still resulted in the same crash.

8/27 02:31:14.073 LogOpen
8/27 02:31:14.119 ConsoleDetectDetectHardware():
8/27 02:31:14.119 cpuIdx: 1
8/27 02:31:14.141 ConsoleDeviceInitialize(): hwDetect = 0, hwChanged = 0
8/27 02:31:14.153 D3d11 Device Create
8/27 02:31:14.153 Format: 1920 x 1080 Window, vsync 1
8/27 02:31:14.175 Taking Adapter 0 by name: Vendor Id 0x10de, Device Id 0x1c8d - Sysmem = 0
8/27 02:31:14.182 NVIDIA GeForce GTX 1050
8/27 02:31:14.182 Detected NvAPI and checking if it’s valid…
8/27 02:31:14.253 Reduce Input Lag: D3DDevice = 0x0000021e31d8a848, IDXGIDevice1 = 0x0000021e31d8a058, hr = 0x0
8/27 02:31:14.261 AFR detection
8/27 02:31:14.273 AFR found with 1 devices(s)
8/27 02:31:14.273 Caps:
8/27 02:31:14.295 Vendor ID: 10de
8/27 02:31:14.307 Device ID: 1c8d
8/27 02:31:14.307 AFR Groups: 1/1
8/27 02:31:14.329 Feature Level: DX=3, GL=0, MTL=0
8/27 02:31:14.351 D3d11 Device Create Successful
8/27 02:31:14.373 CPU Processor Detection: 12 H/W threads
8/27 02:31:14.385 Memory Detection: 8433463296 bytes of physical memory available
8/27 02:31:14.385 Detected Graphics Defaults: 6 (CPU = 6, GPU = 6, MEM = 6)
8/27 02:31:14.411 Resample::CreateResources
8/27 02:31:14.509 RenderSettings::NotifyChanged
8/27 02:31:14.557 Liquid::CreateProceduralTextures
8/27 02:31:15.396 PortraitDeviceCreate
8/27 02:31:15.510 VolumeFog::DestroyResources
8/27 02:31:15.574 VolumeFog::UpdateResources
8/27 02:31:15.574 VolumeFog::DestroyResources

Yes I can see it is Windowed now with Vsync on - try it with Vsync off.

Turned it off, crashed again. I’ve had it on and off at various times through the many times i’ve tried launching WoW Classic tonight, as i was trying to troubleshoot to see if it was specific setting or graphic feature that was causing the issue. I’ve not had a system crash or blue screen since the first one though (might have been two), which is something.

I was playing a bit on classic checking the settings. I don’t see anything there you might try. I would get that ticket open - put a link to this thread in it. Might save some back and forth.

I did open a ticket when you suggested it earlier and gave them a good description of it all, as well as screenshots of the error, and my system info, and even a link to this thread in case they wanted to review what we’d gone over. I was really looking forward to playing tonight, but these things happen. Thanks for trying, I really appreciate it.

I had the exact same problem as you all night sylestria. Tried all fixes here and even reverted my video card driver to an older version suggessted in other nvidia threads i found. Nothing seemed to help my issue either. Please keep this thread updated with the resilts of your ticket or if you find a fix!!

Will do! Let me know if you find a solution too, Zulron. Best of luck!

I’m trying a reinstall of Classic now as i’m turning in for the night, just in case.

Edit: Well, after all that it appears a reinstall has fixed whatever issue I was having, which is definitely a relief it was such an easy fix. This is a new laptop and issues like that are always a worry. Hope that works for you too, Zulron.

Okay sylestria, I will give the reinstall a shot and see if that works.

Thank you Tratt, turning off the discord overlay worked for me, but I’m confused as to why it would cause a problem for classic but not for retail (ie BfA) or any other game I’ve played. Any ideas?

[Edited by Blizzard] This thread has been inactive for some time. Please be mindful of resurrecting older threads. A new or more recent thread can be created to continue the discussion. Locking this thread.