Close
Page 2 of 2 FirstFirst 1 2
Showing results 11 to 15 of 15
  1. #11

    Default

    Quote Originally Posted by Sildenafil View Post
    Hey all,

    I put together my new PC and set up WoW x 5 with isboxer. Having an odd issue when I swap windows:

    Using GTX 580, SSD, 12Gb ram (6 x 2 gb), ASUS x58 sabertooth

    2 x monitors (not identical screen size)

    When I've got all 5 toons loaded up, main on the big monitor, 4 slaves on the smaller one, usually when I switch windows, it swaps without issue, no problem. However, it's having issues where all of a sudden I will switch, and the window I switch to will start flickering with multi-colors around the edges. I can still see the game and it functions, just with flickering. The flickering will either resolve itself or go away after I repeatedly swap a few times.

    2nd swapping issue I noticed is, I swapped windows, and instead of flickering, I get a black window, then when I try to swap back, the original window goes black.. then WoW crashes on those accounts and I get the "cannot read...." wow system crash error.

    Anybody had this sort of problem and know where I should start troubleshooting? My first thought is RAM issue since the WoW crash pop-up refers to a reading problem, but I didn't write down the message. I'll write it down next time it happens.

    *edit* I found a similar thread below with a similar issue but no definitive answer. Anybody figure this out yet?
    I could have missed it but what Operating system are you using and what directory is your wow folder in

    I ask becuase if its (Vista/win 7) and its using the apps folder to run the game you could have read permissions and not have write permisions that will cuase WoW to crash

    Easy fix usaly to that is move wow outside of your Program Files Directory.

  2. #12

    Default

    Quote Originally Posted by Aragent View Post
    I could have missed it but what Operating system are you using and what directory is your wow folder in

    I ask becuase if its (Vista/win 7) and its using the apps folder to run the game you could have read permissions and not have write permisions that will cuase WoW to crash

    Easy fix usaly to that is move wow outside of your Program Files Directory.

    Running Win 7 home premium 64bit

    That's interesting. It's in whatever it defaulted to when I installed it. I'll check what that actually turned out to be. I wonder, though - if that were the issue, shouldn't it affect me when I'm running a single copy of the game? I can run a single instance w/ 0 problems. It's just when I run 5, and even then it only starts happening after I've swapped b/t windows a few times.

  3. #13

    Default

    fyi:

    my Nvidia driver version 266.58 (win 7 home premium x64)
    850w Enermax Galaxy PSU
    my wow is run from direct from E:\ (the only thing on a 64GB SSD)

    As I said before I only had the issue when all windows where running at ultra settings, now they are running on high (with low shadows) i have no issues. (spent a good 7-8 hours playing over the weekend, with multiple window swaps)

  4. #14

    Default

    i would like to add that WoW becomes a CPU limited game faster then others.

    Your graphics card should easily be able to run 5 clients.

    What I would advise is to tone down the AA settings to 1x. Minimal impact on what it looks like, but big impact on performance. What I do myself is that all slaves are set to a very low graphics setting as I almost never use them on the main window anyway. My Master has settings to Ultra ;p

    The artifacts you describe are usually a result of a faulty card (overheating or not) or driver. It has nothing to do with ISboxer itself.

    Turning down the settings on your slaves might stress the card less which could result in a prevention of these artifacts... tho I suspect they will come anyway ;p
    EU-boxer on Executus.

  5. #15

    Default

    I found an obscure post on the net about out-of-date integrated audio and NIC drivers interfering with video drivers. I updated the driver on my integrated NIC and it seems to have fixed the problem (at least for now. still a lot of testing to do)

    weird how these components are interrelated..

Posting Rules

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