Solution for strange app-crashes on Blizzard games when using BosslandGmbH Products

[Elektrozoider]

Hi!

I'm not sure whether I chose a proper title for this topic, but I wanted to publish this post as a self-answer to a recent problem I had, and also as a useful guide that many affected users could read in the future, so lets go...



Known issues:

• DemonBuddy causes an app-crash of Diablo III in some seconds or minutes after start running a profile.

If you are experiencing an strange app-crash as described above, which seems randomlly and is getting you mad, then still reading, if not, then don't waste your time reading my shit!.

These are own conjectures of possible issues, you can ignore this ...or not:

• This bug is present in all current BosslandGmbH Products builds (in older builds of DemonBuddy I never had this problem), at least for surelly in DemonBuddy, and probablly in Honorbuddy (because I seen same issue here: https://www.thebuddyforum.com/honor...184193-wow-crashes-singular-tries-combat.html).
• The crash will happen in all Windows versions at least for surelly in Windows 10, and probablly in Windows 7/8/8.1.

Crash Reason:

• Superficially talking, the reason is that a non-essential Windows service with name "DNS Client" is essential for DemonBuddy.
• Technically talking, probablly some networking algotirhm of DemonBuddy depends on this service to be running for whatever reason, I didn't developed it so I can't tak about what I have no idea how it works.

This problem will affect (and probablly is affecting) to thousands or miles of DemonBuddy users, because there are many users that reads tutorials to clean the Windows shit services that are not essential and not useful, and how the hell you could expect that one of those services will cause an app-crash because DemonBuddy depends on it but is not handling it?.

Crash Conditions:

• The Microsoft Windows service with display name: "DNS Client" (or name: dnscache) should not be running.

Be aware that if the service is set to "automatic" or "on demand" modes, it still will be executed by Windows, so it should be disabled and stopped, in that order.

Steps to reproduce the bug:

1. Take your favorite Windows version (I tested it only in Windows 10 however) then take your favorite task manager or open the Windows servicing manager located at directory: "C:\Windows\System32\services.msc"
2. Find the service with display name "DNS Client" (identifier name: "dnscache"), then disable it, and stop it (in that order).
3. Run Diablo III and DemonBuddy as normally, then load any profile to test.
4. Start the bot/profile, and just wait some minutes (between 1 to 10) to see how the crash is produced.

Additional localization info:

• For Spanish people, the service display name is "Cliente DNS".

How to fix it?:

• Easy, just set the "DNS Client" service in "automatic" or "on demand" mode (it will be ran inmediatelly after the mode has changed).

Now you can still enjoy your favorite bot without app-crashes!.

Suggested actions for @Tony:

• Put an advise for the end-user in your documentation and in the FAQ webpages and related forum topics too, to advertise to enable the mentioned Windows service.
• Modify the behavior of bot products to be smart knowing this issue, implementing the required logic to avoid the user to start a profile if the mentioned service is not running.
• Gimme one unlimited Session to HearthBuddy for making the life and experience of many of your clients easier, haha!
• Feel free to edit, improve, update, have sex with, censore, or remove any content of this topic, you and any other mod.

Thanks for read!

 

[misosozi]

Glad you resolved your problem.

Just to add a few words. I have tried to play with DNS Client service but it does not have any affect on my environment. I tried on Windows 7 and Windows 10, both physical and virtual machines.

Cheers

 

[Elektrozoider]

Glad you resolved your problem.

Just to add a few words. I have tried to play with DNS Client service but it does not have any affect on my environment. I tried on Windows 7 and Windows 10, both physical and virtual machines.

Cheers

Hi

You will mean that you are experiencing an app-crash, and you tried to activate DNS Client but that didn't solved your crash, or you will mean that you tried to deactivate DNS Client service just for curiosity to see whether DemonBuddy crashes or not, but it didn't crashed for you?, or you will mean other thing?.

PS: I did the tests on Windows 10 x64 (in my host system and in a VM), the only way I found to be able run a profile without a crash is by enabling the mentioned service!.

 

[misosozi]

Hi

or you will mean that you tried to deactivate DNS Client service just for curiosity to see whether DemonBuddy crashes or not

Exactly this .