World of Warcraft crashes

[Unkreativum]

Hey,
I got since yesterday everytime a game crash after a few minutes.
Before the new patch from Wednesday in Europe, everything runs fine.

The game crash after 3-5 Minutes with an Access_Violation.
http://imgur.com/a/aCvoF
This is a picture of a Crash. I need to play a instance with Sandboxie, because my wife plays on the same Computer like me. We play since 6 months on this Setup and never have trouble like now. Re-Installed the game, deleting the folders Cache and Wtf like Blizz told but nothing helps.
If you need information about the System, i can get it later.

Maybe, somebody can help here

[Barb@Invincea]

Hello Unkreativum,

Please provide this information so that we can review it:
viewtopic.php?f=11&t=19746

Does the game work fine outside Sandboxie?
Please test it in a new Sandbox with default settings to see if that makes a difference.

Regards,
Barb.-

[Syrinx]

It's been a few years since I touched WoW but even after Battle.net got added you were able to bypass the launcher with a shortcut flag and launch more than one instance, unless I am recalling wrong.

Does the error still occur if you only run the one instance sandboxed?

[Unkreativum]

Hi,

Thanks for the fast help. I run a Win 10 pro 64Bit Version with a 5.20 sandboxie Version and using Kaspersky total Security as anti vir.
Its just World of Warcraft with the issues. Outside of sandboxie it works fine. On tuesday everything works fine.


With the launcher Option to start another application of wow doesn't work for me. The Second Player will get a large "could not load because…" and a ton of Problems.


Greetings

[Unkreativum]

After some testing i Got news.

The Problem occurs just in 64 Bit Version of wow. The 32bit Version runs normal but the mouse gets on this Version a hughe speed up. Its a known issue with this Patch.

[kofoedsan]

Out of curiosity, why do you run Warcraft in a sandbox? Doesn't it slow it down at all?

[fatlight]

Same issue here.

Windows 10 64 1607 (and i wont update to Creators Update or Fall Creators Update)
Sandboxie 5.23.1 beta, same issue with 5.22
World of Warcraft 7.3.2 25549 (problem started in this build)
Kaspersky Total Security

Battle.Net client also run in Sandbox, works without issues, infact all applications i have is run under sandbox.

No sandboxie popup-dialogs.

All other applications work without issue inside sandboxie.

[Barb@Invincea]

All,

I tested World of Warcraft Starter Edition v7.3.2.25549 + Sbie 5.23.1 Beta + Wino 10- x64.
I was able to create a character and finish the first quest, and after 3 minutes I got the crash: "Error #138 (Ox8510008a) Fatal Exception ...Access_Violation...."

I am not sure if this will be addressed at any point, but I will bring it up to the devs.

Regarding trying to launch multiple versions of the game, please see Battle.net's official response about it:
https://us.battle.net/forums/en/bnet/to ... 45095739#7
Sandboxie was not designed to bypass software restrictions.

Regards,
Barb.-

[Digitonin]

I tested World of Warcraft Starter Edition v7.3.2.25549 + Sbie 5.23.1 Beta + Wino 10- x64.
I was able to create a character and finish the first quest, and after 3 minutes I got the crash: "Error #138 (Ox8510008a) Fatal Exception ...Access_Violation...."

Thanks for testing Barb. New guy to the forums but wanted to get in on the discussion as this is driving me nuts! Same error I am seeing yet it was working without issues until 20th November. I went on holiday, came back to this beast of a problem. Oh boy.

I also tested with Sbie 5.22 and 5.18 for good measure. Latest version of WoW on my end is Nov 21st. Suspect it is something Blizzard have implemented yet I can't see anything in the hotfix/patch notes to support this.

Been working on this all day, even tried expanding sandbox size to 99 GB and placing the entire 45 GB WoW folder inside (I am not an expert user so this could be rather dumb). Tried things like Drop Rights as well. Issue is not present when not using sbie.