Today I decided to update my drivers for my Lenovo ThinkPad P15 with an RTX A3000 running Windows 11, and unfortunately my screen has become permanently dim despite being at full brightness as a result of this driver update. I did a clean reinstall, and during the period between drivers, the full brightness had returned, but after completing reinstallation, the dimness came back. I’m not sure if this is the right place to be posting about this, but this is the closest I could find.
@ geometrydashidk, I just upgraded my ThinkPad P16 Gen 1 with RTX A5500 GPU and I’m experiencing the same issue. If I use the default Lenovo driver (outdated by about a year), I get full screen brightness. Once I install the latest driver from NVIDIA, I get the dim screen. Adjusting the brightness, contrast, and gamma in the NVIDIA Control Panel doesn’t seem to get the original brightness back. I’m curious as to what others are seeing with this issue and if anyone has a good solution. I’ll be watching for responses.
Hi there @jnelson0504 and @geometrydashidk, welcome to the NVIDIA developer forums.
It seems while this is a rather isolated occurrence, engineering does have an eye on it and there is an internal tracking bug open.
I added your comments to that thread, so hopefully there will be a solution soon.
Thanks!
@MarkusHoHo this is not an isolated occurrence unfortunately, There are a lot of portable workstation with this issue. I had this problem with my P15 since I bought it. I have since uninstalled the nvidia drivers and used the P15 with other drivers. Now I have tried to reinstall the nvidia drivers (560.76) and I get the same thing. It is very annoying.
Same Problem here with Lenovo ThinkPad P1 Gen 2, P1 Gen 3 and P1 Gen 4.
No problem with P1 Gen 5, P1 Gen 6 and P1 Gen 7.
Could it be a problem with older graphic card models? eg. P2000 or T2000?
Ive been having this issue with a geforce laptop (t15g gen1) with a 2070 super for well over 8 months. i have to roll back to 551.23 in order to fix it. I reported it, sent in the logs and everything and im just sort of stuck here now.
Recently updated the drivers on my P16 with the 3840 by 2400 16:10 screen and Nvidia A4500 GPU.
Experienced the same brightness issue… a very dim display.
Tried installing different drivers, GameReady, Workstation, Creator drivers, all sorts of different “current” versions.
I tried everything I could.
Nothing fixed the screen brightness until I rebooted into Safe Mode (which immediately temporarily fixed the problem) and then promptly completely nuked the Nvidia drivers.
Reinstalled a much older version, 538.78
Now the display works as it is supposed to.
I won’t be updating again until this problem is resolved… and I hope it can be resolved!
Made this account just to add this information, my apologies if it is rambling.
-Alex
Has there been an update on this? I have updated my P1 (T2000 card) and instantly got a dim screeen. I do graphic design, so this is very problematic.
Hi @mysticjoojoo and @galacticboy2009, welcome to the forums.
I am sorry, but I do not have any new information to share.
Yor best solution at the moment is still to roll back to an earlier driver.
Internal testing showed 551.23 should still work normally.
Thanks!
Using ~25 Lenovos P15G2 and T15g, were having the same issues on several machines, with the current drivers.
Due to driver issues (Sudden reboot) we where forced to update the GPU driver on the T15Gs, this resulted in dimmed laptop screen (Around 50-80%)
Tried booth 566.03 and 553.50 today, but still with dimmed screens.
Conservative drivers 538.78 and 538.95 seems however to work fine.
Note sure if it helps.
Thanks for acknowleding the issue.
Do we have any update? I have had some legacy old drivers that came with my laptop, and now even the oldest “archived” drivers from Nvidia website don’t help my Lenovo
Just installed 572.16 on a Lenovo P15g2 (RTX A3000), in order to use Broadcast v2. The screen is now dimmed again, so the issue is definitely driver related.
@MarkusHoHo: Any updates? Are we stuck with legacy drivers? :)
I’ve been having /following this dimming issue since driver version newer than 551.23. My machine: P17 G2 (A5000 mobile) (monitor model: B173ZAN06.C)
Here is what I know (experimented with):
-
I reinstalled the driver and clear the EDID using CRU (custom resolution utility)
-
On the old driver (studio driver 551.23), using EDID from the internet/manually set the EDID works flawlessly (Full brightness control and HDR).
-
On any driver newer than studio driver 551.23 OR Professional RTX driver 551.52, manually setting EDID will be stuck at full brightness (which is normal), the dimming situation will occur when the “Traditional Gamma - SDR” was checked under “Transfer functions” <“HDR Static Metadata”<“CEA-861 - Extension Block”
I am wondering if the issue was caused by “HDR capable laptop monitor + Thinkpad VBIOS” not able to work with Nvidia HDR config or some other vendor specific issue.
Same issue here with the A2000 at a P16 Gen1… New drivers and the laptop screen 100% brightness is not bright enough for a comfort day of work. I’ve been updating the drivers since I got the issue and no fix came up. Unfortunately this issue only started when I requested the IT department to disable the CPU IGP, so I could have less thermal throttling there, but relying only at the A2000 made this issue come up…
Entering windows on safe mode makes the brightness perfect, also while reinstalling the drivers, the moment the driver is removed, then my screen gets brighter and then when the resolution gets back to what it should be the screen get dimmed again.
Is there any fix for this issue being worked on?
About editing the EDID, any idea of what it should look like?
Thanks!
Editing EDID currently won’t help, in case you want to know:-
About editing EDID, you need to know the model of your monitor (HWinfo > monitor could help), then try to Google the model number with keyword “EDID” to see if anyone uploaded an existing EDID file or config, you can download, import and apply the EDID using CRU.
Assuming your P16 is with the 2k screen option, the monitor model is “NE160QDM-N63”, there is a EDID config on “linux hardware” website for “Probe #c718fe33be of Lenovo Yoga 7 16IAH7 82UF”, you can copy the hex code and paste then save as a text file, using CRU to import and apply the EDID, you can also apply EDID through Nvidia control panel.
Alternatively, you can also manually modify the EDID config using CRU, you have to do do your own research and instruction to see which configuration item to apply/change since different monitor has different requirement (resolution/refresh-rate) and feature (HDR/G-sync).
Actually it worked for me! I exported the EDID with the CRU, loaded the exported file and edited the profile fixing the peak and avg luminance values (I used 139), saved and then at the nvidia control panel forced it to the laptop screen. It gave me an error message, but after I restarted my system, the brightness was perfect and I could use the hot keys to properly adjust it as it was before I had disabled the CPU’s IGP.
Thanks!
Same issue with the latest Nvidia Driver for RTX Ada 1000 on my Lenovo P16 Gen 2 , Windows 11 , 4k monitor , super annoying……
Issue still occuring after installing 572.70 on Thinkpad T15G with RTX 2080.
Hi Markus, checking in on this thread again since my hand has been forced back onto latest drivers due to software beginning to require it. Dimming issue is still present on 572.60. Honestly crazy to me that it’s been 8 months (!!!) and still no fix for this. Is there anything that can be shared? There clearly seems to be a rather sizeable group of people with this issue still
Just came here to say that I was having this same issue with my lenovo p15 gen 2 and nvidia 570 rtx drivers. Seems like sticking to the latest 535 driver (which is actually named a notebook driver) seems to have no issues and that driver had a release in jan this year. I would not necessarily download the latest driver the nvidia app tells you to or what comes on top of the list of the driver site, as based on the release dates, there are multiple drivers (535, 550, and 570 in my case) that are all being developed and one of which may be better suited for your machine. The app in my case was recomending 570 so I think the logic for determining if your spec needs an update is not very sophisticated (570 > 535).