[Gratis Intel Display Adapter Management Tool
Betty Neyhart
I have a problem whose root can be seen in the advanced display settings. There are displayed wrong native resolution and frequency and therefore I have distortion and glitching of the picture as I have no simple way to correct the values.
What makes me suspicious is that I have none such problem with other machines with same version of windows 10 and HD graphics 3000 or HD Graphics 520 as well as with the problematic machine when only Microsoft Basic Display driver are installed. That would not be a problem if I would not need the better performance of the intel driver as also the audio output over the GPU. The problems only occurs when I install any recommended Intel driver for UHD Graphics 600 from the first across the last to the newest beta.
Am I getting it right that the wrong information in Advanced Display Settings are read over the Graphics driver from the Display? Then the root cause sertently would be the Driver. I mean, when the Microsoft basic Display Driver is working, it can not be any restriction in the BIOS?
3. Please provide a comparison screenshot/photo of the display difference using the Intel Graphics Drivers and the Microsoft Basic Display Adapter. Please include the a screenshot of the Advanced Display Settings, additionally; can you explain how do you know that the wrong resolution and frequency are shown? What are the expected specifications?
Regarding your question about how do I know that the wrong resolution and frequency are shown: Because on other maschine there are other (the same in every maschine) values in the Advanced Display Settings and it works, whereas, on the original setup that gives me the problem, the values are different to the other systems.
1. I also noticed that 1920x1080 is written in the report, but I would have blinders on to overlook that I simply had to switch the resolution. The problem is, there is no other working resolutions or modes available as you can see in the Pictures "IMG_1684.JPG and IMG_1685.JPG". The other available resolutions or modes have the same problem.
2. Based of the above, why should it be a limitation on hardware, so I ask you again to explain to me: how could Microsoft basic Display Adapter possible work when there would be any limitation on hardware?
3. See #1, i do not see how I should set the resolution your driver is recognizing but not making available
5. Of course I will try to reporting this to the manufacturer (OEM) but they will have questions, and before I did not ruled out (with explanation) why it works without the driver but not with it, I will not attempt so. I have already updated anything the OEM provides at this point of time.
Please keep in mind that the Microsoft Basic Display Adapter only works with the basic functions on the system, it will not enable full integrated graphics card (iGPU) features. The Intel graphics driver will enable full iGPU features and ports (included all by OEM design).
Also, you can see that like your other system that uses HD 520, the same driver package will work with that and other systems, therefore; it is not a driver problem. Check under This download is valid for the product(s) listed below:
1. The Brand of the Specific Display that I want to use is a WAVESHARE 16103 5.5inch HDMI AMOLED 1080x1920 with the HDMI interface chip Toshiba tc358779XBG but I now also have (with the same problem) a DFROBOT DFR0524 5.5'' HDMI OLED-Display with the HDMI Interface chip Lontium LT6911C. When everything is working I want to solder one of them directly together.
2. I use the provided short 20cm generic brand HDMI cable (with UHD 600 and HD 520), but I also tried a Apple MC838ZM/B and can confirm that both of them are working with my Samsung TV and do not work with either of the displays in combination with the critical system. What else I noticed is that although I tried to find other PCs with intel graphic that have native HDMI ports, the protocol of the HD 520 for example reports connection over Displayport anyway, that was also the type of connector IS used with the HD 3000 (5m Display port to HDMI adapter cable). So maybe it is a HDMI (software) Problem, as it sems to work with Display Port.
NO, I did bypassed the inability of your driver (no, i will not stop saying this till somebody explained to me why it is that the Microsoft Basic Display Adapter is capable of showing a picture and Intel Driver is not). I ruteforced the problem by reading the EDID values when Intel Drivers are not installed and it is working fine with Microsoft Basic DIsplay adapter, then installed the most recent Intel drivers, deleted the current EDID entries and entered the EDID values read out before with some further tweaking.
Please be aware that the Intel graphics controller reads the EDID from the monitor directly and does not read Windows registries for that, then the Intel graphics driver will enable all the features and capabilities from the port and graphics card, that is why the output is different.
As we confirmed the driver works (tested with different systems), we strongly believe this problem is not Intel related. As we advised before, you need to work with the OEM since you might need a customized driver from their side.
Hello,
Having exactly same issue. Even when using adapters like DisplayLink (DL-3100) that physically do not rely on hardware and still having same issues, on boot display works, but when driver kicks in display stops working. Will there be any plans to support/fix that?
Thanks, Julius
I came here to confirm the same problem : Amoled 5.5 that has the basic mode set to 1080 x 1920 and 60hz is incorrectly recognised by win 11 minipc LarkBox with uhd 600 while it works flawlessly on other windows machines (and linux arm sbcs for that matter).
The funny thing is while the intel graphics command center seems to corretly detect the display device with the correct mode , buut you cant really do anything with this knowledge.
@Ksanto can You post the step by step solution to Your problem?
You need to uninstall the driver to fall back on the Microsoft Basic Display Adapter to read out the then flawless recognised EDID with "AW EDID Editor". Write them down for later or as I did, make a picture.
Now you need a second display and connect both displays to the PC. Install the latest drivers and Custom Resolution Utility, then make a custom resolution in the "Intel Graphic Controll Panel" for the Display. After that go to "Coustem Resolution Utilety" to delet all standart resolutions and extensionblocks for the mini Display and leave only the costem resolution. At this point I'm not really sure if I have tweaked the values further more.
Ive got the same exact settings when my oled display is connected to the uhd 600 and its still glitched, so this isnt it.
Intel Graphics Command Center is adamant that this settings for custom resolution is not supported either by the display or the adapter.
Also Could You share the screen of Your Custom Resolution Utility setup with this particular oled ?
You have to make sure that you delete intel software completely every time you start over, maybe you have to delete the registry entries for the EDIDs additionally and make sure to delete everything except the one custom resolution in the Custom Resolution Utility.
I remember that I deleted the wrong resolution many times in my 3-4 attempts to get it right, because i hat to setup the pc 3-4 times to resolve other errors. Last time was at least 2 yars ago. When I rember correctly now, you could bypass the step with Intel Graphics Command Center completly an only user the Coustem Resolution Utilety, it was only more simple to use it for any reason at some point.
Im not mad at anybody sorry if I came that way.
Im just curious that established cpu and gpu manufacturer fails so hard when confronted with fhd display turned 90 degrees.
Also why it is so hard to make the igpu work when raspberry pi with its poor powervr gpu for ants is working out of the box with this setup.
EDIT:
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
The Lenovo ThinkSystem ST50 V2 single-socket tower server is an entry level server ideal for small businesses, home offices, retail, educational institutions and branch offices. The server is based on the Intel Xeon E-2300 Series processors, formerly codenamed "Rocket Lake".
This product guide provides essential presales information to understand the ThinkSystem ST50 V2 server, its key features and specifications, components and options, and configuration guidelines. This guide is intended for technical specialists, sales specialists, sales engineers, IT architects, and other IT professionals who want to learn more about the ST50 V2 and consider its use in IT solutions.
The Lenovo ThinkSystem ST50 V2 single-socket tower server is an entry level server ideal for small businesses, home offices, retail, educational institutions and branch offices. The server supports one Intel Xeon E-2300 Series processor (formerly codenamed "Rocket Lake") or Intel Pentium ("Comet Lake Refresh") and up to 128 GB of 3200 MHz TruDDR4 ECC memory.
The ThinkSystem ST50 V2 offers enterprise-class reliability features such as error correcting code (ECC) memory, the onboard RAID controller, and enterprise-class hard drives and network adapters at an affordable price. The server has Intel Active Management Technology (AMT) built-in, along with support for industry-standard management tools. The ST50 V2 runs a wide range of server operating systems and is quiet enough and small enough to fit under or beside an office desk.
795a8134c1