Hey all, I just wanted to post a possible work around for some folks having trouble either loading the game (or even the Battle.net launcher as was my case), or FPS problems. I spent hours banging my head against the wall.
For context, I was running an Asus ROG laptop, Windows 8.1, DX 11, with Nvidia GeForce GTX 860m gpu and the latest up to date drivers version 456.71
To briefly describe the issues I was having:
- Battle.net opened but froze on the first screen with no visible content links…could not switch between game icons on the left side
- Could click “Play” to launch WoW, however…
- WoW opened to extremely choppy/laggy/low FPS
- Character select screen would not display characters at all (while background animations continued to be choppy and slow
- Multiple crashes due to “Error #132 - Fatal Exception - Access Violation”
Note: This was happening for both retail client AND classic versions of the game (although I couldn’t even make it to the character screen on classic…), and again, I was using the most up to date driver for my GPU.
MY SOLUTION:
- Install the previously used graphics driver (mine was actually a few months old, version 442.59)
You can go to this link and search for older drivers for Nvidia:
I realize this may only help those with Nvidia cards, but it might apply to others as well… and save you hours of uninstall/reinstall, delete folders, etc.
I’ve seen a few reports where rolling back the Nvidia was the fix. I would recommend using the DDU tool to uninstall.
https://www.wagnardsoft.com/forums/viewtopic.php?f=5&t=3300
Awesome post.
Just a note to make it even better. You should include a link with the full text of the error reports you were getting.
Why ? Because the #132 error report is actually a very general error the causes of which can vary wildly from player to player. So what works for one player might not necessarily work for another player.
Think of the #132 less as an error but as a forensic report - it’ll tell you what the conditions were present , what was loaded , what was in memory and what variables were being used at the time of crash. This assists you in coming up with a solution and hence the factors should match when attempting a solution
1 Like
Great suggestion, unfortunately in my ignorance (and frustration lol) I neglected to save that information. To be honest, I wasn’t sure how it even related to the problem. In hindsight, I see how that would have been even more helpful.
Thanks for the feedback!
You have it saved unless you reinstalled the game during all of this:
Navigate to the main Wow folder. Look for a folder called Errors. The crash reports should be inside. Open the most recent with notepad. Copy/Paste the entire wall of text on your thread here.
(If you can put that wall of text in code blocks would be great. To do that paste the report in a chat box. Then right click > “select all” - should highlight everything. Once highlighted click on the little </> symbol on the bar above the chat box.)
If you have issues pasting on the Forum here go ahead and paste it up on Pastebin.com then provide link. Provide the link code portion of the URL - example below.
(The green bold portion of the link: https://pastebin.com/Qk28Ed1P)
I would like to take a look at it as well Ninja. Make Bluespace and myself happy old troubleshooters.
1 Like
You guys are da real MVPs. Incoming error log… let me know if you spot anything interesting or noteworthy.
Not that it matters much but I redacted my username and computer name from the text. 
I’ll take a look and let you know Ninja
Ok, having real trouble posting the text here, so hopefully this Pastebin thing works…I have no idea why it is saying “potentially offensive” yeesh:
It works - looking through it now. That warning is something new that Pastebin implemented. I was looking for a way to turn it off.
Cool cool…seems everything is offensive these days lol. Even trying to post the log here was blocking the term “SpellProcs PerMinute” (without the space)…because letter case doesn’t matter hehe. 
It is a useful error for the reason that it doesn’t have any clues. It isn’t pointing at the graphics. Error is pointing at the Wow.exe. We hate those kinds of errors - but it does offer us something to look for in the future.
Bluespacecow is more Techy than myself. They may see more. Thanks for that Ninja
1 Like