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

[NonSequitur777]

@gr999,

No problem -and the screenshot explains what is happening.

It looks like your account currently does not have the attachment option in the Community editor, and the forum is also explicitly rejecting the .zip file as an unsupported file type. So, my previous instructions about simply attaching a ZIP were too optimistic -sorry about that.

Please don't email the dump to an address posted publicly on the forum. A minidump can contain system information that shouldn't be shared through an unknown or unofficial address.

We have a couple of alternatives.

Option 1 — OneDrive:

The easiest solution would be to put the ZIP containing: 081226-25609-01.dmpin your OneDrive and create a sharing link that allows anyone with the link to view/download the file. You can then post the OneDrive link in your HP Community reply.

If you do this, please make sure the link points specifically to the ZIP containing the minidump rather than giving access to your entire OneDrive folder.

Option 2 — We can continue without the dump:

The dump would be very useful, but we don't necessarily have to stop here.

The 0x139 / parameter 0x1D bugcheck already establishes that Windows detected corruption of a kernel data structure. The next useful question is whether this is happening repeatedly with the same failure pattern.

If you have another crash, please provide the corresponding BugCheck Event 1001 details and, if another minidump is created, its filename.

Also, the fact that Windows subsequently installed:

HP Inc. SoftwareComponent Driver Update — 1.87.4769.0 is worth recording, but I would not assume that update caused or fixed the problem. It occurred after the crash and could simply have been an unrelated Windows Update/HP driver delivery.

For now, I would leave the BIOS at F.35 and avoid changing Secure Boot settings whilst we investigate the actual crash.

If you can provide a OneDrive link to the minidump, however, that would be my preferred next step. A debugger analysis of the actual .dmp file could potentially tell us considerably more than Event Viewer alone.

Kind Regards,

NonSequitur777

[gr999]

Thank you for looking at this,

- System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {abce23e7-de45-4366-8631-84fa6c525952}

EventID 1001

Version 1

Level 2

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2026-08-14T11:00:24.0778091Z

EventRecordID 219047

Correlation

- Execution

[ ProcessID] 1552
[ ThreadID] 1556

Channel System

Computer HPS01

- Security

[ UserID] S-1-5-18

- EventData

param1 0x00000139 (0x000000000000001d, 0xfffffd0cc4acb330, 0xfffffd0cc4acb288, 0x0000000000000000)
param2 C:\windows\Minidump\081426-24875-01.dmp
param3 b46e6966-4385-4204-a076-62dd2b92e3c2

[NonSequitur777]

@gr999,

I apologize for the delays -I am assisting here in this Community as a volunteer, but obviously I have other responsibilities and places to go so to speak.

Anyways, this was excellent — this is exactly the Event Viewer entry I was hoping you would find. It confirms that Windows generated a kernel crash dump and gives us the BugCheck details.

The crash is 0x139, KERNEL_SECURITY_CHECK_FAILURE, with parameter 1 = 0x1D, which indicates that Windows detected corruption involving a kernel LIST_ENTRY structure. That often points toward a kernel-mode driver or other low-level software, although the BugCheck itself does not identify the culprit.

More importantly, Windows confirms that the actual minidump is:

C:\Windows\Minidump\081426-24875-01.dmp

Please upload that exact .dmp file to OneDrive (or another file-sharing service) and post the share link here.

Please don't compress it unless necessary, and make sure the link permits downloading the file.

The dump itself is what I'd like to examine next. With WinDbg, we can potentially determine the crash stack, the thread that detected the corruption, loaded modules/drivers, and whether there is a particular third-party driver that deserves suspicion. That should give us considerably more actionable information than Event Viewer alone.

One caution: please don't delete or overwrite 081426-24875-01.dmp before uploading it. That is the artifact we need.

How to upload the dump to OneDrive:

If you're not familiar with OneDrive, no problem. Please do the following:

1. Open File Explorer.

2. Copy and paste this into the address bar:

   C:\Windows\Minidump

3. Press Enter. You should see a file named:

   081426-24875-01.dmp

4. Right-click that file and select Copy.
5. Open your OneDrive folder in File Explorer.
6. Right-click inside the OneDrive folder and select Paste.
7. Wait for the file to finish uploading/synchronizing to OneDrive. Depending on your connection, this may take a little while.

Then:

1. Right-click 081426-24875-01.dmp in OneDrive.
2. Select Share.
3. Choose the option to Copy link.
4. Make sure the link is accessible to people who have the link (rather than requiring your Microsoft account to sign in).
5. Paste that OneDrive link into your reply here.

Please don't open, modify, rename, or delete the .dmp file. I need the original file as Windows created it.

If OneDrive isn't available on your system, that's also fine — another file-sharing service can be used. The important thing is that I can download the actual 081426-24875-01.dmp file.

Once I have the dump, I can analyze the crash stack and loaded drivers with a debugger. That has a much better chance of identifying what actually caused the 0x139 crash than the Event Viewer entry alone.

Kind Regards,

NonSequitur777