Victus power light blinks not turning on

[Waji64]

Hello, when i shut down my hp victus after few hours if i turn on again it just light up the power button light and keyboard light for a second it blink once then again the process repeats .after sometime keyboard stop blinking only power button lights up for a second and go off. This process repeats meanwhile screen does not light up.

I leave it for few hours after that it turn on normally but the time in windows changes .

Also note of i put it on sleep no matter when i open it turn on normally.

I dont know why, i have done bios update every trouble shoot but cannot figure out why it does not turn on directly from shut down state but from sleep it is all ok.

[Hawks_Eye]

Hi @Waji64 

Welcome to the HP Support Community! We're here to help you get back up and running.

Thank you for sharing the details. I understand the concern. Based on your description, the notebook powers on normally from Sleep, but after a full shutdown it may enter a cycle where the power button and keyboard lights blink briefly, the display remains off, and Windows time may be incorrect when it eventually starts.

Before suggesting additional troubleshooting, we would like to understand the behavior a little better:

• Which version of Windows is currently installed (Windows 10 or Windows 11)?
• When the issue occurs, is the AC adapter connected or does it happen on battery power as well?
• Have you noticed if the date and time reset to an older date, or is it only a few minutes/hours off when Windows loads?
• When the notebook finally starts after being left for some time, do you see any BIOS recovery, checksum, or CMOS-related messages?
• Have you already run HP PC Hardware Diagnostics and completed the Battery and System Board tests? If yes, please share the results.
• Could you confirm the current BIOS version installed on the Victus 15-fa1000?

The detail that the system starts normally from Sleep but not consistently from a full Shutdown, combined with the Windows clock changing after startup, may help us narrow the issue toward power initialization, RTC/CMOS time retention, or firmware-related behavior.

Please share the information above, along with any blink pattern observations, and we will help you continue the diagnosis.

Take care, and have an amazing day!

Regards, 

Hawks_Eye

[Waji64]

Using windows 11 latest updated.

Bios updated to latest available on hp website.

Not everytime,but few time it show CMOS error. That is cmos checksum imvalid.cmos reset 502.

Also the date does not change only time changes and go back 6 to 8hours back.

I have run all diagnostic nothing show up.

[Hawks_Eye]

Hi @Waji64 

Thank you for providing the additional details. I understand the concern. The information you've shared is very helpful, especially the CMOS Checksum Invalid (502) message, the time shifting back by 6 to 8 hours, and the fact that the notebook starts normally from Sleep but may not start correctly after a complete Shutdown.

Based on what you've described, the behavior appears to be related to how the system is retaining real-time clock (RTC) and firmware settings when the notebook is fully powered off. Since the BIOS is already updated and HP Hardware Diagnostics passed, the next steps are focused on confirming the RTC/CMOS and power initialization state.

Please try the following:

Load BIOS defaults:

• Turn off the notebook.
• Power on and repeatedly tap F10 to enter BIOS Setup.
• Press F9 to load BIOS defaults.
• Select Yes.
• Press F10 to save and exit.

Verify the BIOS date and time:

• Re-enter BIOS after a shutdown event when the issue occurs.
• Check whether the BIOS time itself is incorrect before Windows starts.
• If the BIOS clock has moved backward, this helps identify whether the issue is occurring at the firmware level rather than within Windows.

Perform a complete power drain:

• Shut down the notebook.
• Disconnect the AC adapter.
• Press and hold the Power button for 15 seconds.
• Reconnect the adapter and test several shutdown/startup cycles.

Disable Fast Startup in Windows temporarily and test:

• Open Control Panel > Power Options.
• Select "Choose what the power buttons do."
• Select "Change settings that are currently unavailable."
• Clear the checkbox for Turn on fast startup.
• Save changes and test multiple shutdowns.

Observe whether the CMOS 502 message appears more frequently after the notebook remains powered off for an extended period (for example, several hours) compared to a short shutdown period. This detail can help isolate whether the RTC settings are being lost while the system is fully powered down.

Since the notebook can resume from Sleep normally, but occasionally reports CMOS Checksum Invalid (502) and loses time after a full shutdown, the BIOS clock behavior will be particularly important to verify.

Please let us know:

• Whether the BIOS time is also incorrect when the issue occurs.
• If loading BIOS defaults changes the startup behavior.
• Whether the CMOS 502 message still appears after the above checks.

Regards,

Hawks_Eye

[Waji64]

Hello, i have done everything but issue is same. Sometime even it turn on from shut down all ok and from sleep also. But sometimes the above enent occurs. Kindly come up with solution instead of asking much about it. I think i am already clear.

[Hawks_Eye]

We sincerely thank you for your patience and co-operation during this troubleshooting process.

If after following these steps you still face issues, consider reaching out to our HP service center for further assistance.
 

Click on the link below and fill in the required details to find the closest service center and their availability.

Service Center Locator: https://support.hp.com/us-en/service-center

Please call before visiting a service center.

Thanks!

Hawks_Eye

[prince_jha02]

hey what was your problem finall does it solved because same problem happening to my laptop also 

[Waji64]

It just stopped happening. As i mentioned sometime it startup normally sometimes it doesn't. But now its starting normally i think the hard reset method worked or maybe due to Microsoft update. May be some drivers from Microsoft was causing the issue in windows 11 known issues.