Demonbuddy crashes after giving error

gclol · Jun 15, 2012

so i bought DB yesterday and it gave me this error
[03:33:21.562 N] Demonbuddy v1.0.495.103 started
[03:33:36.708 N] Logging in...
[03:33:38.083 N]
[03:33:38.208 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 7413279F [299]!
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at ...ctor(ExternalProcessReader memory, IntPtr endscene)
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

this is actually the new test client that was made today but with .100 it gives the exact same error i just deleted the folder so i dont have the log, anyways has anyone gotten this type of access violoationexception error? i unstalled all required files, deleted DB redownloaded everything, all microsoft programs are in and its still giving me this error, btw im at my charc screen. i tried to email for help and all i got back was did you uninstall and install everything? i replied yes and havnt gotten a response then, can anyone else help me out? thank you.

oh yea this is started up in admin mode so yes tried that tip already

DavidKDean · Jun 15, 2012

I've noticed that if you simply restart Diablo itself. It fixes this problem.

srps · Jun 15, 2012

Code:

[03:46:05.768 N] Demonbuddy v1.0.495.103 started
[03:46:07.465 N] Logging in...
[03:46:08.086 N] 
[03:46:08.191 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 58A8279F [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
   at ...ctor(ExternalProcessReader memory, IntPtr endscene)
   at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
   at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
[03:46:25.402 N] Demonbuddy v1.0.495.103 started
[03:46:26.909 N] Logging in...
[03:46:27.521 N] 
[03:46:27.594 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 58A8279F [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
   at ...ctor(ExternalProcessReader memory, IntPtr endscene)
   at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
   at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
[03:46:31.467 N] Demonbuddy v1.0.495.103 started
[03:46:33.176 N] Logging in...
[03:46:33.795 N] 
[03:46:33.876 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 58A8279F [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
   at ...ctor(ExternalProcessReader memory, IntPtr endscene)
   at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
   at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
[03:46:57.041 N] Demonbuddy v1.0.495.103 started
[03:46:58.562 N] Logging in...
[03:46:59.189 N] 
[03:46:59.282 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 5A2E279F [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
   at ...ctor(ExternalProcessReader memory, IntPtr endscene)
   at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
   at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
[03:40:24.268 N] Demonbuddy v1.0.495.103 started
[03:40:27.212 N] Logging in...
[03:40:27.905 N] 
[03:40:28.066 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 5C7F279F [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
   at ...ctor(ExternalProcessReader memory, IntPtr endscene)
   at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
   at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
[03:40:57.498 N] Demonbuddy v1.0.495.103 started
[03:40:59.714 N] Logging in...
[03:41:00.742 N] 
[03:41:00.871 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 7028279F [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
   at ...ctor(ExternalProcessReader memory, IntPtr endscene)
   at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
   at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

Etc and all. Can't use the bot, tried with versions 100 and 103, enGB and enUS clients, ingame or in menus, every single time the damn error. Yes, I also restarted D3 a lot, launching with launcher or -launch option, same crap.

Also, tried with .NET and vcredist with and without windows updates. What's up with the program?

gclol · Jun 15, 2012

what do you mean, load up DB then load up d3 then exit d3? i just tried loading d3 and then DB and it crashes on me, i tried again and crashes

gclol · Jun 15, 2012

cool im not the only one then, if there isnt any fixable way how can i get a refund ~_~ because its getting really annoying trying to get this to work

srps · Jun 15, 2012

gclol said:
what do you mean, load up DB then load up d3 then exit d3? i just tried loading d3 and then DB and it crashes on me, i tried again and crashes

You need to run D3 before running DB. But if you're getting that error you're doing what you're supposed to.

gclol · Jun 15, 2012

yup getting the same error ~_~

DavidKDean · Jun 16, 2012

I'm having the same issue. When I get that error though I just restart D3 and it goes back to doing nothing but giving me a "Process must have frozen ...."

srps · Jun 16, 2012

Now it suddenly worked, after like 30 restarts. I just installed vcredist 2010 x64 as well, maybe that did the trick?

Try it, I guess, if it works it's a damn bug or a missing requirement from the list.

Edit: Nevermind, after some freezes (out of sync) and client restarts, back to

Code:

[04:12:48.207 N] Demonbuddy v1.0.495.103 started
[04:12:49.860 N] Logging in...
[04:12:50.492 N] 
[04:12:50.631 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 624B279F [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
   at ...ctor(ExternalProcessReader memory, IntPtr endscene)
   at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
   at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

DavidKDean · Jun 16, 2012

srps. Did you install that with x86 installed as well? Or did you uninstall x86 before installing x64?

gclol · Jun 16, 2012

theres an order to follow?

srps · Jun 16, 2012

DavidKDean said:
srps. Did you install that with x86 installed as well? Or did you uninstall x86 before installing x64?

Didn't uninstall anything. But nevermind, it was probably a coincidence, since it's gone back into the crapper. I'm gonna try this dump in other computers. How can a single guy (rolle3k) get this right for free and an entire team asking for money can't?
Never had any issues with d3a (R.I.P) which used .NET 4.0 as well.

DavidKDean · Jun 16, 2012

rolle3k was the SHIT! Sadly bein' bought out or w/e was much more important then the community.

With D3A gone and Immortal shady as hell. DemonBuddy is the next best thing. The company is known for fixing whats wrong.

gclol · Jun 16, 2012

zzz this sucks seeing as only a few of us are getting this error and not many reponding

srps · Jun 16, 2012

Still want this noticed, since it's a fatal bug that prevents us from even using the program.

Tony · Jun 16, 2012

you still got problems?

gclol · Jun 16, 2012

Yes we still have problem

Gdrel · Jun 16, 2012

[17:42:18.280 N] Demonbuddy v1.0.486.100 started
[17:42:19.869 N] Logging in...
[17:42:20.473 N]
[17:42:20.563 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 705D279F [299]!
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at ...ctor(ExternalProcessReader memory, IntPtr endscene)
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

Getting same error.

Tony · Jun 16, 2012

do you have any 3rd party D3 stuff enabled?

gclol · Jun 16, 2012

I have dark d3 installed will that mess it up?

Demonbuddy crashes after giving error

New Member

Member

New Member

New Member

New Member

New Member

New Member

Member

New Member

Member

New Member

New Member

Member

New Member

New Member

"The Bee"

New Member

New Member

"The Bee"

New Member