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

D3 always closes in 3-4 hours

M

markws1

Member
Joined
Dec 14, 2013
Messages
35
Reaction score
0
I don't know if this is a d3 or a db issue, but its been going on since last weekend, i start the bot and it will keep going smoothly from 1-4 hours max then the game closes, it is not like a crash where the game will be hanging just the d3 window closing instantly.

I did the following :

1- Fresh DB installation, updated Trinity and Questtools using EZupdater. (more than 3 times)
2- Reinstalling D3 .

the issue occurred 7 out of 10 times after porting to the town but iv'e seen it happening also in the Grifts after going from instance to another.

although it happened more than 20 times in the past 7 days but I'm uploading the most recent log where the game closed after entering another instance in Grift.

hopefully someone can help with this one.

thanks!
 

Attachments

11:00:25.567 INFO ZetaDia Diablo III Exited, Demonbuddy terminating in 20 seconds.

looks like game dc
 
Tony said:
11:00:25.567 INFO ZetaDia Diablo III Exited, Demonbuddy terminating in 20 seconds.

looks like game dc
Click to expand...

not really, I've seen DC's but this one was instant crash the game window closes and monitoring the game when it happened... it is instant crash where the game won't hang just crash >> close window
 
so it was a crash followed by an error pop up window?
 
you can call it crash and say 5 out of 10 had error pop ups the one in the original post had error pop up and i was around when it happened but this one in the attachment below happened while i was sleeping and there was no error pop up window when i checked it.

and just for the record this one went for a longer duration before crashing than the others because I was using rrrix blank profile for a while before i loaded the rift farming and went full afk.
 

Attachments

I apologize for the delay i went away for a job related mission and i just got back but before leaving home I started the bot.

when I checked the game window was already closed and an error window is popped up... this is the log for the most recent crash after removing teamViewer.

thanks for the great support
 

Attachments

try latest beta build plz and let me know
 
Ok, I just installed it and gonna run it all night if things went smooth, "if it passed 6 hours without closing" that will be a progress usually closes 2-4 hours

will update this post tomorrow morning.


Update 1: it kept running for around 6 hours then the game closed but I highly believe it disconnected due an internet issue than the usual crash, I will give it another run and update you if the crashing issue still there.

I attached the log just in case if you want to check it : View attachment 5648 2015-06-05 02.19.zip
 
Last edited:
it went longer than the usual 3-4 hours but eventually it crashed, kindly review the log in the attachments... thanks
 

Attachments

Tony said:
looks like a dc tho
Click to expand...

It might be, because I was AFK when it happened I can't really tell... but I came back home to another issue... I can live with a DC or crash every 5-6 hours but.... this happens after one rift run tried fresh installation of both regular and beta.. old and recent versions of trinity and questtools... couldn't figure it out and it is driving me insane....

kindly review the attachment, and I apologize if I'm not replying immediately... I'm away from home for few days...
your great support and responding time is appreciated...
 

Attachments

it started with the beta actually.... i switched to regular and it is there as well.
 
are you sure you tried latest beta build?
 
yes, I freshly downloaded and installed a DB beta and got the same error... it occurs after closing the rifts... this is the latest log....
 

Attachments

You must log in or register to reply here.
Back
Top