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.

[ROBERT_U_Intel]

@dspot The issue you are seeing may different than what we are seeing with the UX31 and HDMI. Please post specifics about the system configuration, display model, driver versions, etc.

[idata]

How convenient. To pick one workaround that reportedly helped some and declare that the solution to the problem while ignoring all reports that invalidate this hypothesis to begin with.

It is obviously a borderline issue: sometimes it only just works and sometimes it doesn't. "If all others factors involved are perfect, our shortcomings would not be an issue so don't look at us".

All history considered I cannot help but feeling this matter is deliberately stalled. The "investigation" has involved wiggling connectors and trying lots of combinations of hardware. It would not take me half a year to do that. For a problem like this that is not a serious approach anyway. They should be analysing the protocol dialogue and do signal strength measurements. And they may very well have done so but may not be willing to share the results. I am generally willing to assume good faith but the pattern just makes it too hard.

My understanding of HDMI cables is that for cables of 2 m or shorter, price or "quality" do not matter at all, you can hardly go wrong. For longer ones (5 m and up) your milage may vary, regardless of price.

[idata]

Are you kidding me? I posted here at least 4 times explaining the issue with... guess what... my UX31A ! (page 10) And don't tell me that mine is UX31A and not UX31, cause the UX31 has HD3000 and not HD4000, what is the issue here... Btw, the topic name is generic, nothing specific to the UX31A, or other. But, you are right by pointing that laptops with this issue KNOWN FOR 6 MONTHS(!) are doomed cause we can NOT have an other graphic card... The only solution is on page 14 by Mantis... And even with it, Intel and its awesome IT are stuck... nice...

Can you just imagine the nice advertising I'm doing for Intel last 3 months to my circle?

[idata]

i have previously posted my setup, i have a hd2000 and the display i am using is a palsonic tv with 1360x768 screen res. The problem seems to be that the tv's hdmi port is only a 1.0 or 1.1 port. I bought a hdmi to vga convertor off ebay and it supports hdmi 1.3, the hd 2000 works fine with this. The tv only works with the disable / enable device trick. This has been happening for over 6 months, from day 1 of my purchase

[idata]

Robert_U wrote:

@Cameron ,, Take a look at this thread, /message/172505# 172505 http://communities.intel.com/message/172505# 172505 .

More and more evidence is pointing to cables, especially low cost varieties, causing the issue on HDMI. The reason you see POST screens is that not all HDMI pins are active during POST and also POST is low resolution, low bandwidth. Once Windows boots you are now at a high bandwidth connection that poorly designed cables may not be able to handle.

Robert, thank you for pointing this out and for taking the time to reply.

However, I'm no tech expert but I do believe my cable is working correctly given that I can get the the HDMI display on my TV by disabling and then enabling the driver.

I'm reluctant to spend more money on another lead but will consider it.

[idata]

The cable problem is not the whole solution:

MB: Asus P8Z77VLX CPU:3570K 8GB ram

Windows 7 Ultimate X64

Connected Displays : 1. VGA 2.HDMI

W7 : primary display via HDMI

UEFI : primary display VGA

When booting with both displays connected the problem shows at login time:

No signal on hdmi, vga has black screen with cursor only,

even after entering my password to login which works, the hdmi doesn't show up and the VGA has a black screen with cursor.

Booting with VGA physically disconnected and reconnected after login no problem,

I can then reconnect the VGA for dual display mode and everything works flawlessly.

Note: the VGA cable must be disconnected physically, power off the vga monitor doesnt help,,,,

[idata]

I have the same problem , and i tried all possible solutions suggested in this post but nothing. After windows startup screen the HDMI display nothing!!!!!!!!!!!

MB: Asus P8Z77-V Pro CPU:2700K 8GB ram

Windows 7 Ultimate X64

Connected Displays : 1. VGA 2.HDMI

Graphic card: Intel HD Graphic 3000

I am disappointed ............

So either give us the solution which until now Intel ( one of the most advanced and biggest company in the world) can not, or simply tell us sorry there was manufacturing problem or what ever and you need to buy a graphic card (nvidia or ATI) because we can not solve the problem and be like any other cheap company.

Sorry for the words but you do not imagine how much i used to believe in Intel, but not any more.

[idata]

Your monitor with hdmi, is it an older one?

[idata]

I've been following this thread patiently, tried basically all suggestions and drivers being provided but non success until the disable and enable method, my system is

-Asus P8Z77-VLX

-I5-3570K

-Corsair 16 G ram

From day one, I can't extend the second display to the DVI, the cables and displays are all working one from my last P4 computer with a low end dual display card, nothing fancy, just running from PC under the desk to displays on the desk. These displays and cables work not just with my old P4 but any computer at home, Dell desktop and 3 other laptops.

I am now using a Geforce 520 temporary and keep waiting for a new driver that really work without disable and enable every time, but today reading the suggestion of " More and more evidence is pointing to cables, especially low cost varieties" make me more frustrated and lost further confident with Intel, are we playing expensive Hi-Fi that make a big difference between low end and expensive signal cable, even it is like a Hi-Fi system with the cheapest ebay cable, that should work. But now after months with so many test results from the group, we are talking about a normal cable that works in every computer but may not on the new intel chip. As I said I've been quietly and patiently waiting for a proper intel solution even though I am very frustrated as some other friends here, but this time I am annoyed and I hope intel can seriously come up with a solution rather than advising me to try a better DVI cable, I can tell you my DVI cable works perfectly in all my computer, as well as after disable and enable the HD4000 driver, if its not good then after disable/enable, it shouldn't work.

[idata]

It is a 42in LCD Philips, it is new I just bought before 1 month and it is full HD.

[idata]

Thanks for your help to previous posters on this Robert, I'm facing the same issue. Well, not exactly the same.

The system:

Gigabyte B75-D3H

Intel Pentium G620 (Intel HD Graphics)

2GB G.Skill 1333MHz, single slot

Win 7 x64

System is connected to a Marantz SR5005 AV receiver with an HDMI cable. The receiver then connects to a Tohiba AV10 TV using the exact same brand and length HDMI cable. These are Nithos HDMI 1.4 cables.

The problem is that I will get between one and two successful attempts at getting the display working every ten power-ups. Whether they are cold or warm reboots. Whether the TV and AVR are powered up, powered down or in standby.

The biggest problem is that restarting does not fix it - nor does the machine actually restart at all. When I lose all display the board stays powered down, and I can hear the onboard speaker (the little one) clicking away.

I have to carry across a monitor, hook up the cables, and be welcomed by a beep, followed immediately by a 'Failed Boot' screen. After getting into BIOS and then booting all the way into Windows I will still get no display on the TV (monitor works). I then have to run the driver application program to set up all the displays all over again, then unplug the monitor and it seems to work.

My problem is that I never know if I will have a picture on my screen when I turn the machine on. I've had EDID problems with Intel graphics before (when 1680x1050 wasn't a supported resolution back in '04) and I suspect it's something similar.

On a side note, I get a lot of these 'Failed Boot' screens (from the first day I've used this motherboard and CPU), even when the PC was connected to only a monitor. I am not sure if the problems are related to each other, or because of a faulty component.

Obviously this has gone to a whole new level - once I hook up the AVR and TV and expect it to work exactly the same way as a monitor, and it doesn't.

I do know your level of support for third-party products isn't really at the same level as your own motherboards, but I hope that you may be able to offer some insight. I was really hoping that my first Intel system in 8 years would give me a good video experience. It's not there yet - I can take any competing chipset motherboard, plug and unplug all sort of displays, start it headless and plug in a display later, or remove a display before restarting and still be able to get some sort of picture on a screen. The way it is now, the graphics card (in the CPU) is blind and keeps the motherboard in suspend until it detects what it deems to be a valid display on its output.

Strangely enough, the system does start when it is fully headless (no video connections at all, into any port), it simply refuses to do so when it feels like it (apparently, as I cannot find any reproducible symptoms).

[JHaki]

Well, at the very least then, if the cables have to be of a higher quality than previously needed, Intel should send a check or supply new cables to everyone who purchased an Intel processor thinking their old cables and monitor setup would work.

And how about a voucher for $25 off your next Intel processor or something. This is a big pain we should not have to go through, these CPUs and motherboards should have been thoroughly tested before release.

[idata]

As a follow-up to my earlier post, my Intel DN2800MT desktop board is flawless in HDMI operation. There is a momentary pause in the output when the HDMI chain is interrupted (if the TV goes into powersave, eg) but it comes right back up without any issues. There are no pauses or blanking out during HD playback (tried three hour straight). Board also boots fine in headless mode (all downstream units connected, but not powered up).

By contrast, the (far more powerful and supposedly capable) G620/B75 combination lost sync with the receiver six times in half an hour (sing the exact same cable and rest of the chain was identical). It keeps clicking when there is a cable connected but monitor is not powered up, moving to a filed boot screen when the displays are turned on. With no cable (headless mode) it boots fine. I suppose not enough combinations were tried with HDMI devices in various states of waking. An then there are the sync issues.

An important point to note is that the graphics chip on that Intel DN2800MT board was NOT made by Intel. So this issue is restricted to Intel CPUs with inbuilt graphics - it would seem, all the way from the lowly G620 to the HD4000.

Next up, testing with AMD integrated chipsets, the 780G and later the 880G. Will report back so that the issue (in my case at least) can be properly identified.

[idata]

Dear Robert

Am happy to report that there is some light at the end of the tunnel. Though I have not carried out long-term and multiple scenario testing, the prognosis of the remedy seems really promising at the moment.

I first tested the system (Gigabyte B75/G620) with a DVI-HDMI cable, connecting this to the DVI port on the motherboard. The result was 100% stable and flawless lock though of course the solution cannot transmit audio.

I figured the problem is something to do with the HDMI sync, so I continued to use the same cable *as well as an HDMI cable* to connect the system to the Marantz. I am basically trying to 'trick' the motherboard into thinking that there are two connected displays.

Using the Intel driver Control Panel, I set the graphics to single display mode using the HDMI as primary. The system obviously reports two connected displays but outputs to only one. Thankfully I have multiple inputs on the AVR (one of which is blocked by this solution).

I suspect the way these solutions are tested are by using a TV a a secondary attached display *and not the only display* in a typical user configuration. The reality is a few of us would like to use a PC as the center of a home entertainment solution and to have a second display permanently attached is probably not viable. Most folks running this kind of a setup will probably have a receiver of some sort, and HDMI sync issues are unwelcome when it comes to closed boxes. I do hope this post will offer some insight into the problem and help in creating a solution.

[idata]

I was definitely skeptical about the issue being cable related, it seemed to be too easy an out. I've been having the same issue with a brand new machine I had just built. After being up super late fighting with the issue, I went to sleep and tackled it again today. To be sure, I took a look at the DVI-D port on the motherboard. Sure enough, I noticed that the plastic was bent in one of the cells, blocking access to the corresponding pin. It easily bent back into shape. I then checked the cable, and there was the culprit. One of the pins was bent so far it was touching another, so it wasn't inserting properly into the DVI-D port on the motherboard. I bent the pin back, reconnected, and BOOM! It worked instantly. To be sure then, I bought a new DVI-D to DVI-D cable to replace this one. I'm typing this post using the computer that had the no display issue, which is now working perfectly.

So, my conclusion is that this problem is related to either the cable, or the ports on either end. Bent pin, not enough juice, somethign physical.

[idata]

Robert: I'd just like to report that I bought a new HDMI 1.4 spec cable and the HDMI-out function on my Asus UX21 Zenbook (HD3000) now works correctly.

Thanks for your assistance in the matter.

For anyone with a UX21/UX31 this is the cable I purchased (genuine Sony Ericsson brand): http://www.ebay.com.au/itm/200808418847?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649# ht_1571wt_1140 eBay Australia: Buy new & used fashion, electronics & home d�r

[idata]

Hi,

Just registered to voice my concern about this issue. My system is:

Asus Sabertooth Z77

Asus GTX 660Ti DCUII

Corsair Vengeance 2x8GB

Corsair HX520

Intel 3770K

It was all working fine on Win8 with just the HD4000. This until I bought the 660Ti a week ago. I started by hooking up the hdmi cable to the HD4000 out, as I was hoping to use VirtuMVP. Nothing.. same performance as the HD4000.. Then I hooked it up to the 660Ti hdmi output. I started to worry as all I got was blank screen. Tried all the combination of options on the bios, virtumvp on/off, 1st device as pcie/onboard, etc.. To no avail.

My only 'solution' was to install Win7 again and prevent windows update from installing the HD4000 driver. Win8 installs it by default on 1st startup, so there's no way of using my 660Ti with Win8 now.

I leave bios at auto and the card sends the signal (as it should)..

But I'm missing quicksync and I feel like this should be dealt with, not just shrugged back as a cable issue.

I'm pleading, a new driver has a way of correcting this serious problem, or since Intel outsourced it's dual graphics implementation to Lucid, we won't see this solved anytime soon?!

[ROBERT_U_Intel]

@Puscifer I would highly recommend you contact LucidLogix* for the specific issue you are seeing. Dual GPU via the LucidLogix Hydra* chip and Virtu* software are not supported by Intel. BTW,, Intel does not "farm out" it's dual graphics implementation to LucidLogix.

[idata]

Thanks for the fast reply, Robert.

This issue doesn't relate to Lucid, since I don't have it installed. I did a fresh install of win7 and the blank screen issue occurred when I tried installing the HD4000 driver. Thanks anyway.

[ROBERT_U_Intel]

Was the 660Ti still plugged in the system when you did the Win 7 install?

[idata]

The 1st win8 install it wasn't. Blank screen (on the asus output). Then when I reverted to win7, it was. Blank screen no matter what options I use. Tried every combination on the bios, no luck 😕

Tried the devcon workaround and with aero disabled. Are you suggesting I do a hd4000 driver install without the gtx660 plugged in? Well, can't hurt.