I would be surprised if hardware were the issue. In fact, the mere suggestion and the lack of action makes me wonder what people are on this. It smells like an outsourced project with the driver developers being a long long way from the support staff.
Too many people are suffering from this very same issue, the hardware works (albeit in Standard VGA mode for most) and I got it working perfectly just by unplugging a cable, as some other people have. And, there is another problem: the tray app doesn't work properly. Apparently It also doesn't recognize the hardware properly, it only shows me a clipped logo and I cannot access any settings. Suggesting this might be hardware shows the undoubtedly well meaning support staff has no clue as to what is going on. I am afraid we're in for a long session here.
Allow me to speculate a little more. This driver was developed on one particular combination of hardware, not tested on any other, signed off, and the external developers were assigned to another project. Now someone else (if at all available) has to get his head around it or start over from scratch and people at Intel are contemplating whether this is worth the trouble to accommodate a limited number of users. This should be very simple and it appears to be impossible for months. The biggest problem is not with the driver, it is the operational structure within Intel on this matter.
Yes, I am getting a little annoyed. Does it show?
I also have this problem. With a ASUS P8Z77-V motherboard and an i3 3225 (HD4000 graphics) I can't seem to get my display to work when I use a VGA cable after loading the latest drivers. I can however use hdmi which seems to work fine.
A few strange things;
1) when i try to install the driver, going from the simple MS VGA adapter driver to the latest intel, if I have both my HDMI cable and VGA cable plugged in then the install crashes the computer. I have to install using only with the vga cable plugged in. After the install but before the restart I can actually plug my hdmi cable in and it will work with the display.
2) I can setup dual displays using the VGA cable in another monitor however although it is detected it will not show anything. The name of the monitor is also strange and has some musical notes at the end (in the name). Likewise if I remove my HDMI and just have the VGA plugged in to the other monitor it doesn't change to the VGA output it just stays blank.
3) If I boot without a cable at all and then plug in the VGA after windows is up it will work for a split second before the screen goes blank.
Shame on Intel for this shambles, and for not being more communicative on what owners of HD4000 chips should do, wait for an answer or just return the product. Robert_U could you log a response more frequently so that people on this thread can see that you haven't abandoned it.
We have not abandoned this issue, if fact, it is our highest priority issue right now. Unfortunately this issue is very system / HW dependent and because of this it is very, very difficult to replicate and debug. I can assure you however that we are doing all we can to investigate and resolve this issue. I will post updates as I find new information or when I have a solution. Otherwise I will be working on the issue.
In defense of Robert_U:
He has been working with me the past week (which if you look back on the posts, his last one was exactly one week ago today) on the theory that it might be CPU related. I have sent him my CPU, and he has tested it, and that was not the issue - and now he is moving on to some hardware dependent driver related issue.
So I have monopolized his time this past week with regard to this issue - blame me if you will.
Originally, I was quite unhappy with Intel and their support - but I would be hard pressed to find some other tech company that would offer to do all that Robert has done for me thus far. I could just buy an AMD and move on, or buy a dedicated GPU and move on - but I have been working with him to try to get the problem resolved.
In the process of my testing, I have identified a right angle adapter as my problem. I required this adapter to use the system in my nice case. I had a spare case that I put all of the guts into, and I no longer needed this adapter - and all worked as it should. My guess (and only a guess) is that the driver and the display together don't like it when the full HDMI signal isn't sent, and I am also guessing that the right angle adapter did not pass the HDCP info. I never would have thought that stupid little part, which just bends the connector at a right angle, could be the problem - but it was for me.
I have updated Robert_U and I am even sending him the stupid little adapter so he can test with. If any of you are using any kind of adapter, or using an older or cheap HDMI cable - consider changing it out. I cant say that it'll work for you, but that seems to have been my problem all along.
By the way, the offending adapter was bought here
Good luck y'all. Trust in Robert - he's working harder on this than others would at other big tech companies. I know - I used to work for Bell Labs.
OK, hurray for Robert. Reading mr. d's latest post I just remembered something that may be relevant. About ten years ago I had a similar issue with the same monitor (the old Samsung SyncMaster 193P). It would not display on the DVI input using an ATI card. Those were the AGP days, I searched the internet and found reports of other people dealing with the same issue. So I had a bit of a struggle with it and finally gave up and just used the RGB port which worked just fine.
Adding to that mr. d's report about garbled monitor id info with his old cable/adapter makes you wonder whether this is a poor signal issue. Either the monitor's signal is too weak (possibly out of spec) or the HD 4000 is not sensitive/tolerant enough when receiving identification signals. Or, and this is what we seem to be dealing with, a combination of both, which would indeed make it hard to replicate. In which case it could be hardware related after all. This should all show up if measurements were done at the cable level using known problematic hardware.
Glad to see someone working on it and keeping us updated.
I figure I'd register and add a little information from my side:
I encountered the same issue as many others; UEFI working fine, signal loss after Window 7 loading animation (except when booting in Safe mode). My setup is a P8Z77-V Pro with a Iiyama ProLite E2208 HDS, using a HDMI to DVI cable (the monitor does not have an HDMI port). I resolved my initial problem by replacing the cable, changing it to a DVI - DVI cable; in other words, I started using the DVI out port of my motherboard instead of the HDMI port in a situation where the signal loss issue occured.
Now I don't have issues at boot...but I do, at times, have the problem of signal loss when my system wakes from sleep. So my computer goes to sleep (after 5 minutes inactivity, set in power management options) and when I wake it up, the monitor stays in its sleep mode. When I turn the monitor off and on again, it will give the message 'no signal' and go to sleep again. Only resetting my computer will recover this at this point.
The interesting thing in this situation is that after the reboot, the widgets on my desktop are re-arranged (always at the same place, always the same widgets stacked). This makes me believe that the display output signal was indeed changed after coming out of sleep; it appears that the resolution was reset, forcing the widgets to another location.
Perhaps this helps you track this down....good luck.
I would just like to say thanks to both Robert_U and Mr.D. Seeing a community work together with a supplier to improve things is fantastic. I am holding off from buying a GPU for the time being whilst these efforts continue. Thanks for saving me some money! And keep you the good work.
We are currently focusing on a potential issue with some cables and adapters for connecting displays as a source of this issue.
Could I ask anyone who can to try a different brand / manufacturer of display cable to see if the behavior changes? Also, please be sure not to use any adapters, dongles, KVM's, or other devices between the motherboard connector and the display connector. Please test with a straight through cable, such as DP--> DP. Please report back with your results.
Here my software/hardware combination showing this bug:
OS: Windows Vista Ultimate 32bit
Mainboard: Asus P8B75-M LX
CPU: Intel Pentium G860 (graphics Intel® HD 2000)
RAM: 4GB DDR3-1333 Kingston Value
Display: Hanns-G TFT with 1440x900 (low-end thing) with the delivered VGA-VGA cable
The display with the very same cable and very same operating system worked flawlessly with two different AMD onboard graphics before.
Now I put the graphics to default VGA drivers and hope MS Update doesn't mess it up with pushing some Intel drivers before this issue is resolved.
edit: defined kind of cable
I first tried using the OEM cable - DVI to DVI which came with my monitor and has been used for several years.
I also ordered an HDMI to DVI cable from Ebay - unbranded OEM - and currently use this - both exhibit same problem.
Have you been able to try different monitors? Unfortunately I don't have access to one here - I wonder if it is a particular type of sleep mode on a sub-set of monitors which requires a particular signal to "wake up"?
Could you contact a systems integrator/builder who could test this? For instance, my system is based around a recommended PCPro (UK Magazine) motherboard (MSI Z77A-G43) and processor - i5-3570K so they must have had it working?
Please keep up your efforts - they are appreciated.
Same problem here can't boot with dual screen Windows7 64 ultimate, Asus8p77vlx,8GB in normal mode,
in safe mode ok. single monitor (either) ok.
However I noticed a behavior that might help to trace the problem:
The hdmi monitor (which is my primary monitor for W7) is responding a 1/2 second slower on the boot screen,
and the 'starting windows' screen. Exactly at the time (clocked it) the cursor should change to the animated waiting cursor, the hdmi screen goes black while the vga monitor continues with a normal cursor on a black screen, that is moveable by the mouse.
I hope my 2 cents will nudge you in the right direction to solve this issue.
NB. disabelling the onboard HD4000 and using an Old NV6800GTS PCI board in dual graphics-mode boots the system just fine.
I have a mobo gigabyte z77x-ud3h and an i5 3570k, decided to buy this like im not a gamer so i dont have to buy a GPU, what a big mistake, theres no possible way of fixing this issue, i have tried every driver compilation available and always ALWAYS everything goes south, after the windows logon screen, my monitor (Asus ve247h) goes dark, says there is no input signal and after a few seconds the PC reboots itself as it a major error ocurred which i can not see, it doesnt matter if i use vga, dvi or hdmi, if the hd 4000 drivers are installed it doesnt work, its incredible this issue has been opened for months, intel should be paying more attention to this.
Hi, i have the same problem aswell, here are my specs:
- i5 3570K using HD 4000
- 8GB RAM
- Asrock z77e iTX motherboard
- Windows XP pro x64
I was using a VGA monitor which worked fine using the drivers, but now i'm trying to use a larger monitor using a DVI-I dual link connector, the cable I'm using is a DVI-I single link cable, i get a blank screen once a boot past the XP loading screen. my trail and error points me towards the idea that with the intel driver enabled no digital signal is outputed from my motherboard, only an analogue one is.
i'm not sure if this is any help but i dual boot with Ubuntu 12.10 and the built in drivers for it work perfectly.
i have an HD 7870 in the post anyway but i thought i'd give my info,