Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20623 Discussions

Unable to set resolution

idata
Employee
2,356 Views

Setup:

Windows 7 x64

ASRock H67M

Intel i3-2105 (HD 3000)

Connected via HDMI to a 55" Samsung LED TV.

I just went through a reinstall on my computer (replaced the harddrive with a new SSD). Prior to this, everything seemed fine. Resolution was running at 1080p and looked great.

After reinstalling Windows, I used Intel's automatic update website to locate the latest driver and downloaded it (15.28.7.2875). However, after installing this driver, I get no resolution options. It sets itself to 1280x720 - and that's it.

The Windows display option has the dropdown for resolution showing the 1280x720, but it is disabled so I cannot choose anything else:

Through the Intel Control Panel, NOTHING shows up at all. The dropdowns for resolution, color depth, refresh rate, etc are all completely empty - not even a default value:

I tried going to the "previous" driver (15.28.7.64.2867), but it does the same thing. I do not know what driver version I was on before the reinstall - it was probably old (2011-ish?).

Any ideas??

0 Kudos
17 Replies
idata
Employee
1,412 Views

I forgot to mention, if I uninstall the Intel drivers (so Windows falls back to Standard VGA), I can then select 1920x1080 (it is the recommended resolution in fact).

0 Kudos
NICHOLAS_F_Intel
Employee
1,412 Views

Hi Cabadam,

Can you provide for me two things please?

1. A copy of your dxdiag (Start -> Run -> dxdiag -> Save All Information) Just copy and paste that info here and I'll take a look at it.

2. A copy of your Intel® Graphics and Media Control Panel™ report? (Right click desktop -> Graphics Properties -> Options and Support -> Information Center -> "Save") Copy and paste this info here as well.

Thank you,

-Nic

0 Kudos
idata
Employee
1,412 Views

Nic,

Reports are below as requested. Let me know if I can provide any other information.

Thanks

DXDIAG

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

System Information

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

Time of this report: 12/10/2012, 21:23:06

Machine name: ACLAUSS-SERVER

Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120830-0333)

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: 04/27/12 17:24:37 Ver: 04.06.05

Processor: Intel(R) Core(TM) i3-2105 CPU @ 3.10GHz (4 CPUs), ~3.1GHz

Memory: 8192MB RAM

Available OS Memory: 7894MB RAM

Page File: 1043MB used, 14742MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: 120 DPI (125 percent)

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

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.

Sound Tab 3: 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 3000

Manufacturer: Intel Corporation

Chip type: Intel(R) HD Graphics Family

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_0112&SUBSYS_01121849&REV_09

Display Memory: 1760 MB

Dedicated Memory: 256 MB

Shared Memory: 1504 MB

Current Mode: 1280 x 720 (32 bit) (59Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: SAMSUNG

Monitor Id: SAM07C3

Native Mode: 1920 x 1080(p) (60.000Hz)

Output Type: HDMI

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

Driver File Version: 9.17.0010.2867 (English)

Driver Version: 9.17.10.2867

DDI Version: 10.1

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 9/28/2012 11:51:44, 12604416 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-4252-11CF-CA70-1821B7C2C435}

Vendor ID: 0x8086

Device ID: 0x0112

SubSys ID: 0x01121849

Revision ID: 0x0009

Driver Strong Name: oem3.inf:Intel.Mfg.NTamd64:iSNBD0:9.17.10.2867:pci\ven_8086&dev_0112

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 VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

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

0 Kudos
NICHOLAS_F_Intel
Employee
1,412 Views

Thanks for providing that information. The motherboard and manufacturer appear to be missing from the dxdiag info. Is this a custom system, or did you purchase it through an OEM? Can you provide the model/manufacturer of your motherboard to me as well?

Thanks,

-Nic

0 Kudos
idata
Employee
1,412 Views

Custom built - it's the ASRock H67M referenced in my initial post.

Thanks!

0 Kudos
NICHOLAS_F_Intel
Employee
1,412 Views

Oops. Yeah I forgot to check there, sorry about that.

Try using the Intel® driver they provide on their website; http://www.asrock.com/mb/overview.asp?cat=Download&os=Win764&Model=H67M H67 Motherboard Series Manufacturing - ASRock Inc.

Also, there is a BIOS update available that may help with this issue. Try this if the driver update doesn't solve the issue: http://www.asrock.com/mb/overview.asp?cat=Download&os=BIOS&Model=H67M H67 Motherboard Series Manufacturing - ASRock Inc.

Let me know how it goes!

-Nic

0 Kudos
idata
Employee
1,412 Views

Not a problem.

I... feel like I tried that, although I don't remember the specific result (tried a lot of things). I will try that this evening and provide an update.

I DID update the BIOS to the latest version already (prior to installing new Windows again).

0 Kudos
NICHOLAS_F_Intel
Employee
1,412 Views

The BIOS I linked are dated for the end of May, which makes it appear to be a newer one than the April version you have, the actual specified 2.10 version # they use on the website doesn't seem to mesh with anything outside the website though.

0 Kudos
idata
Employee
1,412 Views

Unfortunately, not much luck to report.

I noted there were actually two graphics drivers available on the ASRock website:

15.21.10.64.2291 dated 2/14/2011

15.26.1.64.2618 dated 5/10/2012

The earlier one (2011) gave me nothing at all. As soon as the installer did it's thing, I lost video, even before the computer rebooted. Guessing what the installer wanted, I hit the enter key twice, and sure enough it then rebooted. But still no video. TV just indicated "no signal". I had to go into Safe Mode to uninstall the driver.

On the later one (2012 version), they behaved like the ones I downloaded from Intel's website - the resolution option in Windows was disabled, and the Intel tool just showed empty dropdown boxes.

I did confirm that the BIOS you referenced is what I have installed. I went ahead and redownloaded and reflashed it, but I still see the April date in DXDIAG. I do not know why there is a discrepancy in the dates? Maybe the April date is an internal build date, and the May date is when it was actually posted to the public website????

0 Kudos
NICHOLAS_F_Intel
Employee
1,412 Views

Are you using any AV equipment in between your machine and your TV? Also, you'll want to test using a different HDMI cable, we've seen a rash of issues with them recently.

The BIOS date may be as you said, some of our drivers on the website show up the same way.

Let me know how it goes with another cable,

-Nic

0 Kudos
idata
Employee
1,412 Views

There is an AV receiver between the PC and the TV, although it was fine that way before I reinstalled Windows (wish I knew what driver version that was).

Redoing the cabling will mean pulling the entertainment center away from the wall - I'll certainly give that a try, but it may mean I don't get to it until this weekend. Unless I get really motivated this evening... we'll see!

Thanks

0 Kudos
idata
Employee
1,412 Views

Well, it took a bit of rewiring, but when connected directly to the TV it now allows me to select resolutions as expected.

Any idea why this was happening? I noticed in the Intel file I provided earlier, it listed out all of the resolutions under "Monitor Supported Modes:" and the DXDIAG did indicate that 1920x1080 was the "native" resolution. So it did know what it was supposed to do - it just wouldn't let me do it.

Also, I still think something is wonky with the drivers. Playback of Blurays under the 720 resolution was smooth, however now at 1080 it is choppy. I am using Cyberlink PowerDVD, and made sure the option for hardware acceleration is checked. 1080 played back smoothly before I reinstalled Windows.

0 Kudos
NICHOLAS_F_Intel
Employee
1,412 Views

As far as the primary issue goes; there have been a lot of issues recently with HDMI cables as well as AV equipment. You might consider visiting your AV manufacturer's website and see if there are any firmware updates available. I know Onkyo* HDMI/handshake issues have been showing up frequently on our forums as of late, and they have a simple method for updating their firmware, which sometimes resolves these issues.

To clarify on the second part; the playback of Blurays on 1080 being choppy, this is on your secondary display, or your primary?

Thanks,

-Nic

0 Kudos
idata
Employee
1,412 Views

It's a Yamaha receiver (I don't have the model number with me at the moment), but I did see there was a firmware update available. The notes for it didn't mention anything like this (it was all about 3D support), but I can definitely try and see if that helps.

Regarding the choppy playback - the TV is my primary (and only) display connected to this computer.

0 Kudos
idata
Employee
1,412 Views

Alright, took me a little while to get around to it (and to actually get the receiver upgrade done correctly).

The firmware upgrade on the receiver DID fix the problem with not being able to set the correct resolution. I now have everything re-wired to go through the receiver (like I originally had it) and I was able to then change the resolution to 1920x1080.

Unfortunately, the playback remains choppy at 1080 (not that the receiver firmware upgrade was really going to do much about that).

0 Kudos
NICHOLAS_F_Intel
Employee
1,412 Views

To confirm; is the choppiness at 1080 only experienced when going through the AVR?

0 Kudos
idata
Employee
1,412 Views

No - I first noticed the choppiness when you had me connect direct to the TV instead of going through the receiver. that was the first time I was able to set it to 1080. The choppiness stayed when I then went back through the receiver after upgrading its firmware.

0 Kudos
Reply