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

Error attaching to Diablo III

jodum

New Member
Joined
Oct 17, 2010
Messages
225
Reaction score
0
Hey, so i get this error on my computer after formatting disc c:.

[18:54:27.947 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 6C19279F [5]!
w Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
w Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
w Zeta.MemoryManagement.Executor..ctor(ExternalProcessReader memory, IntPtr endscene)
w Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
w Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

And yes, i used buddywizard, used visual and .net from links on forum, reinstalled old ones, installed new ones, well i tried everything with those two. Also tried running d3 and bot as administrator. Any idea?
 
upload your log on our forums plz,we dont check external links
 
you are completely logged in to diablo 3 correct? it needs to be sitting at the Hero screen, once its there you can start up demonbuddy.

also what os are you on?
 
Windows 7 pro sp1 64bit - always updated. Sitting at hero screen
 
try disabling your anti-virus, some are overzealous and block can block demonbuddy.
 
Using comodo - tried in "game mode" and tried turning it off completly. Also - on other computer it works just fine with comodo in game mode. This "problematic" computer is freshly after C: format.
 
Using comodo - tried in "game mode" and tried turning it off completly. Also - on other computer it works just fine with comodo in game mode. This "problematic" computer is freshly after C: format.
the other thing are you sure your running diablo 3 in windowed mode?

also make sure comodo has demonbuddy and d3 on your whitelists i had issues with it before sandboxing things without me knowing.
 
update your DB and try again


do you have any 3rd party D3 hacks/tools/programs?
 
the other thing are you sure your running diablo 3 in windowed mode?

also make sure comodo has demonbuddy and d3 on your whitelists i had issues with it before sandboxing things without me knowing.
Seems like it was sandboxed, even if i turned off comodo. Thanks a lot mate!
 
Seems like it was sandboxed, even if i turned off comodo. Thanks a lot mate!
i figured that was the case, comodo is nice in theory but its very overkill, in the end i just installed MSE (microsoft security essentials) and its been the best thing, since it hasn't bugged me for really thing and hasn't given me false alarms ether.
 
Back
Top