I am not sure if issue is resolved but i had the same problem on my 2500K and Gigabyte GA-H67MA-UD2H-B3.
I am using Display port as primary display but when connecting HDMI i had bsod.
I had a lates drivers but error still appears.
Someone suggests to downgrade drivers, THIS HELP ME !!! hdmi works, bsod disappears.
Downgraded to 2279, issue resolved. Still unable to use newest driver without BSD when using HDMI on external HDTV using Windows 7.
FYI, the older driver is here (for 64 bit Vista/7 systems):
Just adding tp this new thread that I experience this problem. With any driver other than the supplied driver from ASUS or the new 2401 without immediate BSOD upon connecting HDMI. However when using 2401 I am unable to use 1080p 23hz or 59hz. After applying changes the resolution changes 1024x768. Robert_U have you been able to replicate the issue in your lab?
I cannot comment on the long term stability of the 2401 driver because I require those refresh rates for my setup so I had to once again roll back to the asus supplied driver.
Darth,, what model TV are you connecting to?
I should note that 23 and 59 work fine on the 2219 driver found on ASUS's web site and the mobo CD.
All drivers and windows updates installed without issue. System runs fine on standard vga drivers (tried DVI and HDMI) but reboots on "starting windows" loading screen after installing intel graphics drivers. Just trying older drivers that the two available from download centre.
Fails on: DVI & HDMI
Tried drivers from: Win7Vista_64_15221 & Win7Vista_64_152113
We are looking at this issue now, stay tuned.
Okay, a bit more testing completed.
Reinstalled Windows 7 (64-bit) from scratch, this time without SP1. Installed drivers 2291, and I can select 23 Hz in the menu. However, according to MPC-HC my refresh rate is still 24 Hz, even though I disabled UAC, and I got at double frame every 40 seconds or so. Do I need to change anything else to achive something closer to 23.976 Hz? From what I understand, disabling UAC should be the key to success and epic win.
When 23,976 Hz is supported? Can wait 3 weeks but not another 3 months. Then need another graphics card.
this mode has never been correctly supported by Intel; according to web reviews from trusted sources, you could get almost 23,... Hz if you turned off UAC; otherwise it's just another name for 24 Hz; check e.g. here http://www.missingremote.com/review/intel-sandy-bridge-core-i5-2500k-and-dh67bl-motherboard for "24p"; if I remember correctly, someone reported here http://communities.intel.com/thread/20439?start=0&tstart=0 that with latest "testing" driver (2401), there's no 23,... even with UAC turned off
What is the current staus for the fix for SandyBridge 23.976Hz output? There wa s lengthy discussion on the subject here:
Which was locked because it was "unweildy".
The issues for 23.976 remain.
Robert can you give us any update. DH67GD Intel MB. Regardless of whether I choose 24 or 23 Hz, I get 24Hz. I have a high end scaler that reports theinput frequency to 3 places, correctly. Other devices reflect correct settings. I do not have trouble with 60Hz (59.9xx) , it functions correctly.
Becase of the number of people reporting BSOD on HDMI out, I'm afraid to update the video drivers until you think ther eis a fix. Mine does not BSOD, but it also does not handle the frequency correctly.
still tuned, because product already bought..
2476 has still the same problem (among others), bad work guy, it's september now..
Five months later: is the 23,976 Hz issue fixed or not? Can anyone test it for me? Use the newest driver 22.214.171.1249. Thanks!
well, I've experienced 2 issues in past:
1.) with all these "testing" drivers, all modes with these frequences defaulted to (as far as I remember) just 1024x768x60Hz
2.) with (otherwise buggy in different way) driver provided by Asus these frequences worked as expected (= TV correctly reported the expected mode parameters) except for the fact that I got 24 (exact) and 60 Hz when measured by MPC-HC instead of correct ones
2509 driver solved the first issue, the second still persists (but doesn't bother me considering the fact I finally have at least 1 driver that doesn't behave platitudously obviously buggy)
So it is not fixed as expected.