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

HD 4000 No longer powering high resolution monitor

fbunn
Beginner
4,607 Views

After updating to windows 8.1 and installing the new intel driver for HD 4000, I can no longer run a custom mode of 2560x1440 at 55hz over hdmi.

This worked fine for months, but now I get the bandwith exceeded error in custommodeapp.exe

Please help, but please don't tell me HDMI 1.4 does not supply enough bandwidth, because I know it does. Not only does it say so in the literature, but I was doing it flawlessly for a long time, until the new drives came out.

Is there another version of custommodeapp.exe that I can use, that won't limit me?

Thanks

0 Kudos
12 Replies
Kevin_M_Intel
Employee
2,354 Views

Hi bunnyfluffy,

At this point the only Graphics controller that supports resolution 2560x1440 is the graphics controller included on 4th generation processors. The 3rd generation processors with a HDMI connection can get up to 1920x1200 and it is possible to get the 2560x1440 using Display Port only.

The Custommodeapp.exe, as you know, allows user to create custom resolutions if the requirements are met only.

You can check the information at the following link:

http://software.intel.com/en-us/articles/3rd-gen-hd-graphics-quick-reference-guide http://software.intel.com/en-us/articles/3rd-gen-hd-graphics-quick-reference-guide

0 Kudos
fbunn
Beginner
2,354 Views

On that page you linked to, where does it say that 3rd gen can't output 2560x1440? Please show me, because I've read that page 3 times. That page advertises HDMI 1.4, which DOES have enough bandwidth transmit that resolution.

Again, I was running the monitor happily, until intel put a limit in the software. Maybe the engineers writing the driver mistakenly believed the same thing as you, but it's clear a mistake has been made.

All I'm asking for is for intel to remove the limit in the software on their next driver release. There is no reason to throttle my HDMI bandwidth, especially when the page you linked to advertises HDMI 1.4.

0 Kudos
fgerb
Beginner
2,354 Views

Hi Kevin, I am having the same issue since I upgraded to windows 8.1.

I was happily powering a Catleap Q271 monitor at 2560x1440 over both HDMI and VGA from my Samsung Chronos 7 Laptop with Intel HD4000 gfx + dedicated 8870M radeon Card. I believe it's the HD4000 that is outputting video to the ports?

I had created my custom resolutions in the "Intel Graphics and Media Control Panel" program. This program seems to have been uninstalled during the Win 8.1 upgrade (windows thinks the program is installed but the exe is missing). I am unable to select a custom resolution in the "Intel(R) HD graphics" program.

I used the following settings: http://www.notebookcheck.net/fileadmin/_migrated/pics/2560x1440_intel_hd_graphics_4000_ivy_bridge.png http://www.notebookcheck.net/fileadmin/_migrated/pics/2560x1440_intel_hd_graphics_4000_ivy_bridge.png

I installed Win8.1 tonight and the best it can muster is 1920x1200 over HDMI (i still get 2560x1440 over VGA but it does not look as sharp as I was getting over HDMI)

Please can you talk to your engineers about this since I was viewing my display at 2560x1440, and in fact i was able to run both the VGA and HDMI at the same time from this laptop and both were 2560x1440.

See the enclosed screenshot of VGA set to 2560x1440:

So, as you can see from both image links in this post, people are getting 2560x1440 from these cards over HDMI and VGA, despite what the official specs are saying.

0 Kudos
fbunn
Beginner
2,354 Views

Kevin,

As you can see, this was not a fluke. Many other people have reported the same thing on other sites.

The software is limiting the resolution for no reason. Please, can you help us to remove the limt?

Thanks

0 Kudos
Kevin_M_Intel
Employee
2,354 Views

Hi All,

I would like to confirm more information about this. I will need the following:

  1. Post the dxdiag report here.
  2. Let me know if you are using a direct connection or video adapters.
  3. Make sure to install the monitor drivers in the system before posting the dxdiag report.
0 Kudos
fgerb
Beginner
2,354 Views

Hi Kevin, thanks for taking the time to help us on this.

I don't know about bunnyfluffy, but I have solved this issue and I am now viewing this website at 2560x1440 resolution over HDMI. You guys need to give your hardware more credit

I was able to add the custom resolution by following this article:

http://www.intel.com/support/graphics/sb/CS-029478.htm# HDGFX http://www.intel.com/support/graphics/sb/CS-029478.htm# HDGFX

I used the C:\Windows\System32\CustomModeApp.exe utility using the following settings:

Width: 2560

Height: 1440

RefreshRate: 55

Timing Standard: CVT-RB.

and restarted my laptop. The custom resolution was then available by right clicking the desktop and selecting the standard windows resolution menu item.

 

thanks!

0 Kudos
fbunn
Beginner
2,354 Views

Hi Kevin,

Here is the report:

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

System Information

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

Time of this report: 12/6/2013, 21:04:53

Machine name: BunnyFluffy

Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_gdr.130913-2141)

Language: English (Regional Setting: English)

System Manufacturer: SAMSUNG ELECTRONICS CO., LTD.

System Model: 700Z7C

BIOS: P03ABP

Processor: Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz (8 CPUs), ~2.4GHz

Memory: 8192MB RAM

Available OS Memory: 7814MB RAM

Page File: 4871MB used, 5357MB available

Windows Dir: C:\WINDOWS

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.03.9600.16384 64bit Unicode

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

DxDiag Notes

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

Display Tab 1: No problems found.

Sound Tab 1: 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 Type: Full Device

Device Key: Enum\PCI\VEN_8086&DEV_0166&SUBSYS_C0CC144D&REV_09

Display Memory: 1792 MB

Dedicated Memory: 32 MB

Shared Memory: 1760 MB

Current Mode: 2560 x 1440 (32 bit) (41Hz)

Monitor Name: Dell U2713HM (Digital)

Monitor Model: DELL U2713HM

Monitor Id: DEL407E

Native Mode: 2560 x 1440(p) (59.951Hz)

Output Type: HDMI

Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32

Driver File Version: 10.18.0010.3304 (English)

Driver Version: 10.18.10.3304

DDI Version: 11

Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1

Driver Model: WDDM 1.3

Graphics Preemption: DMA

Compute Preemption: Thread group

Miracast: Supported

Hybrid Graphics GPU: Integrated

Power P-states: Not Supported

Driver Attributes: Final Retail

Driver Date/Size: 9/9/2013 09:35:44, 12081664 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-4226-11CF-A07B-C1E0B4C2C435}

Vendor ID: 0x10DE

Device ID: 0x0FD1

SubSys ID: 0xC0CC144D

Revision ID: 0x00A1

Driver Strong Name: oem46.inf:5f63e5341859ec8c:iIVBM_w81:10.18.10.3304:pci\ven_8086&dev_0166&subsys_c0cc144d

Rank Of Driver: 00DA0001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C

DXVA2 Modes: DXVA2_ModeMPEG2_IDCT DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_VLD DXVA2_ModeVC1_IDCT DXVA2_ModeWMV9_IDCT DXVA2_ModeH264_VLD_NoFGT

Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

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

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

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

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

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

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

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

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

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

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

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

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

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

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

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

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

{335AA36E-7884-43A4-9C91-7F87FAF3E3...

0 Kudos
fbunn
Beginner
2,354 Views

Hi Kevin,

I've uninstalled all other driver installs, down the the generic windows driver, then installed the version you linked to, version 3345.

How should I proceed?

I would like to note that the previous poster and I have the same Samsung Series 7 laptop, and his is working now.

0 Kudos
Kevin_M_Intel
Employee
2,354 Views

Hi bunnyfluffy,

At this point since you have done all steps provided before, I recommend you testing a different cable in case it is causing this issue or contact the computer manufacturer so you can install their latest driver.

0 Kudos
fbunn
Beginner
2,354 Views

Kevin,

Can you request that the next driver remove the limit? I have tried different cables.

Since this only occurred to everyone after the 8.1 upgrade, it has to be a software problem.

If you think of anything else, please let me know.

Thanks for your help

0 Kudos
Kevin_M_Intel
Employee
2,354 Views

Hi bunnyfluffy,

I will pass the information to the proper department for future considerations.

0 Kudos
Reply