Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
When this occurs have you tried disconnecting/reconnecting the cable to the affected monitor? I'm guessing it may have to do with the length of the cable vs noise. You may also check to see if the affected monitor has a different type/length of power cable. When it comes to length, the thicker the wire gauge the better.
Not sure of a real solution except consider shorter cables/thicker gauge cables or see if there are powered "amplifiers" available. Odd situation.
Yes I suspect noise as well, as I mentioned before. But all cables are identical and are high quality cables, and there is no noise during live operation of the panel, so it seems a bit odd that a wake up signal would be the only thing affected.
Huh? I said I didn't think it was a noise issue. Re-read.... I think the affected monitor is receiving less than ideal power or is more sensitive to the cable length. Or the graphics card is sensitive/affected by the cable length.
A potential "workaround" is to unplug then plug that monitors cable when the problem occurs to force everything to wake up.
Here's something I found that might be related - if you google "displayport pin 20 problem" there are several forum discussions about similar problems caused by bad Displayport cables. Apparently some cables wrongly connect a power pin between the monitor and video card which can interfere with power-on/sleep modes.
I have no such power on issues with dual FirePro 2450's. If you arent already, I would consider running windows drivers instead of AMD's drivers. Usually when I have issues with these cards (be it AMD or Nvidia) its running the OEM drivers instead of the Microsoft drivers. I called up AMD to ask, and they also recommended I run the windows driver unless I need the added utility of their Catalyst Control Center, which I do not. The 2460's you had have more RAM per card than the W600 does by itself... and combined its 4x as much. I'd probably prefer to run the dual 2640's, but YMMV. Is your artifacting when you move something from one screen to another and you are moving that windows 'above' a bunch of already open windows (such as ladders or charts)? If so, I get that too, but it goes away as soon as I click on the window that has the 'artifact' in it.
Also, one more note: Being that the W600 is a 6 monitor card, I severely doubt it is untested in a 6 monitor config, as that is what its designed for. I am with you when it comes to running the 4 monitor cards in dual config to run 6 or 8 monitors, its very hard to find info on that and the manufacturers dont have much feedback... but that W600 is a 6 monitor card from the get go, it must be fairly well tested before its released.
Certainly an interesting post above this one. Id buy new cables and delete and reinstall the windows drivers. Hopefully it solves the problems.