Intel HD 630 - Activation of second monitor on HDMI not working

[BRude2]

Hello,

I have a simple 10" Touchscreen Display connected via HDMI as second monitor to my PC. The display is detected but it seems, not fully.

With recent driver versions, I can choose it in several settings, but it is not activatable. There is no resolution selectable, neither in the Intel settings nor in the Windows settings. It seems, the supported information of the display via EDID is not satisfying enough for the graphics driver.

But with older driver version (154518.4664) it is working.

I'am currently using Win10 (64bit) 1607 (14393.2551, LTSB 2016) on a Core i3-7100T with Intel HD 630 graphics for this.

Here the EDID dump of the connected display:

*****************************************************************

Active : No

Registry Key : DISPLAY\LGD0345\4&25dd50e0&0&UID54942464

Manufacture Week : 0 / 2011

ManufacturerID : 58416 (0xE430)

ProductID : 837 (0x0345)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.4

Display Gamma : 2.20

Image Size : 409.5 X 409.5 cm (228.0 Inch)

Maximum Image Size : 22 X 14 cm (10.3 Inch)

Maximum Resolution : 1280 X 800

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : Yes

Supported Display Modes :

1280 X 800 60 Hz

*****************************************************************

On another PC with HD4600 series graphics it is also working properly with driver version (153631.4414).

Later Versions not tested on this.

On PCs with dedicated graphics from AMD it works. On Raspberry PI with Linux or Win10 IoT it works also.

Please help me to be able to use the latest driver version. Or can I continue to use the old version without hesitation?

By the way: with the latest driver for Intel HD 630 (V 25.20.100.6326), even the Intel graphics settings crash when the display is connected.

Message was edited by: Benjamin Rudert&# 13; &# 13; I've added some diagnostic outputs. But these are made under Win10 version 14393.2273 (same behavior in this topic).&# 13;

[idata]

Hello bruderT

Thank you for posting in the Intel® community. The Intel® HD Graphics 630 driver version 25.20.100.6326 supports:

• Microsoft Windows* 10-64 - Fall Creators Update
• Microsoft Windows* 10-64 - April 2018 Update
• Microsoft Windows* 10-64 - October 2018 Update

This information could be found in the readme notes on the download link. Reference link: https://downloadcenter.intel.com/download/28240/Intel-Graphics-Driver-for-Windows-10?product=98909 https://downloadcenter.intel.com/download/28240/Intel-Graphics-Driver-for-Windows-10?product=98909 Looking into the configuration of your system you are currently running Windows® 10 64 bit build 14393 (version 1607 Redstone 1, anniversary update) I would recommend testing the behavior with a supported Windows® version on the system as mentioned previously. Please let me know the outcome, by the way, what is the brand and model of the display that is presenting this behavior? Hope this helps. Regards,Leonardo C.Intel Customer Support TechnicianUnder Contract to Intel Corporation

[BRude2]

Hello,

Thank You for your reply.

Yes, I could test the newest Windows version on that PC, but that is no option. The PCs where the display must work on are supplied by OEM. And we do not use the LTSB version of Windows without any reason.

So, please can you tell me, which would be the most recent driver, supporting our Windows version? (Windows® 10 64 bit build 14393 (version 1607))

If there are such big differences in compatibility, perhaps the OS selector at your driver search website should be more filigree (to select different versions of Windows 10).

Edit: Sorry i forgot to answer your Question: It is an Joy-It 10,1" display with IPS Panel from LG ( https://www.joy-it.net/en/10-touchscreen-display/ https://www.joy-it.net/en/10-touchscreen-display/ ) .

Regards,

B. Rudert

[BRude2]

Perhaps this Problem bases on the missleading EDID information of the display?!

Here the binary dump:

00000000 00 FF FF FF FF FF FF 00 30 E4 45 03 00 00 00 00 ........0.E.....

00000010 00 15 01 04 90 16 0E 78 02 E8 87 96 5A 55 95 28 .......x....ZU.(

00000020 22 51 55 00 00 00 01 01 01 01 01 01 01 01 01 01 "QU.............

00000030 01 01 01 01 01 01 4C 1D 00 EC 50 20 18 30 40 30 ......L...P .0@0

00000040 57 00 D9 88 00 00 00 1B 16 12 00 80 50 20 16 30 W...........P .0

00000050 FF FF FF FF FF FF FF FF 00 1B 00 00 00 FE 00 43 ...............C

00000060 33 47 52 4E 80 31 30 31 57 58 31 0A 00 00 00 00 3GRN.101WX1.....

00000070 00 00 41 32 A8 00 00 00 00 01 01 0A 20 20 00 9A ..A2........ ..

I can imagine that these FF in address 50 to 57 are not valid .

This causes these abnormal values regarding the image size. (4095x4095mm)

Does the graphics driver use this values? Perhaps it disables the display in cause of this?

[idata]

Hello bruderT

Thank you for the information and for the feedback provided I am going to share it with the appropriate department. You could test on the system the Intel® graphics driver version 15.47.02.4815 (https://downloadcenter.intel.com/download/27199/Intel-Graphics-Driver-for-Windows-15-47-?product=98909 https://downloadcenter.intel.com/download/27199/Intel-Graphics-Driver-for-Windows-15-47-?product=98909). Allow me to share with you the EDID Reader link (http://www.edidreader.com/ http://www.edidreader.com/) to phrase the binary report that you have shared for better understanding. 00 FF FF FF FF FF FF 00 30 E4 45 03 00 00 00 0000 15 01 04 90 16 0E 78 02 E8 87 96 5A 55 95 2822 51 55 00 00 00 01 01 01 01 01 01 01 01 01 0101 01 01 01 01 01 4C 1D 00 EC 50 20 18 30 40 3057 00 D9 88 00 00 00 1B 16 12 00 80 50 20 16 30 FF FF FF FF FF FF FF FF 00 1B 00 00 00 FE 00 4333 47 52 4E 80 31 30 31 57 58 31 0A 00 00 00 0000 00 41 32 A8 00 00 00 00 01 01 0A 20 20 00 9AAfter phrasing the EDID on the timing bitmap there is no resolution supported according to the report. You could also verify with the display manufacturer for firmware updates available. Hope this helps. Regards,Leonardo C.Intel Customer Support TechnicianUnder Contract to Intel Corporation

[BRude2]

Hello,

After phrasing the EDID on the timing bitmap there is no resolution supported according to the report.

You are right. But 1280x800 is no very common resolution. So it cannot be defined by the default resolution bitmap. I guess, that's why the manufacturer defines its supported resolution only by detailed description.

Nevertheless, I've contacted their support team to clarify this.

Furthermore: The driver version 15.47.02.4815 does also not activate the display.

Regards,

B. Rudert

[idata]

Hello bruderT

Thank you for the information.You could test the following Intel® graphics driver versions:

• Intel® Graphics Driver 15.45.19.4678
  • https://downloadcenter.intel.com/download/26836/Intel-Graphics-Driver-for-Windows-15-45-?product=98909 https://downloadcenter.intel.com/download/26836/Intel-Graphics-Driver-for-Windows-15-45-?product=98909
• Intel® Graphics Driver 15.46.02.4729
  • https://downloadcenter.intel.com/download/26941/Intel-Graphics-Driver-for-Windows-15-46-?product=98909 https://downloadcenter.intel.com/download/26941/Intel-Graphics-Driver-for-Windows-15-46-?product=98909
• Intel® Graphics Driver 15.46.05.4771
  • https://downloadcenter.intel.com/download/27058/Intel-Graphics-Driver-for-Windows-15-46-?product=98909 https://downloadcenter.intel.com/download/27058/Intel-Graphics-Driver-for-Windows-15-46-?product=98909

NOTE: bear in mind that these Intel HD graphics drivers are generic drivers (not customize for your system) I would also recommend contacting the Original Equipment Manufacturer (OEM) for Drivers availability since each OEM would customize the drivers for their systems; in addition, you could present this behavior for more inside on their side. Hope this helps. Regards,Leonardo C.Intel Customer Support TechnicianUnder Contract to Intel Corporation

[BRude2]

Hello,

Thank you furthermore for you support.

The 3 versions of driver software you've suggested are working.

By the way, we have experienced that the graphic cards electronics seems to be very sensitive to the quality of the cables. Cables that we have used in other thousands of scenarios without any problems cause the graphics here to refuse output to the connected display.

But with the right "exquisite" cable, it works out fine.

But this electronical issue could also be a topic of the OEM. so i think we should not further discuss this here. Unless you have any clues there.

But nevertheless and despite the best cable, the latest driver doesn't want to recognize the display correctly.

Perhaps you and/or your team can also retrace the special EDID. So apart from the cable I think the compatibility problem has it's roots in the EDIDs data.

Regards,

B. Rudert

[idata]

Hello bruderT

Thank you for the information. In this case, the diver 25.20.100.6326 might not be working due to of the OS build as mentioned previously (OS supported version), in reference of the EDID data we have to take in consideration the system design/components (motherboard, cable, display) comparability. Hope this helps. Regards,Leonardo C.Intel Customer Support TechnicianUnder Contract to Intel Corporation

[BRude2]

Hello,

ok, thank you. I think we're coming to the end of this.

There's just one more thing. Can you please confirm to me that the EDID information of the display is okay. I just need to know that so that I know if I need to go back to the manufacturer.

Regards,

B. Rudert

[idata]

Hello bruderT

Thank you for the information. The display is the one that provides the EDID information to the system, some data is missing this might be due to a miscommunication/comparability on the configuration used. Hope this helps. Regards,Leonardo C.Intel Customer Support TechnicianUnder Contract to Intel Corporation

[BRude2]

Hello,

come on. "some data" , "might be" ? Can you please be more specific? I'm not a gamer, I'm a developer.

Regards,

B. Rudert

[idata]

Hello bruderT

I think it would be better to share with you a EDID report from a DELL™ display model P2314Ht that is working properly:00 FF FF FF FF FF FF 00 10 AC 9A 40 4C 48 42 41 33 19 01 03 0E 33 1D 78 EA E5 95 A6 56 52 9D 27 10 50 54 A5 4B 00 71 4F 81 80 A9 C0 D1 C0 01 01 01 01 01 01 01 01 02 3A 80 18 71 38 2D 40 58 2C 45 00 FD 1E 11 00 00 1E 00 00 00 FF 00 37 52 31 4B 33 35 43 4A 41 42 48 4C 0A 00 00 00 FC 00 44 45 4C 4C 20 50 32 33 31 34 48 0A 20 00 00 00 FD 00 38 4C 1E 53 11 00 0A 20 20 20 20 20 20 00 A9 You could refer to the EDID reader link provided previously to phrase the data Regards,Leonardo C.Intel Customer Support TechnicianUnder Contract to Intel Corporation

[idata]

Hello bruderT

I was checking your case and would like to know if you need further help. If so, please do not hesitate in replying back. Regards,Leonardo C.Intel Customer Support TechnicianUnder Contract to Intel Corporation

[BRude2]

Hello,

No, i'm satisfied with the old drivers for now. But if you want to get to the bottom of this, i will support this, to get better driver support for our solution in future.

Otherwise we ...

... simply remain with kind regards.

B. Rudert