What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Crashs

sten15

New Member
Joined
Nov 30, 2012
Messages
65
Reaction score
0
Can someone enlight me about this crash.

I blocked the inspectorReporter.exe on the FW.

But today when i woke up, it was on the desktop, and the error is this one:

[08:30:47.050 N] ToggleTargeting, new values: Looting:True LootRadius:60 Combat:True KillRadius:50
[08:30:47.050 D] Replaced hook [ProfileOrderBehavior_Hook] c44d0b11-ec69-46e7-8105-158f2b223b6f
[08:30:47.150 D] Replaced hook [ProfileOrderBehavior_Hook] 5b07d201-e672-46e3-8561-0cd0e25d775e
[08:30:47.580 D] [BotEvents] EventChecker  threw exception Could not read bytes from 00000000 [299]! in check
[08:30:47.590 D] System.Reflection.TargetInvocationException: Uma exceção foi acionada pelo destino de uma chamada. ---> System.AccessViolationException: Could not read bytes from 00000000 [299]!
em Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
em Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
em Zeta.Internals.Actors.DiaObject.()
em Zeta.Internals.Actors.DiaObject.get_ACDGuid()
em Zeta.Internals.Actors.DiaObject.get_CommonData()
em Zeta.Internals.Actors.DiaUnit.get_Level()
em Zeta.CommonBot.GameStats.(Object , EventArgs )
--- Fim do rastreamento de pilha de exceções internas ---
em System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
em System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
em System.Delegate.DynamicInvokeImpl(Object[] args)
em System.Delegate.DynamicInvoke(Object[] args)
em Zeta.CommonBot.Pulsator.(Delegate , Object[] ) --> System.AccessViolationException: Could not read bytes from 00000000 [299]!
em Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
em Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
em Zeta.Internals.Actors.DiaObject.()
em Zeta.Internals.Actors.DiaObject.get_ACDGuid()
em Zeta.Internals.Actors.DiaObject.get_CommonData()
em Zeta.Internals.Actors.DiaUnit.get_Level()
em Zeta.CommonBot.GameStats.(Object , EventArgs )
[08:30:47.590 D] System.Reflection.TargetInvocationException: Uma exceção foi acionada pelo destino de uma chamada. ---> System.AccessViolationException: Could not read bytes from 00000000 [299]!
em Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
em Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
em Zeta.Internals.Actors.DiaObject.()
em Zeta.Internals.Actors.DiaObject.get_Position()
em Zeta.CommonBot.InactivityDetector.(Object , EventArgs )
--- Fim do rastreamento de pilha de exceções internas ---
em System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
em System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
em System.Delegate.DynamicInvokeImpl(Object[] args)
em System.Delegate.DynamicInvoke(Object[] args)
em Zeta.CommonBot.Pulsator.(Delegate , Object[] ) --> System.AccessViolationException: Could not read bytes from 00000000 [299]!
em Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
em Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
em Zeta.Internals.Actors.DiaObject.()
em Zeta.Internals.Actors.DiaObject.get_Position()
em Zeta.CommonBot.InactivityDetector.(Object , EventArgs )
[08:30:50.040 N] Diablo III Exited, Demonbuddy terminating

Someone can tell me some tips to avoid some crashs?

I have searched the words 'demon' or 'buddy' on the blizzard Error log file, and i didnt find any evidence of these words.

should i worry about it? I just checked that when d3 exits, db closes too, so it might prevent the db being in memory before the inpector catchs it?

Ty in advance
 
Last edited:
have you tried a fresh D3 installation?


i cant see a DB flaw on your log
 
Back
Top