Close
Page 4 of 7 FirstFirst ... 2 3 4 5 6 ... LastLast
Showing results 31 to 40 of 74

Hybrid View

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

    Default

    Quote Originally Posted by Smedbox View Post
    Have you guys tried with the NVIDIA 275.33 driver version? It could be that other driver versions don't like the combination of recent RIFT optimizations and IS hijacking all D3D calls to display the IS overlays.
    See above with regards to NVidia vs ATI -- I have one box with each type of graphics card and are (with the exception of the disk subsystem) identical in CPU/motherboard/RAM/etc..

    Quote Originally Posted by Smedbox View Post
    Also, it could be interesting to see if you guys also have problems with FRAPS, since it does a similar D3D-hijacking as IS does?
    Hmm...an interesting thought. I don't have fraps but I may download the trial version and see what it does.
    Now playing: WoW (Garona)

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

    Default

    Quote Originally Posted by Smedbox View Post
    Have you guys tried with the NVIDIA 275.33 driver version? It could be that other driver versions don't like the combination of recent RIFT optimizations and IS hijacking all D3D calls to display the IS overlays.
    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.

    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.
    Now playing: WoW (Garona)

  3. #3

    Default

    Quote Originally Posted by Ughmahedhurtz View Post
    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.

    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.
    Is Octopus still available?

    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.
    Schadenfreude Rogue ( MM/Ranger ) / Dekoy Rogue ( MM/Ranger ) / Medyc Cleric ( Sentinel/Warden ) / Rhiggs Warrior ( Champion/Warlord ) / Murtaugh Mage ( Chloro )

  4. #4

    Default

    I'm working on tracking this down, but when I kill rifterrorhandler.exe and attach a debugger I'm not getting any crashes. And of course, the rift error handler won't share any of its information it will only send it to Trion and there doesn't seem to be a log of it.

    So... if anyone wants to try killing the rifterrorhandler.exe processes (there is one per instance of rift.exe) and see if the crashes stop for them too... report back
    Lax
    Author of ISBoxer
    Video: ISBoxer Quick Start

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

    Default

    Quote Originally Posted by Lax View Post
    I'm working on tracking this down, but when I kill rifterrorhandler.exe and attach a debugger I'm not getting any crashes. And of course, the rift error handler won't share any of its information it will only send it to Trion and there doesn't seem to be a log of it.

    So... if anyone wants to try killing the rifterrorhandler.exe processes (there is one per instance of rift.exe) and see if the crashes stop for them too... report back

    I will do that now. After my test with older ati drivers fails.

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

    Default

    Quote Originally Posted by Lax View Post
    I'm working on tracking this down, but when I kill rifterrorhandler.exe and attach a debugger I'm not getting any crashes. And of course, the rift error handler won't share any of its information it will only send it to Trion and there doesn't seem to be a log of it.

    So... if anyone wants to try killing the rifterrorhandler.exe processes (there is one per instance of rift.exe) and see if the crashes stop for them too... report back
    I'll give this a shot when I get home tonight.
    Now playing: WoW (Garona)

  7. #7

    Default

    Quote Originally Posted by Lax View Post
    I'm working on tracking this down, but when I kill rifterrorhandler.exe and attach a debugger I'm not getting any crashes. And of course, the rift error handler won't share any of its information it will only send it to Trion and there doesn't seem to be a log of it.

    So... if anyone wants to try killing the rifterrorhandler.exe processes (there is one per instance of rift.exe) and see if the crashes stop for them too... report back
    Perhaps try that packet sniffer tool (pcap or something) and see if the data rifterrorhandler.exe sends out is readable?
    Team 1: 7x60p80 Clerics + 3x60p60 Mages (Legio IX)
    Team 2: 5x60 Clerics + 5x60 Rogues
    Team 3: 10x60 Warriors

  8. #8

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

    Default

    I still crash at the 15/16 minute mark even with the Error thing disabled.

  10. #10

Posting Rules

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