Generic PNP Driver failing - new IPS screen

[sporkeh]

Hello, Hoping someone can help. I have upgraded my TN screen on my 725 G3 with an 'allegedly' compatible model (BOE NV125FM-N82). I'm aware that there are different eDP cables required when using screens with increased resolution, however the specification and servicing guide makes no reference to a 1 lane or 2 lane cable, nor does it specify in the product catalgoue whether it is 1 or 2 lane - in fact, the product code for the cables relating to the TN display and the IPS display appear to be the same (821669-001). The screen powers on, works perfectly fine in BIOS, runs at 1920x1080 while installing Windows 10 64bit. However, when I load my desktop I get a display adapter issue with the windows generic pnp driver. The screen will flicker (occassionally its fine, and works for up to an hour), other times it just goes black and a hard reset is required. I have installed all applicable HP software, including all the critical Softpaqs using SDM. I have also run each of the diagnostic tests using the UEFI tool and no errors have been reported. I have followed Windows instructions to uninstall / reinstall generic driver, and have tried different versions of the AMD drivers - ultimately, the issue returns. The BIOS version is N73 - dated April this year. I can't see anything newer on the support pages Now as well as working in BIOS etc, there is absolutely no issue with the screen while in Safe Mode (which reports a resolution of 1920x1080 at 125% text zoom), and the screen works just fine after a fresh install of windows (until it returns after a restart). I can always revert back to my old TN screen, however if someone could assist with this or advise further (including whether a specific 2 lane cable is needed and indeed exists) it would be much appreciated. Many thanks.

[sporkeh · Accepted solution]

Fixed it myself. For anyone else having a similar problem:

- start in safe mode

- navigate to Advanced System Settings > Visual Performance tab

- set visuals to best performance (i.e turn off Windows Peek'

Reboot. Problem solved