Intel HD 4000 No Display after loading Windows 7

[idata]

I have a new build. Its a 3770k with an Asrock Fatal1ty Professional and 16Gb of Mushkin memory.

The computer has been working great all week. Then all of a sudden today after switching my display via a button on the front from VGA to DVI between my old rig and my new rig the screen no longer displays on my new rig. I also have 2 keyboards on my desk and may have hit a hot key and changed something, I'm not sure.

I have tried Windows Key + P to change to projection mode and get nothing.

After rebooting the screen works until after the windows 7 loading icon disapears then the screen goes into power save mode.

When booting into safemode the screen works fine.

When changing the resolution and then booting back out of safemode the screen does not load.

When deleting the Intel HD 4000 driver and restarting then the screen will load.

After reinstalling the Intel HD 4000 Driver the screen nolonger loads.

I don't know why its doing this but I am no longer able to use the HD 4000 with my intel driver installed. Which renders onboard video pretty much useless for anything but basic functions.

I have tried deleting and reinstalling the driver and also the monitor and its driver as well.

Nothing seems to work.

Is there some kind of keyboard shortcut to change display ports? I'm currently on HDMI and my board has both HDMI and displayport. I have no way to test if its working with the display port. Also I am using an HDMI to DVI cable already.

This is just really odd seeing how everything was working preffectly fine then all of a sudden, nothing just blank.

I can hear the computer load, even the sound. I can even type and login, but I'm unable to see anything.

Also I have tried to set onboard video as default in my bios and still nothing will load as long as the Intel HD4000 driver is installed.

I have tried two different drivers versions, they both do the same thing.

Any suggestions would be greatfull thanks.

[idata]

Hmm... I got another idea from the last few posts. This may be a power issue. It seems as soon as Aero (Direct3D) kicks in, the signal drops to a level the monitor does not pick up any longer. The processor is drawing too much power, => video out is getting too little power for a good strong signal, it gets distorted or the voltage drops and the monitor says "not good enough" and goes black.

I have a pretty capable PSU though (Seasonic X-760) and I did insert the separate 12V processor lead (EATX 12V). My system is still working by the way after several reboots. I fixed it by unplugging the video cable on the first reboot after installing the drivers.

If it is lack of power (being provided externally or transferred internally in the processor), unplugging the cable may just pull a little less power from the video output or keep some circuits disabled altogether, leaving more to the video logic at a time when it matters, when the driver is doing diagnostics to configure itself.

If it is power related and it is not due to the lack of externally provided power, this would be bad news.

[RPapa1]

More info here...

board: Intel DH77EB, BIOS updated to latest

CPU: Core-i5 3570

RAM: Corsair DDR3-1600 2x4G

BootHD: Crucial SSD

OS: Win7 Pro x64

Same exact issue with me - install latest driver, restart, 'No Signal' on display.

This mainboard has DVI, HDMI and DP. - NO VGA!!

I'm using DVI with an older CMV 19" flat LCD, works fine and has been working fine for many, many years

System is not crashing since pressing the power button once initiates and completes a shutdown.

Safe Mode gives display in VGA mode

So I create a LogMeIn connection, then install the latest driver, restart - no display. Fine

Using LogMeIn I can logon just fine. What makes LMI different than RDP is that I don't get a custom display but I actually see exactly what is going on at the other end.

So, come to find that the Intel HD4000 has not even identified my DVI connected monitor and is trying to run with VGA. Well, that's certainly not going to work. Here's a screen shot:

So, it seems that once installed, the HD4000 is not seeing something or other correctly. It's not board, power or RAM specific I don't believe. I tried the 'one stick of RAM' thing - no difference. Seems more like it's trying to read what's connected and adjust itself accordingly, inproperly so. Maybe the problem is how Windows is conveying data - heck, I don't know.

Thanks and Good Luck to us all! And Thanks to Intel as well. Love the new Visual BIOS! Although, it's about time...

R

[idata]

Hi again,

I'm pleased to report that Nav/Robert's suggestion of a BIOS update did the trick. Hopefully this will work for others as well. My sanity is intact! Thanks all.

Cheers,

Rog

[idata]

Wow, 5 months, 9 pages, and the big powerful intel still can't fix it? 😕

I recently bought an Asus ZenBook Prime UX31A, with the HD4000 graphics, and today i just realized that.. like everyone else, hdmi is good for nothing thanks to the drivers or whatever.

You can't recreate this problem? ask Asus to send you one of the zenbooks, no one that i know managed to get the hdmi working. i tried everything here, your latest drivers (no go), older drivers (no go), no matter what, the computer won't recognize that there is another display connected. BUT bios and up to windows welcome screen, works like a charm.

Robert - i'l give you all the information you need, everything that can help you, just name it and i will check it for you.

I'm using an Micro HDMI to HDMI cable, no adapters, i tried 4 different TVs (3 samsungs 1 toshiba). only progress i get is when i disable/enable or reinstall the intel hd drivers - it suddenly recognizes something.. but for the life of me i can't get it to send video to the tv. no matter what setting i play with change or whatever, nothing works. and then, when i disconnect the cable - it will not find any more screens again, till next time i reinstall.

Edit - 29/9/2012

Also, i did update the bios of my ultrabook to the latest version - 212, didn't help 😕

[idata]

I have a similar problem with Intel HD Graphics 2000. Both the dvi and vga outputs work with the default windows driver and in safe mode, but after installing the Intel drivers and while windows start loading the monitor goes black and the message no signal appears. I can enter the bios setup before the problem occurs. None of the the suggestions in this post helped.

Motherboard: MSI H77MA-G43

Processor: Intel Core i3-2120

Monitor: Samsung SyncMaster XL2370XL

[ROBERT_U_Intel]

FYI, updated test driver version.

For the 32 bit version test driver - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21839 http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21839

For the 64 bit version test driver - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21840 http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21840

[idata]

Hi Robert

I tried the 64bit driver but same problem - no change sorry!

Thanks for all the work though - keep it going!

Regards

[idata]

Robert,

the 64bit driver works for me for HDMI output only. (DVI is not working)

I do have the same blackscreen problem when using a graphics card (ATI HD7850). Both DVI and HDMI on the card have the same black screen once I install drivers for it. Can it be in any way related?

(motherboard MSI Z77A-G43 with latest bios)

[idata]

64bit drivers dont work, same issue.

[idata]

Ok, so i have SOME progress. when i removed intel's drivers and booted with hdmi connected, (which btw made my screen go all blurry and disrupted that i had to hard reset my zenbook) i got the display to show on the tv through the hdmi cable, but only on the tv, couldn't make it switch or clone or whatever, and it worked only with restart, if i were to connect it after windows was running, nothing happens.

Now i also downloaded older drivers from asus website for the intel hd version V8.15.10.2696.02, didn't help. it worked only with a number 5 tv, which was an Haier brand, and only when the cable was plugged in, i disable the driver, and then enable it again, and right when i enabled it, everything worked so smooth that i wanted to cry. but then i did the stupid thing of closing the zenbook's lid. then i cried because nothing worked again

Right now i'm writing from the desktop, and waiting for the factory restore of my zenbook, i want to test the drivers and the state it was shipped to me with, before all the updates i did. i wonder if it was ever going to work. will update with my findings.

***********************************

Edit:

Well, that sucks. looks like it was never ment to work like plug and play thing. after factory install, still doesn't work without the disable/enable trick, and this thing only works on my Haier tv, with the samsung i can see something only if i like brute force it. i think i should explain that - the samsung i have doesn't let you "browse sources" unless it detects some kind of input from them. so what i did was connecting something that works into an hdmi input, setting the tv to that hdmi source, and disconnecting it, and connecting the zenbook to the same input without switching the channel. it gives picture, but the TV giving a floating error of "check source cable", even though there is picture behind it. and when i try to switch source, it will not go back to that hdmi input. so partly TV's fault, but mostly drivers. if they were working from the start, none of this would have happen.

[ROBERT_U_Intel]

Hi Mish

Thanks for the detailed write up. I acquired a ASUS UX31A and with the default ASUS build I was able to connect via HDMI to a Samsung PN64D660 plasma TV and a Sharp LC70LE LCD TV,, and both worked fine. I ran as Dual Display Clone, and Extended Desktop. I then updated the driver to the 2857 version (latest) and both TV's worked perfectly. Ohe thing I did see is that if I wiggled the mini HDMI to HDMI cable adapter right where it plugs into the UX31A the connection to the TV is lost. However, I can continue to wiggle the cable and get the TV connection back. This may be isolated to the mini HDMI to HDMI adapter I have though.

I understand your frustration with this issue and I have the same frustration trying to replicate the issue. I have tried to replicate the issue on over 20 systems and have not seen it however, the investigation goes on.

One thing to note is some of the folks here that have reported the issue have seen it resolved with various remedies. The issue is very system specific which makes it very difficult to debug and fix. I will continue to work on the issue.

[idata]

Oh... you're wiggling connectors now? I appreciate your efforts but I was hoping you would be passed that by now and called in an electrical engineer to do some measurements at the video outputs to see if anything is out of spec or can be pulled out of spec using different scenarios. Like hi/lo impedance monitor stubs and different processor loads (CPU/GPU activity). Trying 70 different televisions is nice but it won't tell you diddly-squat once you can reproduce the problem. Seeing the difference in output behavior between HD3000 and HD4000 would tell you a lot though, considering HD3000 does not suffer from the issue. You could either rule out the power issue if there is no significant drop/distortion compared to HD3000 or you could kick HD4000 straight back to the HD4000 design team and have them address the issue.

Another possibly interesting thing to find out would be the source of the problem processors. It may be a limited number of batches yielding the processors suffering from this issue. But then again it may be hard to find people willing of disassemble their machines and provide the processor's serial number.

Anyway, good luck.

[idata]

I've been silent for a bit now - mostly because my issues was resolved (with an ADAPTER by the way), but also I wanted to see the progress that has been made.

First of all, I want to THANK Robert. He has been working on this problem quite steadily since before my first post in this thread. I really, honestly dont think that we would be getting the same response, or the same level of response from - say ATI. However, if you feel wronged by any company - Intel or otherwise - your best means of recourse to to vote with your wallet. Grip, bitch, moan, complain all you want - but that wont get your problem resolved. I currently work in Customer Service and I can tell you Robert is doing it right. If you have an issue - address it here - like the civilized people we all are. Flaming the guy trying to help you is like pissing off the waitress at Denny's - you might feel better but you better like spit on that burger.

I admit I was quite unhappy at first. My first post reflected that. I, however, was WRONG and addmitted it. Not only did I admit I was wrong, I left my original post in place with an edit pointing to my retraction so that others could see an unhappy customer successfully turned to a happy customer.

Robert did ask for, and I was going to supply my entire system to him before I identified the adapter as the issue. Yes, most people cant do that, but I could and I was willing to take one for the team - so to speak - to get the issue resolved, or at least narrowed down.

Anybody else wanna step up and take one for the team?

With regards to the 'level' of support - Robert is the PSE for Customer Support - that E stands for Engineer.

I will now step off my soap box. If anyone is interested in further reading regarding forum posts, check http://www.webopedia.com/DidYouKnow/Internet/2008/forum_etiquette.asp this out!

[idata]

Huge +1 to mr.d.

I am also not happy with the problem, and the solution i have for it right now is not the best and rather annoying, but i really don't understand flaming Robert for it. He's doing his job, and even though he can't reproduce the problem for a long time, he still believes it's real and trying to help us.

I am also in touch with Robert in private for this issue, and i am willing to give up my system to debug as long as it can be done @ intel in my country. I hope it will be possible and will help the driver team figure out this issue.

I never angry the person who tries to help me, it's not right and not fair. Again guys, he's doing his job!

[idata]

hi

i'm having the same issue when i'm connecting my zenbook to a monitor (tried LG LED and Samsung LED).

when i opened a call @ asus support for my UX31A for this issue, i got this answer:

"Dear Valued Customer,

You may need to use the asus Micro HDMI to HDMI Cable.

http://www.asus.com/Peripherals_Accessories/Cable/Micro_HDMI_to_HDMI_Cable/ http://www.asus.com/Peripherals_Accessories/Cable/Micro_HDMI_to_HDMI_Cable/

Best Regards,

Eleven

ASUS Customer Service"

ASUS using Apple attitude?

[idata]

hi to all,

i have been on this thread since ever, as i'm another lucky user that have same iusse!

i'm finally found the problem: i have win7 32 bit with paePatch to support 36bit memory index for more than 4GB of ram.

this was the problem with intel driver!

back to standard win32 4gb ram the drivers was ok.

moving now to win64 and driver is ok!

bye to all!

[idata]

I have an Asus Zenbook Ux31A (Intel 4000 HD) and I'm having a similar issue. Asus tech support is also completely useless, so don't even bother with them.

So this is my issue. The Micro HDMI to HDMI connection doesn't work with my Asus external monitor, but the VGA connection works fine. However, when I update the driver, my computer finally detects the HDMI connection and the external monitor. If I restart the computer (which you are actually supossed to do after the update), or even Hibernate, it no longer detects the monitor and I have to reinstall the driver. This doesn't make any sense because the driver is still installed. However, it does confirm that my cable works, the hardware works, and in theory, the computer and the monitor can communicate with one another.

The other unique part about it is typically, I can toggle between LCD, CRT, and CRT + LCD. However, after installing the driver I get 3 new options (HDMI, LCD + HDMI, CRT + HDMI). When I pick HDMI, everything works fine. When then check my Graphics settings, it finally recognizes that I have an external monitor, though it seems to think its a Television instead of a monitor, so that might be part of the issue. Regardless, if I restart my computer, it seems to forget everything and I have to once again reinstall the driver. I hope this is enough information to go on. I included a screenshot below of A) What the HDMI toggle option looks like and B) what my graphics settings look like when its functioning properly.

[idata]

Ashrit Kamireddi- same thing with my zenbook. as i stated before, there is an easier way to make the hdmi work. go to the device manager and disable the hd4000, then enable it, it will start working untill the next sleep/reboot 😕

it's messed up but, at least we can make it work a little bit.

[idata]

Hi Mish and Ashrit Kamireddi, I have exactly the same product (Asus UX31A) and the same issue (late vession 8.15.10.2761) and I will probably make a short-cut doing what you say. But I'm very disappointed about the support of this driver : a large number of complains are around the Internet about the same issue and none of Asus nor Intel are talking about it. The last update of the driver is 5 months old... Hopping they will finally come back to work after this loooong holiday!

[MSchm21]

This is only half of the truth. I agree regarding the last official Windows 7 driver release, having there an over 4 months old driver on downloadcenter looks ridiculous poor considering they released a brand new dx11 HD generation just 5 months ago. The other truth is that the newer 15.28 2792 driver for Win 8 works inofficially for Win 7 as well and since then several newer test drivers were posted to possibly address various issues. The last was posted last week in this thread. Also Intel/Robert_U replied more than once in this thread. To say none is talking about or enjoying a 5 months holiday is impolite, incorrect and not worth any more support from Intels side for you because obviously you didn't even bother to read the last 2 pages.

[idata]

Wow, I didn't mean to offended anyone, and I hope so that they don't take 5 months breaks (joke inside), but if it looks like... However, none of the previous "wizard's tricks" worked for me except to disable the driver and to re-able it (or to reinstall it). I wish more "luck" (what a strange word for computing...) for all others who will try to use the Windows 8 drivers.