hd4000 h61 BSOD or crash frequently on hdmi connect?

[idata]

I have an i3-3225/foxconn h61 based home theater PC running 24x7 on windows 7 64 and windows media center as my front end for live and recorded Tv.

I was running on the older drivers fine with my hdmi cable directly connected to my Panasonic plasma tv and the spdif connected to my older receiver.

I have since purchased a new Yamaha rx-473 receiver which can route HDMI and use the sound, and have had no end of issues since then.

Now when I power on the receiver I hear the sound windows makes when it detects new hardware a couple times in short succession. I estimate I have about a 30 or 40% chance of failure. When the tv comes up I now often either see a "windows media center has stopped responding" message, or the tail end of a BSOD dumping message. This machine is 100% stable any other time (although I anticipate hyperspin issues due to the pending mp4 known problems)

I have confirmed that the box is running just fine prior to me powering up by connecting to it remotely and either disconnecting right before powering up, or staying connected right through to see what happens. I have a hunch that it might be only when video is still being displayed (like when I left a tv channel going and just turned the tv on again later)

I am running the latest intel driver 9.17.10.2932 (previous versions had hdcp issues with live tv and made it unusable)

Minidumps look similar, here is the latest one:

Crash dump file: C:\Windows\Minidump\031713-6130-01.dmpDate/time: 3/17/2013 1:40:53 PM GMTUptime: 14:53:49Machine: Bug check name: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MBug check code: 0x1000007EBug check parm 1: 0xFFFFFFFFC0000005Bug check parm 2: 0xFFFFF80002EEB358Bug check parm 3: 0xFFFFF880009FE648Bug check parm 4: 0xFFFFF880009FDEA0Probably caused by:ntoskrnl.exeDriver description:NT Kernel & SystemDriver product: Microsoft® Windows® Operating SystemDriver company: Microsoft CorporationOS build: Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431Architecture: x64 (64 bit)CPU count: 4Page size: 4096

Bug check description:

This indicates that a system thread generated an exception which the error handler did not catch.

Comments:

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Also have a few event viewer entries as such below:

Faulting application name: ehshell.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd053

Faulting module name: audiokse.dll, version: 6.1.7600.16385, time stamp: 0x4a5be01e

Exception code: 0xc0000005

Fault offset: 0x0000000000067ca8

Faulting process id: 0x%9

Faulting application start time: 0x%10

Faulting application path: %11

Faulting module path: %12

Report Id: %13

Finally, here is my dxdiag as I know it may be requested:

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

System Information

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

Time of this report: 3/19/2013, 11:53:24

Machine name: TASTYHTPC

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130104-1431)

Language: English (Regional Setting: English)

System Manufacturer: To be filled by O.E.M.

System Model: To be filled by O.E.M.

BIOS: BIOS Date: 05/22/12 10:53:00 Ver: 04.06.05

Processor: Intel(R) Core(TM) i3-3225 CPU @ 3.30GHz (4 CPUs), ~3.3GHz

Memory: 8192MB RAM

Available OS Memory: 7640MB RAM

Page File: 3472MB used, 11804MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: 144 DPI (150 percent)

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Enabled

DxDiag Version: 6.01.7601.17514 32bit Unicode

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

DxDiag Notes

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

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Sound Tab 2: No problems found.

Input Tab: No problems found.

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

DirectX Debug Levels

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

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

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

Display Devices

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

Card name: Intel(R) HD Graphics 4000

Manufacturer: Intel Corporation

Chip type: Intel(R) HD Graphics Family

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_0162&SUBSYS_0DCA105B&REV_09

Display Memory: 1760 MB

Dedicated Memory: 512 MB

Shared Memory: 1248 MB

Current Mode: 1920 x 1080 (32 bit) (29Hz)

Monitor Name: PnP-Monitor (Standard)

Monitor Model:

Monitor Id:

Native Mode:

Output Type:

Driver Name: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32

Driver File Version: 9.17.0010.2932 (English)

Driver Version: 9.17.10.2932

DDI Version: 11

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 12/12/2012 16:42:36, 12615680 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-4222-11CF-9F78-C02DB7C2C435}

Vendor ID: 0x8086

Device ID: 0x0162

SubSys ID: 0x0DCA105B

Revision ID: 0x0009

Driver Strong Name: oem42.inf:Intel.Mfg.NTamd64:iIVBD0:9.17.10.2932:pci\ven_8086&dev_0162

Rank Of Driver: 00E02001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C

Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoPr...

[Fred_D_Intel]

Hi Kurt,

I recommend installing the latest motherboard BIOS and if the issue persists I recommend contacting the computer manufacturer in order to get more advanced troubleshooting steps for this issue.

[idata]

Hello Fred,

I do have the latest available bios for this motherboard already prior to the issue.

I have also worked with Foxconn directly on issues with getting the sound device to appear before as well. I resolved this only through rolling back and forth my intel drivers and making no other change in relation to theirs. When researching my problem before making my post I found a great number of users posting similar issues on other forums. It sounds like it all points back to problems with the intel audio over hdmi drivers. That is why i decided to post my question here. Unfortunately it does not look like the motherboard manufacturer would be able to help me there.

On a related note, is there an official Intel utility or method to ensure 100% clean driver removal when trying different versions to test?

[Fred_D_Intel]

Hi Kurt,

The best way to uninstall the graphics drivers is removing it from Programs and Features in Control Panel.

As additional troubleshooting step you can try connecting the home theater PC directly to the TV which is to check if the issue is being caused by the receiver or not.

[idata]

Thanks Fred,

I did uninstall and re-install the graphics card drivers from the control panel once more and install the fresh driver.

I have also had some observations and determined where the issue is. This is a windows media center machine and I watch Live tv. If I leave the machine tuned in to an mpg4 channel and turn the tv off when I come home from work later and turn on the tv is when it would crash and fail. I have successfully avoided crashes since my last post by changing that 1 thing.

HOWEVER

After reinstalling the driver and tweaking it again- I now just can't tune mpeg 4 channels at ALL. I get the driver error saying the display drivers are missing to play the content. I also have to un-maximize and maximize again to continue watching content from time to time - especially when I turn off media center to play hyperspin then return to media center and watch tv.

As the mpeg 4 issues have been a known issue by Intel for over 1 year and still not addressed I have instead decided to purchase an AMD graphics card and use that. I post my response here to hopefully help others looking to use their hd4000 in a media center build in the future. I chose the intel over an amd trinity build to save money on electricity which is now moot using external graphics. I will not make that mistake again and look towards AMD in my future. Maybe someday if intel can release a semi functional driver I would consider it again, but for now I feel burned.

Thank you for at least trying to help.