D3 Crashing and Poor Performance - Common causes and possible fixes

There are many, many reasons why Diablo 3 client can be crashing. Because there's never usually an easy way to tell what's causing YOUR Diablo 3 to crash more than somebody elses, I've written a guide that covers all of the causes I have seen myself or heard about, so that you can try to find a solution. I should point out that many, many people can bot without ever crashing anymore - and there are players that don't bot who get crashes in D3 all the time.


After a Patch:
Delete your Data_D3 directory in your Diablo 3 home directory. You will need to re-download all data but this can often solve a LOT of problems with the game.

Clean Diablo 3 Install:
Yes, really! This sounds like a lazy support message (I remember the old "re-format your PC" tech support helplines for every single problem!), but honestly - reinstalling Diablo 3 fresh has genuinely fixed crash problems for people. This is probably because of errors created during various major Diablo 3 updates, or from random file corruptions from too many file-reads and writes in a row during the many hours of playing/botting, or who knows what. But seriously - if you have crashes, and they are driving you crazy - take the time and effort and start with a brand new clean install of Diablo 3!


Diablo 3 Settings:

Graphical Settings:
Open Diablo 3 up and go into Options->Video. Set everything as low as possible, and set it to windowed mode, so your options should be;
Display->Windowed.
Vertical Sync: UNTICKED.
Texture Quality: Low.
Shadow Quality: Off.
Physics: Low
Clutter Density: Off
Anti-Aliasing: UNTICKED.
Low FX: TICKED.
Drag the Diablo 3 window size to make it as small as possible (this will be 800*600). Save/OK your settings.



Diablo Gameplay Options - HUD:
Disable all HUD options!




Advanced Settings:
Now close Diablo 3, and go to your "My Documents" folder, and open the "Diablo 3" folder - in this folder you will see a file called "D3prefs.txt". Edit this WHILE DIABLO IS CLOSED.
Find these settings and change them to what I have listed below - these will make your graphics VERY VERY BAD!
DisplayModeBitDepth "16"
Vsync "0"
Antialiasing "0"
DisableTrilinearFiltering "1"
MipBias "2.000000"
HardwareClass "1"


Install Folders/Locations:
DemonBuddy can sometimes have problems if it is installed in a very long path. Try moving both your Diablo 3 folder and DemonBuddy folders to a ROOT drive, you don't need to change any registry values or anything - you can literally move the entire folder and still run both Diablo 3 and DemonBuddy fine. For example;
C:\Diablo3\
C:\DB\
WARNING: You may need to update any start menu/desktop shortcuts to Diablo 3/DemonBuddy if you move their locations!


Non-English Diablo 3:
Non-English clients *MIGHT* cause more crashes than English ones - this is a problem with Diablo 3 itself. Currently I don't know of anything that can help reduce problems that are specifically related to the language of your client, but this is something to keep in mind if you use a non-English Diablo 3 client. If you are using a non-English client, then try all of the other fixes and keep your fingers crossed.


Virtual Machines:
If you are running Diablo 3 inside of a Virtual Machine - you automatically give yourself more problems - you make Diablo 3 more sensitive to CPU spikes, memory read errors, and general problems. If you are running in a virtual machine and suffering crashes, try running Diablo 3 without one - on your main machine. Note that I myself run ALL my D3 clients on one machine without any virtual machine use, I always have and have never had a problem or been banned from a game. If you have no choice in running a Virtual Machine, then try all of the other fixes and keep your fingers crossed.


High Ping/Latency/Virtual Private Network's:
If you have a bad connection, bad packet loss, high pings, then you can actually increase your crash rate. This is because DemonBuddy will KEEP sending command after command to Diablo 3 memory for Diablo to process, while the Diablo client is sat waiting for a response from the server. These constant requests can cause it to crash.

If you are using a Virtual Private Network, try a better one/a closer one, or not using one at all.

If you have other programs downloading from the net, try disabling them. Try doing some google searches for "Diablo 3 latency" - there are some registry tweaks and network settings you can change to try to improve it. Try do anything you can to improve your ping and connection.


Clean DemonBuddy Install:
As always - you should try downloading DemonBuddy from the DemonBuddy site again, and try with a fresh, clean install - into a new, empty folder.

DON'T simply update/overwrite your old folder! Sometimes old files/folders left by old installs or created by old plugins can cause random problems.

Using old settings can cause problems to persist.

Using old plugins is also a recipe for trouble.


Trinity and FunkyBot
Trinity is not compatible with FunkyBot - you cannot have them both installed at the same time. It will break everything!

Other Plugins/Profile Managers:
Try removing plugins one at a time (QuestTools and Trinity are typically required at all times).
Armory, KadalaSpree, fBaseExtensions and others have been known to make the bot misbehave and throw errors or act strangely. Delete them and restart your bot.


Reloggers/batch-launchers:
Some reloggers/batch launchers can cause random problems. Always make sure you are using an updated version if possible. You should also ALWAYS try running Diablo 3 and DemonBuddy manually - the normal way - without using any batch launcher. See if the crashes still happen when you DON'T use any reloggers or batch-restarters/command line tools.


Log into Battlenet first:
After opening Diablo 3, try logging in to Battlenet first and get to your character screen, BEFORE starting DemonBuddy. While this shouldn't affect crashes, it can sometimes fix other random problems - so is always something to keep in mind.


DemonBuddy Dependency Installer/.Net Framework:
DemonBuddy, like many programs, relies on a lot of built in Windows functions to run properly - usually these are in the ".Net Framework" you may have seen mentioned in your programs list or windows updates, or installed by other games. Sometimes these files can be out of date, or have problems.

In your DemonBuddy folder is a "Help" folder - in here is "Demonbuddy dependency installer.exe" file. Try running this as Administrator (right click->run as administrator). This will make sure that all of the windows-related files that DemonBuddy uses are correctly installed (all of the ".net" framework stuff). You should reboot your computer after doing this. You may also want to check for Windows Updates, as this can sometimes fix random issues.


Graphics Card Driver:
This is an obvious one to many people, but I will mention it anyway. Make sure your graphics card driver has been updated - it may well be that an older driver is causing your D3 client to crash more often.

Sound Card Driver
This is a not so obvious one. Diablo 3 will still try and use the windows sound API's even if you have sounds and music disabled. Make sure your sound device drivers are up to date from your vendor (even if it's built in to your motherboard!).

Antivirus / AntiMalware

Do not completely disable your Antivirus / Antimalware under any circumstances!

However, you DO want to whitelist Demonbuddy.exe and Diablo3.exe. It may also help to whitelist the .dll files in the Demonbuddy directory, or the entire Demonbuddy itself (as long as you keep it clean, use fresh installs and install other 3rd party programs into the Demonbuddy Directory!)

Many antimalware programs will identify Demonbuddy as a trojan or malware due to the advanced system hooks it uses to interact with Diablo 3. These types of hooks are required for the bot to operate.


Still Having Problems?:
If you still have problems after all that - and the problems *ONLY* exist in Diablo 3 (so you are sure your computer RAM is fine, and your CPU is fine, and your graphics card is fine) - try running Diablo 3 and playing manually for a few hours. Does it still crash? If so, then it's pointing to a compatibility issue between your computer, and Diablo 3. If it ONLY crashes with DemonBuddy attached, and none of the above fixes have helped, then try posting a support thread - explain your problems in as much detail as possible, and attach a log (found in DemonBuddy "logs" folder).

 

well it's bit odd everything.. my barb runs 24/7 no problem.. when using my wizard im getting alot of crashes,, like every 1-2 hour, had this issue with all the bots on my wizard but my barb always runs smooth without problems

 

Running a critical mass wizard? Your computer probably can't cope with the spell-re-use spam... try enabling the "TPS" setting and reducing it to 6-7-8, see if that helps.

 

yes cm wizard

my cpu spec:

2600k @3.4ghz
geforce gtx 580 soc
gigabyte g1 sniper 2 motherboard
8gb mushkin redline 1800mhz memory

have diablo + bot on a ssd, have a 50mb internet connection
maybe it needs more juice, I overclocked my cpu to 4.2ghz.. going to give it another go and see if it runs better.. still honstly i think my cpu is already a total overkill for diablo 3

 

would like to add,

If you let the bot run in "Zoom" in mode, it'll lower the CPU load by about 10-15%. just press "Z" (default) while ingame across all your bots and ull notice a better performance all around.

 

Excellent tip, never even knew about that, thanks!

 

Would that be to much to ask if i request adding auto zoom function in next version of your plugin Giles, so those of us who use reloggers could benefit from that discovery ?

 

it's excactly the same.. I even overclocked my cpu to 4.2ghz and it kept freezing, tried everything, all settings, diffrent profiles for act3, fresh install, it's same my wizard always freezes and yes im only running him not another bot with it.

im starting to think that the only botters that are running this 24/7 without problems are barbs.
starting to wonder that those who are making this bot and scrips are all botting on barbs therefore it's running 100% smooth for a barb nothing else.

 

Lots of people run Trinity with Barbs, Monks, Wizards, Witch Doctors, and more recently even Demon Hunters. Very, very, very few of them have crashing issues.

Crash issues do tend to be computer specific GENERALLY - depending on when/where it's crashing etc. (there have been DB versions that have crashed for everyone more often than others, and plugins that cause more crashes at certain points etc. of course!). Beyond all the tips and advice I've tried to put in, at the end of the day I'm neither a computer wizard, a technician, nor a DemonBuddy developer - I literally am just a DemonBuddy user and DemonBuddy is my first ever foray into the more complex worlds of computing (eg programming!). So I'm afraid I don't know what else I can do to try and help, except say - lots of wizards are running with Trinity just fine without any crashes, so there *IS* a solution, but what that is I'm afraid I don't know and apparently it isn't one I can solve for you.

 

reinstalling diablo fixed it.

so guess all those crashing problems people have is just diablo.. uninstall it and install again

 

you could try without the cpu overclocked, in my experience overclocks seem to cause some errors with programs.

 

Quick question, how do you make it pernamently zoom in? Everytime bot creates a new game, the view goes back to unzoom.

 

Can't find any version earlier than 1.1 of RadsAtom. This being on Github or the forum.

 

Probably a dumb question here, but is there a way to default set it to zoom mode versus having to press it every time a game loads? When I am botting, I press it once and its great performance, but on the next run it defaults back to non-zoom... any tips on this?

 

Happened to me twice or thrice - the english version of diablo crashed immediately upon v p n client (ciscoanyconnect) launch. not sure if it was accidentally or not though.

 

I wanted to add a note to this - something that was causing my system to crash was the Sound Channels (In control panel under Sound) set to "High (128)" - I set this to "Lowest (16)" and my CPU usage dropped and no more crashing.

Cheers,

rrrix

 

To correct the last poster to change your sound setting from high to low, the option is not in your control panel. Log-in to Diablo 3 then hit Esc>options>sound and on the top right corner is a hardware list, directly underneath that is the option to change your sound channel setting.

 

Having issues with the 1.05 update when it flashes d3 window it crashed db

this is my picture it happens as it flashes d3

 

exact same thing happening here

 

http://www.thebuddyforum.com/demonbuddy-forum/75980-beta-demonbuddy-daily-beta-builds.html

its the one for 1.05

sorry folks you can delete my posts if you need.