Crash

[imap30]

update: I fixed the problem by reinstalled diablo. I was using a graphics mod to make my graphics "sharper" and "darker" that seemed to mess with the bots ability to function.


Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: demonbuddy.exe
Problem Signature 02: 1.0.540.125
Problem Signature 03: 4fde4120
Problem Signature 04: Demonbuddy
Problem Signature 05: 1.0.540.125
Problem Signature 06: 4fde4120
Problem Signature 07: ba4
Problem Signature 08: 0
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

 

[heartspains88]

Same issue here.

 

[imap30]

more details in logs:

[22:22:02.116 N] Demonbuddy v1.0.540.125 started
[22:22:04.291 N] Logging in...
[22:22:05.124 D] System.AccessViolationException: Could not read bytes from 66FE279F [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)
[22:22:05.124 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 66FE279F [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)