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

System.AccessViolationException: Could not read bytes from 00000000 [299]!

xMrAce

New Member
Joined
Jun 2, 2012
Messages
4
Reaction score
0
[02:49:09.234 D] System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_Distance()
at Zeta.CommonBot.Logic.BrainBehavior.Œ(Object ret)
at Zeta.TreeSharp.Decorator.CanRun(Object context)
at Zeta.TreeSharp.Decorator..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.CommonBot.BotMain.()
 
hi,

I keep getting this so i cant do anything else. thx for fixing this. (I dont think im doing something wrong)!
 
i am getting this error with the latest DBrelogger.

Can anyone help?
 
[20:19:10.113 D] System.AccessViolationException: Could not read bytes from 00000008 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.ACD.[](ACD , Int32 )
at Zeta.Internals.Actors.ACD.GetAttribute[T](Int32 attribute)
at Zeta.Internals.Actors.ACD.GetAttribute[T](ActorAttributeType attributeType)
at Zeta.Internals.Actors.ACDItem.get_Gold()
at Zeta.CommonBot.Logic.BrainBehavior.?(Object )
at Zeta.TreeSharp.Decorator.CanRun(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.CommonBot.BotMain.()
 
just one thing don?t use any torrent clients while playing diablo 3....
 
nono, of course NO filesharing while running D3 :)

So i assume it's my provider lagging D3 and Relogger out untill this error message...

Yesterday my connection was better, no error...
 
This error has nothing to do with 3rd party software. I've been getting this ever since .215. Sometimes the bot runs for an hour and gets it, sometimes it runs for 2 minutes. I have nothing but Diablo 3 and DB installed on the machine running this. Everything worked perfect (never ever saw this error) prior to any of the 1.0.4 versions of DB.
 
This error has nothing to do with 3rd party software. I've been getting this ever since .215. Sometimes the bot runs for an hour and gets it, sometimes it runs for 2 minutes. I have nothing but Diablo 3 and DB installed on the machine running this. Everything worked perfect (never ever saw this error) prior to any of the 1.0.4 versions of DB.


I can't confirm or reproduce this tho and I am running DB 24/7
 
I can't confirm or reproduce this tho and I am running DB 24/7

Using DBrelogger and antiIdle only.
This can be re-create after DBrelogger recall your D3 first then your DB, but sometimes when lag D3 couldn't complete launched before DB, then the error came out.
Forever hassle on Relogger problem... :(
 
Last edited:
Using DBrelogger and antiIdle only.
This can be re-create after DBrelogger recall your D3 first then your DB, but sometimes when lag D3 couldn't complete launched before DB, then the error came out.
Forever hassle on Relogger problem... :(

exactly this.
 
So it happens only when using the relogger?
 
Back
Top