F5F Stay Refreshed Hardware Desktop Light on the motherboard flickers during startup

Light on the motherboard flickers during startup

Light on the motherboard flickers during startup

L
Leon1481
Member
53
03-16-2020, 01:18 PM
#1
The CPU indicator has begun activating during startup and while intensive tasks, then shutting off briefly after a short pause. When it turns back on, the system pauses for 1-2 seconds before responding again. Task manager shows no abnormal activity, and overall performance remains stable. The issue might relate to background processes or software conflicts. Considering a clean Windows installation could help if suspicious programs are present. The problem seems linked to the motherboard model ASUS TUF GAMING Z490-PLUS, with the light appearing in the designated zone.
L
Leon1481
03-16-2020, 01:18 PM #1

The CPU indicator has begun activating during startup and while intensive tasks, then shutting off briefly after a short pause. When it turns back on, the system pauses for 1-2 seconds before responding again. Task manager shows no abnormal activity, and overall performance remains stable. The issue might relate to background processes or software conflicts. Considering a clean Windows installation could help if suspicious programs are present. The problem seems linked to the motherboard model ASUS TUF GAMING Z490-PLUS, with the light appearing in the designated zone.

N
NGNLxReiga
Member
186
03-16-2020, 09:38 PM
#2
Have you already reinitialized the BIOS? It would be wise to update it to the most recent release.
N
NGNLxReiga
03-16-2020, 09:38 PM #2

Have you already reinitialized the BIOS? It would be wise to update it to the most recent release.

L
louytekj
Member
144
03-16-2020, 10:10 PM
#3
The bios was recently updated, and it remains the latest release. The issue began some time ago. I also switched from Windows 10 to 11 for comparison, though that happened before the problem arose.
L
louytekj
03-16-2020, 10:10 PM #3

The bios was recently updated, and it remains the latest release. The issue began some time ago. I also switched from Windows 10 to 11 for comparison, though that happened before the problem arose.