Widescreen Gaming Forum

Hi

When i set my displays as told in the title the computer freezes strangely:

- mouse still in movement,
- keyboard stil under tension because hitting several times the "capslock" key, the respective led reacts normally,

The only thing i can do at this point is RESET the machine since i can't do anything anymore, no task manager, no start menu to restart the machine correctly.

Informations about my hard and softwares, displays:

software
- Win8.1 activated and uptodate,
- Chipset, audio, lan, USB3, sata controller are installed from asustek and they are specific to this OS

hardware
- CoolerMaster 1200w silentpro gold
- RIVE x79 chipset BIOS 4403
- Ivybridge-e i7 4960x
- 16Go (4x4) TridentX 1666 @ 10-12-12-31-2T
- Titan sli, drivers geforce 331.58whql
- SSD samsung 840 pro 256Gb firmaware uptodate
- keybord logitech g510
- mouse Roccat kova+

displays
- surround: 2x Iiyama prolite X2485ws + 1x syncmaster 245b (all 24" 16/10 1920-1200 -> 5760-1200)
- 4th dispaly: syncmaster 226sw (22" 16/9 1680-1050)

Rqs:

- fresh install on a brand new SSD, no upgrade from any other OS.
- i had no issue at all on Win7 64
- i like this news OS since i have nothing against the changes it brings so i would like to keep it but i cant have my 4th display at the moment
- my device manager shows that nothing is missing.

Maybe is W8.1 too young yet ?

Thanks reading my post

Hi!

I'm actually running 3+1 screens on win 8.1 (was running it on preview and now on retail) and it's working just fine, but then again I've got AMD cards running so might be driver related I guess?
Are there any older gpu drivers you could try?

_________________
| i7 3770k @ 4.4, 16GB | 2x Sapphire 7970 GHz @ 1150 | Carbide 540 w H100 & HX850W | 3x Dell U2312HM @ 5760x1080 |

Allow me to chime in here with many reports of this... Here are the relevant threads I have located:

Reported in EVGA forums:
http://forums.evga.com/tm.aspx?m=2041571

Reported in Geforce Forums:
https://forums.geforce.com/default/topi ... und-is-on/

Reported again in Geforce Forums:
https://forums.geforce.com/default/topi ... ows-8-1/2/

Reported on Technet:
http://social.technet.microsoft.com/For ... rohardware

Manuel G a rep from Nvidia stated:

"Thank you. We are looking into this."

and

"We will be launching a new driver very soon and so its not going to be part of that release but hopefully we can fix it in time for the follow up driver which will be released shortly after."

So the last few released drivers did not have a fix, so theoretically the next one may. The solution for now, disconnect/disable your accessory display. Stay out of Metro UI apps after you do. Or go back to Windows 8.

Still not fixed in 331.82 WHQL drivers

_________________
Cooler Master Cosmos II | ASUS X99-Deluxe | Thermaltake Water 3.0 Extreme S | 5930k @ 4.5GHz | 32GB G.Skill Ripjaws V 3200MHz | SLI GTX 1080 Ti's | Samsung 960 Pro NVMe M.2 SSD | Corsair AX1500i | 3DMark Fire Strike Ultra - 13,780 | Windows 10 Pro 64-bit | Nvidia Surround® 3 x BenQ XL2735 | Samsung CHG90 Auxiliary Monitor

@ FrostByghte: Thx for the links man, appreciated

@ GitDat: No, neither in the latests 331.87quadros...

'Wil give a go in the latests beta's 331.93

ManuelG or one of the nvidia guys could see this and say something about it,

Cheers

Edit: ortho'

Issue still there with 331.93.

I'm using my Surface Pro 2 for the Battlescreen on the auxiliary monitor via KVM switch in the meantime

_________________
Cooler Master Cosmos II | ASUS X99-Deluxe | Thermaltake Water 3.0 Extreme S | 5930k @ 4.5GHz | 32GB G.Skill Ripjaws V 3200MHz | SLI GTX 1080 Ti's | Samsung 960 Pro NVMe M.2 SSD | Corsair AX1500i | 3DMark Fire Strike Ultra - 13,780 | Windows 10 Pro 64-bit | Nvidia Surround® 3 x BenQ XL2735 | Samsung CHG90 Auxiliary Monitor

Yep, still not fixed.

Seriously considering going back to Win7 because of this lack of efficiency from who ? i don't know...

This would be a Nvidia issue, those of us with Eyefinity setups don't have any problem with this configuration at all on windows 8.1.

I thought I would update this thread...2 weeks ago Manual G posted on the EVGA forums:

"We just fixed and verified the fix for this bug. The fix will appear in our next driver release."

http://forums.evga.com/FindPost/2078006

So hopefully after uh...however many months this will be fixed with any driver update after 331.93...HOPEFULLY