WOW crashing alot lately

[papathick]

I bot using 2-3 accounts on one puter at the same time for about 2 months now. Lately my wow has been crashing about 5 times a day with the do you want to report thing coming up. I read somewhere on here that they will watch accounts that crash alot and sometimes bann is this true?

 

[Lockwood]

I am getting this as well but no word from the devs.

 

[mopysworld]

Been happening to me too since the last couple of build #132 or 123 Error even with a brand new install(OS,WOW,HB) with no addons running. It will eventually get fixed I hope soon but as of yet I would not leave your bot unattended without some sort of relogger/loader.

 

[Kuku]

Been happening to me too since the last couple of build #132 or 123 Error even with a brand new install(OS,WOW,HB) with no addons running. It will eventually get fixed I hope soon but as of yet I would not leave your bot unattended without some sort of relogger/loader.

Sure you have no other Programs installed that could read the memory at the same offsets of WoW?! I have this Problem only when a Tool like "ESL Wire" (Anti-***** Software) is activated. So keep an eye on tools that may interrupt HB+WoW.

 

[projektt]

I bot using 2-3 accounts on one puter at the same time for about 2 months now. Lately my wow has been crashing about 5 times a day with the do you want to report thing coming up. I read somewhere on here that they will watch accounts that crash alot and sometimes bann is this true?

They don't ban accounts from crashing a lot because it could be a bunch of problems such as registry errors on your computer.

 

[mopysworld]

Sure you have no other Programs installed that could read the memory at the same offsets of WoW?! I have this Problem only when a Tool like "ESL Wire" (Anti-***** Software) is activated. So keep an eye on tools that may interrupt HB+WoW.

I meant that literally I just wiped my other machine the only thing on it is window7 64bit with all updates (minus SP1 Not fond of the invasion of privacy they are trying to implement in that patch. Scanning your system for terrorist crap is a bullshit excuse) from WU. and the newest HB download and a fresh install of wow. No addons, no adobe flash, no java, etc... you get the point.

 

[Kuku]

I meant that literally I just wiped my other machine the only thing on it is window7 64bit with all updates (minus SP1 Not fond of the invasion of privacy they are trying to implement in that patch. Scanning your system for terrorist crap is a bullshit excuse) from WU. and the newest HB download and a fresh install of wow. No addons, no adobe flash, no java, etc... you get the point.

And have you ever noted the Memory Offset Number and reported it at Bugtracker?! The Devs need all Informations of the Crash.

You find all ErrorLogs under the "Error"-Folder in your WoW Intallation.

The important Part is this:

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program: C:\Users\Public\Games\World of Warcraft\Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:6B715CEE

The instruction at "0x6B715CEE" referenced memory at "0x6B730AF4".
The memory could not be "written".

And your HB Log for sure

The Devs can only fix these errors with all the Information they need.

 

[papathick]

Loged in again today and same thing with only one account going. The error is the 132 everyone else getting this do you guys play in windowed mode and constantly switch to web pages and so on?? So im deleteing my catch and WTF files now after doing some research i saw that was the problem i'll post back how it worked.

 

[papathick]

After deleting my wtf and catch no more crashes all day with 2 accounts running!!