HB wow crashes every other hour

[Leetzorz1]

WoW crashed 2 times in the past 6 hours..

I just got honorbuddy today.. Just curious how can i fix this because i want to bot over night

 

[BeepBeep]

WoW crashed 2 times in the past 6 hours..

I just got honorbuddy today.. Just curious how can i fix this because i want to bot over night

Are you using HB v1.924?

Post a log if you are.

 

[Leetzorz1]

Yep

here it is.. idk if it's up there

 

[Leetzorz1]

[6:52:45 PM:431] Frostbolt pull of Witherbark Venomblood at distance 22
[6:52:45 PM:521] CastSpellById: 8408
[6:52:53 PM:499] Took 8019 ms to cast:Frostbolt
[6:52:53 PM:657] Frostbolt.
[6:52:53 PM:733] Is auth server lagging?
[6:52:53 PM:770] CastSpellById: 8408
[6:53:01 PM:707] Took 8002 ms to cast:Frostbolt
[6:53:01 PM:719] Frostbolt.
[6:53:01 PM:724] Pull Complete.
[6:53:02 PM:178] Frostbolt pull of Witherbark Venomblood at distance 22
[6:53:02 PM:319] CastSpellById: 8408
[6:53:10 PM:434] Took 8190 ms to cast:Frostbolt
[6:53:10 PM:446] Frostbolt.
[6:53:20 PM:657] Wow exited, Honorbudddy stopped!
[6:53:31 PM:548] Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. - From: Honorbuddy at EndScene.ExecutorRand.#I2()
at Styx.Logic.BehaviorTree.TreeRoot.Stop()SmartExceptionsCore.UnhandledException @ 2807, offset:73
[6:53:21 PM:134] Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. - From: Honorbuddy at EndScene.ExecutorRand.Execute()
at Styx.WoWInternals.WoWMovement.CGPlayer_C__ClickToMove(ClickToMoveType clickToMoveType, UInt64 guid, WoWPoint clickPos, Single precision)SmartExceptionsCore.UnhandledException @ 2806, offset:202
[6:53:21 PM:442] Thread was being aborted. - From: Honorbuddy at Styx.WoWInternals.ObjectManager.get_IsInGame()
at #Ov.#rt.Pulse(Object sleepTime)SmartExceptionsCore.UnhandledException @ 2399, offset:68
[6:53:38 PM:799] Pull Complete.
[6:53:39 PM:32] ReadUInt at 0x15A85028 failed. - From: Honorbuddy at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.Tick()SmartExceptionsCore.UnhandledException @ 3179, offset:68

 

[BeepBeep]

[6:52:45 PM:431] Frostbolt pull of Witherbark Venomblood at distance 22
[6:52:45 PM:521] CastSpellById: 8408
[6:52:53 PM:499] Took 8019 ms to cast:Frostbolt
[6:52:53 PM:657] Frostbolt.
[6:52:53 PM:733] Is auth server lagging?
[6:52:53 PM:770] CastSpellById: 8408
[6:53:01 PM:707] Took 8002 ms to cast:Frostbolt
[6:53:01 PM:719] Frostbolt.
[6:53:01 PM:724] Pull Complete.
[6:53:02 PM:178] Frostbolt pull of Witherbark Venomblood at distance 22
[6:53:02 PM:319] CastSpellById: 8408
[6:53:10 PM:434] Took 8190 ms to cast:Frostbolt
[6:53:10 PM:446] Frostbolt.
[6:53:20 PM:657] Wow exited, Honorbudddy stopped!
[6:53:31 PM:548] Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. - From: Honorbuddy at EndScene.ExecutorRand.#I2()
at Styx.Logic.BehaviorTree.TreeRoot.Stop()SmartExceptionsCore.UnhandledException @ 2807, offset:73
[6:53:21 PM:134] Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. - From: Honorbuddy at EndScene.ExecutorRand.Execute()
at Styx.WoWInternals.WoWMovement.CGPlayer_C__ClickToMove(ClickToMoveType clickToMoveType, UInt64 guid, WoWPoint clickPos, Single precision)SmartExceptionsCore.UnhandledException @ 2806, offset:202
[6:53:21 PM:442] Thread was being aborted. - From: Honorbuddy at Styx.WoWInternals.ObjectManager.get_IsInGame()
at #Ov.#rt.Pulse(Object sleepTime)SmartExceptionsCore.UnhandledException @ 2399, offset:68
[6:53:38 PM:799] Pull Complete.
[6:53:39 PM:32] ReadUInt at 0x15A85028 failed. - From: Honorbuddy at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.Tick()SmartExceptionsCore.UnhandledException @ 3179, offset:68

Have you tried doing a clean install?

Try reinstalling your CC's completely, not sure if that's an issue or not. Hopefully Ski/Tony or someone can give you a better answer.

 

[jarheaded]

its a core issue that's throwing exceptions out .. that need to be fixed and its been reported and im dealing with the same issue with my 53 lock