You can try the steps below in order to solve the issue you are having:
1. 1. Try a BIOS update to your Intel desktop board.
2. 2. Try to access the operating system with F8 in safe mode.
3. 3. Install the latest Chipset Software Installation Utility.
4. 4. Install the latest Graphics driver.
5. 5. Avoid the use of any HDMI connector or converter.
6. 6. Please install the latest driver of the HDMI TV or display.
You can find these files here:
i do all these things but result is same no signal and when i install 8600gts graphic card all is well no problem with graphic card hdmi.and when i remove
graphic card and plug in to motherboard hdmi slot same no signal after windows logo
my pc spec
core i5 2500
diplay Lg 32ld550
Did you enable the HDMI in the BIOS?
yes i enable the HDMI in the BIOS
Its not just him, I'm having the same kind of problems. I have an i3-2105 with the hd3000 graphics, a 23" hdmi monitor as my main screen and a 15" vga monitor as the secondary windows 'extended desktop'
With the previous "new" driver, I got a blue screen when windows booted and had to roll back to an older driver for the hd 3000. With the latest driver, windows boots and I see the windows splash screen on both monitors, then the signal gets dropped to the hdmi monitor. I see a mouse cursor on the 'secondary' vga connected unit but cant do anything because its not the primary screen.
When I unplug the hdmi monitor and reboot, windows comes up fine on the vga screen. Then I enable multiple monitors and extended desktop and the hdmi monitor lights up and works fine after that.
I havent tried a reboot yet though to see if it still works.
I have a new Z68 motherboard, and tried tweaking all the bios settings for multiple monitors and so forth, but no change in the boot behavior of lighting up the vga and not the hdmi. I havent tried booting hdmi only without the 15" vga screen.
This setup worked fine with the 3rd gen older driver, but as mentioned blue screened on the 2nd gen older driver, and has this improper handling of the dual screens/extended desktop on the current september revision.
As a followup, my reconfiguration survived a reboot and still works fine.
So the bad behavior is that the new driver ignores hdmi primary monitors in a dual monitor/extended desktop configuration until reconfigured while running the new driver and apparently even single monitor hdmi primary monitors since the original poster is having that problem.