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

This is what causes 2 crashes

LucidReality

New Member
Joined
Oct 4, 2012
Messages
79
Reaction score
0
This is what causes 2 crashes (NOT the APPHANGB1 CRASH)

These past days of using this bot have been horrible.. I've been messing around trying to get this bot in an operational state.

I notice that when leveling up characters, this is the only time I experience D3 crashing.. Any fully geared level 60 characters I have never die, and never crash. So I figure it had something to do with death. I have around 6 bots going at the moment so its easy to just sit watch and wait to get an idea of why they are crashing.

After countless questioning, many simply said "oh the profiles you use suck blah blah" -- but they had no evidence to back this up and would stay arrogant in the whole conversation with nothing that was really helpful.

I am using the latest version of Demon Buddy, GilesTrinity along with RadsAtom as many people suggested, so perhaps these could be the real cause of what I'm about to describe -- I don't know I'm a new user to this software seeing that the other bot I used is never coming back, or at least any time soon.

I've done all the typical checks and solutions for D3 crashing issues -- I never had crashing issues with Immortal. Fresh installs between two computers, etc.

In the process of leveling up characters, they would die sometimes and I had leave on death enabled -- but while the bot is in the 10 second screen, it would sometimes continue in the background to revive itself and even fight monsters! First that has got to be a red flag for Diablo -- you can't legitly do this ever. I have watched my bot countless times CRASH when this happens. -- What is the solution?

So great, lets just turn off leaving upon death.. This noticeably helped.. but hey I'm still crashing so I watched the bots some more and noticed a lot of times that when I started back the bot--it needed to repair.. So when the bots weapons were breaking I'd watch waiting for it to go repair.. Well sometimes the bot would start to leave the game (10 second screen) BUT ALSO START TO GO TO TOWN TO REPAIR. Again, something that shouldn't even be happening in the first place since it isn't even possible to legitly do that... But bam.. another crash.. -- What is the solution?

Thanks for reading.

EDIT: ** Also note, this is NOT the Windows HANG crash this is the DIABLO crash where they want you to send the report in to them.

1p8qht.webp

LOGS: http://www.tizzytazzy.com/14940 2012-10-10 00.38.txt
LOGS2: http://www.tizzytazzy.com/1108 2012-10-10 01.58.txt

EDIT: Here is a video I recorded, I can now predict when the bot will crash. Sorry for the quality and the weird slant, this was my first time using the record program and youtube.. I have no idea how the quality got that wierd..

Demon Buddy Crash - YouTube

Notice he gets in position to town (you just don't see the bar) with the 10 second timer popped up.

He sometimes will also be attacking monsters if he isn't trying to town which causes the same exact crash as mentioned. If he isn't trying to town or attack monsters while he is on that 10 second screen the bot doesn't crash.
 
Last edited:
I'm also having crashes in d3 and these are some of the plugins that worked before d3 started crash frequently (like every 1 hour or so)..

Before crash (bot could run 24/7 for days, except when DB gets kicked out from nav server):

DB v.259
Giles Trinity v1.6.1.1
Radsatom v1.1

Start of the crash (App crash and D3 asks to send in the report):

DB v.259
Giles Trinity v1.6.2 (updated to latest ver)
Radsatom v1.3.6 (updated to latest ver)

All other settings remained the same... so it has to be either of the 2 plugins... I'll probably test it more when i'm back home later tonight but hope this little info helps.
 
Last edited:
I'm also having crashes in d3 and these are some of the plugins that worked before d3 started crash frequently (like every 1 hour or so)..

Before crash (bot could run 24/7 for days, except when DB gets kicked out from nav server):

DB v.259
Giles Trinity v1.6.1.1
Radsatom v1.1

Start of the crash:

DB v.259
Giles Trinity v1.6.2 (updated to latest ver)
Radsatom v1.3.6 (updated to latest ver)

All other settings remained the same... so it has to be either of the 2 plugins... I'll probably test it more when i'm back home later tonight but hope this little info helps.

Which crash are you getting? The apphang windows crash or the crash where diablo asks you to send in the report?
 
Same as yours. App crash and D3 asks to send in the report. I'll update in my post.
You get both? There is a huge difference.. I'm just getting the D3 report crash or the crash where D3 just poofs.. An apphang crash is when the screen goes white and windows wants you to send a report in.

EDIT: I added a screen shot, that is the type of crash I get.
 
Last edited:
Exact same problem here... I'm using same plugins thunderdogz uses...
It started crashing after I updated Demonbuddy v259, Giles 1.6.2 and RadsAtom 1.3.5(or 1.3.6). I don't know exactly after which one since most of them doesnt keep old versions up for diagnostic. (just Giles, our president)

Sometimes I get D3 crash followed by D3 window poofing and send report, this normally occurs five minutes or less after reloading a profile after the first run.
And sometimes I get D3 process freezed on blank screen.

:(

I will try to see what exactly the bot was trying to do when D3 crashed so I can add more info here, but I noticed it's always after the first run, which was very clean.
 
Last edited:
a report bug thread without log files posted its 100% useless
 
a report bug thread without log files posted its 100% useless
Not sure how you figure this, I described exactly what the issue is and how to duplicate it so you can see for yourself. Last time I posted logs for anything you simply said you forwarded it to someone and no one ever got back to me. :rolleyes:
 
i dont remember the specific case you are talking about but for every bug report we need your log
 
i dont remember the specific case you are talking about but for every bug report we need your log

Edited the post and added the logs.

[05:16:04.460 N] ####################################################
[05:16:04.516 N] [GilesTrinity] Items may need repair, now running town-run routine.
[05:16:04.555 D] Replaced hook [ProfileOrderBehavior_Hook] 75407bad-8c50-41ba-a56b-fa5f5b8afbde
[05:16:14.685 N] Diablo III Exited, Demonbuddy terminating
 
You get both? There is a huge difference.. I'm just getting the D3 report crash or the crash where D3 just poofs.. An apphang crash is when the screen goes white and windows wants you to send a report in.

EDIT: I added a screen shot, that is the type of crash I get.

hmm somehow i can't see your screenshot, but when i went to check my bot I only see the D3 crash report only. I'm assuming DB also crashed (or shutdown by itself?).
 
You get both? There is a huge difference.. I'm just getting the D3 report crash or the crash where D3 just poofs.. An apphang crash is when the screen goes white and windows wants you to send a report in.

EDIT: I added a screen shot, that is the type of crash I get.

Yup its the same as your screenshot. When i went to check my bot I only see the D3 crash report only. I'm assuming DB also crashed (or shutdown by itself?).
 
Yup its the same as your screenshot. When i went to check my bot I only see the D3 crash report only. I'm assuming DB also crashed (or shutdown by itself?).
Yeah when you crash DB will shut down by itself it appears from reading the logs.

The difference between windows hang crash and this crash is that windows crash is usually caused by something to do with windows, such as you overloading your PC with too many instances.

Typically I notice when its a diablo crash, or what ever you want to call it, it is directly caused by the bot itself.
 
Yeah when you crash DB will shut down by itself it appears from reading the logs.

The difference between windows hang crash and this crash is that windows crash is usually caused by something to do with windows, such as you overloading your PC with too many instances.

Typically I notice when its a diablo crash, or what ever you want to call it, it is directly caused by the bot itself.

I agree with you that the diablo crash is caused by the bot or the plugins. Happens quite often when a new update for either the bot, plugin is released.
 
So I kept wondering why the bot trys to leave sometimes for almost no reason (basically has to be in the situation you see in the video).. I looked for settings but couldn't find any.. I decided to try disabling "RadsAtom" -- and bam.. No more crashing! :D
 
Tony said same thing, I tested here and crashes stopped, yet Radonic says it has nothing to do with RadsAtom :/

This is sad, Rads is an awesome plugin, and a must for all my profiles.
 
Back
Top