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

HD 3000 driver forced subpixel antialising after update to 9.x version

PVone1
Beginner
10,413 Views

I have Lenovo X220 notebook (Core i5, HD 3000), Windows 7 x64 SP1. I can't stand any kind of antialiasing so I use Windows Classic theme and have ClearType disabled in Performance Options.

After video driver update from version 8.15.10.2769 to 9.17.10.2843 (Lenovo specific versions) I noticed the black text on grey background is blurry and some kind of antialiasing (different than the Windows one) was applied after the update. I couldn't find any way to disable it, no such option in Intel Graphics panel. The only way to get rid of it was rollback to old 8 version. Notice I'm talking about Windows desktop, not a 3D games.

Is there any solution for it (at least edit a value in registry) ? I don't want to use older (possibly buggy and vulnerable) version but this kind of forced antialiasing is blocking issue for me. Attached screenshot (poor image quality) shows the difference, it needs a fullscreen view. Notice the forced red "ghosting" on the right edge of black pixels.

More observations. It affects all output on the notebook display, not a text rendering only. For example BMP or PNG image with screenshot of Start menu without antialiased text also looks blurry now. On the other hand digital output to external monitor is not affected (not blurry). It seems as the new driver set some kind of hardware antialiasing (or less sharpness) in the notebook display controller, is it possible ? I've tried all advanced Intel Graphics panel settings and nothing helped.

The change (non-blurry to blurry text) happens in the middle of a new driver installation, even before restart.

Thanks.

0 Kudos
49 Replies
PVone1
Beginner
3,901 Views

Suppose that Lenovo will not solve it and the generic driver does not work (on screen display and other features), what else to check ? Is there any detailed list of changes made to the driver between these two versions ? The issue goes beyond Windows software antialiasing (ClearType) that can be easily detected and explained by making a screenshot (PrintScreen) and zoom it (paste and zoom in MS Paint). It is rather close to a hardware based sharpness control used in some desktop monitors.

In other words, is there any antialiasing technology added to the Intel kernel driver 9.x version that might cause such behavior (no 3D applications) and it is independent of Windows ClearType ?

Can I enable any diagnostic debug log to help resolve it ?

0 Kudos
DArce
Valued Contributor III
3,901 Views

Could you please confirm what happens when you test our generic driver?

We may not establish what would be different from the drivers provided by your OEM and the generic drivers we provide. What we may provide is the release notes of the drivers we provide and that is available in our download center.

0 Kudos
PVone1
Beginner
3,901 Views

I've tested latest generic Intel graphics driver 15.28.15.64.3062 (9.17.10.3062) and the issue is exactly the same. The interesting part is that it seems to be more like a hardware setting of the internal display controller since it affects displaying text on PNG images (screenshots) as well but does not affect digital output to external monitor. It reminds me sharpness hardware setting available on some LCD monitors that allows to make whole display look blurry. Someone calls that "enhanced readability" but for me such feature is killing Again, please do not confuse it with ClearType, it makes blurry font rendering only but this issue affects everyting that is displayed. Aero is disabled.

 

Note that using the Intel generic driver causes Lenovo brightness control and on screen display to fail but this is as expected, that's why there is the Lenovo OEM specific driver.

I also exported content of registry HKEY_CURRENT_USER\Software\Intel\Display for both 8.x and 9.x driver versions to compare them. The only interesting difference I found is:

[HKEY_CURRENT_USER\Software\Intel\Display\igfxcui\Media]

"EnableFMD"=dword:00000001

The value is '00000000' for the 8.x one (that one without the issue) and 00000001 for 9.x one (the one having the issue).

I have installed all Windows updates except http://support.microsoft.com/kb/2670838/en KB2670838 that is known to have stability issues.

0 Kudos
DArce
Valued Contributor III
3,901 Views

Are you seeing this same behavior if you test connecting an external video monitor or display to the system?

Could you please provide the dxdiag report in your system? (Go to start, type dxdiag, press enter and click on Save all information)

0 Kudos
PVone1
Beginner
3,901 Views

No, external monitor (connected via DisplayPort) does not have the issue.

The DXDiag report for non-affected 8.x driver

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

System Information

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

Time of this report: 4/18/2013, 20:46:40

Machine name: X220

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

Language: Czech (Regional Setting: Czech)

System Manufacturer: LENOVO

System Model: 428759G

BIOS: Default System BIOS

Processor: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz (4 CPUs), ~2.6GHz

Memory: 4096MB RAM

Available OS Memory: 3980MB RAM

Page File: 1125MB used, 6830MB 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.01.7601.17514 32bit 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 Family

Manufacturer: Intel Corporation

Chip type: Intel(R) HD Graphics Family

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_0126&SUBSYS_21DA17AA&REV_09

Display Memory: 1696 MB

Dedicated Memory: 64 MB

Shared Memory: 1632 MB

Current Mode: 1366 x 768 (32 bit) (60Hz)

Monitor Name: Wide viewing angle & High density FlexView Display 1366x768

Monitor Model: unknown

Monitor Id: LEN40E2

Native Mode: 1366 x 768(p) (59.850Hz)

Output Type: Internal

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

Driver File Version: 8.15.0010.2769 (English)

Driver Version: 8.15.10.2769

DDI Version: 10.1

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 6/11/2012 14:37:06, 8314368 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-4266-11CF-CB7E-D001A9C2C535}

Vendor ID: 0x8086

Device ID: 0x0126

SubSys ID: 0x21DA17AA

Revision ID: 0x0009

Driver Strong Name: oem18.inf:IntelGfx.NTamd64.6.0:iSNBM0:8.15.10.2769:pci\ven_8086&dev_0126&subsys_21da17aa

Rank Of Driver: 00E60001

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 DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Fra...

0 Kudos
DArce
Valued Contributor III
3,901 Views

Could you please provide more screenshots, one showing what you are referring to with anti-aliased pictures and also one of the text aliasing issue, but with not zoom so just with a normal size/view?

0 Kudos
PVone1
Beginner
3,901 Views

The driver-caused aliasing issue is not limited to Windows text rendering only but affects everything that is displayed on the notebook display. I'll describe the test steps again:

1. The Lenovo 8.15.0010.2769 driver is installed.

2. Store following screenshot image (taken from Start menu) BlurryDisplayTestImage.png to a folder

3. Open the BlurryDisplayTestImage.png in MS Paint or any other graphic viewer without resizing it. It contains non-anti-aliased black text on grey background.

4. Notice the text on notebook display is sharp and non-anti-aliased. Take a macro picture of the display by camera.

5. Install Lenovo 9.17.0010.2843 driver or latest generic Intel Graphics driver and restart.

6. Repeat step 3.

7. Notice the text on notebook display is not sharp and anti-aliased. Take a macro picture of the display by camera and compare it with picture taken in step 4. You will notice a (hardware based ?, kernel driver based ?) subpixel anti-aliasing applied to the image, as shown on my picture in first post.

I use the test screeshot image in step 2 to prevent any potential issues with Windows ClearType (that I have disabled) but the issue is same for text rendered by Windows (it becomes anti-aliased even with ClearType disabled). So it looks like a more low-level issue because external display output is not affected, its output is exactly the same in steps 4 and 7.

0 Kudos
PVone1
Beginner
3,901 Views

Is there anything else I can provide ? I think the steps and sample picture should be enough to understand the issue.

Additional question, when exactly the new driver version actually becomes effective (loaded) ? Is it right after the installation of new version has finished (before restart) or after restart ? Because the issue with antialiasing happens in the middle of installation of the new driver, even before restart. So it could be just a wrong setting that applies to the old version as well (in case the new version is applied after restart).

0 Kudos
DArce
Valued Contributor III
3,901 Views

The driver installation completes until the system is fully restarted

Concerning the additional information that was requested, we explicitly need more screenshots, one showing what you are referring to with anti-aliased pictures and also one of the text aliasing issue, all of them with not zoom so just in normal size and not just a png file that has been cut.

0 Kudos
PVone1
Beginner
3,901 Views

That's interesting because the issue happens in the middle of new driver installation. That would support the idea it is just a global driver setting made by the new version driver installation that also affects the old one (until reboot). In other words it is not caused by the new driver code in DLL or SYS files itself but its setting (in the registry) made by new version installation. The scenario can be as follows:

1. old driver 8.x is installed with its default settings -> no issue

2. driver 9.x setup is started -> no issue

3. driver 9.x setup completes, some settings (in the registry ?) has been modified by the 9.x setup but the old 8.x driver is still used -> the anti-aliasing issue is present since that, even with current 8.x driver (assuming the 9.x version becomes effective later, after restart)

4. restart

5. driver 9.x instalattion completes -> anti-aliasing issue is present with 9.x driver

I would like to find the registry setting that causes it.

As for screenshots. There is no difference between "text" and "graphics", consider Windows desktop as a bitmap that have pixels with colors. Another example: I can open MS Paint fullscreen, fill background with gray color, draw single vertical black line and take a screenshot (and post it here). The line will look anti-aliased on the internal notebook display with 9.x driver version and non-anti-aliased with 8.x driver version. Again, the png file screenshot will be pixel-by-pixel exactly the same for 8.x and 9.x driver version. The anti-aliasing is not made on that level.

It is exactly same as "l" letter in the "Calculator" word in my small screenshot. It is just black line on gray background that shows the added anti-aliasing by red subpixel on the right edge. The screenshot is attached, contains both pictures and text.

0 Kudos
PVone1
Beginner
3,901 Views

Updating BIOS to latest 1.38 version (and installing the driver after that) did not help. But I found that my assumption that the new driver is used after restart was wrong. It is loaded during the installation so when the installer finish (before restart), the new driver is already loaded and used. And yes, the issue persists after restart as well.

I saved content of [HKEY_CURRENT_USER\Software\Intel] and [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet] registry and IntelGFX.log file for both driver versions. There are differences in some HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000 values.

Since the issue is clear now, can you tell what feature of new 9.x driver can cause that ? Could it be something with Color Management, ICC profiles, software brightness/contrast color distortion algorithm (note that external monitor is not affected) ? I have latest Lenovo monitor INF file version 4.38 installed. It would support following comparison of the screenshot area. Notice that the solid background color looks different for 9.x and 8.x driver version:

Thanks.

There is http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/Blurry-fonts-on-T420-with-64-bit-Win-7-Intel-HD-Graphics-3000/td-p/1093969 another customer experiencing similar issue on Lenovo T420 notebook. He has another experience that might help to resolve the issue: "The only this that has helped so far was running on low battery when all the sudden and by itself the font display became all good for until I plugged the power source back in." ... "We couldn't find any difference between the settings on my laptop compared to a colleague's exact same alike that displays all just perfect."

0 Kudos
DArce
Valued Contributor III
3,901 Views

Thank you, let me forward this to our research team so I can get a response for you.

0 Kudos
DArce
Valued Contributor III
3,901 Views

It seems that we are not being able to replicate this behavior. So then, could you please provide a before and after picture of what the issue (zoomed out to normal view, not zoomed in) looks like with our driver and without the driver installed?.

0 Kudos
PVone1
Beginner
3,901 Views

The only screenshot I can provide is PrintScreen copy saved as bitmap or PNG file. Again, there is no difference here, the difference is made in a lower level. That's why I posted these pictures of display made by a camera.

Is there is a way to make a "screenshot" of driver raw output to the display, including all these brightness/contrast/etc. Intel display settings applied ?

0 Kudos
DArce
Valued Contributor III
3,901 Views

Let me check on this and get back to you.

0 Kudos
MLund4
Beginner
3,901 Views

Hi

I think I have the same issue with a Lenovo X230 here using Drivers version 8.15.10.2696.

And I can easily reproduce the error using FastStone Capture

Check this program: https://dl.dropboxusercontent.com/u/527756/FSCapture.zip https://dl.dropboxusercontent.com/u/527756/FSCapture.zip

Running it and create a snapshop, then draw. If you turn on round corners and anti-alias it will not let you save the changes. Tick off anti-alias and it will save.

0 Kudos
DArce
Valued Contributor III
3,901 Views

klunde, from what I can see, your issue seems to be different than the one reported here, and you are using an out dated version of the graphics drivers. And updated driver for your system is posted here:

https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Graphics&ProductLine=Desktop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+4000&ProdId=3712&LineId=1100&FamilyId=39 https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Graphics&ProductLine=Desktop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+4000&ProdId=3712&LineId=1100&FamilyId=39

puppy, in your case, you may need to check on this directly with your Original Equipment Manufacturer, Lenovo and open a Service Ticket with them so they may check directly on this.

0 Kudos
PVone1
Beginner
3,596 Views

Diego_Intel wrote:

puppy, in your case, you may need to check on this directly with your Original Equipment Manufacturer, Lenovo and open a Service Ticket with them so they may check directly on this.

It is almost hopeless since it is a corner case on an older machine. It would result in try this ..., try that .... replace this ..., replace that. No attempt to actually diagnose the issue Moreover the issue affects only people who can not stand any kind of anti-aliasing on todays low DPI diplays as described here: http://annystudio.com/misc/anti-aliased-fonts-hurt/ Anti-aliased fonts hurt eyes and damage eyesight.

Do you have an idea whether the Intel video driver 9.x version contains code/feature/functionallity that might cause this and got activated in the new driver version ? I can not imagine it is caused by a hardware setting of the display component.

Again, enabling a video driver debug log would be the best way, if there is any.

0 Kudos
Reply