Problem Started today .

[dave1240]

Using Arelog and both of my WoW both in icecrown constantly get the blizzard report a issue screen and this error.

System.Exception: Could not write the specified bytes! 00000000 [5]
at BlueMagic.Memory.WriteBytes(UInt32 address, Byte[] val)
at Styx.Helpers.AllocatedMemory.WriteBytes(Int32 offsetInBytes, Byte[] bytes)
at Styx.WoWInternals.Lua.GetReturnValues(String lua, String scriptName)
at Styx.WoWInternals.Lua.GetReturnVal[T](String lua, UInt32 retVal)
at Styx.WoWInternals.WoWObjects.LocalPlayer.get_IsIndoors()
at Bots.Grind.LevelBot.#Hic()
at Bots.Grind.LevelBot.#Dxc(Object ret)
at TreeSharp.Action.RunAction(Object context)
at TreeSharp.Action.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Sequence.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.#h.#nF.MoveNext()
at (Object )
at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.Tick()
[2:21:03 PM:984] Cleared POI - Reason Exception in Root.Tick()
[2:21:03 PM:984] Cleared POI
[2:21:04 PM:046] Not in game
[2:21:06 PM:765] System.Exception: Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired.
at BlueMagic.ExecutorRand.GrabFrame()
at Styx.Logic.BehaviorTree.TreeRoot.Stop()

strangely my 3rd wow questing in cata has not seen this issue.

 

[Tony]

full log plz
http://www.thebuddyforum.com/honorbuddy-forum/guides/9859-how-attach-your-hb-log-file-pictures.html

 

[dave1240]

View attachment 1-21-2012_2_17 PM 4212 Log.txt

Knew i should of done a log, was hoping it was a known problem. Anyways this has happened lots of times arelog just kept logging me in.

 

[Tony]

its a known Gb2 issue,fixed on next release