D3 crash every 1-2-3 hour
- Thread starter funker
- Start date
Tony
"The Bee"
- Joined
- Jan 15, 2010
- Messages
- 128,827
- Reaction score
- 570
04:11:14.761 D] System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
в Zeta.MemoryManagement.Executor.Execute(String debugMessage)
в Zeta.Internals.Actors.DiaActivePlayer.UsePower(SNOPower power, Vector3 clickPos, Int32 worldDynamicId, Int32 targetACDGuid)
в GilesTrinity.GilesPlayerMover.MoveTowards(Vector3 vMoveToTarget)
в Zeta.Navigation.DefaultNavigationProvider.()
в Zeta.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
в Zeta.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
its Trinity that errors there
report it on its thread plz
в Zeta.MemoryManagement.Executor.Execute(String debugMessage)
в Zeta.Internals.Actors.DiaActivePlayer.UsePower(SNOPower power, Vector3 clickPos, Int32 worldDynamicId, Int32 targetACDGuid)
в GilesTrinity.GilesPlayerMover.MoveTowards(Vector3 vMoveToTarget)
в Zeta.Navigation.DefaultNavigationProvider.()
в Zeta.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
в Zeta.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
its Trinity that errors there
report it on its thread plz
GilesSmith
New Member
- Joined
- Jun 2, 2012
- Messages
- 1,564
- Reaction score
- 34
Looking through your logs, it's your DB, D3, or computer itself at fault.
Something is going horribly wrong with the D3 client, and then all DemonBuddy attempts to read memory are screwing up. Obviously because you are using Trinity, almost all attempts are coming from Trinity (since Trinity is doing all the work instead of DemonBuddy default) - so Trinity appears in the logs - but it didn't cause them. Trinity actually reads memory *LESS OFTEN* than default DemonBuddy, and much less times each loop, so it generally REDUCES crash problems caused by memory reading issues.
Things I can suggest:
Diablo 3 Settings:
Make sure Diablo 3 is set to the *LOWEST* possible graphical settings in all areas - do this from the in-game settings, lower EVERYTHING.
Make it be in windowed mode, and drag the window to be as small as possible.
Now close Diablo 3, and go to your "My Documents"->"Diablo 3", and 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 - it will make your graphics VERY bad
DisplayModeBitDepth "16"
Vsync "0"
Antialiasing "0"
LowFX "1"
DisableTrilinearFiltering "1"
MipBias "2.000000"
HardwareClass "1"
DemonBuddy Dependency Installer/.Net Framework:
Next - try running the "Demonbuddy dependency installer.exe" in your "Help" folder in DemonBuddy, and rebooting.
Install Folders/Locations:
Try moving Diablo 3 and DemonBuddy to root folders in your hard drive, eg;
C:\Diablo3\
C:\DB\
(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 - note you MIGHT need to update shortcuts if you had desktop shortcuts to them!).
Other Plugins:
If you use Rads Profile Manager/Rads Atom - check for updates (on ciggarc.com) - and check for updates to the routines/profiles you use. I know some past versions have caused crashes, but I think he has fixed these.
(if you use any other plugins, try removing them temporarily)
Reloggers/command line tools:
Some reloggers/batch launchers can cause crashes. Try running diablo 3, and then demonbuddy, MANUALLY - without using any reloggers.
Log into battlenet first:
Make sure you log into battlenet, and are at your character screen, before running demonbuddy.
Trinity Advanced Config to reduce load:
Once you have done ALL of the above, open Trinity config window up, go to the "Advanced" tab, and tick the "Enable TPS" button, and slide the TPS value next to this *DOWN* to 7.
Non-English Diablo:
Non-English clients *MIGHT* cause more crashes than English ones - this is a problem with Diablo 3 itself.
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 can be because DemonBuddy will KEEP sending command after command to D3 memory for D3 to process, while the D3 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 things running or downloading, 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.
Virtual Machines:
Do note - If you are running in a Virtual Machine - you automatically give yourself ten times more problems. So if you ARE running in a virtual machine, I suggest you try running without one. (I run ALL my D3 clients on one machine without any virtual machine use).
---
I really cannot give you any specific help as a plugin developer of Trinity, because Trinity is not causing these bugs. Trinity is reducing the chances of them happening, but it's certainly not causing them. I am just trying to be helpful.
Please tell me if any of this fixed it for you or not. If it didn't, I don't think there's much else I can do besides advising a complete reinstall of everything from scratch including Windows
Good luck
Something is going horribly wrong with the D3 client, and then all DemonBuddy attempts to read memory are screwing up. Obviously because you are using Trinity, almost all attempts are coming from Trinity (since Trinity is doing all the work instead of DemonBuddy default) - so Trinity appears in the logs - but it didn't cause them. Trinity actually reads memory *LESS OFTEN* than default DemonBuddy, and much less times each loop, so it generally REDUCES crash problems caused by memory reading issues.
Things I can suggest:
Diablo 3 Settings:
Make sure Diablo 3 is set to the *LOWEST* possible graphical settings in all areas - do this from the in-game settings, lower EVERYTHING.
Make it be in windowed mode, and drag the window to be as small as possible.
Now close Diablo 3, and go to your "My Documents"->"Diablo 3", and 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 - it will make your graphics VERY bad
DisplayModeBitDepth "16"
Vsync "0"
Antialiasing "0"
LowFX "1"
DisableTrilinearFiltering "1"
MipBias "2.000000"
HardwareClass "1"
DemonBuddy Dependency Installer/.Net Framework:
Next - try running the "Demonbuddy dependency installer.exe" in your "Help" folder in DemonBuddy, and rebooting.
Install Folders/Locations:
Try moving Diablo 3 and DemonBuddy to root folders in your hard drive, eg;
C:\Diablo3\
C:\DB\
(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 - note you MIGHT need to update shortcuts if you had desktop shortcuts to them!).
Other Plugins:
If you use Rads Profile Manager/Rads Atom - check for updates (on ciggarc.com) - and check for updates to the routines/profiles you use. I know some past versions have caused crashes, but I think he has fixed these.
(if you use any other plugins, try removing them temporarily)
Reloggers/command line tools:
Some reloggers/batch launchers can cause crashes. Try running diablo 3, and then demonbuddy, MANUALLY - without using any reloggers.
Log into battlenet first:
Make sure you log into battlenet, and are at your character screen, before running demonbuddy.
Trinity Advanced Config to reduce load:
Once you have done ALL of the above, open Trinity config window up, go to the "Advanced" tab, and tick the "Enable TPS" button, and slide the TPS value next to this *DOWN* to 7.
Non-English Diablo:
Non-English clients *MIGHT* cause more crashes than English ones - this is a problem with Diablo 3 itself.
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 can be because DemonBuddy will KEEP sending command after command to D3 memory for D3 to process, while the D3 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 things running or downloading, 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.
Virtual Machines:
Do note - If you are running in a Virtual Machine - you automatically give yourself ten times more problems. So if you ARE running in a virtual machine, I suggest you try running without one. (I run ALL my D3 clients on one machine without any virtual machine use).
---
I really cannot give you any specific help as a plugin developer of Trinity, because Trinity is not causing these bugs. Trinity is reducing the chances of them happening, but it's certainly not causing them. I am just trying to be helpful.
Please tell me if any of this fixed it for you or not. If it didn't, I don't think there's much else I can do besides advising a complete reinstall of everything from scratch including Windows
Good luck
Last edited:
GilesSmith
New Member
- Joined
- Jun 2, 2012
- Messages
- 1,564
- Reaction score
- 34
You have the Russian language version which is known to have more crashes. You may just have to endure it.
After trying to help you yesterday, I wrote a longer guide here which you can check;
[url]http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/71985-d3-crashing-common-causes-possible-fixes.html[/url]
Also - try disabling "RadsAtom". Delete it from your plugins folder. And try using the older "RadsProfileManager" plugin, which is still available for download here;
[url]http://www.thebuddyforum.com/demonbuddy-forum/plugins/65600-ciggarc-plugins.html[/url]
You will have to make sure you use a routine from the CIGGARC team that is compatible with Rads Profile Manager (*NOT* one that needs the newer RadsAtom).
Lucky for you, the Act 2 routine (the one you are running) looks to be compatible with RadsProfileManager. The Act 2 thread is on the Ciggarc forums here;
[url]http://www.ciggarc.com/forums/index.php?topic=9.0[/url]
Beyond doing all of the things I list in that thread I made (the crashing guide), and removing RadsAtom and using RadsProfileManager plugin instead, I don't know.
After trying to help you yesterday, I wrote a longer guide here which you can check;
[url]http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/71985-d3-crashing-common-causes-possible-fixes.html[/url]
Also - try disabling "RadsAtom". Delete it from your plugins folder. And try using the older "RadsProfileManager" plugin, which is still available for download here;
[url]http://www.thebuddyforum.com/demonbuddy-forum/plugins/65600-ciggarc-plugins.html[/url]
You will have to make sure you use a routine from the CIGGARC team that is compatible with Rads Profile Manager (*NOT* one that needs the newer RadsAtom).
Lucky for you, the Act 2 routine (the one you are running) looks to be compatible with RadsProfileManager. The Act 2 thread is on the Ciggarc forums here;
[url]http://www.ciggarc.com/forums/index.php?topic=9.0[/url]
Beyond doing all of the things I list in that thread I made (the crashing guide), and removing RadsAtom and using RadsProfileManager plugin instead, I don't know.
GilesSmith
New Member
- Joined
- Jun 2, 2012
- Messages
- 1,564
- Reaction score
- 34
any more ideas?i done everything u told me now...
deleted atom and so on
I'm all out I'm afraid. Are you using virtual machines? Are you using any special "language changer" third-party tool to change the language of your Russian client? Have you tried playing Diablo 3 "manually" for a few hours to see if it still crashes when creating new games/loading new map zones?
Could you post a *NEW* log now that you have tried all those things, from the start of the bot-run until it crashed? I'd like to see if doing any of those things has changed the crash-causes or not.
Last edited:
GilesSmith
New Member
- Joined
- Jun 2, 2012
- Messages
- 1,564
- Reaction score
- 34
It's hard to tell exactly because it looks like you manually stopped the bot yourself with that run, but I would SAY it looks like a crash because of DemonBuddy's "useobject" command, which I know is a bit buggy atm and is being worked on for the next DemonBuddy release.
But - it may also be because you are running profiles with some random dungeons in (I think???) - looks like some Act 2 sewer run?
Try run a profile without random dungeons for now, or disable the dungeons from your profiles, see if things improve?