Intel's latest graphics drivers can ruin the Chrome and Edge experience
Intel has admitted that the integrated UHD 770 graphics found in many Alder Lake generation processors are creating stuttering difficulties in Windows-based Chromium-based web browsers. This includes Google Chrome and Microsoft Edge, as well as minorities such as Opera, Brave, and Vivaldi. The original Chromium source build can also be counted, but only Linux users use the browser under such conditions.
According to the chipmaker, "latest drivers for the Intel UHD Graphics 770 of the 12th generation Intel Core processors cause the Edge* and Chrome* browsers to lag significantly. Browsers act as if they are paralyzed. The click response time is 2 seconds, and scrolling is quite slow and choppy. The problem can be reproduced by opening many tabs at the same time, or by scrolling, clicking, and utilizing a mechanical hard disk drive (HDD)."
In other words, according to the business, the most recent versions of the drivers for the UHD 770 graphics have ruined the experience. Users of mechanical hard drives appear to be more affected than those who use SSDs, which could be owing to the slowness of HDDs, which have long been one of the key bottlenecks in household PCs.
The problem was replicated on a computer with an MSI PRO Z690-A DDR4 motherboard, an Intel Core i5-12600K processor, and Windows 10 as the operating system, although the fault should also affect Core i5-12500TE, Core i5-12600, Core i7-12700, Core i7-12700K, Core i9-12900, and Core i9-12900K.
To fix the problem, Intel suggests updating the web browser to the newest version, updating the operating system (Windows), wiping and reinstalling the graphics drivers, disabling hardware acceleration, or replacing the mechanical hard drive. an SSD .
It appears like Chromium or some of its variants are not having a good run, as a severe vulnerability was uncovered this week that was being used against Chrome. We are not aware that the fault discovered in Intel UHD 770 graphics impacts Linux at this time, but if it is discovered, it is best to report it to the business and wait for an update, which would most likely arrive via kernel and/or Table.
Post by Bryan C.
