Error 132. WoW won't start

Support Technical Support
1

Good evening, thanks in advance for any/all help you can give me, or at least of pointing me in the right direction. I click “Play” on wow and it goes to Launching, then back to Play and nothing happens other than an Error report generated in the Error Log.

The error report is as follows:

==============================================================================
World of WarCraft: Retail Build (build 28833)

Exe: C:\Games\World of Warcraft_retail_\Wow.exe
Command: “C:\Games\World of Warcraft_retail_\Wow.exe” -launcherlogin -uid wow_enus
Time: Dec 24, 2018 7:37:18.856 PM
User: John
Computer: DESKTOP-MJR3J0K

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program: C:\Games\World of Warcraft_retail_\Wow.exe
ProcessID: 10856
Exception: ACCESS_VIOLATION

The instruction at “0x00007ff9481cb81d” referenced memory at “0x0000000000000000”.
The memory could not be “read”.

8.1.0.28833
Retail
<Jira.JiraProjectId> 10900
<Jira.JiraProjectKey> WOW8
<Exception.ProjectId> 10
<Exception.BuildNumber> 28833
<Exception.Branch> 8.1.0
World of WarCraft
Client
Type: WoW
Wow.exe
Executable UUID: A41C679B-30AC-4A43-AF1C-DD08D20D66BA
<Wow.Platform> X64
<Exception.Platform> Win 10 (64-bit)
User: John
Computer: DESKTOP-MJR3J0K
Virtual Memory: 0.00 MB
Free Disk Space: 2792.47 GB
Exe Built: Dec 19 2018 15:03:07
Init: 000003FF 00000000
App Up Time: 0 days, 0 hours, 0 minutes, 4 seconds
System Up Time: 0 days, 0 hours, 14 minutes, 45 seconds
QueryPerformanceCounter
Current Frame: 0
Current Time: 0
Current Tick: 0
0
0
Addon resource usage (not including lua memory): 0
Number of thread pool threads (Total/HighPriority): 0/0
Battle.net.exe
<Locale.Text> enUS
<Locale.Audio> enUS
Session Time(hh:mm:ss): 00:00:00
<SessionTime.Grouping> 00:00:00 - 00:14:59
Time in World(hh:mm:ss): 00:00:00
<TimeInWorld.Grouping> 00:00:00 - 00:00:00
Total Time in World(hh:mm:ss): 00:00:00
<TotalTimeInWorld.Grouping> 00:00:00 - 00:00:00
<Addons.HasAny.Loading> No
<Addons.HasAny.Loaded> No
0
0
Yes
<IME.Current> “”, {00000000-0000-0000-0000000000000000}, inactive
<SoundSystem.Restarts> 0
<LoadingScreen.Enabled> No
<CombatLogEntry.Current> CombatLogEntry::PushEvent(casterGuidType, targetGuidType): 0, 0
<BrowserProxy.AttemptedConnect> No
Number of successful WoWConnections: 0
Battle Tag: n/a
Last Known Player: 0000000000000000, (0, 0, 0, 0)
Selected Player: 0000000000000000

CVar Settings:
<CVar.portal> US
<CVar.textLocale> enUS
<CVar.audioLocale> enUS
<CVar.agentUID> wow_enus
<CVar.hwDetect> 0
<CVar.gxApi> D3D12
<CVar.gxMaximize> 1

Installation settings:

UID: wow_enus
Expansion Level: 7
PTR: 0
Beta: 0
ProductCode: ‘WoW’

           GxInfo

D3D12
<Graphics.ShaderModel> dx_4_0

Won’t let me post a reply with the DXDiag, will post upon request, or if you go to Pastebin, it’s followed by /t3EyqfK0

2

Do you run any software like reshade?

Lets go ahead and add the following augments to wow to force dx 11see if the game loads

  1. Open the Battle.net app and go to Settings
  2. Click Game Settings
  3. Check Additional command line arguments for World of Warcraft
  4. Type in -d3d11
  5. Click Okay and launch the client
1 Like
3

That worked and i’m not running any program like reshade as i had never heard of it before and this is a fresh install on a hard drive… the entire operating system and anything else i have added. Twitch/Spotify/Tukui/Discord and wow (besides Norton) are the only programs I have added since i rebuilt.

Based on this, i can try to use a previous driver and then try to upgrade it from there.

1 Like
4

For some reason or another its showing as a shader 4 instead of a 5 which might be a drivers issue, I would definitely try a older driver.

5

Previous driver didn’t so anything. Going to go back even further.

Northern, thanks for your help. I used a free driver cleaner to blow out my video card drivers and did a fresh/clean custom install. It’s working now. I was able to use the previous driver to get it working and then did another clean/install on the latest version driver. It’s working now and thank you for all your great help.