WAIT! READ ME FIRST: If you don't read this all, okay. But, do me one favor, do you know if WoW WotLK 3.3.5a has any known conflicts with Windows 10's 20H2 update? That is the only difference from a working machine I have and a non-working machine. Read on and see what's up. Thanks!
I'm not normally a big forum user anymore, my stats will prove that but I have run out of resources so I bring my situation to you...
I recently bought a new ASUS laptop, it's an all AMD machine, the G15 Advantage Edition. The laptop can run WoW and is currently running every other game I have installed on it - and everything else - without issue. However, here is the timeline:
- After updating the new machine with Windows Updates, driver updates, etc. The usual new computer stuff, I began downloading the games I wanted. I was able to download the BitTorrent of the 3.3.5a client from this site just fine and run it ONCE. It ran once, for 5 seconds and I logged back out.
- Days later when I went to open it again, I began seeing the below error every time.
- Since, I have downloaded the torrent repeatedly to no avail. I have got the 3.3.5a client from other sources as well, for no positive result. I have also done all of the standard Error 132 checks: Game DVR mode off, all Windows "Game" features are off, drivers are all updated, run as Admin, unchecked Read-Only, used Large Address Aware, cleaned my registry, made config changes, cleared my cache and all those sub folders, and more. I have literally done everything I have found to no result.
No matter what I do, still the same results. I am asking for any and all help if you have it. This one is really something else.
The full error displayed:
The application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: C:\Program Files (x86)\World of Warcraft Warmane\Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:008D2412
The instruction at "0x008D2412" referenced memory at "0x00000000",
The memory could not be "read",
Press OK to terminate the application
At first, the account on the new laptop was a Windows Live account. It has since been switched to a local Windows account and still, the issue is there. There are no mods or any advanced textures being run. This is just stock WoW WotLK 3.3.5a I am trying to run here.
What is more frustrating is that I had the Mac client working on my Macbook Pro, but removed it cause I got this laptop for gaming. My desktop has the client running just fine and has never has issue. I have replicated the setup with the new install off the torrent, I have even taken the install off the desktop and dropped it on the laptop to no change.
I have also referenced many of the posts I see referenced here on the forums about the error codes and such. I haven't found an answer there and I saved LAA for last and still - it didn't work. So, any tips on how you might beat this please let me know.
Sounds more like a bad windows install. I've played on this same 3.3.5a client through windows 7, 8, 8.1, 10 1607, 10 1809, 10 20h1/20h2/21h1/21h2. No issues, apart from the ancient graphics api the client uses. Yes, I did apply large address aware to wow.exe - solved a lot of issues for me. i5 8300H / 8GB / GTX 1050.
Sounds more like a bad windows install. I've played on this same 3.3.5a client through windows 7, 8, 8.1, 10 1607, 10 1809, 10 20h1/20h2/21h1/21h2. No issues, apart from the ancient graphics api the client uses. Yes, I did apply large address aware to wow.exe - solved a lot of issues for me. i5 8300H / 8GB / GTX 1050.
I've seen you around the forums when this error pops up so thank you for responding here.
Yeah, I was holding out on LAA as my ace in the hole when it wasn't working since I never needed it on my Desktop. But, no dice so, have to either give up and move on or keep trying to resolve this. It's one of those I don't NEED to but it's such a head scratcher that I want to, you know?
Since it's really just a gaming rig, the Windows reset wouldn't take long. Shall see if I end up going that route. Thanks man!
How's your DirectX doing?
How's your antivirus? Is WoW client made an exception?
If you haven't tried already, try WoW without AddOns. (Disabled/moved away from folders).
If you end up getting new client, do these after downloading:
1. Restart your PC.
2. Close and exit torrent (Delete it as well, if you don't have other use for it). Move your WoW -folder to other folder, away from Torrent's Download folder.
2.5 I recommend making yourself a temporary* folder where you paste the WoW installation.
3. Right click WoW -Folder, select properties, un-check "Read-only" and Apply.
4. If you get prompt, Apply changes to this folder, subfolders and files and click OK.
*or permanent. Any random place will do for now to be honest, consider moving it AFTER you get it running without errors.
WAIT! READ ME FIRST: If you don't read this all, okay. But, do me one favor, do you know if WoW WotLK 3.3.5a has any known conflicts with Windows 10's 20H2 update? That is the only difference from a working machine I have and a non-working machine. Read on and see what's up. Thanks!
I'm quite sure I had Win 10 20H2 without WoW errors. I don't think I played that much at that time, but certainly never crashed during those few hours I played either.
I have exactly the same problem and error code as you. Even the 0x008D2412 is the same, from the million types of #132 error. Did you manage to solve it? And also in a new computer.
I have also tried to reinstall, LAA, remove read-only, modded vs non-modded version, Config.wtf changes, firewall exceptions, drivers all up to date, run on admin mode and all those solutions.
Currently I have W10 on my new PC and I didn't manage to play Wow here. I used to play wow also in W10 without any issue in a ~7year dated notebook and now with a much better setup I couldn't launch game.
To be honest the only way I managed to open client was running on WXP SP3 or less compatibility mode, but I got another problem: disconnect after 10-20s on login (also checked every solution in this forum and nothing worked so far). Don't know what else can be done.
------------------------------------------------------------------------------
World of WarCraft (build 12340)
Exe: D:\WoW\World of Warcraft 3.3.5a\Wow_64bit_patched.exe
Time: Nov 5, 2021 7:27:07.463 PM
User: gusta
Computer: DESKTOP-XXXXXX
------------------------------------------------------------------------------
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: D:\WoW\World of Warcraft 3.3.5a\Wow_64bit_patched.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:008D2412
The instruction at "0x008D2412" referenced memory at "0x00000000".
The memory could not be "read".