I7-2600K Intel HD Graphics (igdkmd64) Crash Win 7 x64 when using HDMI

[idata]

Hi,

Getting frustrated - help please. Every time I try to use an LCD TV (using mobo HDMI-out to TV HDMI-in) it results in a BSOD with STOP 0x16—telling me that the igdkmd64 did not recover. Usually before the BSOD I get something like "Display driver igdkmd64.sys stopped responding and has recovered" several times, and them–KABOOM.

The system works fine with a VGA monitor without the HDMI attached.

This is a clean Win 7x64 (Home Premium) install on a minimal system:

ASUS P8H67 B3 (Realtec HD Audio, and Realtec Gbit Network);

i7 2600K with Intel HD3000 on processor graphics

4 Gb RAM (2x 2Gb) DDR3 1333

HD - Crucial C300 128Gb SSD AHCPI.

Supposedly (?) I have the newest HW drivers

The culprit TV's are an older Olevia 42"-1080i, and a newer 26" VIZIO 1080p. Both are HDCP compliant, and both work fine with HDMI from a DVD, A/V Receiver or cable box.

So far I have tried swapping HDMI cables, tried using a DVI-out to HDMI adapter (TVs don't have DVI ports) – same result. Tried removing one memory stick (leaving only 2Gb on a single slot) same problem. Also tried with various BIOS settings -- no help. The same things happens if I booth in Safe Mode with networking, but not in Safe Mode. So, I disabled the network drivers and devices, and rebooted normally --but didn't help, same BSOD.

Have been searching the web and forums, but nothing seems to be helping.

Any suggestions are much appreciated!

[MSchm21]

Is there a way to upgrade the vbios to check if it's working? I don't think so. Gigabyte and Asus did a bad job with their bios. MSI updated the vbios version with the latest bios for H67MA-E35 and Asrock with a newer version since early march. On the other side of course Intel should provide the users with a stable driver not matter if old or new vbios. It looks to me they are struggling now.

[idata]

Robert_U and developer,

What are we going to do next for the users still having the problem(s)?

Thanks and the BSOD is gone but as other users here mentioned, there are a lot of problems with devices due to signatures, different resolutions, and refresh rates.

Please let us know. thank you.

[ROBERT_U_Intel]

We are looking into the other issues. With such a diversity of system configurations this will not be an easy or quick task.

[ROBERT_U_Intel]

For those with Intel Audio (HDMI) issues, first uninstall any previous graphics drivers and Intel Audio drivers before installing 2401. Please try this to see if it helps.

[idata]

I plan to bombard you with other issues as soon as you fix this.

In my case I can confirm that there were no crashes with the display driver since the new version, but I didn't have the BSOD with previous configurations (I don't know why because I had the BSOD when I first swicthed to this hardware setup). In any case the windows reported crashes of the driver didn't appear yet with the new driver.

What I still have is a display refresh fro all connected devices whenever I turn on the TV and applications that are full screen are changed into window mode. Irritaiting...

[idata]

Thanks Robert_U.

Undersotood and it is not an easy task to make somwthing which will work for anything in the market.

But in my case, I have 2 displays, 1 main plasma and the other is projector. The plasma is 1920 x1080 60Hz and projector is 1920 x1080 23 Hz.

When I use any other than 2219 and latest driver I have BSOD. Now, with the latest drive you provided here, when I first boot up, the screen is formulates 1 1/2 screen and the other 1.2 screen got 4 screeen on the top. I can VNC in and change the setting I wat and correct it. But after I reboot it will go back to that stage and it is impossible to do it every time. Also, as soon as I changed my projector to 23 Hz, it will go to BSOD right away.

[idata]

Just completely removed 2219 and installed the latest drive. 23Hz won't stick, kick back to 60Hz, in 1920x1080 for my 2nd display, projector. 2219 did not have nay problem to stick with 23Hz for BD playback.

[ROBERT_U_Intel]

Please let me remind everyone that this is a test driver. We are looking into the issues being reported with and will work to resolve them quickly.

[idata]

Robert_U,

Took your advice and uninstalled 2219 then rebooted, VMC in since no display in my plasma, reinstalled your latest driver, rebooted, edited all the display setting for my plasma, 1920X1080 60Hz and my projector, 1920x1080 23Hz, but the projector did not stick and kick back to 1024x760 60Hz. After few trials and errors, the only setting close to 1920x1080 23Hz, my projector seeting, is 24Hz. Reboot and now it is working few hours now. Btw, no bitstream on 7MC and missing 23Hz for 1920x1080 otherwise it is cool here. Thanks for the hard work!

[idata]

Robert_U,

Is your latest driver has anything to do with bitstream WMC? It seems to me that I can no longer bistream Dolby Digital from WMC anymore 😞

[idata]

As an experienced and long time system builder who is familiar with current hardware, I have a few comments regarding attempting to use the Intel HD 2000/3000 graphics driver for a HTPC (Windows Media Center) and a few remarks in general about this issue.

My Win 7 Ultimate x64 HTPC uses an i5-2500K in an ASUS P8H67-M EVO with x4 2GB G.Skill DDR3-1333 RAM, 64GB SSD drive, 2TB WD HDD drive, Lite-On BD Disk Player/Writer, and a Ceton InfiniTV 4 PCI-E cable card which I have connected to a Samsung UN55C7000 LED LCD TV and 7.1 Yamaha receiver. After the initial Windows Update to the new driver, resulting BSOD, multiple hours trying to figure out what happened and how to fix it, trying every version of the graphics driver (at one point corrupting the system beyond the ability to reinstall windows from DVD) and multiple system rebuilds, I ultimately settled on flashing the BIOS to 1502 but keeping the driver version 2219, which was supplied on the mobo drivers DVD. Unfortunately, this driver version has several problems that compromise system stability including a memory leak that occurs after just a few minutes watching some DRM protected HD content. Apparently, the Intel control program doesn't provide enough configuration options to prohibit application control of rendering, which fixes the problem for most everyone else. The quality of rendered images, especially skin tones, are far inferior to even a low end NVIDIA graphics card.

This graphics engine is in theory a brilliant solution for a powerful yet energy efficient (380W PSU) HTPC capable of supporting live TV playback, 1080p output, 3D Blu Ray, and 5.1/7.1 surround sound passed through the HDMI port or SPDIF optical audio without the need for expensive and power hungry add on graphics and sound cards. Despite being overkill for a HTPC, I didn't mind dropping $220 on an all in one sandy bridge CPU. Unfortunately, as is demonstrably clear to everyone on this forum, the product isn't anywhere near being ready for prime-time. It's astounding to me that the proposed driver fix recently introduced caused more problems than it fixed or that it's been months without a sufficient resolution to the core problem. It tells me there is something fundamentally wrong with the graphics driver, the chip, or Intel's support resolution process and team. At a minimum, I'd have expected Intel to...

1. Notify Microsoft to yank the deficient driver from Windows Update... Immediately... Like freaking last week already… to spare anyone else this grief.

2. Clearly notify customers that a problem exists and is being worked on and what to do in the meantime.

3. Fix the actual problem... devote sufficient resources to finding the problem, testing it, etc.

Robert, I've been on your side of things and I can't speak for who you report to so I won't throw darts. However, if you haven't run this up the flagpole at your end at whatever level you need to get what is needed, you need to. As it stands on the response so far, Intel is doing a disservice to their customers and probably you as well (assuming you can't get more resources on this).

To folks still experiencing this problem, bite the bullet and buy a graphics card and a more powerful PSU if you need to. Yes it sucks, but time is money. As it stands, you'll be dicking around with this BS for another 6 months before a patch that fixes enough of the problems is haphazardly thrown together by Intel and Robert throws his hands up and joins a competitor or hits the unemployment lines (depending on who is actually at fault here.)

Combined with the B3 stepping recall, new MOBO install, 40-60 hours pissed away on this graphics issue, and now the time needed for a PSU swap and getting a graphics card configured…. I've blown so much time on this project and regret now picking up a cheap AMD chip with a graphics card in the first place. So much for the Sandy Bridge all in one 'savings'.

[idata]

One hundred percent agreed. I'm pretty much satisfied with my SB CPU, it didn't let me down, but come on, the deal also included a good IGP when I made my decision. I clearly cannot make use of that one though. Perhaps it's time for another recall following the motherboards???

[idata]

This pretty much sounds like my experience on my i3 2100+Gigabyte GA-H67N-USB3-B3 setup.

My HTPC ended up more expensive than I calculated, because I had to purchase a proper graphics card.

But this also added more power consumption/heat/fan noise.

[idata]

I would gladly use a dedicated Videocard, but the one PCI-E slot on my M-itx board is used for a TV card....

[idata]

Yeagh no kidding... I built a few lower end 200W HTPC clients with the Sandy Bridge Celeron 620 chip for the other TV's in the home assuming the HD2000 iGPU graphics could handle rendering live TV streamed from the main HTPC and play DVDs without the need for a $100 graphics card... The case I used has no space for a graphics card if they can't fix this BS and I'm beyond the ability to return much of the equipment if I have to start over.

Intel, this HD 2000/3000 graphics engine is your what... third attempt... to get in on some actual market share with a real integrated graphics processor that isn't a joke. It should be a huge selling point done well and not a debauched cluster mug. I mean seriously... you can't get digital video output down solid or fix a memory bleed issue??? HDMI, Bit Streamed Dolby audio, 3D output, etc… these are the future and you need to get with it.

[idata]

I have the color blinking/flashing or blackscreen issue as well but not with hdmi... but with the subd vga output.

I tried most driver versions, none works... only standard vga is safe.

My setup is i3 2100 on GB h67 mini itx and Samsung Syncmaster 22"...

I wanted a setup without video card ... but i'm now thinking about how to get one...

[idata]

Robert,

It sounds like the driver you are working on may have fixed the BSOD issue and are currently working on getting the various output options, resolutions, and bit streamed audio pass through HDMI corrected. Assuming all these issues are nailed down in the next driver release... I'm wondering how many of the problems folks experience stem from any GPU settings in the BIOS including GPU boost functionality, and shared memory settings and if you can share any insight on what modes might work better than others.

I have the BSOD with any driver version other than the standard vs. 2219 that came with the mobo driver DVD and a memory bleed issue watching some HD live TV content in Windows Media Center (other msg boards claim you can fix this issue by setting the graphics adaptor to not allow application control of rendering but I can't seem to disable enough application control settings to make this fix work). I also need to use HDMI output with both audio pass-through and/or running audio through the SPDIF optical out to a receiver. System uses the ASUS P8H67-M EVO mobo running a i5-2500k and x4 2GB of G-Skills DDR3 1333 memory set at 8-8-8-24. I have not yet tried the latest test driver version but saw someone with the same Mobo say it worked.

Mobo manual is here: http://dlcdnet.asus.com/pub/ASUS/mb/LGA1155/P8H67-M_EVO/e5955_P8H67_M_EVO.zip http://dlcdnet.asus.com/pub/ASUS/mb/LGA1155/P8H67-M_EVO/e5955_P8H67_M_EVO.zip

Do you have any recommendations for using the iGPU boost physical MOBO switch (turned on) and auto over clocking BIOS feature (set to XMP mode) on 3-7?

Do you have any recommendations for how to set the System Agent Configuration on page 3-16

Initate Graphics Adaptop: left as default PEG/iGPU

iGPU Memory: Set to 128MB

Render Standby: set to Enabled

iGPU Multi-Monitor: set to Disabled

I noted that one of the newer driver versions I tried caused an IO error black screen of death issue when trying to reinstall Windows 7 from a DVD and another driver version got me to windows for a few seconds until Media Center was launched (launches some sort of application control over graphics rendering) and I'm wondering if there is some sort of shared memory issue that the bad driver versions cause even beyond a HDD format. The memory bleed problem is especially tricky because I have a few mini HTPC's with the Celeron G620 chip on H67 boards and no way to add a GPU to them. If this isn't licked, I have no way of watching my beloved HBO/Shotime/Starx/etc.

[idata]

D_Sherman,

I've the same MB and Windows 7 x64. Latest BIOS and latest driver provided by Robert_U here.

Few notes,

I've no clue what to set in BIOS System Agent Configuration and my setting is same as.

Initate Graphics Adapter: iGPU

iGPU Memory: Set to 128MB

Render Standby: set to Enabled

iGPU Multi-Monitor: set to Disabled

FYI - I tried iGPU Multi-Monitor enabled and memory will go back to 64MB but I do not see any different in the front end.

After few attempts un-installed 2219 and re-installed the latest driver Robert_U provided here, instead of just install on the top of the 2219, I uninstalled 2219 then rebooted, VMC in since no display in my plasma, reinstalled your latest driver, rebooted, edited all the display setting for my plasma, 1920X1080 60Hz and my projector, 1920x1080 23Hz, but the projector did not stick and kick back to 1024x760 60Hz. After few trials and errors, the only setting close to 1920x1080 23Hz, my projector seeting, is 24Hz. Reboot and now it is working now.

Btw, please note that there is no bitstream on 7MC and missing 23Hz for 1920x1080 otherwise I've no problem bistream using TMT5 with any BVD and DVD contents using latest driver.

Again, the latest driver Robert_U provided is okay, it just needs to unistall the older driver, install, set up via some remote access like VNC, reboot then it is fine.

[idata]

hlkc,

Thanks for the info. I admit not having audio completely configured yet or being anywhere close to an expert on it. Its currently sent to the TV over HDMI and I'll set up the receiver with the surround speakers once they arrive then switch to SPDIF optical out. The mini HTPC's will use HDMI to send audio to their flat screens. I just want to make sure the new driver won't blow away the audio config I'm temporarily using. The Samsung UN55C7000 should support either 24/60Hz from what I understand so there shouldn't be a problem there.

Have you had any memory bleeds using WMC 7? I have the Ceton InfiniTV 4 with a multi tuner card, latest drivers, and Verizon FIOS and some (not all) of the HD premium channels last for all of 5 minutes before ehshell.exe consumes all available memory, live TV stutters, and WMC freezes and tries to reboot. Both live TV and recorded TV cause this problem. However, viewing the recorded problem show on my laptop with a NVIDIA graphics card or by bridging one of the four tuners from the main HTPC to watch live TV on my laptop causes no memory bleed at all. Ceton and MS won't go near this and the few forums discussing the problem seem to indicate it's a graphics driver issue that can be remedied by configuring the graphics card to use hardware rendering and disable application control. However, after playing with the available configurable options on the Intel interface package, I can't fix the problem. Strangely no issues with blu ray movies or any other HD video... just a matter of a handful of HD channels playing (presumably) DRM content created very recently (HD movies from a few years ago don't seem to cause a problem).

The GF is at her wits end with this conversion so I'll try to test out the driver on one of the smaller HTPC boxes this weekend to see if it fixes the memory bleed that won't shut off her shows with another BSOD = sleep on the couch until it is fixed incident.

[idata]

D Sherman,

I have Ceton for months now and answered many questions in AVS forum as well.

Can you let me know what do you mean by "the HD premium channels last for all of 5 minutes before ehshell.exe consumes all available memory, live TV stutters, and WMC freezes and tries to reboot."? Is it really crash or other WMC error like "tuners not available..."?

I did have the similar problem, stopping working few mins after Live TV, but NOT crash. I used to have Ceton in the 2nd PCI 2X1_1 slot and after some tests with Ceton support I disable the 1394 inside BIOS since 1394 share the IRQ resources in that the same PCI slot that I have the Ceton installed. Since you and I have the same MB, I encourage you to give that a try. Again, just go to BIOS and disable the 1394 if you've not done so. Please refer more IRQ info in the manual 2-12, bottom table.

I promise you once you set up the Ceton like me you will be SO happy. FYI - I make a mistake by getting rid of the STB and now Ceton is the only TV source in my first floor and there is no way I can have less than perfect TV souce coming in, lot of pressure from family 🙂 So far there are still some small problems but generally speaking it is perforing better than I wished, miles better than any tuners I tried in my 10 years HTPC experience.

[idata]

hlkc,

Your info is much appreciated. I'm more than willing to exchange information with you going forward over email if you want. Perhaps I can be of similar assistance if you ever run into a problem. My public email is mailto:dmsher99@gmail.com dmsher99@gmail.com.

As for the memory leak, ordinarily if I'm watching a normal HD channel like CNBC HD the 8GB of available RAM is about 1.5GB used, 4.3GB standby, and 2.2GB free. Most of the premium HD channels are OK as well. However, suppose I try to watch "to big to fail" or another very current program like "predators" on a HD channel live or even recorded, then the used RAM slowly increases 15MB every couple of seconds, until standby and available RAM decrease to 0 (I set virtual drive space to 500-1000MB instead of being system managed). Then WMC stutters and a msg box appears behind WMC stating that it has encountered a problem and needs to close or will attempt to restart. WMC doesn't restart and I have to force WMC to shut down because the TV stutters and stops playing in a viewable manner.

This only occurs on a handful of HD premium channels and not always with the same program or channel. I've played with the BIOS GPU settings, put virtual memory management back into system hands, and played with graphics settings. However, nothing seems to completely lick the problem. I am connected to the HTPC with my laptop on a home group and have yet to run into the problem with any of the problem programs recorded or on the one tuner I opened up with network bridging... which is why I thought it might be graphics driver related.

I'm currently watching a recording of "too big to fail" with system managed virtual memory and no problems yet. I'm going to try to change the graphics to IGPU from PCG/IGPU in the BIOS and disable the 1394 as you suggested, put my virtual memory back to 500-1000, and see what happens. I have the Ceton card in the small blue (second from processor) PCI slot on the mobo.

Moving it to the bottom black one worked for you with 1394 disabled?