Nic - Before I answer your questions, could you first answer one : Are you using a Single-Link or Dual-Link DVI cable in your test system? Given some people have reported success with changing cables, I'm wondering if the issue is that Intel's driver is trying to send data over the missing dual-link pins and use Dual-Link mode permanently (even at 1920x1080 and lower resolutions where it's completely unnecessary to use dual-link bandwidth), which would cause a single link cable / single-link monitors to show "no signal", whereas the "stock" Windows 7 "VESA" driver (or whatever they call it these days) just uses Single Link and works all the time?
If you're currently using a dual link DVI cable on your test system, could you please retest your system using a single link DVI cable just to rule that out? This would certainly explain why some DVI (and HDMI) cables work but other DVI don't.
For other posters who don't understand, here's what the difference looks like. You might want to add the question : "If DVI, are you using a single link or dual link cable" to your questionnaire. For posters who have already posted, please add single vs dual link cables if you're using DVI.
Anyway, here's my experience:-
Are you willing to send your system to us? : No. I live in Europe and it would cost too much / take too long.
Is your system a laptop or desktop? : Desktop.
If desktop, is it custom built, or manufactured? : Custom built.
If desktop, what is the make/model of your motherboard? : ASUS - P8Z77-M (NB: It was my motherboard but it got sent back for another reason, and I've decided to wait for Haswell in June).
What is the make/model of your system? (COMPLETE model name required) : NA
What is the model of your CPU? : i5-3570k
What is the make/model of your failing display(s)? LG-W2442PA
If laptop, is your built-in display failing? (Yes/No) : NA
What is your operating system? : Windows 7
Is it a 64-bit or 32-bit operating system? : 32-bit
What display driver version do you have installed? : Intel Graphics Accelerator Driver V8.15.10.2712 for Windows 7 32bit & 64bit.(WHQL) downloaded from Asus site. I also tried the newest one from Intel directly. Both the same problem.
What type of connection are you using? (HDMI, VGA, DP, DVI?) : DVI - single link cable.
What happens that results in the blackscreen failure? : Here goes:-
- I bought an Asus P8Z77-M motherboard & i5-3570k CPU and installed it with a discrete AMD 7790 HD graphics card with the monitor hooked up to the discrete card then installed AMD's drivers. Result : Works perfectly.
- Then I enabled dual-monitor & Virtu-MVP support in the BIOS (with the intention of using it in "D-Mode" (GFX card is primary output but Virtu-MVP enables Intel output for QuickSync encoding). Result : Also works perfectly (where Windows 7 uses its own standard "VESA" type driver).
- Then I installed Intel's drivers. Monitor goes dead. Not just on the Intel DVI output - but even on the AMD discrete card DVI output!
- I completely uninstall both AMD's & Intel's drivers, and completely remove the discrete GFX card and connect the monitor to motherboard DVI output. Result : Works perfectly (again, only where Windows 7 uses its own standard "VESA" type driver).
- I then install Intel's driver. Result : Monitor goes dead.
If it works on some cables but not others I can only assume it's a single vs dual link DVI thing or timing issue, and that Intel's driver is forcing the DVI output to use dual-link mode constantly whereas Windows 7 driver uses Single-Link constantly. Likewise, it cannot be a "signal too weak" hardware issue with cable or GFX output, because the monitor & cable works flawlessly with stock Windows 7 drivers at same 1920x1080x60Hz and with a multitude of different AMD / NVidia cards and other monitors / TV's.
The key "black screen" issue appears to be either:-
1. Intel's driver is trying to force all output to dual-link which would fail on single-link cables and single-link only compatible monitors.
2. Intel's driver is screwing up / misreading Windows DDC timings and not "seeing" the monitor because of that.
Hope this helps, Nic.