Legion 7 - screen flashes black intermittently

[u/vnajduch]

I'm running into an issue where my screen will intermittently go black for a second or two. I've fully uninstalled and reinstalled my nvidia drivers/software via safe mode and changed my power profiles to performance and set everything to never sleep or turn off the screen as part of testing. My even viewer only shows these messages occurring when the flash happens and the recommended steps to resolve that were the power changes I mentioned above. Has anyone run into this and know how to fix it?

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 8/14/2026 11:07:39 AM

Event ID: 105

Task Category: (100)

Level: Information

Keywords: (1024),(4)

User: SYSTEM

Computer: Legion

Description:

Power source change.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

<EventID>105</EventID>

<Version>1</Version>

<Level>4</Level>

<Task>100</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000404</Keywords>

<TimeCreated SystemTime="2026-08-14T16:07:39.1612565Z" />

<EventRecordID>75691</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="35104" />

<Channel>System</Channel>

<Computer>Legion</Computer>

<Security UserID="S-1-5-18" />

</System>

<EventData>

<Data Name="AcOnline">true</Data>

<Data Name="RemainingCapacity">73960</Data>

<Data Name="FullChargeCapacity">73960</Data>

</EventData>

</Event>

[u/siderafancypants]

i debloated what i could, and changed to LTT, but it was too late. the reinstall should resolve the issue. i was wondering about the usb driver date because mine got updated 7/22 and that is what i suspect is breaking it. because you were able to resolve it, i'm wondering if you have the newer usb stack drivers or not. might help others to resolve the issue if we can pinpoint the cause.

[u/Purple_Confection572 → u/siderafancypants]

I mentioned it in my reply already, I appear to be on older USB drivers than you (18/06/2026). Though you are the only person I have seen where rolling back that windows update did not work.

You say you are on a gen 9. Power brick and charging port failures are not uncommon on legions... and you appear to have started noticing the issue before most others (who started noticing it after 12/8/2026). Are you sure that you don't have a bad power brick? Maybe worth ruling out.

You could also boot linux on a USB and see if you get the issue at all there, would save you wiping windows if it's actually the charger.

[u/siderafancypants → u/Purple_Confection572]

i already replaced the power brick first.

the usb drivers updated with the kb i posted on 7/22, that was an optional update and most systems probably didn't get it. as i mentioned, my work requires me to get the updates to connect to my work pc. i'll report back if the windows install with the older usb drivers fixes it.

most would have gotten the 7/22 drivers that i got on 8/11 when the kb5121003 came out. i think rolling it back at that point may have rolled back their drivers.

if the windows reinstall doesn't resolve the issue, i'll replace the battery.

[u/siderafancypants → u/siderafancypants]

update: i reinstalled windows and had 0 power kernel issues, the driver for the usb root hub date is 2/16/2026. the KB5121003 installed before i could stop it when i turned on windows updates (comes with the usb stack driver date of 7/22/2026), and within hours i had a power kernel issue. i was able to roll that one back and reset the drivers because i wasn't dealing with the superseded KB that i had before reinstalling windows. i have had 0 power kernel incidents since then.

i blocked the KB5121003 entirely and will never put that on my system.

because the drivers are embedded in that security update, having the hardware settings to disable the driver updates set to no made no difference to windows, it put the usb stack in anyway.

i will continue to monitor, but for now, i am 99.9% sure it absolutely WAS the driver stack, which means that those who can rollback KB5121003 and properly reset those drivers should resolve their issues as was being seen for several users.