The Drivers were fine as well as the MOBO and I was very frustrated and was about to buy a much more expensive card, I had unplugged them and re-plugged them as Arnie recommended
Until I tried one more time to uninstall and re install and everything works perfectly now, I have the number of monitors I need and all is well, so I just wanted to say thank you to the futures.io (formerly BMT) forum, Arnie, and Mike.
Last edited by bathrobe; June 2nd, 2013 at 02:21 PM.
Reason: left out a word
I can't remember what thread I last posted in. Apparently not this one.
But point is, a few weeks ago I replaced my (2) FirePro 2460's with (1) FirePro W600. I have six 24" monitors. I replaced the cards because I was experiencing some random issues with the FirePro 2460's, like random times monitors won't come back on after energy savings poweroff mode, or random screen artifacts.
Well, unfortunately the W600 exhibits identical issues.
It's my belief that the random screen artifacts are caused by poor drivers. It's essentially the same driver between the 2460 and W600, and testing in a 3x3 (6 monitor) config is probably very rarely done with no real quality assurance. In other words, since practically no one runs this config, they've not seen the issue and haven't had a chance to fix it. Bottom line: live with it.
As for the random times a monitor won't awake after being in sleep mode, well that's the most annoying. My PC never enters sleep mode but I do have W7 setup to power down the monitors after 30 minutes. Even with these six Dell U2412M LED's, relatively low power as they are, they put off a lot of heat -- so it's more about keeping my office cool than it is about electricity savings. The real kicker is that when one of them fails to wake up, it royally screws all my window locations for all open apps because Windows has to reconfigure itself to be minus 1 monitor. I scream every time this happens.
I am leaning towards this NOT being a driver issue, my best guess is it is a cable issue. I am pushing the limits on cabling, using 15 foot cables for all six monitors, and they are all crammed on top of each other along with some other noisy cables like USB and speaker cables, and go through a cut out in my wall to the extra bedroom adjacent to my office where I have my computer hardware in a closet. In other words, I think it might be a noise issue, with the "wake up" command simply not making it to the monitor. Odd enough, it seems to always happen to the same monitor, but if I move the cable around, it doesn't follow the cable -- but the monitor... is just a bit weird.
Anyway, this is what the kids would call "first world problems", in other words, just get over it.
I'll be listing my two FirePro 2460's on ebay soon probably.
Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
The following user says Thank You to Big Mike for this post:
Maybe a faulty monitor? What happens if you just run with 3 (also eliminate each card,) 4 or 5 for a while?
I have also had this sleep fail to wake up issue in the past, in one case it was an old cable (missing connected pins) and in the other a hard to see bent pin, but sounds more like a faulty monitor although your cable length is certainly extreme.
(Fyi I run an ATI FireMV 2250 just under the standard W7 Microsoft WDDM driver, mixed with an NVIDIA GeForce GT 420, never a glitch.)