Uhhh. What's this?

[Solus001]

I haven't been using HB long, but just recently, I tried to start up HB after it's update.
My BElf Rogue is sitting at level 88, and I've been using Kick's Profile with no problems at all.

But today was different. I started up HB on my rogue, WoW crashed, and an error message appeared.

The Message Appeared as below:

"ERROR #132 (0x85100084) Fatal Exception!

Program: C:\Program Files (x86)\World of Warcraft\WoW.exe
ProcessID: 5428
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:0176B0AE

The instruction at "0x0176B0AE" referenced memory at "0x00000010".
The memory could not be "read".

Press Ok to terminate the application."

And then a box came up asking me to tell Blizzard what happend during the crash.
Maybe this is me being paranoid over the chance that botting may perma-ban me.
Maybe blizzard is tracking the program (highly doubt it),
Or Maybe this could be something worth looking at.

 

[Victor9909]

your posting in the wrong section

 

[DaveL]

your posting in the wrong section

You´re*

and anyway, many users report same problem, you just need to visit Support section rather than ban one

 

[HipDrahve]

WoW teleport prevention. it's when HB breaches textures by mounting/click to moving where regular wow client wouldn't allow so.

 

[frosticus]

we had that a couple patches ago when druids were taking off in flight form too fast. you can google error 132, blizz has plenty of info on it on their forums.

 

[webhond]

the bot is attached to wow, if the bot fails, 99 % of the time wow crashes also.
If wow crashes, you get that window, that something went wrong, a log has been made of that error and you can send it to blizz.
Ofcourse, when you are botting, you dont want to send that log, ever. But its quite normal that this happens.

For the error, you have to go to support section and ask it there but this could come in handy maybe.

https://sea.battle.net/support/en/article/error-132