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

Crashes/BSODs/Errors? How stable is D3+DB?

which errors you experienced while botting?

  • D3 and DB runs smooth, no crash ever

    Votes: 0 0.0%
  • D3 Crash-window with the error key

    Votes: 0 0.0%
  • D3 freeze (has to restart)

    Votes: 0 0.0%
  • Blue Screen of Death, BSOD, PC Crash

    Votes: 0 0.0%
  • DB Crash (DB stops working and closes)

    Votes: 0 0.0%

  • Total voters
    0
Status
Not open for further replies.
mostly plugin faults, so i wouldn't blame the developers just yest. What I blame them for is they don't advertise us about the plugin incomp or not supporting properly...
 
What did you set the delay timer on?

That varies by the speed of your computer. 625 seems to be optimal for my laptop but a faster computer can be way less (300 easy) and a slower one 1 or 2 sec. If you get error messages when leaving and remaking games or crashing, you've set it too low. If you don't it's good.
 
I had mine on default 1000 and the game would sometimes crash after a few hours (who knows, maybe anti virus / firewall did a scan or something to lag the computer for a bit). I then set it to ~1100 and haven't had a crash since. That being said, I can run it on the lowest possible timer as well, but I can imagine it would crash eventually.
 
I had mine on default 1000 and the game would sometimes crash after a few hours (who knows, maybe anti virus / firewall did a scan or something to lag the computer for a bit). I then set it to ~1100 and haven't had a crash since. That being said, I can run it on the lowest possible timer as well, but I can imagine it would crash eventually.

Could simply put just be heat slowing your computer down after running for a few hours. Getting it past the 1k breakpoint
 
if your getting BOSD's and crashing, theres something going on with your OS or your hardware thats causing that to fail, the bot wouldn't cause that.

O really?

EARLIER: Using two vmwares with d3 botting sarkoth with autoit profiles and normally playing d3 on main host (or leveling with HellBuddy). NEVER GOT ONE BSOD. Dont got bsod for 1 year since changed to new hardware.

YESTERDAY: Tried for first time demonbuddy. Using AGB 0.6.2 Sarkoth profile with DemonHunter running on main host with and without vmwares running in background causing 3 time BSOD in less than 30 minutes. Using Windows 7 64 bit. Sandboxie installed. Stable temperature 55 degree C on 4 cores. RAM without any errors.

Here you can see and analyze my three BSODs:

Crash List
 
yesterday i had my first BSOD without DemonBuddy.

Restarted PC, played for about 3hours in act1, went to town -> BSOD.
 
O really?

EARLIER: Using two vmwares with d3 botting sarkoth with autoit profiles and normally playing d3 on main host (or leveling with HellBuddy). NEVER GOT ONE BSOD. Dont got bsod for 1 year since changed to new hardware.

YESTERDAY: Tried for first time demonbuddy. Using AGB 0.6.2 Sarkoth profile with DemonHunter running on main host with and without vmwares running in background causing 3 time BSOD in less than 30 minutes. Using Windows 7 64 bit. Sandboxie installed. Stable temperature 55 degree C on 4 cores. RAM without any errors.

Here you can see and analyze my three BSODs:

Crash List
Damn you found AGB's rootkit, i do all the syscalls i like, inject my own driver and in combination with all the ring0 shit demonbuddy does a bluescreen is inevitable.
First i tried to exploit your Nvidia Graphics Card driver but caused a bluescreen so i went on to mack around with your keyboard until finally i exploted a buffer overflow in the notoriously unsafe razor mouse drivers until i gave up because the logs you supplied contain no information.
 
Damn you found AGB's rootkit, i do all the syscalls i like, inject my own driver and in combination with all the ring0 shit demonbuddy does a bluescreen is inevitable.
First i tried to exploit your Nvidia Graphics Card driver but caused a bluescreen so i went on to mack around with your keyboard until finally i exploted a buffer overflow in the notoriously unsafe razor mouse drivers until i gave up because the logs you supplied contain no information.
:P :)
 
The latest version of DB with AGB7 has been the most stable i've ever seen it. Runs overnight with no d3 crash.
 
i think its not the DB which has the problem.. i run it(.220) last night and did not get any error (appx.12 hrs)
i tried playing just now with out a bot... and D3 also crashes...

DC.. error 3007,...etc.. also the AH got some prob...
and logging in problem... error 3006
 
Last edited:
Exactly. And 54% experiencing crashes, to say this is hardware related sounds a bit like a fairy tale.

your reading skills are of par above mine... No one said DB crashes cause of hardware, it was said that BSOD is hardware....
 
i dont think anyone can argue that DB has a stability problem affecting the rountine crashing of Diablo3
 
my d3 client just close unexpectedly at sometime, but mostly is stucking in the map for whole night. I have using anti stucker plugins but the bot still go back to the same place and stuck itself.
 
my d3 client just close unexpectedly at sometime, but mostly is stucking in the map for whole night. I have using anti stucker plugins but the bot still go back to the same place and stuck itself.

I was getting that, and started using AntiIdle. All okay now.

Crashing: my D3 crashed a few times this evening, and I did not have DB running ?!?!
I wonder if this crashing is D3 related, not DB ? Kind of reminds me of the nightmare of the early days of D3.
 
it keep crashing

we need fix or a good working relogger

damn i was able to relog at the autoit sarkoth
 
I havent been able to run DB for more than 3-4 hours max nowadays. The DB version that I was using 2 months ago though, I could run it overnight and everything. Its like it gets more unstable with each new version..
 
Status
Not open for further replies.
Back
Top