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

Huge amount of crashes. Hardware problem?

pimpampum

Member
Joined
Nov 29, 2012
Messages
769
Reaction score
23
Lately I've been having lots of crashes, both db and yar and d3. I even got a couple of blue screens -->Bad pool caller and device driver trying to corrupt system.
I checked all drivers and they seem to be up to date, and I made a fresh install of everything d3 related (this is mostly a botting computer). Yet, I still have crashes, and I think they are probably related to some bad connection or hardware problem, not db related.
Anyway, here you have some logs from today when all of a sudden all bots went down at the same time, and maybe you'll be able to confirm my guess, since I'm not really a computer expert.
Thank you for your help!

PD: At the end of every log is the error that could be of use, no need of reading it entirely.
 

Attachments

use the latest beta build and try using only the essential plugins
 
use the latest beta build and try using only the essential plugins

If you don't mind I'll try that tomorrow, would like to keep my little army of bots working overnight. Thanks for the fast response Tony!
 
Spent the whole day repairing windows , installing 6666 drivers and checking everything hardware and software related is fine and running.

I'll run the bot army tonight with Db beta, trinity.10 and yar only, and report tomorrow if any problem show up.
 
Ok so far blue screens are gone ( fingers crossed) but still having DB crashes. Not so often though.

Db Beta, Trinity .10 (will update to .11 in a few minutes), and YAR. Trinity TPS is on 30...not sure if it is relevant or not.

Tony, before you tell me to run it with db and trinity only, please understand that having more than 5-6 bots and not using a relogger is simply not efficient at all. YAR, or a relogger is essential to my botting, as much as trinity is. Would take any advice if developers and moderators would suggest a relogger plugin or even implement one to db itself, that would be amazing!
By the way, sinterklaas who happens to be the YAR plugin author is gone on a vacation (hoping so), given up posting here or gone Giles-like missing, so it would be a perfect time to take over relogger developing! Just saying, hehe.

Here are the logs, there are a few more but these seem to be representative of the problems.

Thank you very much tony and bambam!
 

Attachments

Last edited:
isnt there one called DBRelog? you could always try that.
 
make a try without YAR and also try a different profile
 
Back
Top