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!

[idata]

Still no new BIOS from ASUS for P8H67-I Deluxe either.

Is there any point in testing new drivers when the VBIOS remains old?

Shouldn't Intel pressure manufacturers to make updates available since the VBIOS can't be updated independently?

[idata]

Gigabyte just posted a new BIOS for my GA-H67A-UD3H-B3 that hopefully will have the new video BIOS in it.

I'll try it when I get home tonight.

http://www.gigabyte.com/products/product-page.aspx?pid=3772# bios http://www.gigabyte.com/products/product-page.aspx?pid=3772# bios

[idata]

NM that was wishful thinking. Gigabyte didn't do anything in the F5 BIOS with the vBIOS... so it is still at 2080 and the problem is still there.

[idata]

Gigabyte pasted a new F6 BIOS for my gigabyte ga-h67a-ud3h-b3 board and it does have the new vBIOS included but the issue is still there for me.

I've tried every old driver listed in this thread to no avail with the older vBIOS so now I guess I'll go through all of them again with the new vBIOS to see if I can maybe get a stable platform.

It would be nice to see some activity from Intel on this issue. The quieter they are the more their name is going to get drug through the mud.

[MSchm21]

That means vbios isn't the problem. It's the driver. You should try driver 2219.

[ROBERT_U_Intel]

Just to let you all know we are still working on these issues. I will post up when we have a fix or workaround available.

[idata]

Robert. Thanks for chiming in. Any idea of an ETA? Are there a lot of resources on it? Do you have the issue duplicated?

[idata]

fix SSD power loss first.pls

[idata]

Robert_U:

with all respect, google says same issues accompanied previous integrated gfxs made by Intel, and it too took months to resolve, I don't see different tendention now.. it's not about you not working fast enough, it's about Intel's attitude

[ROBERT_U_Intel]

We take this issue very seriously, the issue has been replicated by our teams , and we have the necessary resources engaged.

.

[idata]

Excellent, thank you. Of course any tid-bit you can share as you progress would be most appreciated. However technical or obscure. I'm a channel parnter and we have halted production of a HTPC unit pending resolution, or apparent progress. I have the highest hopes for a speedy resolution as I'm sure all here do.

[MSchm21]

Do you think it can be fixed this quarter?

[idata]

Robert_U:

ok So why then Intel support tells me that everything is working and it's problem with my Hardware. And you say whole team working on this issue. I agree with Martin it's Intel attitude, disgusting treatment of customers

[idata]

I think the management of Intel should consider to fire out some people, because they are not able to do their job. It's because some lack of knowledge or simply they employ cheap people, really don't know but I do not care. The fact is these products haven't got the correct support from the driver developer teams. This is very very clear and will reflect on the budget as well!

The issue is ongoing since almost 1 year and they have still no solution just some stupid workarounds and beta drivers. As far as I know several stores considering to decrease their stocks with these products because of the extremely dropping quality.

I hope they will do something asap because this behavior leads to nothing....

Sorry for my honest words, I'm not angry, just sad to see this.

[MSchm21]

Has anyone tried driver 8.15.10.2430?

http://downloadcenter.intel.com/Detail_Desc.aspx?lang=deu&DwnldID=20264 http://downloadcenter.intel.com/Detail_Desc.aspx?lang=deu&DwnldID=20264

[idata]

did you notice anonymous cannot write to this forum now?

[idata]

HDMI blank screen, DVI OK

Windows 7 64 SP1

Fresh install

Config

====== Board ======

Intel CorporationDH67BLAAG10189-207BIOS BLH6710H.86A.0125.2011.0705.1517BIOS 05.07.2011 ====== CPU ======Intel CorporationIntel(R) Core(TM) i3-2100T CPU @ 2,50GHz2,5 GHzStepping 7 ====== RAM Kingston HyperX ====== ---- CHANNEL A DIMM1 ---- CHANNEL A DIMM1 DDR3 2048 MB 1333 MHz ---- CHANNEL B DIMM1 ---- CHANNEL B DIMM1 DDR3 2048 MB 1333 MHz ====== Onboard-Devices====== # Video Intel(R) HD Graphics Device # Ethernet Intel(R) 82579V Gigabit Network Device # Spind Realtek High Definition Audio Device Aktiviert ====== HDD ====== # INTEL SSDSC2MH120A2

Display is a Panasonic TX 37 LZD 85 F connected via HDMI. Native resolution 1920x1080 at 50 Hz

Installation went well, after installing the supplied graphic drivers from DVD and reboot, screen went blank after Windows 7 boot sequence. System is alive, just no picture.

BIOS Messages are displayed, entering BIOS OK, starting Windows is not.

I tried different HDMI ports, none worked. Booting into Windows Protected Mode works.

I installed/tried the following drivers:

Win7Vista_64_152113Win7Vista_64_15221Win7Vista_64_15224GFX_Vista64_Win7_64_8.15.10.2430_PV

Not one works correct. Same blank screen.

I tried differen HDMI cables, I tried a HDMI switch. I switched between EFI/normal in BIOS, I tried to fix HDMI in the BIOS. I changed frequencies. I unpowered/repoweed the display. No effect.

What works fine is using a DVI-HDMI cable. Every port on my display that does not work with HDMI-HDMI works fine connected to the DVI out of the mainboard.

When I install a driver with DVI-HDMI connected, the installation/switch of the drivers enables the HDMI-HDMI connect. When switching between display ports, I can see the desktop on both ports.

But after reboot everything works as nefore: Only DVI-HDMI delivers an image.

I tried different graphic cards with my screen. Two nVidia, one ATI/AMD. E.g. Zotac GT430 Zone. nVidia. They worked just fine.

Now please try to make your driver run aswell.

[idata]

2430 driver does not work for me... See my post.

[MSchm21]

Ok I'm not surprised because Robert told they are still working on it.

[idata]

Robert, If this is any consolation, I will send you my 2600k. It was installed at the end of march on a giga. ga67 ud3h b3 board.

Let me know

pisono.....

Follow-up to above:

Problems subsided when updated firmware:

Realtek - audio dated 7/1/11 mailto:R@.63 R2.63 (newer than Gigabytes)

intel graphics - 8.5.10.2430

Intel chipset - 9.2.0.1021

Still cannot play analog audio to receiver with HDMI connected to the TV.

Hope this helps

[idata]

new driver 15224 on DH67GD still have the problem.

BSOD for example drivers_irql_not_less ...

And this information show windows with the new BIOS and default (no) driver. If that will be help. Note: with old BIOS the system run without BSOD and default vga driver.

Problemsignatur:Problemereignisname: BlueScreenBetriebsystemversion: 6.1.7601.2.1.0.256.4Gebietsschema-ID: 1031Zusatzinformationen zum Problem:BCCode: 1000007eBCP1: FFFFFFFFC0000005BCP2: FFFFF88002CA5FF4BCP3: FFFFF8800318BEC8BCP4: FFFFF8800318B720OS Version: 6_1_7601Service Pack: 1_0Product: 256_1Dateien, die bei der Beschreibung des Problems hilfreich sind:C:\Windows\Minidump\062511-8049-01.dmpC:\Users\Microsoft\AppData\Local\Temp\WER-10140-0.sysdata.xmlLesen Sie unsere Datenschutzbestimmungen online:http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407 http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:C:\Windows\system32\de-DE\erofflps.txt

Problemsignatur:

Problemereignisname: BlueScreen

Betriebsystemversion: 6.1.7601.2.1.0.256.4

Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:

BCCode: 1e

BCP1: FFFFFFFFC0000005

BCP2: FFFFF8800719E9A0

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:

C:\Windows\Minidump\062511-7285-01.dmp

C:\Users\Microsoft\AppData\Local\Temp\WER-9266-0.sysdata.xml

Lesen Sie unsere Datenschutzbestimmungen online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407 http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:

C:\Windows\system32\de-DE\erofflps.txt