Solved: Re: Intel HD 4000 No Display after loading Windows 7 - Page 14

idata · ‎05-03-2012

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.

plee21 · ‎05-04-2012

Hi

It sounds like the driver has switched or lost track of which monitor is the default, so once it loads in Windows you lose the display.

Try removing your display completely and booting into Windows and try and log in (blind). Having no display connected might just get the drivers to re-evaluate what they need to do. Try plugging in your display once Windows is logged in, it should get detected and hopefully the drivers wil switch back to it.

If that doesn't help, try booting into safe mode, then from the start menu type msconfig, go to the Startup tab and remove the tick from the Intel Graphics application, then try rebooting in normal mode and see if it is okay now. If it is okay it will at least be running with the correct drivers and not in safe mode anymore, but you have lost the Intel utility to change settings, probably no bad thing.

The problem you have with uninstalling and reinstalling the HD driver is during uninstall it isn't clearing its settings, so once the driver goes back on, it picks up the same settings which results in it failing to send the video to your monitor.

If you are comfortable in doing so, uninstall the HD driver then browse the registry under HKEY_LOCAL_MACHINE/Software and see if you can find any entries for the Intel graphics, if yes rename the key (you could delete but renaming gives you the option of putting it back as it was). Also look in HKEY_LOCAL_USER. Then reinstall the driver and reboot.

Regards

Phil

View solution in original post

idata · ‎12-18-2012

Dear Intel-Team,

i have the same problem with my "mac-mini late 2012" running "windows 7 64bit" under bootCamp.

the problem apears only with a hdmi-to-dvi adapter under windows 7 with installed intel-drivers.

hdmi-to-hdmi is working perfect.

hdmi-to-dvi gives me a black screen and RDP shows that the monitor is not recognized.

windows-7 without intel driver gives me a bad screen, but shows that the cable is working and is giving me a screen.

i tried 3-4 different versions of the drivers without success.

idata · ‎12-18-2012

Well, i fixed it. I bought a new hdmi-to-dvi cable and the problem is gone

my new hdmi-to-dvi cable is made by "Belkin", if anyone cares.

idata · ‎12-18-2012

Intel,

I have been a longtime customer and supporter, and have always relied on the rock-stable Intel platforms. That's not to say there have never been issues, but those issues have always been resolved in a very timely manner. In early October I purchased an Intel platform for a customer who needed a top-end workstation with a high throughput and dual-displays. I went with a i7 3770K and a Z77 Chipset in a Gigabyte GA-Z77X D3H. Because of the issues with the HD4000 graphics, when the computer was set up on site it took 5 hours of troubleshooting, and the cost of 2 cables to attempt to fix it. Ultimately I had to eat the cost of a new graphics card for the computer as well as look like an idiot and cause the customer a 5 hour delay. The next day I found this thread and have been following it ever since. I know there are problems, and that is to be expected when working with technology, but for a blatant issue like this to just be ignored is not the Intel I know. I have heard a lot about HDCP and HDMI versions being a big factor in compatibility, and yes it is a complex thing, but for the largest technology group in the world this issue should be child's play. The Intel I know would have immediately released a work-around (bypassing the HDCP if necessary to get their customers back up and running, or downgrading the output to HDMI 1.0 just until a solution was found). Coming from a background in electronics, blaming this on cables is the most foolish thing I've ever heard. HDMI/DVI has set standards of voltage/resistance/capacitance and as long as the cables are capable of this it should work flawlessly, being a digital interface. If the cables work on one device but not the other, the fault is not the cable, but the device (that's basic problem solving!). If the cables are really making or breaking the connection, consider the fact that the device may not be outputting enough voltage, or may have too high or too low of resistance for the other device to drive. The issues here are elementary compared to what Intel does on a daily basis! Until this is resolved I will have no other choice but to steer my customers in alternate directions (and I hate that, but it's the way Intel has made it).

idata · ‎12-25-2012

Hello fellas,

I have been having a similar problem and found a solution by sheer luck after 3 months of giving up.

I have an Asus z77 sabertooth with i5-3570k and EVGA 660ti. Although I mainly use my PCI-E with DVI for simulations, my wife at the same time uses the HDMI out of intel graphics with our 080p tv to watch windows media player. Until 3 months a go when I decided to update the drivers we lost this ability completely and after many tries I had given up on the issue and began using PCI for both which was causing performance issues.

Yesterday, I borked the Windows 7x64 and started reinstalling and while doing so I decided to try to fix the issue once more. Following are the steps I have taken to successfully to resolve the problem...

1. I plugged DVI to PCI-E and HDMI to onboard and flashed/cleared bios.

2. Hit bios settings and after updating my overclock stuff I went to graphics settings and enabled LucidLogix Multi Monitor support and set primary graphics to PCI-E

3. Installed Windows7 x64 and changed user to administrator, then changed the theme to windows classic

4. Downloaded the newest nvidia drivers from nvidia website, lan, audio, sata, usb and lastly intel chipset drivers from asus website.

5. Installed everything in above order and after restarting twice with chipset driver install, I downloaded the oldest VGA intel HD accl. driver on asus website.

6. I opened up the device manager and found the Video controller device and selected update drivers, directed windows all the way up to the VGA drivers x64 folder and hit okay and voila.

Warning, there is a high chance that it will all go to hell if you unplug the dvi or hdmi or install newer drivers..

Anyways, I hope this works for some of you, because I doubt intel gives a damn about fixing it, after all you already paid for the product. They will just make a newer cpu that doesnt have this problem (possibly some other problem instead) for few more bucks. Solving bugs dont make em any extra cash.. Its business so its useless to get mad at them, its is capitalism..

Good luck...

idata · ‎12-27-2012

Hi, I found this forum after a rather frustrating couple of days post-Xmas

I have plenty of experience in setting up PCs, I've built many a one from parts and have installed graphics cards, drivers, BIOS, and various OSes since 1992 (MS-DOS, Windows, three different distributions of Linux, XP, Windows 7, etc.). But as I get older I have less fun getting things to work, and just want them to work... Especially when they're presents for my kids!

I specifically bought a pair of refurbed HP Slimline S5-1224 PCs because for about $320 it was the perfect form factor for the tight space, it came with Windows 7 pre-installed, had an LGA-1155 socket for the CPU so I could upgrade it to an i3, i5 or i7 some time later if I felt it necessary... And not least, because the OEM graphics chip (an Intel HD chip of some strip) supported dual monitors. I had two extra 17" 1280x1024 LCD screens (in addition to two of the same size attached to their existing PCs), and it seemed perfect to upgrade my two kids' computers from 2003-era Win XP machines that couldn't even properly run Minecraft.

Everything works great with these machines except for the dual monitors. I have one monitor hooked up to the analog VGA output, and another to the digital DVI-D output (which is run with a M/M DVI-D cable for a pure digital signal to its display, no VGA adapter is involved). I found that during setup, even though both displays showed the Windows startup graphics, only the VGA output screen had any signal once the login window appeared. The DVI-D signal just seemed to cut out, the screen read "NO INPUT".

After installing the latest version of the graphics driver, the digital signal came back and I was able to set up a dual monitor scenario. But after installing more software and rebooting, or after putting the system into sleep mode, the digital signal cuts out again. I have to re-install the driver to get it to kick in, then say "reboot later" to be able to use the dual monitor setup.

After futzing around for about 3 hours I managed to do something with one of the two PCs that has it stably running dual monitors (one analog VGA, one digital DVI-D). I don't know what it is. Right now they're both identical as far as I can tell. I had disabled Aero, though re-enabling Aero on the now stable PC seems to work.

The cable I'm using is identical between the two PCs: 6 foot Gigaware DVI-D Dual Link cables, rather high quality cable from what I can tell. Gold terminals and thick, well shielded cables from the looks of it.

I'll re-read this thread in the AM but I'm not sure what to try next. Glad to see I'm not alone here. It seems like a software problem, not hardware, because reinstalling the driver (even the same one, over and over) "pokes" the signal into being recognized. I've tried the test version of the driver posted earlier in this thread and the latest on posted by Intel, to no avail. (FWIW the version that works on the one PC is the one it was shipped with, from 2011, it's 8.15.10.2291, though the digital screen does flicker a bit whenever I do a driver install for some other program, it comes back and remains operational.)

idata · ‎12-27-2012

More info on what causes the digital signal dropout:

1 - On the PC where I had had the dual monitors working for a few hours (which survived several reboots), when my daughter plugged in her iPhone into a USB port the digital screen cut out again. I re-installed the driver to get it to snap back.

2 - After reinstalling the driver and rebooting, that PC now behaves as it used to (and the other one still does) - the digital output line works during startup, then cuts out as the login screen comes up.

3 - With the iPhone plugged in to the USB port, it also restarts (drops power, then gets it again over the USB line) when the system transitions from startup screen to login screen. Hmmm.

4 - I noticed the analog VGA screen also drops out to "no signal" momentarily at that time, but it soon comes back to show the login screen (as if the system had only one monitor) while the digital screen does not (until I re-install the driver)

idata · ‎12-30-2012

I have a similar problem with Windows detects the graphics card in the device manager but after installing the drivers for your video card blanks the screen and you can not include it. Black screen but you can hear how the system works there is something wrong with the drivers. I have a Asus P8Z77-V Pro but what about how you can not use the technology contained in it as the drivers are not compatible and surprise me with the board because I have the latest installation plate bios and no one can help me I wrote to Support Asus see what I will respond to this thread I came across by chance thanks to google: (. GTX 560Ti I have the latest nvidia drivers, and so it's does not surprise me that after the installation just stupid drivers from intel hd 4000 wylancza monitor even though it is connected to gtx 560ti is there anyone can help me what to do? I think we are here How have you wise heads who take money for the creation of these drivers, and they know what's going on?

Help!

idata · ‎01-11-2013

It's definitely a software driver issue in my case guys, since installing or rolling back the driver causes the dual monitors to kick in until the next reboot. Most likely some kind of timing/race condition type of bug with the driver when Windows loads it up (since both monitors work on bootup and initial startup screen, losing the DVI connection only when the login screen is about to appear.)

Anyway, I solved my problem by giving up on getting a good driver, and spent $40 and 15 minutes to install a Sapphire AMD Radeon HD6450 video card in the PCIe x16 slot. All monitors were detected and worked immediately. Too bad for me that I had bought the HP PCs in part because of the built-in dual monitor support, but at least the "fix" (which was to ditch relying on the Intel graphics chip/driver support) was only $40. I just wish I'd done that before wasting an entire Saturday (about 10 hours) trying different configurations, searching for drivers, buying and trying new HDMI cables, going back to return the cables when they had no effect, etc., etc.

idata · ‎01-16-2013

Hi Warren,

Solved, but my EVGA graphics card cost alot more than $40 😞 Good gaming though 🙂

Hi Robert_U,

I think the HD 4000/Driver has issues that are not cable related. I built a new media center, installed Windows 7 from scratch, and have tried three very high quality HDMI - HDMI straight through cables (no mini involved). The monitor is a top-of-the-line Panasonic VT50 TV. The media center and TV worked together perfectly for one month using the HD 4000 graphics. Then this past Sunday 1/13 with no changes made, I turned the system on and got no signal to the TV. To diagnose the issue I moved the media center to a smaller Samsung TV where I also got no signal over HDMI. I implemented the devcon.exe driver disable/enable workaround and scheduled the task at Windows startup. The result was that on the Samsung TV, Windows would load, then go to blank screen, then become usable over HDMI until the next reboot. However, the Panasonic VT50 does not see a signal from the HD 4000. To be clear, I unplug the HDMI cable from the working Samsung and immediately plug it into the Panasonic and the Panasonic does not see a signal. Plug it back into the Samsung and there is a signal. I tried to correct the issue with various iterations of the Intel driver with no success. The Panasonic is only one month old and there is nothing wrong with the HDMI inputs (however, I suspect that it requires a slightly higher signal strength than the cheaper/smaller Samsung). At this point I'm not willing to spend more time debugging because I have resolved the issue with an EVGA graphics card which so far is working perfectly. I think there is a marginal signal strength problem on the HD4000 as well as a driver loading issue that can occur that causes the need for the disable/enable device after Windows loads. Keep in mind that my system ran for a month (with many reboots) without seeing the blank screen issue or nosignal issue. Sure, some folks may find that a cable swap resolves the signal strength issue; to me that is just more evidence that the HDMI signals are marginal. BTW, the EVGA card is working great with same cable and Panasonic TV. The only other thing I can think of is the discussion about HDCP blacklisting, however, not sure how much of that to believe; we tried setting the Panasonic back to factory settings with no success. Too bad, I expected to not have to purchase a graphics card for this system, but oh well, games are smoother anyway 🙂 Wish you the best in resolving the real issues, just saying that I don't think cables are the root problem.

idata · ‎01-01-2013

I'm having a similar problem on my Macbook Air(2012 - Intel HD 4000) in Boot Camp. I installed the latest driver, but it gives me the BSOD once Windows boots. The older driver works, but games take forever to load on it. I've only been successful booting the latest driver twice, which fixed the gaming issue.

idata · ‎01-01-2013

Why no one from the company Intel will not say anything and did not help is crezy

idata · ‎01-03-2013

3570K

Windows 7 64bit ultimate with latest drivers after fresh install

Gigabyte Z77x-D3H F16 bios

Monitor connected with DVI cable and TV with HDMI cable.

I'm only using HD4000, I don't have a dedicated graphic card yet.

I wanted to use dual monitor today for the first time with my TV as second screen. In windows nothing happened when I connected the HDMI cable, so I did a reboot and my TV turned on immediately, but as soon as Windows was loaded it turned off again. I've tried changing to a different HDMI port on the TV but no luck. I don't know what else to try so any suggestions are welcome.

idata · ‎01-03-2013

Hi,

i have same problem!

It is not a problem of graphic driver!!

If the fault effect, LCD on DVI does not work immediately after starting the PC.

----------------------------

My PC use dual display. First is on analog VGA - works fine. Second LCD is in DVI port - after installation worked without problems for several days. Then one by one starting PC, agrees sleep mode.

To restore the image helped to re disconnected from the PC and LCD power supply.

For several days, the situation was repeated ....

My configuration is as follows:

GIGABYTE H77M-D3H (rev. 1.1)

CPU INTEL Core i3-3240 BOX (3.4GHz, LGA1155, VGA)

LCD on DVI :

LG 23" IPS 231P-BN 1920x1080, 5M:1, 5ms, 178 / 178, D-Sub, DVI, Pivot,

Speaker

I have last MB BIOS, new DVI(single link) cable,.... did not help anything.

In my opinion, the problem is detecting activity on the DVI port - a problem in VGA Intel CPU, or some problem with the motherboard BIOS.

Please solution!

Thank you.

idata · ‎01-07-2013

I have a DZ68DB motherboard and one monitor in the DVI port and work fine, I connect a LCD full hd digital televisor to the hdmi port with a hdmi-hdmi cable. Alfter reboot the PC in the HDMI appears the Intel Logo and the Windows 7 initial screen appears in bot monitors, after the message: "No signal Found" after Windows 7 loguin appears in the hdmi port. I try to disable the hd4000 graphics card in the control panel and when Reboot the hdmi work fine in 1980 x 1020 but not have signal in the DVI port.

Exists any way to use extended monitor with this configuration?.

My Configuration:

Intel DZ68DB motherboard

Intel Core I7-3770 box

Windows 7 Ultimate

Monitor in the DVI port.

LCD 40" full hd in the hdmi port.

Thans in advance.

Sorry for my English, i speak in spanish.

idata · ‎01-07-2013

A new intel driver just came out a few days ago, you guys can try to see if it has fixed anything for you.

idata · ‎01-08-2013

I have a fix but it's only for Sabertooth Z77 users...

I upgraded my BIOS from 1308 to 1708 (latest) and found that a host of problems that just popped up when I finished the upgrade. The iGFX was reporting Code 10 errors on Windows 7, despite a fresh install... My PC would crash when installing the drivers from any age and teamviewer looked rather funky when the PC did crash.

One last ditched effort before taking the whole system back was to downgrade the BIOS to what it was shipped with (1308) and the problem fixed itself.

Anyone who has iGFX or Lucid problems and have recently updated their BIOS to 1708, download the 1308 BIOS from ASUStek and downgrade the BIOS, your problems will start to disappear.

The proper procedure for installing Lucid is:

1. Install latest drivers for your discrete card (NVIDIA/ATi).

2. Restart PC into BIOS and turn on Lucid TwinViewer and set your primary card to PCI-E (make sure that your card is in PCI-E # 1).

3. Install ALL the Intel INF drivers for the motherboard only (newest preferred) and restart.

4. Install the EARLIEST Intel GFX driver on the ASUStek website.While installing the drivers, if your screen doesn't turn off unexpectedly the driver has installed properly. Restart.

5. Install Lucid and Restart.

I never used a second cable from the iGFX, just a DVI-D cable from my card to my monitor. I have a NVIDIA GTX570, using PCI-E 2.1

Downgrading the BIOS works for Sabertooth's but it may also work for anyone with ASUS boards. Download a BIOS around June/July 2012 and see if the problems goes away and this can also be applied for Gigabyte board users too.

Seems ASUS needs to get their act together on release faulty BIOS's.

idata · ‎01-17-2013

I had the same issue as the original poster.

My solution: I was using an older 2005 ViewSonic VX2035wm monitor which apparently isn't fully PnP on the DVI-D port. It worked fine on the analog VGA port.

When I attached my 2010 Dell U2711 to the DVI-D port everything worked perfectly.

Buying a graphics card would likely have solved the problem, but that defeats the purpose of buying a CPU with integrated graphics.

It would be nice if the HD4000 driver was more backward compatible towards older monitors, or at least provide a warning that you may experience issues with such displays so you're not spending hours banging your head against the computer.

idata · ‎01-22-2013

I have a ViewSonic VX2835wm and my Intel HD 4000 thinks it is an HDTV, it looks terrible. My old laptop didnt have that problem. I have tried connecting with DisplayPort to HDMI, and the HDMI mini to HDMI cable, same thing.

idata · ‎01-23-2013