D3 Crashing and Poor Performance - Common causes and possible fixes

I'm getting a lot fo crashes recently as well. All the profiles I use crash, and the custom ones i modified that were running awesome crash too.

It seems like everytime the game crashes, its becuse the inactivity timer in db or trinity or atom doesnt trigger becuase the bot isnt standing still. the bot is stuck but its moving back and forth slightly. While the subtle movement isnt enough to trigger db and the plugins, its enough for d3 to consider your client afk and disconnects me from the server, which if clicked ok puts you back in the menu screen if you catch it quick enough. If you dont catch it quick enough, after about an hour or so while sitting on that screen with the game disconnect message, the game will simply crash.

I did see something about the unified trinity somewhere mention that it should click ok on that screen and restart the profile. Im testing that now, if i can adjust the loot rules becuase it filled my stash up with ultra junk items in 1 run.

Im thinking that if it simply restarts the profile, then you will get stuck aghain becuase most profiles are multiple xml's and it will load the profile you were on when you were 5 profiles deep in a a2 key run, instead of the usual "start here" profile. so you jsut get stuck and leave and get stuck and leave. we'll see.


edit: after sitting all night, using my modified act2 profile and unified trinity and the new atom plugins, it ran all night no crashes. No legendaries or keys in the stash so im thinking it needs to be watched for a while... but no crashes yay!

 

I had this issue as well, and i simply reinstalled diablo and DB and now i have been perfect for a day without crashing. I suggest doing it as well if you still face this problem. And now might be a great time to seeing as how 1.0.6 just came out and they need to update DB.

 

i have d3 crashes sometimes. and i think its related to the client's language/ i have ruRU.
can somebody tell me may i log-in and play if i'll just rename mpq's from english version and place them into russian client's folder?

 

iam also having issues with this, seems like it allways(~90% of the time) is when its at rakkis crossing.
Ihave tried diffrent runs(alkazier By gnome, champhunt etc) all with radsatom and giles

 

I retract my previous statement. It stopped for a day, but now it is freezing again.

 

???

 

you mean a Gibson like from that movie hackers? lol

 

proc overklocked from 2900 to 3500 Mhz

but it is still strongly loaded

 

help please. diablo 3 always terminated after some time when two different games started with -locale=ruRU option.

if i started enGB or enUS and ruRU simultaneously, all OK. but if two russian localisations....

 

same my demonbuddy crash and shows that error log

 

Blizzard patched demonbuddy

F01923FF-A082-420E-A945-88596C11E42C

 

Well back to the grind....

 

I wonder if the error report will report us all....are we screwed?

 

Time to cash out, if that's the case.

 

hm... since updating to 1.0.6a (today), while using DB game is crashing, and nothing helps (mean reinstalling, using different versions of db atom and giles), what could this mean? does anybody have any issue of this problem?

 

same for me, today after the d3 update, after i start DB, diablo 3 crashes....what now ?!

 

Alot of this has to do with what plugins you are using as well as what profiles you are running. Other factors also come into play such as: CPU speed, how many bots you are running, etc. If your computer starts to slow down due to the bot working to long try reducing all the graphic settings and etc. in D3. Do you have any sort of sleep on your PC (while you go afk if your computer was to sleep would cause problems). If you have logs of the crash it would be alot easier to see what was going on here

 

Go to Demonbuddy.com. Make a fresh install with the new version of DB. Move your plugins and profiles over to the fresh install. Start D3 and load DB should work fine if you installed correctly.

Don't minimize to try currently it is causing some people some trouble.

 

Db beta is running awesome atm, 12:16

 

i saw when i started DB that it had an update but it said if i'm in europe not to update, so i didn't. So should i update?