BuddyWing Crashed OverNight - Log > 500mbs

[15outland]

Hi,

I decided to leave BW go over night, as it didn't really have any issues during the day, checked it 5am this morning, to find both SWTOR and BW 'Not Responding' and went to check the logs, only it's 500mbs, and to large to want to open.

And it must've been not long after I went to bed, as it didn't progress very much as all, experience wise.

I've never had this, and now I can't tell why it happen, anyone else had this happen to them, or any staff know a fix for what ever it may be?

All these problems are p*ssing me off.

(And what is with the damn site being Down nearly every time I check it)

I was using Mizzles Empire 10-50 grind pack! - Level: 20-24.

 

[15outland]

Nobody at all?

 

[Developer]

Was the client frozen, or did this cause a crash?

Either way, this happens to me sometimes after a lag spike. It can also occur when there are server problems with the game. I think it's just the result of connectivity issue. When this happens, restarting the bot is usually required; if SWToR has been running for more than a few hours, restarting the game client might be prudent as well.

 

[15outland]

Perhaps, but I never have connectivity issues with this game, ping is always around 88ms, and I even left it on last night using 24-28, woke up to find it still going, which was good, I mean, It is possible it may have had a small problem the other night, but why would that cause the logs to spam so much, and the client and bot were both frozen.

 

[CodenameG]

well we need a log. clear your log folder and see if you can replicate the issue then zip the log and upload it so we can take a look.

 

[cylak12]

This happens everynight on my newest PC, older ones are fine, it has something to do with new pc's.

if you want specs i will provide

 

[iCKR]

This happens everynight on my newest PC, older ones are fine, it has something to do with new pc's.

if you want specs i will provide

Create your own thread for your issue. Easier for us to track it and resolve the issue that way. Since your issue and his might appear to be the same but are in actual fact not.

Please include your log file when you create your own thread

How To Attach A Log