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

"Diablo III has stopped working"?

kbarnes57

New Member
Joined
Feb 27, 2012
Messages
17
Reaction score
0
Hey all,

I recently built a rig to bot as many clients as possible:

AMD FX - 8150 3.6 8-core OC'd to 4.1
16 gigs Kingston HyperX Blu RAM
1TB Seagate HDD
2GB DDR5 GTX 550 TI EVGA

The problem I am having is that when I attempt to run more than 3 Diablo clients, they either crash and say "Diablo III has stopped working" or just flat out error code crash.
Any thoughts would be helpful, or if anyone has had a similar issues, I am all ears.
I have each client running out of a different folder that I copied from a clean install, and my DB is running from a clean install as well.

Thanks

UPDATE: It would appear as though after a certain point every client will end up with the same problem. Again, any ideas are welcome.
EDIT: Another problem I have had is with Diablo just freezing. In this case it does not show that it is not responding until I click on the specific client.
 
Last edited:
Need more information... How long are the bots running when they crash? Are you using any virtual machines (vmware, etc)? Did you forget to put -launcher at the end of the shortcuts for each D3.exe (probably not the issue but still...)? Are you running the DB in admin mode? Does DB give you any logs?

D3 clients will crash if the memory is sent wrong and can crash for random reason. (Usually will happen if the bot is trying to send to much info at one time. Rarely happens.)
 
No virtual machines. Have "-launcher" at the end of every shortcut. Tried running in both administrator and without. The problem appears to become more active when I have more than 3 clients open. There is no information in regard to this in the DB logs. The RAM on my comp hits 7GB max when this happens, and the CPU is running around 50-60 degrees and 70-80% capacity when this happens as well. The bots can run from anywhere from 5 minutes to an hour when only 3 open before the issue, but it appears to occur sooner with more than 3 clients open.

MORE UPDATES: I just dropped the OC 4.1 back to the stock 3.6. Will update is any changes.
 
Last edited:
Are all of your drivers up to date? (I know I know but it's actually common.) Video card drivers and sound drivers mainly? Which plugins are you using?

Try running D3 in admin mode as well.

Also there was an old issue with the in game sound that would cause D3 to crash with certain sound cards. You should try to disable the D3 sound and run it for a while and see what happens.
 
Last edited:
All my drivers are up to date. Updated them the second the OS was fully updated. Windows 7 Home premium 64-bit by the way. The sound was disabled when the problem occurred. I am using Giles Trinity for stash replacer and Notification OK for the gold farmers I have. The Barb item farmer is running the same with Profile Reloader with the same problem if whatever the underlying cause is hits that specific client. Running Belphagor for the gold farmers and Giles Trinity for Barb item farmers.
 
Last edited:
Are you using the latest version of DB? If so try a fresh install of DB and I would add the plugins 1 by 1 to see if any of them cause the crash. You can also try a fresh install of D3. There might be a corrupted file in your D3 folder. Other then that I am out of ideas.


Edit: Try using RadsAtom or RadsProfileManager instead of the profile reloader.

Edit 2: Did you change the .agent.db file to "supports_multibox" : true,

Edit 3: What is your max fps set to for each bot?
 
Last edited:
I am using the newest version of DB, but have had similar problems with previous versions. Have used different addons in the past with similar issues as well. I have not changed my .agnet.db file ever. I will look into that and see if any progress is made. Max FPS is 35 with background unticked. Thank you so much for your help.

Where is the .agent.db file located?

Also, I have each client in an individual folder. I don't know if that changes whether or not I need to edit the agent.db file.
 
Last edited:
The .agent.db file is located in your D3 folder and can be edited with your favorite notepad program :)
 
I added the "-launch" line to the shorcuts and not the original Diablo III.exe files that they are tracked back to. I don't know if that makes a difference either.
 
The shouldn't make a difference. In fact in think you can only add the -launch or -launcher to the shortcut. (Not sure haven't tried)
 
Would editing the agent.db file make a difference if each shortcut goes to its own individual folder? C:/Program Files (86x):/Diablo III, Diablo III 2, Diablo III 3, etc...
 
Honestly I am not sure. I have my .agent.db edited in all of my folders. I seldom have crashes from D3 clients. Usually my cause is from internet crashing for a second or two. I highly doubt it is from the .agent.db file though. It was just something that popped into my head. :P

Either way good luck to you and I hope your issue is solved. If not now hopefully soon. I must get some sleep now though.
 
For the record: the problem I am having outside of the client no longer responding and going white is called an apphang, just found that out. Any solutions welcome.
 
What is your cpu and ram usage at?
You can reduce DB usage by opening D3 prefs and changing:
Hardwareclass to "1"
DisableTrillinearFiltering to "1"
Mipbias to "9.999999" <------ this makes your graphics worse than runescape and will lop of TONS of memory usage.

Also windows 7 is set to shut down programs when ram/cpu usage increases above 70% and will randomly close Diablo III windows. I don't remember entirely how to disable it.
 
Back
Top