I have discussed this topic with Fred in chat already, proposing me to update the BIOS driver, which however was not successfull:
My problem is:
I have built an new PC including Intel I5 3570K processor on motherboard Asus P8Z77-M PRO. I have a monitor Iiyama Prolite E485S 19'' native resolution 1280x1024, 60 Hz connected to it. Before that monitor was connected to a PC running Win XP 32 bit on DVI-D interface no problem.
Ever since the first boot on the Win 8 PC, the DVI-D loses the signal on the DVI-D Interface right after BIOS bootscreen upon boot of the Windows OS. Before, i.e. BIOS setup, is working on DVI just fine.
The following has been tried, so far:
1. Reinstalling Intel 4000 HD driver, switching to another version Intel 4000 HD driver proposed by ASUS: After removing the Intel driver, the DVI interface works on native resolution. Upon reboot, the signal is lost again.
2. Testing Linux on the PC, installed on dual boot: DVI interface works fine!!
3. Updating the ASUS BIOS to the newest version - no effect.
4. Reinstalling the Intel chipset driver - no effect.
5. Removing the monitor from the device manager - no effect.
6. Uninstalling the Intel graphics driver 4000 HD using the Programs and features section in order to completely remove leftovers - same result as 1 above.
This issue seems similar to that relating to Windows 7:
I have read
Which suggests to override an EDID such that the information received by the system from a monitor are disregarded and override preferences are used instead. Could this solve the problem? Would this require also a DVI-D cable with removed DDC Pin 7 and/ or DDC hotplug detect pin 16?
I have registered my E-mail and got a case number from Fred. Unfortunately I did neither receive the chat transcript, nor an E-mail regarding that case, Could I get that information forwarde via PM?
I apologize for you not neither receiving the chat transcript, nor an E-mail regarding that case.
Our software support and engineering group is working on having the DVI-D loses the signal issue fixed on the next driver version. We cannot provide an estimated time for this to happen, but your feedback for sure is important and will be forwarded to higher levels of support.
Looking forward to assisting you further