SECURE BOOT UPDATE FREEZING LAPTOP HELP PLEASE

[YURKAYURVA]

My Laptop Keeps Freezing While in use its happening more than 5 times a day I don't know what could be wrong. 

GPT5 CODEX RESPONSE:

Summary

Windows logged Event ID 1796 from Microsoft-Windows-TPM-WMI, meaning the operating system tried to push a Secure Boot database (DB/DBX) update into your firmware and the firmware rejected it with error 0x900700C1 at 2025‑10‑06 06:52:54 UTC. Windows will retry the update on subsequent boots until it succeeds or the underlying condition is fixed.
What the event means

Microsoft documents Event 1796 as the catch‑all failure bucket for Secure Boot DBX updates: if the firmware returns any unexpected error while Windows is applying the revocation list, event 1796 is raised and the specific firmware error code is included in the payload so you can troubleshoot it.1
Decoding the error code

HResult = -1878589247 converts to 0x900700C1. Stripping the high diagnostic bits leaves the Win32 error code 0x000000C1, which is ERROR_BAD_EXE_FORMAT (“%1 is not a valid Win32 application”).1 In Secure Boot update scenarios that usually indicates the firmware rejected the payload because it didn’t like its format, signature, or the current Secure Boot state.
Likely triggers

Secure Boot disabled or not fully provisioned. Systems running with Secure Boot off often throw 1796 because firmware refuses to accept DBX updates when Secure Boot isn’t active; Microsoft support engineers call this out directly.1
Out-of-date or buggy UEFI firmware. OEM firmware that predates Microsoft’s 2023–2024 Secure Boot certificate rollovers may mis-handle the newer payloads.
Temporary firmware state (e.g., pending BitLocker/TPM changes). Clearing or toggling TPM/Secure Boot settings mid-update can cause momentary rejections.

Recommended next steps

Confirm Secure Boot status. In Windows, run msinfo32 and check Secure Boot State. If it’s “Off”, decide whether to enable it (often under Boot or Security in UEFI setup). Save and reboot if you turn it on. (Follow your motherboard manual; enabling may require switching the boot mode to UEFI only.)
Validate TPM readiness. In tpm.msc, ensure the TPM is Ready for use. If it shows a warning, follow the console prompts to prepare it. Support guidance suggests toggling TPM off/on in firmware if it’s stuck.1
Update your BIOS/UEFI. Grab the latest firmware from HP (Omen 17) and apply it; OEMs frequently release fixes tied to Secure Boot database updates.
Let Windows retry. After the above changes, reboot twice; Windows will automatically reattempt the DBX write on each restart. If it succeeds you’ll see Event ID 1034 (“Secure Boot Dbx update applied successfully”).
Only if issues persist: consider clearing/reloading Secure Boot keys from the UEFI menu (restore factory keys, then re-enable Secure Boot). Document existing BitLocker recovery keys first because firmware changes can send BitLocker into recovery.

If you intentionally keep Secure Boot off

Expect this error to repeat periodically; it does not usually impact day-to-day operation, but it means the latest revocation list isn’t taking effect. You can either accept the noise (Windows will retry occasionally) or filter the event in Event Viewer.
When to involve the OEM

If Secure Boot is enabled, firmware is current, and the error still fires on every boot, collect the recurring Event 1796 entries and open a case with HP. Provide them the firmware error code (0x900700C1) so they can escalate to their BIOS team.

XML CODE

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-TPM-WMI" Guid="{7d5387b0-cbe0-11da-a94d-0800200c9a66}" />
<EventID>1796</EventID>
<Version>2</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-10-06T06:52:54.5024321Z" />
<EventRecordID>7114</EventRecordID>
<Correlation />
<Execution ProcessID="16920" ThreadID="1840" />
<Channel>System</Channel>
<Computer>XOMEN17</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="HResult">-1878589247</Data>
<Data Name="UpdateType">1024</Data>
</EventData>
</Event>

[Max3Aj]

Hello @YURKAYURVA, and welcome to the HP Support Community!

Thanks for posting your question. I'm here to help you get things back on track.

Based on your description and the Event ID 1796 with error 0x900700C1, your OMEN laptop is freezing because Windows is trying to apply a Secure Boot DBX update, but the firmware is rejecting it. This is a known issue when Secure Boot is disabled or the firmware is outdated.

Here’s how to resolve it step-by-step:

Check Secure Boot Status

1. Press Windows + R, type msinfo32, and hit Enter.
2. Look for Secure Boot State:
   • If it says Off, you’ll need to enable it in BIOS.
   • If it says On, proceed to Step 2.

To enable Secure Boot:

• Restart your laptop and press Esc or F10 repeatedly to enter BIOS.
• Navigate to Security or Boot tab.
• Set Secure Boot to Enabled.
• Ensure Boot Mode is set to UEFI (not Legacy).
• Save changes and exit.

Check TPM Status

1. Press Windows + R, type tpm.msc, and hit Enter.
2. Ensure it says TPM is ready for use.
   • If not, follow prompts to prepare it.
   • If stuck, toggle TPM off/on in BIOS under Security > TPM Device.

Update BIOS/UEFI Firmware

Your firmware may be outdated and incompatible with the latest Secure Boot payloads.

Official HP® Support

• Go to HP OMEN 17-ck1000 Drivers
• Select Windows 11, then download and install the latest BIOS update.

⚠️ Ensure your laptop is plugged in and do not interrupt the update process.

Reboot Twice

After enabling Secure Boot and updating BIOS:

• Reboot your laptop twice.
• Windows will retry the DBX update automatically.
• If successful, you’ll see Event ID 1034 in Event Viewer.

Optional: Reload Secure Boot Keys

If issues persist:

• Enter BIOS > Secure Boot Configuration.
• Choose Restore Factory Keys.
• Save and reboot.

Important: Back up your BitLocker recovery key before making firmware changes. You can find it at https://aka.ms/recoverykey

If Secure Boot is intentionally disabled

You can ignore the error, but Windows will keep retrying the update. It won’t affect daily use, but the latest security revocation list won’t apply.

I hope the information shared has been useful and resolves your concern.

Wishing you a smooth and hassle-free experience ahead!

If this solution helped, please click “Accepted Solution” so others can benefit too. Don’t forget to hit the “Yes” button if you found this helpful!

Warm regards,

Max3Aj

HP Support