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

[BUG] Critical bug at ReadProcessMemory/WriteProcessMemory DIABLO III CRASH !!

Status
Not open for further replies.
E

Elektrozoider

Member
Joined
Jun 4, 2015
Messages
114
Reaction score
10
Hi

Today I came back to play Diablo III, I installed latest version of DemonBuddy with Trinity, and this is the first time that I used this new "Adventurer" plugin, and my first experience using this is all bad...

I just tried to use my DemonHunter to make normal rifts with the profile of the "Adventurer" plugin, but Trinity is always crashing the game...

I'm not sure if the problem is that the plugin tries to cast a Sentry before the spell is available, or it is related to ReadProcessMemory or WriteProcessMemory win32 functions.

If the problem is about the casting, then why should throw an exception that causes a critical bug in the game?, we can live with some missing spell castings to still botting, consider that and change the error-handlings behavior (please), because we can not live with constantlly crashes in the Diablo III process.

A full log:
https://www.zerobin.net/?7478bd68617438a1#JxEiiD8fxOFzTRKgCDb6KmQLIm8Htyuyc/c3IAloa+E=

A partial log:

01:25:55.211 INFO Logger [Trinity 2.14.45.1][Targetting] Calculating TargetPosition for Sentry using TargetPositionSelector at <590.9329, 634.9161, 0.1000003> Dist=60,60272 PlayerIsFacing(CastPosition=False CurrentTarget=False) CurrentTarget=Ghoul_C
01:25:55.212 DEBUG Logger [Trinity 2.14.45.1][Behavior] Selected new power=DemonHunter_Sentry pos=x="591" y="635" z="0" acdGuid=-1 preWait=1 postWait=1 timeSinceAssigned=0 timeSinceUse=13043,0896 range=85 charges=1
01:25:55.212 DEBUG TrinityDebug [Trinity 2.14.45.1][Behavior] Object in Range: noRangeRequired=False Target In Range=True stuckOnTarget=False npcInRange=False power=DemonHunter_Sentry target=Ghoul_C, Type=Unit Dist=0 IsBossOrEliteRareUnique=False IsAttackable=True
01:25:55.212 DEBUG TrinityDebug [Trinity 2.14.45.1][Targetting] Attack Target=Ghoul_C Power=DemonHunter_Sentry SNO=4203 Elite=False Weight=1000 Type=Unit C-Dist=6,1 R-Dist=0,0 RangeReq'd=85,0 DistfromTrgt=0 tHP=30 MyHP=69 MyMana=33 InLoS=True Duration=0
01:25:55.212 DEBUG Logger [Trinity 2.14.45.1][Behavior] CurrentTarget is Ghoul_C, Type=Unit Dist=0 IsBossOrEliteRareUnique=False IsAttackable=True
01:25:55.212 DEBUG Logger [Trinity 2.14.45.1][Behavior] DemonHunter_Sentry Using CurrentTarget Position/ACD
01:25:55.213 DEBUG Logger [Trinity 2.14.45.1][Behavior] DemonHunter_Sentry Using target position only.
01:25:55.217 INFO Logger [Trinity 2.14.45.1][Targetting] Casting DemonHunter_Sentry at <590.9329, 634.9161, 0.1000003> WorldId=1999896582 ACDId=-1 CastOnSelf=False Flags=None
01:25:55.218 DEBUG Logger [Trinity 2.14.45.1] Used Power Sentry (DemonHunter_Sentry) at x="591" y="635" z="0" dist=60) Range=85 (Spender Offensive) Delay=50/50 TargetDist=60,60272 CurrentTarget=Ghoul_C charges=1
01:25:55.218 DEBUG Logger [Trinity 2.14.45.1][Targetting] Recorded power=DemonHunter_Sentry pos=x="591" y="635" z="0" acdGuid=-1 preWait=1 postWait=1 timeSinceAssigned=6,4721 timeSinceUse=13049,5617 range=85 charges=1
01:25:55.218 DEBUG TrinityDebug [Trinity 2.14.45.1][Behavior] HandleTarget returning Running to tree from HandleObjectInRange ForceTargetUpdate
01:25:55.301 DEBUG Logger [Trinity 2.14.45.1][Movement] Surrounded BlockedPoints=6 Required=4 TotalPoints=6
01:25:55.302 DEBUG Logger [Trinity 2.14.45.1][Movement] IsBlocked! Timer=1644ms TestObjects=3 TestPoints=6
01:25:55.306 DEBUG Logger [Trinity 2.14.45.1][Behavior] Not Selecting Ability WaitingForPower=False WaitingBeforePower=False CurrentPower=power=DemonHunter_Sentry pos=x="591" y="635" z="0" acdGuid=-1 preWait=1 postWait=1 timeSinceAssigned=91,0152 timeSinceUse=84,5431 range=85 charges=1 CurrentTarget=Ghoul_C, Type=Unit Dist=0 IsBossOrEliteRareUnique=False IsAttackable=True
01:25:55.308 INFO Logger [Trinity 2.14.45.1][Targetting] Calculating TargetPosition for Sentry using TargetPositionSelector at <634.6263, 588.1002, 0.1000003> Dist=6,057077 PlayerIsFacing(CastPosition=False CurrentTarget=False) CurrentTarget=Ghoul_C
01:25:55.308 DEBUG Logger [Trinity 2.14.45.1][Behavior] Selected new power=DemonHunter_Sentry pos=x="635" y="588" z="0" acdGuid=-1 preWait=1 postWait=1 timeSinceAssigned=0 timeSinceUse=89,5717 range=85 charges=1
01:25:55.308 DEBUG TrinityDebug [Trinity 2.14.45.1][Behavior] Object in Range: noRangeRequired=False Target In Range=True stuckOnTarget=False npcInRange=False power=DemonHunter_Sentry target=Ghoul_C, Type=Unit Dist=0 IsBossOrEliteRareUnique=False IsAttackable=True
01:25:55.308 DEBUG Logger [Trinity 2.14.45.1][Behavior] CurrentTarget is Ghoul_C, Type=Unit Dist=0 IsBossOrEliteRareUnique=False IsAttackable=True
01:25:55.309 DEBUG Logger [Trinity 2.14.45.1][Behavior] DemonHunter_Sentry Using CurrentTarget Position/ACD
01:25:55.309 DEBUG Logger [Trinity 2.14.45.1][Behavior] DemonHunter_Sentry Using target position only.
01:25:55.309 INFO Logger [Trinity 2.14.45.1][Targetting] Casting DemonHunter_Sentry at <634.6263, 588.1002, 0.1000003> WorldId=1999896582 ACDId=-1 CastOnSelf=False Flags=None
01:25:55.331 DEBUG Logger [Trinity 2.14.45.1][Behavior] Failed to use Power Sentry (DemonHunter_Sentry) at x="635" y="588" z="0" dist=6) Range=85 (Spender Offensive) Delay=50/50 TargetDist=870,0679 CurrentTarget=Ghoul_C CurrentAnimation=Demonhunter_Female_Bow_Multishot_01
01:25:55.332 DEBUG TrinityDebug [Trinity 2.14.45.1][Behavior] HandleTarget returning Running to tree from HandleObjectInRange ForceTargetUpdate
01:26:02.897 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 1C93BC78, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:02.900 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 1C93BC78, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:02.964 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 1C93BC78, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:02.966 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 1C93BC78, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:02.980 INFO ZetaDia Diablo III Exited, Demonbuddy terminating in 20 seconds.
01:26:03.030 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.032 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.097 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.099 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.163 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.166 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.229 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.233 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.295 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.299 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.361 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.366 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.427 ERROR BotMain Exception during bot tick.
System.Exception: Solo se completó una parte de una solicitud ReadProcessMemory o WriteProcessMemory, at addr: 01E9A234, Size: 4
en GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
en GreyMagic.MemoryBase.Read[T](IntPtr addr)
en GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
en Zeta.Game.ZetaDia.get_CurrentTime()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
en Zeta.Bot.BotMain.?????????????????????????????????????????()
01:26:03.432 ERROR BotMain Exception during bot tick.
Click to expand...
 
Last edited:
Hi Elektro, sorry you're having a bad time with this.

I had a look at your log. The exceptions are not occurring in Trinity; they appear to be caused by the Diablo3 client crashing.

The client crash could have been caused by Trinity or another plugin or something unrelated to db but unfortunately we don't have enough information to determine what happened.

You said "but Trinity is always crashing the game..." - how often does your Diablo3 client crash? every game? if you have additional logs we could compare them to figure out if its a specific class or skill or situation when the crash happens.

I noticed that you have a lot of old and broken plugins. KadalaSpree, Armory, Belphagor and an outdated version of Trinity. So the first thing i would suggest to try is:


  1. Make a completely new empty folder on your computer.
  2. Extract the latest DB Beta Zip into it. https://www.thebuddyforum.com/demonbuddy-forum/238694-beta-demonbuddy-beta-builds.html
  3. Go into the plugins folder and Delete Trinity.
  4. Download the latest Trinity and Extract it to your /plugins/ directory https://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/
  5. Start Db, enter your key etc, select trintiy as your routine, to the plugins tab and make sure all the plugins are enabled.
  6. Load a profile and give it a test.
 
@xzjv

Thankyou so much for answer!. I have old plugins and trash but those plugins could interfere with Trinity behavior?, anyways I played with those plugins disabled/unchecked.

I got the same error/bug/whatever using Trinity v2.14.539

Its too late in my country, I didn't tested your suggestion yet, tomorrow i will do it (a full clean installation of all that) and I'll comment here how it goes...

EDIT: The game crashes every time that I use Demonbuddy, actually I only tested the NormalRifts profile, tomorrow I will choose different heros to properlly answer your questions.

PS: I'm under a fresh and recent installation of Windows 10 x64, if that matters.

Thanks again.
 
Last edited:
@xzjv

I followed your steps, a clean installation of demonbuddy, latests Adventurer and Trinity plugins from the links you shared, all three plugins active, default settings for demonhunter's combat and ticks per second, but the game is still crashing because Demonbuddy.

The bug happens for all my heroes...

Its a light of hope for me that you've listened to this, because at least I would like that Trinity devs. hear my problem to proceed analyzing the issue, I want to do botting :(.

pf... please understand that I'd paid for this product and now I still can't use it... it crashes my game every time.

---------------------------------------------------------------------------------------------------------

xzjv said:
Hi Elektro, sorry you're having a bad time with this. You said "but Trinity is always crashing the game..." - how often does your Diablo3 client crash? every game? if you have additional logs we could compare them to figure out if its a specific class or skill or situation when the crash happens.
Click to expand...

Yes it crashes every game in which I use demonbuddy bot, this means everytime that I'm start running a profile, and some minutes elapses until crash EDIT: In both fullscreen and windowed mode. Diablo III doesn't crash when I don't use Demonbuddy bot.

Please let me know if you need more logs than the attached ones, I can reproduce the crash how much you need.

---------------------------------------------------------------------------------------------------------

System Specifications:
  • Windows 10 Core/Home Edition (build number 10586) of 64-Bit.
  • No user-privileges problems, I'm under the hidden "Administrator" account.
  • .NetFx 4.0, 4.5.0, 4.5.1, 4.5.2, 4.6.0 and 4.6.1 (installed by Windows 10 and/or by Visual Studio 2015).
  • Diablo III.exe build: 2.4.0.36090 (117826-1449087).
  • Diablo III server region: Europe.
  • nVidia GTX 650 card.
  • Latest official nVidia Drivers (for Windows 10 edition).
  • CPU: AMD FX-8350

---------------------------------------------------------------------------------------------------------

Attached files:
  • Diablo III debug log (D3Debug.txt)
  • Diablo III preferences file (D3Prefs.txt)
  • Demonbuddy's UI log (console log.txt).
  • DH crash file log (DH 5080 2016-04-07 11.49.txt).
  • Barb crash file log (Barb 4752 2016-04-07 11.42.txt).
  • Demonsbuddy global settings file (GlobalSettings.xml).
  • Trinity settings file (Trinity.xml).
  • Adventurer settings file (Config.json).
  • QuestTools settings file (QuestToolsSettings.xml).

---------------------------------------------------------------------------------------------------------

Notes/Commentarys:

  • DemonBuddy makes crash my game always in less than 2-5 minutes ( the DH crash logfile is very very funny... :-/ )
  • I didn't experienced ANY bug/crash playing without using DemonBuddy, I played D3 today for a while around 1 hour doing normal rifts, all as normally.
    This confirms is a bug of Demonbuddy.
  • The Diablo III debug log (D3Debug.txt) contains error information at the bottom of textfile.
  • I need to think about which could be the cause of the problem, so just I will launch a hypothesis without much argument, but I think that maybe the Greymagic lib is the cause of all these problems, I don't confide in custom home-made memory manipulation implementations that tries to avoid CLR limitations... I would like to remark "home-made" (possible bugged and/or not deep-tested). It was tested under Windows 10?. It was tested under the current .NetFx that is targetting Demonbuddy application?, because I read time ago in the Technet forum from Microsoft team guys, talking about C++ performance tests on reading and writting memory, that some important changes (fixes) are made in the .NetFx 4.6.0 or 4.6.1 and some custom implementations will become slower, or something like that, I really didn't remember the article at all and I'm not an expert of that thematic, but I think that for many reasons Greymagic needs a new performance test and a unit-testing in general if it is not tested under .NetFx 4.6.x and if that lib can cause the bugs that I'm experiencing, because I imagine that lib is used by DemonBuddy to read D3 offsets so...
  • Please think that probablly I'm not the only user who is experiencing this bug, consider to give priority to this problem, please.
    I don't know the DemonBuddy developers in what environments realizes the post-build tests, but did you guys tested DemonBuddy under Windows 10?, because I just installed Windows 10 and Demonbuddy stopped working in difference as how great it worked under Windows 8.1 for one year...
    I think that could be the problematic factor: "DemonBuddy + Windows 10 + Greymagic?", or maybe not, again with not much argument to say that, but if its not Greymagic then what the hell would be?, I will remark again that this is not my thematic, but I only see memory errors in the log file and related to the dettached injection in D3 process so... that is what I think.

Thanks for read!
 

Attachments

Last edited:
Any news to this problem?. please say something

thanks for support!.

------------------------------------------------------------------------

EDIT: I have news to proof that definitelly this is a bug in Demonbuddy/Trinity/GreyMagic

  2. I installed Windows 10 in a Virtual Machine using VMWare WorkStation.
  4. I Installed Diablo III
  6. I Installed DemonBuddy.
  8. Then I used DemonBuddy (normalrift adventurer profile) and the same crash again...

So I'm really thinking that Demonbuddy/Trinity/GreyMagic was never tested under Windows 10 (and it should be tested, when selling a product)... could someone of Demonbuddy dev. team confirm or not my doubt?.

I'm the end-user, I mean that I'm not the one who should do and try all these things in other operating systems... then I expect a solution from you guys (I really preffer that than a refund as last resource), just please say something about this problem with Windows 10... did you tested Demonbuddy in Windows 10?, did you hear my problem?, are you trying to inspect this?, you need more logfiles? something else?, lets talk about this, because I NEED HELP.


( click in the images to enlarge )



 
Last edited:
I haven't had a chance to fully look through all your information; you provided a lot of it so thanks for that.

I've mentioned this thread to Tony who takes care of DB support issues; i think he might have more insight into common issues with DB and conflicts with operating systems, we'll see.

I can assure you though that DB has been working under Windows10 for me and thousands of other users for a long time. So unless you are on a strange version of Windows10 like a beta/alpha its probably something else specific to your install, your hardware/drivers or software installed on the system.

Will let you know when i know more. Thanks.
 
xzjv said:
So unless you are on a strange version of Windows10 like a beta/alpha its probably something else specific to your install
Click to expand...

Thankyou so much for answer.

I'll clarify that I'm not under a Windows 10 beta/alpha neither under a Insider Preview build,
I'm using the formally known "Windows 10 1511 (TH2 10586)" build, which is a public release,
it's really a major update that contains important fixes for many problems from old releases (much of them related with Windows UI aspect and behavior),
also, the build I'm using it's considered the latest estable build of Windows 10, you can see it in Wikipedia:


Wikipedia said:
Latest estable build: TH2, Version 1511, (Build: 10.0.10586.164)
Click to expand...

The article is written in Spanish, but the language no matters to see the only interesting thing which is the table containing the version history of Windows 10, and also this description about the TH2 build that I translated for you:

Wikipedia said:
November update - Windows 10 Threshold 2

On November 12, 2015 Microsoft released a "Update November," for Windows 10 (also known as "Threshold 2", "TH2", "1511 version, build 10586" and "build 10586.3").
The update has been in development since August 2015 and contains many more than the first version for the public Windows 10 (10240) improvements.
New features include the ability to add a fourth column to the start menu, restoring the ability to apply the accent colors for title bars, menus improved context, numerous improvements in Microsoft Edge and the ability to use a product key Windows 7, 8, or 8.1 to activate Windows 10. New applications included in this update are messaging, phone, video Skype, and Xbox beta (not to be confused with the Xbox app). The November update was scheduled for launch with the new Xbox One Experience (NXE).
Información del Traductor de GoogleComunidadMóvil
Acerca de GooglePrivacidad y condicionesAyudaDanos tu opinión
Click to expand...

It is the only build marked as green color (green = estable) in the Windows 10 version table seen in wikipedia (Threshold2 category).

More info about that update at Microsoft:

decorative-line-1.png


xzjv said:
its probably something else specific to your install, your hardware/drivers or software installed on the system.
Click to expand...

Having clarified all the doubts with my install, which is a "normal"/estable build, now about the hardware I can tell that I'm using the same hardware that I was using before installing Windows 10, I was using Windows 8.1, on which I ran Demonbuddy with no issues, however, I never tested the latest/current build of Demonbuddy in Windows 8.1 (you see, I had old plugins and profiles),
If I remember good the reason why I didn't tried it is because the current build of Demonbuddy requires .NetFx 4.6.x and for that I need to install a major update in Windows 8.1 to let me install .Netfx 4.6.x, something that I don't want to install, so I upgraded to Windows 10 directlly to gain more beneffits in general and to be able run the current build of Demonbuddy, on where unfortunately I found that it constantlly causes a crash for Diablo III, something that I never experienced in Windows 8.1, Windows 8 x64, or Windows 7 x64.

About the hardware drivers, I just needed to update two drivers under Windows 10, one for the grpahics card and the other for the sound card, any other drivers are managed by Windows driver repository itself, I didn't messed any strange things in my system environment, all is fine, I use my head properlly when using a operating system hehe.

If this matters, these are the drivers that I installed for Windows 10:


( In Windows 8.1, I was using/installing the equivalent drivers for Windows 8.1)

A DirectX diagnostic (using dxdiag.exe) does not mark any issue.

decorative-line-1.png


xzjv said:
Take a look at this and see if any of it might apply to your case.
Click to expand...

From the list of software that you linked, I don't have any product installed.

I'll remark that when installing the nVidia drivers, I only choose to install the card drivers, and the Audio HD drivers, I never choose to install Shadowplay and GeForce Experience features ...just because I don't need to keep expenssive background services running on my OS which does not serves for nothing, now you gave me more reasons to avoid installing that, thanks.

Also, I'd ensured that I didn't have any non-Microsoft background services or 3rd party programs running when I tested Demonbuddy (well, I mean additional than the safety ones like nVidia display service, SoundBlaster audio service, and VMWare services), on both my host and guest Windows 10 OS.

decorative-line-1.png



If I have time to do it, I'll download the bugged old release of Windows 10 (build 10240) on which I imagine you guys is the Windows 10 build where Demonbuddy is tested and is running fine,
so I will try the same build in a Virtual Machine to see whether for me is running fine in that Windows 10 version, however, it will be just a personal test I will do to see if I have problems or not with that build, but Is not an option for me to go back to that buggy release of Windows 10 in any case, because bugs of Windows 10 that I suffered like this one:

CENSORED (to avoid be banned by Blizzard)

(A very annonying aesthetic bug, like much others bugs of any kind that can be seen in the bugfix history of Microsoft releases, that are only fixed after the Windows 10 build that I'm using, Windows 10 1511 (TH2 10586))

Please, understand it, I mean my reasons, and the focus that Demonbuddy dev. team should give to this problem,
I mean that it is more reasonable to determine that Demonbuddy should be made estable for running on a major update of Windows 10 (Windows 10 1511 (TH2 10586)), than any other possible solution like explicit force end-users to use a specific Windows 10 build to be able run your product (in case of using Windows 10 build 10240 could be a solution for everybody, or maybe not).

decorative-line-1.png


xzjv said:
I can assure you though that DB has been working under Windows10 for me and thousands of other users for a long time.
Click to expand...

I know that you are starting to work in this problem, but I need to say all what I said,
sorry if some of my words or intrusive questions about how Demonbuddy/Trinity build is unit-tested could be offensive, I'm just trying to think or find a reason for this problem doing the only thing I could do being a user: Ask questions.

I'm not enraged or anything similar, maybe manners could be lost on translation, I'm just very sad and desperatelly for can't use Demonbuddy anymore since I'm on (a specific estable build of)Windows 10 :(.
 
Last edited:
most likely this has to do with your VM installation

DB supports Win10 and according your screenshots its an OS issue
 
@Tony

Thanks for answer and trying to help me, but that is not the reason, because I have installed VMWare Workstation after I'd published the main post with the crash log and have explained the problem I have under Windows 10, then I installed VMWare to try there (in another install of windows 10 TH2), obtaining the same crash.

I really don't know what more to try on my side, I think is not an OS (itself) issue because its a fresh install, I don't have "trash" files or registry keys in my OS (I used CCleaner), I don't have conflicting 3rd party programs or services running, and about the screenshot I just have some customizations in the taskbar (that I always had in Windows 8.1/8//7 with no issues running DB) with the program StartIsBack++: http://startisback.com/ and some Windows metrics color values safelly modified to look a dark Windows theme, things that will never can't conflict with DemonBuddy because are not related (and never conflicted in older Windows versions).

EDIT:
This is the only software I have installed in the VM (Microsoft Windows v.10.0.10586 a.k.a TH2):

SmIuUPf.png


And, with only that software installed, still happens the same crash again and again in diablo III only when using Demonbuddy (the crash occurs in some random minutes after ran a profile to do botting).
Even if I uninstall the non-essential WinSnap (a simple screenshot program), and UxStyle (a safe Windows theme personalization hack), after reboot to affect changes, and try play Diablo III using DB, happens the same crash.

What more proofs could be need to ensure its a DB problem then take attention to investigate it and not think it's an OS-alone or user problem?. Please, see what I mean!.
 
Last edited:
gimme your log from native Win10 machine plz,but upload it on our boards
 
Tony said:
gimme your log from native Win10 machine plz,but upload it on our boards
Click to expand...

Of course, but please could you tell me where you mean with "our boards"?, I want to do things right, sorry if this is not the proper place to upload logs.

Also, you'll need that I set specific log config parameters on demonbuddy settings or maybe in Lumber Jack plugin?.

EDIT: By now I'll try to download/Install diablo from battle.net client from scratch to discard that maybe updates had messed some thing.
 
Last edited:
This is what I did now:

Download Demonbuddy and demonbuddy beta, updated trinity and adventurer to last version, all set to default settings, I didn't modified anything.

Both the estable and beta DB versions gives me a crash, here are attached the logs, from host Win10.

----------------------------------------------------------------------------------------------

This is the Win32 exception information from Visual Studio debugger if I select to debug the Diablo III crash instead of close it:

Unhandled exception at 0x76F9D8A8 (KernelBase.dll) in Diablo III.exe: 0x000003E6: Se realizó un acceso no válido a la ubicación de memoria.
Click to expand...

Exact English equivalent error message:
Invalid access to memory location.
Click to expand...

And If I continue the break, this exception:
Unhandled exception at 0x776287E2 (rpcrt4.dll) in Diablo III.exe: 0xC0020043: Error interno en una llamada RPC (parameters: 0x00000001, 0x000003E6).
Click to expand...

Exact English equivalent error message:
An internal error occurred in a remote procedure call (RPC).
Click to expand...

EDIT:
I found a user with a post about Honorbuddy which had game-crashes with same win32 errors due to have Honorbuddy running (I assume Honorbuddy and Demonbuddy uses more or less same libraries so could be related?):

EDIT 2:
There is one obvious thing in all this:
Eventually (like 5-10 minutes) something happens in Demonbuddy and/or Diablo III, some kind of event is fired, that for whatever reason causes a crash in Diablo III (in some Windows configurations who knows why) when Demonbuddy is injected (or in WoW with Honorbuddy for that other user),
that is absolutelly a fact, and I hope also it could be a good hint for @Tony to determine what is happening here.

Now the question would be, what the hell could be the exact reason that generates a crash?, and maybe could be related to a remote access connection with the client for some kind of verification?,
I'll try monitor the demonbuddy process connections and calls in general and analyze some things by myself about the Windows services related to RPC calls to try take something in clear.

I hope this can help for something... :(
 

Attachments

Last edited:
pm me your Skype and we will teamviewer your native Win10 machine
 
Status
Not open for further replies.
Back
Top