Close
Page 5 of 7 FirstFirst ... 3 4 5 6 7 LastLast
Showing results 41 to 50 of 74

Hybrid View

  1. #1

    Default

    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...
    Team 1: 7x60p80 Clerics + 3x60p60 Mages (Legio IX)
    Team 2: 5x60 Clerics + 5x60 Rogues
    Team 3: 10x60 Warriors

  2. #2
    Member Norrin's Avatar
    Join Date
    Dec 2008
    Location
    In the middle of nowhere
    Posts
    207

    Default

    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.

  3. #3

    Default

    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.
    Team 1: 7x60p80 Clerics + 3x60p60 Mages (Legio IX)
    Team 2: 5x60 Clerics + 5x60 Rogues
    Team 3: 10x60 Warriors

  4. #4
    Member Ughmahedhurtz's Avatar
    Join Date
    Jul 2007
    Location
    North of The Wall, South of The Line
    Posts
    7169

    Default

    Same crash with rifterrorhandler.exe closed. Ran 16.5 minutes from the time I clicked Play before they started crashing.
    Now playing: WoW (Garona)

  5. #5
    Member Norrin's Avatar
    Join Date
    Dec 2008
    Location
    In the middle of nowhere
    Posts
    207

    Default

    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.

  6. #6

    Default

    Hmm, are you guys using any addons?
    Team 1: 7x60p80 Clerics + 3x60p60 Mages (Legio IX)
    Team 2: 5x60 Clerics + 5x60 Rogues
    Team 3: 10x60 Warriors

  7. #7
    Member Norrin's Avatar
    Join Date
    Dec 2008
    Location
    In the middle of nowhere
    Posts
    207

    Default

    No addon's at all here.

  8. #8
    Member Ughmahedhurtz's Avatar
    Join Date
    Jul 2007
    Location
    North of The Wall, South of The Line
    Posts
    7169

    Default

    Same here, just the base game.
    Now playing: WoW (Garona)

  9. #9

    Default

    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.

  10. #10

    Default

    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.

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •