I'm so glad I found this thread. I knew I was not alone but previous posts referred to tweaking with the Memory voltages.
Another gentelemen http://forum-en.msi.com/index.php?topic=138787.msg1038898 reported a specfic relationship with Intelgraphics.
(which makes sense given the crash happens in an Intel module.. :-) but he has aperentlyu swapped hardware and tested with many different configurations.
As soon as he replaced the video card with an AMD the problem was gone.
My setup is an Intel DH76CF board and I also use the integrated graphics over HDMI.
Before this board I had the DH57JG, in which I had never seen/experienced the specific crash.
As soon as I switched to this new board, the problem has been there a few times a week, sometimes days not, then 3 times in a row.
I don't have DVBLink, but I use 2 USB attached Anysee DVB-C tuners and their latest drivers.
My troubleshooting consited of:
- Swapping memory (since other threads indicated that might be the rootcause) but no luck
My first memory was Corsair (sorry no further details without opening the box)
- Alwas updating to latest BIOS and Intel Graphics driver
- Clean install with only the basics to use Media Center (tuners)
The crash mainly occurs when starting or switching TV channels (Live TV), but I have also seen this (less frequently though) when starting
recorded TV Shows. To me this proves that it is not related to the TV Tuner driver as that driver is not used when playing back recorded TV.
I believe it is HD noly, but cannot confirm, all the channels I use most are HD.
I have not seen this wth DVD/Bluray playback, or any other movie format.
Knowing that there are more people with different hardware configurations and the same crash, makes me stop researching memory.
(I was about to buy another memory kit, just to see if that would help.)
I'm hopefull that now this is documented on an intel board it will become more visibile and that a driver/bios update at some point will fix it.
I'm done trying reinstallations and different driver combinations, my hope is on drive and bios updates to fix this.
Happy to report more information from my system, as I will keep monitoring this thread.
I've test with 2 different types. My first was Corsair, and the second was a less known brand (not Kingstonn definitely).
Both consited of 2 modules, making up 4GB and had different speeds.
I would have to open up both systems to get more details, but I'm starting to be more convinced that it is not memory related.
Some people might have been able to solve it by tweaking memory, but the situation clearly needs better handing in the driver.
For completeness, here's the infor from my latest crash:
Pad naar toepassing met fout: C:\Windows\ehome\ehshell.exe
Probleem met handtekening
Naam van probleemgebeurtenis: APPCRASH
Application Name: ehshell.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bccdc
Fault Module Name: igdumd32.dll
Fault Module Version: 220.127.116.119
Fault Module Timestamp: 4e5e8fd6
Exception Code: c0000005
Exception Offset: 000f90d0
Versie van besturingssysteem: 6.1.7601.2.1.0.256.1
Extra informatie over het probleem
I tried to clock down memory, using lower speed to be more stable - no success (giving a bit more voltage also has no effect)
In every setting Memtest86+ does not find any Memoryfailures.
The Problem occuered even when using VGA Monitor (DVI to VGA), it's not HDMI specific!
It must be an Intel Integrated Video driver issue...
Oops, I had te revert back to 2509.
The crash in igdumd32.dll was, all of a sudden, all over the place (when switching channels)
Now, the new 2559 is not (yet) certified/released for my Intel board, but it is interesting to note that it enhanced the problem.
Maybe this can help Intel think in a certain direction.
I'm getting more and more convinced that this is an Intel driver issue.
After having been stable for a few days, this problem was in Crisis Mode yesterday
We were watching a prime-time-family-live-show. (Ok we didn't exactly watch live, started 30 minutes later to skip commercials..)
Well during playback of this program, which was stil recording, we had about 8 crashes in a row. Mostly while we were trying to skip the commercials.
I don't have to mention what this did to the Media Center confidence in the family....
And no, this was not an attempt from the advertisers to get me back to watching commercials...
What this might add to the scenario, is that it not only happens when switching channels.
- Switching Channels
- Starting Recorded programs
- Skipping/rewinding/fastforwarding in Recorded programs
All seem to be able to force the crash, and I think it is in HD Channels only, but as I only ever watch HD channels reguarly, I cannot fully confirm that.
Since Intel doesn't respond to this, I tried to log a Support call in an attempt to try to point intel to this thread.
I believe the thread has all information about this problem and it is experienced by multiple users.
But Intel doesn't support components individually through Chat/e-mail
Any other tips on getting Intel's attention to this?
Intel HD+ Intel drivers = Garbage
Tell your friends, stop buying this crap... they will learn or go out of buisness...( they have great Cpu's but their video graphics bite it )
Intel HD are basic garbage to see what goes on in your system, other than that they bite the big one...
Psst, Hey intel why does your competition make great video cards... maybe the bought ATI ... hint .... Intel HD compaired is garbage next to them.
Almost 2 weeks later and still silence from Intel, how do we activate them?
Saying that Intel Graphics is garbage doesn't help anyone and I'm sure Intel would have an interest in investigating such crashes.
Anyway, I've been able to rule out that it is tuner related, I'm also seeing it with playback of my 1080i AVCHD files from my Sony camera.
So maybe the problem description becomes simpler in that Windows Media Center (ehome) crashes in igdumd32.dll during playback of HD format files (Video Clips, Recorded TV, Live TV all the same).
Since a few of us more or less ruled out hardware (memory), it is not really up to Intel to come up with a suggestion what we could try.