HP s01 has problems with latest windows 11 changes. Copilot says HP has abandoned the S01

[gr999]

HP s01 has problems with latest windows 11 changes. Copilot says HP has abandoned the S01 and will leave the dodgy bios asis. Is this correct?

[NonSequitur777]

@gr999,

Welcome to our HP Community forum!

[EDIT:] Well, to be honest, I would not rely on Copilot's statement that HP has "abandoned" the S01. That is not established by the information in your post.

I don't think we can conclude that HP has "abandoned" the S01 from the information you've provided.

In fact, HP's current driver page for the HP Slim Desktop PC S01-pF2000i (4M0H6AV) shows that the 89B4 system-board configuration has a BIOS newer than the F.24 version that was available previously. The current BIOS is F.30.

That is important because it means we first need to determine whether your computer is actually running F.30.

Please press Windows + R, type:msinfo32

and press Enter.

Then provide:

• BIOS Version/Date
• BaseBoard Product
• BaseBoard Version
• BIOS Mode

Also tell me exactly what you mean by "problems with latest Windows 11 changes." Please identify the Windows 11 version/build you're running and describe what stopped working or what changed.

If your system is an 89B4 machine and is running an older BIOS than F.30, the first logical step would be to compare it with HP's current F.30 BIOS offering.

If you are already running F.30, however, then simply saying "HP abandoned the S01" doesn't explain the problem. We would need to determine whether the issue is actually caused by the BIOS, Windows 11, a driver, or a particular new Windows feature.

So, I would not rely on Copilot's characterization that HP has "left the dodgy BIOS as is." HP is still publishing BIOS updates for at least the 89B4 configuration of this S01-pF2000i family. The next step is to establish exactly which BIOS and system-board configuration you have.

Kind Regards,

NonSequitur777

[gr999]

Thanks for your interest:

Edition Windows 11 Home
Version 25H2
Installed on ‎29/‎03/‎2025
OS build 26200.8973
Experience Windows Feature Experience Pack 1000.26100.344.0

BIOS Version/Date AMI F.35, 19/03/2026
BaseBoard Manufacturer HP
BaseBoard Product 89B4
BaseBoard Version A (SMVB)

PC crashes about once a day, from the event log:
-The Secure Boot update failed to update SBAT with error Unknown HResult Error code: 0x800700c1.
For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-The hardware real-time clock was not set because evaluation of the ACPI Time and Alarm Device method failed. Status: 0xC0000001.

-A timeout was reached (45000 milliseconds) while waiting for the Intel(R) Platform License Manager Service service to connect.

[NonSequitur777]

@gr999,

Thank you -that information is very helpful indeed, and it actually changes my assessment of the situation.

First, your system is definitely not sitting on the old F.24 BIOS I was concerned about in my previous reply. You have:

• Windows 11 Home 25H2
• OS build 26200.8973
• HP motherboard/system board 89B4
• AMI BIOS F.35, dated 19 March 2026

So the "HP has abandoned the S01" statement from Copilot does not appear to be correct. HP has continued to issue BIOS updates for the 89B4 platform, and F.35 is obviously newer than the F.30 version I referred to previously.

The three Event Viewer errors you have found are interesting, but I would be careful about assuming that they are the cause of the crashes.

1. Secure Boot / SBAT — 0x800700c1:

This is a genuine Windows Secure Boot servicing error:

The Secure Boot update failed to update SBAT with error Unknown HResult Error code: 0x800700c1.

Microsoft has been rolling out changes to the Secure Boot certificate/SBAT infrastructure, so this is certainly relevant to the "latest Windows 11 changes" you mentioned.

Interestingly, there are other HP systems reporting this same 0x800700c1 error even with relatively recent BIOS versions. Therefore, I would regard this as a problem that needs to be investigated, but not yet as proof that it is causing your daily crashes.

2. ACPI Time and Alarm Device — 0xC0000001:

This one is more interesting from a firmware perspective.

Windows is reporting that it attempted to set/access the hardware real-time clock through the ACPI Time and Alarm Device, but the corresponding ACPI method failed:

Status: 0xC0000001.

That establishes an interaction problem between Windows and the system firmware's ACPI implementation. It does not, however, establish that this is what is crashing the computer.

Since you are already running BIOS F.35, this is something I would document carefully rather than simply telling you to "update the BIOS."

3. Intel Platform License Manager — 45-second timeout:

I would be much less inclined to blame this one for the crashes.

The 45000-millisecond message is a Windows Service Control Manager timeout. In other words, Windows waited 45 seconds for the Intel Platform License Manager service to connect and it did not respond in time.

There are other reports of this particular Event ID 7009 message on Intel systems, so by itself it isn't evidence of a hardware failure or of the cause of a crash.

What I would like you to check next:

Because you are experiencing an actual crash approximately once a day, let's concentrate on what Windows records at the exact moment of the crash, rather than assuming that every red Event Viewer entry is causal.

Please open Reliability Monitor:

1. Press Windows + R
2. Enter: perfmon /rel
3. Press Enter.
4. Find one of the days on which the PC crashed.
5. Click the red X at approximately the time of the crash.
6. Please provide the details under Critical events and Windows failures.

Also, in Event Viewer, look around the exact time of one crash for:

• Kernel-Power, Event ID 41
• BugCheck
• WHEA-Logger
• Windows Error Reporting
• Display-driver errors
• Disk/NVMe/storage errors

The distinction between a BSOD/restart, a complete power loss, and a system freeze is also very important.

If you can provide the Reliability Monitor entry for one of these daily crashes, plus the Event Viewer events immediately before and after it, I think we can get considerably closer to determining whether we're dealing with a Windows 11/Secure Boot problem, an ACPI/BIOS problem, an Intel driver/service problem, or an underlying hardware/power issue.

At this point, though, I would definitely retract the idea that your S01 has simply been "abandoned." Your 89B4/F.35 configuration demonstrates that HP has continued to provide firmware support for this platform.

Kind Regards,

NonSequitur777

[gr999]

Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x000000000000001d, 0xfffffc0ef5598250, 0xfffffc0ef55981a8, 0x0000000000000000). A dump was saved in: C:\windows\Minidump\081226-25609-01.dmp. Report Id: 54a9cc6b-60af-4d01-917c-4b8fb89dae04.

[gr999]

[NonSequitur777]

@gr999,

Thank you -this is much more useful than the earlier Event Viewer entries. We now know that the computer isn't simply "crashing"; it is actually experiencing a BSOD and automatically rebooting.

The important part is:

Bugcheck: 0x00000139

Parameter 1: 0x1d

Microsoft identifies 0x139 as KERNEL_SECURITY_CHECK_FAILURE, meaning Windows detected corruption of a critical kernel data structure. In this particular case, parameter 0x1D indicates corruption of an RTL_BALANCED_NODE (red-black tree) entry.

That points us much more toward kernel-mode memory corruption, commonly caused by a defective/incompatible driver, although faulty RAM or another hardware/firmware problem can also corrupt kernel memory.

There is another important clue in your screenshots: the Kernel-Power Event 41 is around 9:47 PM, whereas the SBAT Event 1796 is around 9:53 PM.

So, I would not blame the SBAT 0x800700c1 error for this particular crash. It appears to have occurred after the reboot rather than immediately before the BSOD.

The next step is the minidump:

You have the exact dump file: C:\Windows\Minidump\081226-25609-01.dmp

Please attach that .dmp file to your next reply. That would be much more valuable than additional screenshots.

An analysis of the dump may identify the driver that was executing when Windows detected the corrupted kernel structure.

I would also hold off on changing BIOS settings, reflashing F.35, or resetting Secure Boot for now. Your 89B4 / F.35 configuration is established, and we now have a specific Windows kernel crash to investigate.

If the dump does not identify a culprit, then I would move on to RAM/hardware diagnostics and driver verification. Microsoft specifically recommends examining multiple dumps because the same 0x139 pattern occurring repeatedly can help distinguish a faulty driver from more general memory corruption.

So, at this point, I would say the evidence does not support Copilot's claim that HP has abandoned the S01. We have a genuine 0x139 / 0x1D kernel-memory-corruption problem, and the minidump is our best chance of determining what is actually responsible.

Kind Regards,

NonSequitur777

[gr999]

Can I email the dmp file? Am not able to attach.
Also note this last night some time after the crash:
Installation Successful: Windows successfully installed the following update: HP Inc. SoftwareComponent Driver Update (1.87.4769.0)

[NonSequitur777]

@gr999,

To attach a minidump file to the HP Support Community, you must first copy it to another folder and compress it into a .ZIP archive. The HP forum directly blocks raw .dmp files for security reasons, but it will accept a .zip file.

Here are the step-by-step instructions how to do that:

Step 1: Copy and Zip the File:

Because the Minidump folder is a protected system directory, Windows will not let anyone zip a file directly inside it.

1. Open File Explorer and go to: C:\Windows\Minidump
2. Right-click the file 081226-25609-01.dmp and select Copy (or press Ctrl + C).
3. Go to your Desktop, right-click an empty space, and select Paste (or press Ctrl + V).
4. Right-click the copied file on your desktop, hover over Compress to ZIP file (Windows 11) or select Send to > Compressed (zipped) folder (Windows 10).

Step 2: Attach it to the HP Forum Response:

1. Go back to your forum thread and click Reply.
2. Look at the bottom of the reply text box for the Drag and drop here or browse to attach files area (or look for a paperclip icon).
3. Drag your new Desktop ZIP folder into that area or click browse to select it.

Kind Regards,

NonSequitur777

[gr999]

no paperclip icon