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