ERROR #132 WOW critical error. WHILE running bot.

This error is actually caused by passing in a bad pointer to the CTM function that HB uses. It's not a DirectX issue. (Or any form of graphics issue)

To be technical; WoW is trying to grab a pointer to the objects descriptor table, and since the object passed in is either old, or bad, it throws an error. (#132 is access violation, as well as the 0xC0000005 HRESULT return value)

WoW was trying to access 0xC3C17F0 (which would be [objPtr + 0x8]), and failed to read it due to an access violation. (Corrupt/invalid memory. Or misprotected memory)

In short; chances are, you were doing something wrong, or there is a bug in HB that allows the active player to be 'dropped'. The only real other explanation, is HB passing in the wrong object for some odd reason. (The function only takes a pointer to the current, active, player)

Make sure you're logged in game before starting HB again. (Just make sure it doesn't crash anymore) This is likely caused by being logged out, or at a loading screen. (Loading screens 'refresh' the entire object manager, which can cause the issue if the list isn't refreshed yet)

 

The following is the actual ASM from where the crash is happening:

Code:

.text:005CFB70     ; char __thiscall CGPlayer_C__ClickToMove(WoWPlayer *this, CLICKTOMOVETYPE ctmType, WGUID *guid, Vector3 *pos, float faceAngle)
.text:005CFB70     CGPlayer_C__ClickToMove proc near       ; CODE XREF: CGUnit_C__sub_5D3C50+162p
.text:005CFB70                                             ; CGPlayer_C__CTMFace+59p ...
.text:005CFB70
.text:005CFB70     a2              = Vector3 ptr -18h
.text:005CFB70     var_C           = byte ptr -0Ch
.text:005CFB70     ctmType         = dword ptr  8
.text:005CFB70     guid            = dword ptr  0Ch
.text:005CFB70     pos             = dword ptr  10h
.text:005CFB70     faceAngle       = dword ptr  14h
.text:005CFB70
.text:005CFB70 000                 push    ebp
.text:005CFB71 004                 mov     ebp, esp
.text:005CFB73 004                 sub     esp, 18h
.text:005CFB76 01C                 push    ebx
.text:005CFB77 020                 mov     ebx, ecx
.text:005CFB79 020                 mov     eax, [ebx+8]
.text:005CFB7C 020                 mov     ecx, [eax]
.text:005CFB7E 020                 cmp     ecx, g_activeMover.dwLow
.text:005CFB84 020                 push    esi
.text:005CFB85 024                 jnz     short loc_5CFBE0
.text:005CFB87 024                 mov     edx, [eax+4]
.text:005CFB8A 024                 cmp     edx, g_activeMover.dwHigh
.text:005CFB90 024                 jnz     short loc_5CFBE0
.text:005CFB92 024                 mov     eax, s_ctmClickType

 

disable your addons(if you have any)
and clear your wow cache

 

The issue is with the bot itself. Not any config, etc.

Would be nice to know exactly when it crashes, and where.

Basically;

What was the bot doing when it crashed?
Where was it?
Anything else important we need to know?

As a developer (not for HB or GB), people like me need more info than "it crashed and here's the WoW crash log". We can figure out why WoW crashed, but figuring out why the code crashed is a different story.

Note: I'm not an HB/GB dev.

 

we want your Hb log too