Error 132

[Woofies]

Today I found myself in very odd situation. I tried to start the game, using Freakz launcher, yet within less than a minute in the game, I keep receiving 132 error. I did some research, made myself familiar with the following threads:

https://forum.wow-freakz.com/WoW-Legion-client-download-t452441.html
https://forum.wow-freakz.com/ERROR-132-0x085100084-Fatal-exception-with-solution-t488977.html
https://forum.wow-freakz.com/Error-132-t488320.html
https://forum.wow-freakz.com/Game-Crash-Error-132-t485234.html

Following the instructions I executed these 'potential' solutions:

1. Unstucked.
2. Re downloaded launcher.
3. Removed Cache, WTF, Errors and AddOns folders.
4. Removed all existing WoW files and installed brand new client.
5. XBOX Game DVR off.
6. Compatibility Mode set to Windows 7.
7. DirectX set to 9.
8. I continued trying to login using 32 Freakz launcher.
9. Data Folder unchecked for Read Only.

Since my boyfriend is also playing on Freakz and his client (later copied from him) has no issues, I figured the blame lies within my system, therefore I:

10. Installed new Windows 10.
11. Installed new drivers.
12. Copied error free client from my boyfriend.
13. Restarted both router and PC dozens of times.
14. Considered praying.

I honestly tried everything that came to my mind. Then I noticed two things; my issues started together with Xavius release, and your launcher hasn't been updated since June.
I also tried to use non freakz launcher, (I DON'T CRASH THEN!), but I get kick out for not using Freakz launcher.

I do know that many of such posts have been produced. I do know that there's no known cure for it. I am just writing it here, to raise the awareness that error 132 is the real issue. I play on this server since 2012 and I've never came across a technical issue that I cannot bypass or fix myself. Please, consider working on your launcher, or remove kicking mechanism for not using Freakz launcher.

Spoiler:

[Kadamedo]

I've got the exact problem, made a post but no one replay.
I thought that my wow have a general problem, but after reading your post it seems that the non freakz launcher works for me too, but with same disconect...

I will follow this post, maybe a solution from dev. team will be posted.

[Shocker]

Woofies wrote:

or remove kicking mechanism for not using Freakz launcher.

That will defeat the whole purpose of the launcher, won't happen.

Crash has nothing to do with xavius, I explained somewhere already that I believe it's from blizzard's content delivery links (which wow freakz uses), maybe they are doing modifications for their patch (7.3) and it may affect us, but currently the issue is unknown/extremely isolated...

P.S.: https://forum.wow-freakz.com/ERROR-132-0x085100084-Fatal-exception-with-solution-t488977.html this guy says he fixed his error

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[Woofies]

Shocker wrote:

Woofies wrote: or remove kicking mechanism for not using Freakz launcher. That will defeat the whole purpose of the launcher, won't happen.

Pardon my ignorance, but what purpose exactly serves the freakz launcher?

Quote:

P.S.: https://forum.wow-freakz.com/ERROR-132-0x085100084-Fatal-exception-with-solution-t488977.html this guy says he fixed his error

Thanks for that suggestion but I haven't corrupted my files via Blizzard app therefore his fix is obsolete in my case.

I already found solution for my WoW crash. I noticed in Task Manager, that when I'm trying to start the game via 32 freakz launcher, my system ignores it and goes for 64 instead. I deleted 64 freakz launcher, and I can play with no problems since then. No random disconnects, no 'you are not using freakz launcher msgs' and so on. Perhaps you can pin it to official solutions, maybe it will help someone



@Shocker

[Shocker]

Woofies wrote:

I already found solution for my WoW crash. I noticed in Task Manager, that when I'm trying to start the game via 32 freakz launcher, my system ignores it and goes for 64 instead. I deleted 64 freakz launcher, and I can play with no problems since then. No random disconnects, no 'you are not using freakz launcher msgs' and so on. Perhaps you can pin it to official solutions, maybe it will help someone

This solution is already mentioned in the list of solutions (Solution #4) here https://forum.wow-freakz.com/WoW-Legion-client-t452441.html, but players keep saying "BUT I TRIED ALL SOLUTIONS AND STILL NOT WORKING" after trying 1-2. Not our fault....

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[Woofies]

Thing is, I deleted mentioned aplications (in your solution you mentioned 2).

Quote:

This usually means your operating system doesn't support 64 bits application (or there is something wrong with your configuration). You can try deleting Wow-64.exe and launcher_freakz-64.exe and start the game using launcher_freakz.exe. It might also mean you are using an old launcher, redownload it above

Now I deleted all 3 of them, Wow-64, launcher_freakz-64 and launcher_freakz-64.dll (last one is not mentioned in your solution), and it did the trick. Please edit your solution.

[Shocker]

Woofies wrote:

Thing is, I deleted mentioned aplications (in your solution you mentioned 2). Quote: This usually means your operating system doesn't support 64 bits application (or there is something wrong with your configuration). You can try deleting Wow-64.exe and launcher_freakz-64.exe and start the game using launcher_freakz.exe. It might also mean you are using an old launcher, redownload it above Now I deleted all 3 of them, Wow-64, launcher_freakz-64 and launcher_freakz-64.dll (last one is not mentioned in your solution), and it did the trick. Please edit your solution.

That shouldn't have any impact.. 64.dll is used only by 64.exe...

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[Woofies]

Shocker wrote:

Woofies wrote: Thing is, I deleted mentioned aplications (in your solution you mentioned 2). Quote: This usually means your operating system doesn't support 64 bits application (or there is something wrong with your configuration). You can try deleting Wow-64.exe and launcher_freakz-64.exe and start the game using launcher_freakz.exe. It might also mean you are using an old launcher, redownload it above Now I deleted all 3 of them, Wow-64, launcher_freakz-64 and launcher_freakz-64.dll (last one is not mentioned in your solution), and it did the trick. Please edit your solution. That shouldn't have any impact.. 64.dll is used only by 64.exe...

I wouldn't know, I'm average windows user. All I know is that only after deleting all 3 of them I got rid of the problem.

[hexxen69]

I tried deleting the three files, running the 32 bit launcher, still getting the error. My 32 bit launcher was as well starting the 64 bit exe instead of the 32, even before the error.

I was literally playing (9/16) in the morning, then logged off. A few hrs later had done the updates. Then a few hrs later started up the game to find it doing this error.

Did anyone else apply a Windows update just before this happened to them? Just curious. I am running Win 7 Pro and had just applied an update right before the game started this error. I checked the list that was applied and nothing seemed out of the ordinary in a systems respect.

At this point I've tried everything I can think of and all of the suggested fixes short of deleteing everything and starting all over with the download, and I'd prefer not to have to do that.

[Woofies]

hexxen69 wrote:

Did anyone else apply a Windows update just before this happened to them? Just curious. I am running Win 7 Pro and had just applied an update right before the game started this error.

As a matter of fact I did. That's why I initially thought that fault lies within my system. Following this logical conclusion I installed new Windows 10 and updated it via Windows 10 Upgrade Assistant to get the latest update. I would blame Microsoft entirely if not the fact that my boyfriend also updated his Windows 10 the same day, with same update, yet with very different result - his WoW didn't crash, mine did.

[hexxen69]

Can you check to verify you both installed the same updates?

[Woofies]

We did verify that immediately. Its the same update.

[hexxen69]

OK, thnx Woofies. I am at a loss at this point. Here my MOP install still works fine, the Legion one just plain took a crap...

BTW, if anyone is interested. I checked the error logs from some of the crashes and I'm seeing this. Both the 32 bit and 64 bit versions are doing it.

WOW-32
<Inspector.IssueType> Exception
<ExceptionType> Crash
<Inspector.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<675f654d>("launcher_freakz.dll") <- DBG-ADDR<675f6f0d>("launcher_freakz.dll") <- DBG-ADDR<771a336a>("kernel32.dll") DBG-OPTIONS<>)
The instruction at "0x675f654d" referenced memory at "0x4fbe0002".
The memory could not be "read".
<:Inspector.Summary>

WOW-64
<Inspector.IssueType> Exception
<ExceptionType> Crash
<Inspector.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<000007fef77d6b23>("launcher_freakz-64.dll") <- DBG-ADDR<000007fef77d75c8>("launcher_freakz-64.dll") <- DBG-ADDR<00000000773b59cd>("kernel32.dll") DBG-OPTIONS<>)
The instruction at "0x000007fef77d6b23" referenced memory at "0x0000000052660042".
The memory could not be "read".
<:Inspector.Summary>

[Shocker]

I may try to debug it but I need some exact info: this part from the errors

Quote:

The instruction at "0x675f654d" referenced memory at "0x4fbe0002".

I need those exact values and if they're identical in all crashes (and you must be running the 32bit client, meaning you need to delete wow64.exe)

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[hexxen69]

I have tried both 32 and 64 bit launchers, had deleted the 64 bit stuff when running the 32. Same issue either way. I will get a few sets of mem references from the crash files for you, but it looked like it was different each time.