Running 4 clients right now with the error handler disabled. Will report back with results
Printable View
Running 4 clients right now with the error handler disabled. Will report back with results
I still crash at the 15/16 minute mark even with the Error thing disabled.
Ok, all clients still crashed with the error handler disabled :(
Perhaps try that packet sniffer tool (pcap or something) and see if the data rifterrorhandler.exe sends out is readable?Quote:
Originally Posted by Lax
Also, does anyone know if there's debug setting to run Rift in single-threaded mode? Perhaps it's using multiple threads and there is a race condition somewhere that only occurs on some machines and with the timing difference of IS running.
It could also be a memory leak (GPU or CPU) that causes the machine to run Out Of Memory and crash. Check your CPU memory usage in Task Manager. Not sure how to check GPU memory usage without a GPU tool like PerfHUD or something, and I'm not sure that's system-wide anyway...
According to the Error logs I have the error is an access violation error.
Not sure at all what or why is causing it.
I am loading up Wireshark now and see if I can get anything from the ErrorHandler.
Yeah, an access violation error means a bad pointer - it could be 0 (or a small offset from 0) which could indicate Out Of Memory. If the accessed address is a large number, it's probably not Out Of Memory.
Same crash with rifterrorhandler.exe closed. Ran 16.5 minutes from the time I clicked Play before they started crashing.
I got nothing from the Packet Sniffer, which admittedly is not my strength.
I also tried forcing the game into Dx9 mode by adding the -dx9 parameter.
Still crashes.
Hmm, are you guys using any addons?
No addon's at all here.
Same here, just the base game.
I'm running 260.99 on my NVidia and Catalyst 11.8 on my ATI. Just to reiterate, I played for almost an hour with no crashes with ISBoxer unloaded (used Octopus instead). With ISBoxer running, 4 of 5 clients crashed within 60 seconds of each other and all in 11-18 minutes.Quote:
Originally Posted by Smedbox
I'm sure it'll get figured out soon but considering how many different drivers, hardware solutions and platforms this is failing under, I seriously doubt it has anything to do with video drivers. ;)
I don't think it is hardware specific.
Last week I was happily boxing using ISBoxer on 2 subscribed and accounts 3 trial accounts, after the latest Rift patch, my 2 subscribed accounts kept crashing after 15 mins but the trial accounts were fine.
My trials ran out so I upgraded them to subscribed accounts and now all 5 accounts crash within 60 seconds of each other after about 15 mins.
So i'm confused why my trial accounts were fine until I upgraded them. I made no hardware or driver changes, I just upgraded my accounts.
I have also found out that if around 13 or 14 mins you log out to the character select screen and then log straight back in again on all of your accounts then this seems to reset some sort of timer within rift and you are fine for another 13 or 14 mins, it's a pain but it's not as bad as all of your clients crashing.
Is Octopus still available?Quote:
Originally Posted by Ughmahedhurtz
I may need to setup HKN net again as I am taking part in the extra-life.org 24 hour event this coming weekend and I need to have something in place that works.
Running one client with ISBoxer still crashes.
I tried something this morning. 1st using ISBoxer with my 2 accounts and it did crash 13-15 mins in. I then tried the 2 accounts without ISBoxer and no crash. But then again I couldn't play it in proper boxing fashion.
Hotfix #5 is to be released to NA servers at 8.00am PDT.
No Details of what's in the Hotfix yet, but fingers crossed :)
http://community.riftgame.com/en/
Inner Space build 5474 may correct this issue. I have it available as of now as a development build. To try it out, right click IS and select Patcher, check "Download development (test) patches" then close and restart Inner Space.
I ran with 5474 for a good 45 minutes this morning, and someone else in the ISBoxer chat room has been going for 30+ minutes now as well. I've moved this build live, you can patch to it just by restarting Inner Space
Yay!!!!!!!!!!!!!!!!!
You da man!Quote:
Originally Posted by Lax
Can't wait to try this out tonight.
So the obvious question would be, why did some people run fine whereas others were having the crashing issue?
:)
Yeah that has me baffled as well.
Been running the new update and been in game with my smaller team and no crash.
Been about 40 minutes now.
Been playing for a couple of hours now and no crashing.
Thanks Lax
So, what was the root cause?
I am curious to know as well.
same been on for couple hours not and all smooth and running great. thanks for the fix =)
Only played for half an hour tonight but no issues.Thanks, Lax.
Was logged in and/or played for about 4 hours last night, no issues at all.
Thanks again, Lax.
So a funny thing happened on the way to fixing this bug.
2 of my 3 accounts were suspended for 24 hours, about a week apart from each other. So like a week and a half ago I got a suspension email from Trion that I thought must have been a phishing attempt, until I tried to log in to be sure and the game wouldn't let me.
Knowing that I hadn't done anything other than fix this crash, and that the question of whether ISBoxer is allowed or not had already been answered some time ago, I started wondering if my account had been stolen, or if since their email said it was an "in-game report" that someone might have reported my 3 year old son when I let him play in the newbie area, etc. Sadly when I tried to verify what it was that got me suspended all I was able to confirm (over the course of several emails) was the timeframe (being while I fixed this crash) and that they said it was indeed my own IP address (so it wasn't stolen). Beyond that all they told me was that their logs were right and that the action would not be reversed, but they did specifically tell me that ISBoxer is fine and insisted that's not what I was suspended for. Well thanks, jerks.
This morning I checked one of my non-primary e-mail addresses and, herp derp, another suspension email from a few days ago! Same thing, second account, a week later, same incident. I haven't even logged into RIFT since the last email exchanges had left me angry, so I know damn well that it's not from anything new.
So once again I sent them an email. Here's what happened this time!
http://i.imgur.com/awx28.png
(note: that is not an "endorsement", but this just goes to show that multiboxing is acceptable behavior and ISBoxer is not prohibited)
Thanks GM Morgana! :)
Perhaps you had Visual Studio or another debugger attached and they detected that?
I was indeed debugging and I had even sent in a crash log at one point, I'm not too worried about it.
That is nice to see. I'm sure the GMs get a TON of people emailing them and saying they did nothing wrong..when in fact they were cheating or exploiting in some way. So they just treated you as one of the numbers. Your continued pursuit of an answer made them dig deeper and it all turned out good in the end. Whats best about it is now we have some clear cut documentation from a GM stating they are fine with ISBoxer AND MBing in general. NICE!