Honorbuddy crushing WoW in raids

[Angelo17110]

Hey there. I am using HB + combat routines (tuanhadruid + stars) and last 2 days it keeps crushing my wow on every boss pull. So after boss is pulled in like 5 second wow freze and then it is closed. And it only happens in raids when boss fight starting. Tested both dx11 and dx9 also. I really need help to fix this because this way i loosing my raids spots all the time

Here is log that happend 15 mins ago on Butcher pull in Highmaul:

[21:32:47.548 N] [47:548]: Starting Up Combatlog -- Bot Started
[21:32:47.548 N] [47:548]: Stars.CheckBotBase: Switched over to Manual Style
[21:32:50.568 N] [50:568]: Talents: Feline Swiftness, Yseras Gift, Typhoon, Incarnation, Ursols Vortex, Natures Vigil, Euphoria,
[21:32:50.583 N] [50:583]: Glyphs: Grace, Rebirth, Stars, Entangling Roots, Travel, Guided Stars,
[21:34:16.369 N] [16:369]: BossBase: Detected The Butcher
[21:34:17.623 N] [17:623]: [Nature's Vigil][On: Me] [HP:100.0%][Reason: On cooldown]
[21:34:17.651 D] Opener pressed.
[21:34:18.039 N] [18:039]: [Starsurge][On: Boss] [HP:99.9%][Reason: Lunar Empowermnent down]
[21:34:19.339 N] [19:339]: [Starfire][On: Boss] [HP:99.6%][Reason: Pre-Cast]
[21:34:21.495 N] [21:495]: [Moonfire][On: Boss] [HP:99.0%][Reason: Apply Moonfire & Sunfire]
[21:34:22.947 N] [22:947]: [Starfire][On: Boss] [HP:98.7%][Reason: Lunar Empowerment]
[21:34:25.033 N] [25:033]: [Moonfire][On: Boss] [HP:98.1%][Reason: Apply Moonfire/Sunfire before end of Celestial]
[21:34:26.537 N] [26:537]: [Starsurge][On: Boss] [HP:97.5%][Reason: Lunar Empowerment]
[21:34:27.880 N] [27:880]: [Starsurge][On: Boss] [HP:96.9%][Reason: Lunar Empowerment]
[21:34:29.218 N] [29:218]: [Starfire][On: Boss] [HP:96.4%][Reason: Lunar Empowerment]
[21:34:56.352 Q] Bot stopping! Reason: Main window is closing
[21:34:59.065 N] [59:065]: Exception thrown at CooldownTracker.OnCooldown: System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at Styx.WoWInternals.Lua.GetReturnValues(String lua, String scriptName)
at Styx.WoWInternals.Lua.GetReturnVal[T](String lua, UInt32 retVal)
at Styx.WoWInternals.WoWSpell.get_CooldownTimeLeft()
at Stars.Base.CastBase.OnCooldown(WoWSpell spell)
[21:35:01.362 N] Window can't close because bot thread hung
[21:35:01.840 N] Wow exited, Honorbuddy stopped!
[21:35:01.840 N] Honorbuddy terminating in 20 seconds.
[21:35:14.069 D] Exception was thrown in BotBase.Root.Tick
[21:35:14.070 D] Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at Styx.WoWInternals.Lua.GetReturnValues(String lua, String scriptName)
at Styx.WoWInternals.Lua.GetReturnVal[T](String lua, UInt32 retVal)
at Styx.WoWInternals.WoWSpell.get_CooldownTimeLeft()
at Styx.WoWInternals.WoWSpell.get_Cooldown()
at Stars.Base.CastBase.OnCooldown(WoWSpell spell)
at Stars.Base.CastBase.CanCast(WoWSpell spell, WoWUnit onUnit, Boolean rangeCheck, Boolean checkMovement, Boolean facing)
at Stars.Base.CastBase.<Cast>d__34.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Stars.Base.CastBase.<Cast>d__2b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Stars.Base.HotkeyBase.<Opener>d__88.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Stars.Base.HotkeyBase.<RunHotkeys>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Stars.Root.<_CombatBehavior>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CommonBehaviors.Actions.ActionRunCoroutine.
.
.
.
()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.(Boolean )
at Buddy.Coroutines.Coroutine.(Boolean )
at Buddy.Coroutines.Coroutine.Resume()
at CommonBehaviors.Actions.ActionRunCoroutine.Run(Object context)
at Styx.TreeSharp.Action.RunAction(Object context)
at Styx.TreeSharp.Action.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.Common.HookExecutor.Run(Object context)
at Styx.TreeSharp.Action.RunAction(Object context)
at Styx.TreeSharp.Action.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.CommonBot.TreeRoot.()
at Styx.CommonBot.TreeRoot.
(Action , String , Boolean )
[21:35:14.070 N] [Enyo] ------------------------------------------
[21:35:14.071 N] [Enyo] Shutdown - Performing required actions.
[21:35:14.071 N] [Enyo] -------------------------------------------

[21:35:14.073 D] Handler for OnBotStopped threw exception!
[21:35:14.073 D] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 01F65CE0, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Styx.WoWInternals.Lua.get_State()
at Styx.WoWInternals.LuaEvents.
()
at Styx.WoWInternals.LuaEvents.(EventArgs )
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Styx.CommonBot.BotEvents.
(Delegate , Action`1 , Object[] )
[21:35:14.073 N] [14:073]: Shutting Down Combatlog -- Bot Stopped

 

[CodenameG]

if you would, please post a full log as an attachment so we can see whats going on.
[Guide] How to attach your log [Kick]

 

[Angelo17110]

This is full log. I started hb just before butcher pull.

 

[Tony]

How To: Attach your HB-DB log file [with pictures]

 

[Angelo17110]

View attachment 1764 2014-12-18 22.28.txt

here you have file from that whole day i guess.

 

[CodenameG]

try changing wow to dx9 mode, you can do this from your wow graphic options.

 

[Angelo17110]

try changing wow to dx9 mode, you can do this from your wow graphic options.

i said in the first post that i already did that and it is same.

 

[Tony]

give us the log file from your dx9 attempt in that case plz

 

[Angelo17110]

Here you go both dx9 and dx11 here. On 1 try my wow freezed and turned off, and on second try wow frezeed for 40-50 seconds then rezumed. Please help me i really need to fix this
View attachment 2148 2014-12-20 18.43.txt

This is happening on boss pulls everytime.

 

[Angelo17110]

Tested again and got 1 wow freeze on dummy for 30-40 sec and 1 wow frezee on butcher for 40+ sec. Help me please, i cant play like this. Here is that recent log:
View attachment 1360 2014-12-21 01.35.txt

Things i tried:

- dx11 and dx9
- checked for programs and addons that can make problems
- reinstalled HB multiple times
- checked wow for errors
- deleted WTF anc Cache
- tested settings from high to low in wow
- tested singular and few others CR's
- checked for latest gpu drivers and run buddy wizzard updater

And every time i get same problems: wow frezee for 30-40 sec and then come back or shut down.

 

[CodenameG]

follow the instuctions here on how to clear your caches.
https://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-guides/108771-help-desk.html#post1067458


after that run the wow repair tool from your wow or battle.net launcher to make sure your wow installation is complete.

 

[Angelo17110]

follow the instuctions here on how to clear your caches.
https://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-guides/108771-help-desk.html#post1067458


after that run the wow repair tool from your wow or battle.net launcher to make sure your wow installation is complete.

Did all that you told me and still the same
Here is freeze log i just got on dummy:
View attachment 1792 2014-12-21 22.01.txt

Yea can see here how long freeze lasted:
21:19:08.081 N] [08:081]: [Starfire][On: Boss] [HP:99.9%][Reason: Lunar Empowerment]
[21:19:34.180 N] [34:180]: Opener Finished -- Disabling.

Please help me, i cant play for a week now.

 

[CodenameG]

[21:19:40.764 N] Stopping the bot!
[21:19:40.764 Q] Bot stopping! Reason: User pressed the stop button

it didnt crash, you pressed stop.

 

[Angelo17110]

[21:19:40.764 N] Stopping the bot!
[21:19:40.764 Q] Bot stopping! Reason: User pressed the stop button

it didnt crash, you pressed stop.

Nop this time but wow frezzed for so long and sometimes after freze wow craches, not every time tho. But i think i found what is wrong after long testing. One of the CR's was the problem. Still not 100% sure, still testing.

 

[CodenameG]

well let us know, i guess.