System.Exception: Only a part of ReadProcessMemory- or WriteProcessMemory

[da.nephalem]

[SOLVED] System.Exception: Only a part of ReadProcessMemory- or WriteProcessMemory

I got my bot running A5 Siege Camp with DB 517 + Trinity 2.6.5 fine. But time to time I get the errors:

ERROR Logger [Trinity] Error in HandleTarget: System.Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen, at addr: 00000000, Size: 416
bei GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
bei GreyMagic.MemoryBase.Read[T](IntPtr addr)
bei Zeta.Game.Internals.Actors.ActorMovement.
()
bei Zeta.Game.Internals.Actors.ActorMovement.get_Speed()
bei Zeta.Game.Internals.Actors.ActorMovement.get_SpeedXY()
bei Trinity.Trinity.UpdateStatusTextTarget(Boolean targetIsInRange) in c:\Users\Jarvis\Desktop\VOL2.2\Plugins\Trinity\Combat\HandleTarget.cs:Zeile 962.
bei Trinity.Trinity.HandleTarget() in c:\Users\Jarvis\Desktop\VOL2.2\Plugins\Trinity\Combat\HandleTarget.cs:Zeile 112.

The result is often that Diablo 3 disconnects and db throws error after error.

Would be sweet to get that thing stable again. Actually the bot has no need to fight at all, so if its any combat routine I'm free to disable it at all.

Thank you guys.

 

[derptard1]

I have the exact same problem.

The bot will run fine for.. 1 hour, or 5, or sometimes even 10, but it will always and without exception disconnect with this error.

It leaves the game to make a new one, but doesn't - and just sits in menu with DB giving this error. Then it gets disconnected from D3 servers because of "inactivity" and DB just spams error after error for hours on end. It has been like this for months for me.

 

[da.nephalem]

I'm using Wizzard class and farming chests in act5.

you?

 

[Tony]

make a new installation from scratch and use EZUpdater for Trinity and Questols

 

[da.nephalem]

It actually is a fresh install. No other plugins.

 

[Tony]

using EZUpdater?

 

[da.nephalem]

EZUpdater fails, invalid working directory....

I updated to Trinity 2.7.0 manually. Lets see if that helps.

 

[iCKR]

EZUpdater fails, invalid working directory....

I updated to Trinity 2.7.0 manually. Lets see if that helps.

Let us know how that goes.

 

[Tony]

EZUpdater fails, invalid working directory....

thats just to inform you,not a real issue

 

[da.nephalem]

@Tony: I think it is an issue, because he doesn't update any plugin.

@iCKR: Seems like my problem is solved with trinity 2.7.0

500 Runs @ 32GPH without crash. Only need to speed it up a little.

Thanks guys!

 

[Tony]

alright!