Windows 11 home was installed on a HP Z4 G4, which also dual boots into AlmaLinux.
After selecting to update to 24H2 the PC no longer boots into Windows.
Fails with:
- Stop code: IRQL_NOT_LESS_OR_EQUAL
- What failed: ntoskrnl.exe
Byitself the PC doesn't enter Windows Recovery. At the point of failure the PC only responds to the power button, and powers off without a delay.
Setup is:
- Windows 11 installed on a NVMe
- AlmaLinux installed WDC SATA HDD
If boot into AlmaLinux can mount the NTFS partitions on the NVMe, only mounted as read-only.
From AlmaLinux identity of the NVMe:
$ sudo lspci -v -s 37:00.0
37:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD
Flags: bus master, fast devsel, latency 0, IRQ 48, NUMA node 0, IOMMU group 87
Memory at 9b000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=8 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [158] Power Budgeting <?>
Capabilities: [168] Secondary PCI Express
Capabilities: [188] Latency Tolerance Reporting
Capabilities: [190] L1 PM Substates
Kernel driver in use: nvme
Kernel modules: nvme
Result from smartctl on the NVMe:
$ sudo smartctl --all /dev/nvme0n1
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.18.0-553.30.1.el8_10.x86_64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZVPW256HEGL-000H1
Serial Number: S34ENB0K432429
Firmware Version: CXZ74H0Q
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 256,060,514,304 [256 GB]
Unallocated NVM Capacity: 0
Controller ID: 2
Number of Namespaces: 1
Namespace 1 Size/Capacity: 256,060,514,304 [256 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 c481b15dae
Local Time is: Tue Dec 17 15:11:11 2024 GMT
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Warning Comp. Temp. Threshold: 70 Celsius
Critical Comp. Temp. Threshold: 73 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.80W - - 0 0 0 0 0 0
1 + 5.60W - - 1 1 1 1 0 0
2 + 4.40W - - 2 2 2 2 0 0
3 - 0.0400W - - 3 3 3 3 210 1500
4 - 0.0050W - - 4 4 4 4 2200 6000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 19 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 2%
Data Units Read: 11,785,268 [6.03 TB]
Data Units Written: 12,506,925 [6.40 TB]
Host Read Commands: 212,844,304
Host Write Commands: 470,665,339
Controller Busy Time: 1,798
Power Cycles: 1,134
Power On Hours: 1,578
Unsafe Shutdowns: 228
Media and Data Integrity Errors: 0
Error Information Log Entries: 3,867
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 19 Celsius
Temperature Sensor 2: 26 Celsius
Error Information (NVMe Log 0x01, max 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 3867 0 0x4005 0x4004 - 0 0 - Invalid Field in Command
1 3866 0 0x400a 0x4004 - 0 0 - Invalid Field in Command
2 3865 0 0x4016 0x4004 - 0 0 - Invalid Field in Command
3 3864 0 0x400a 0x4004 - 0 0 - Invalid Field in Command
4 3863 0 0x000c 0x4004 - 0 0 - Invalid Field in Command
5 3862 0 0x400a 0x4004 - 0 0 - Invalid Field in Command
6 3861 0 0x001c 0x4004 - 0 0 - Invalid Field in Command
7 3860 0 0x000c 0x4004 - 0 0 - Invalid Field in Command
8 3859 0 0x2016 0x4004 - 0 0 - Invalid Field in Command
9 3858 0 0x0015 0x4004 - 0 0 - Invalid Field in Command
10 3857 0 0x401a 0x4004 - 0 0 - Invalid Field in Command
11 3856 0 0x2008 0x4004 - 0 0 - Invalid Field in Command
12 3855 0 0x4002 0x4004 - 0 0 - Invalid Field in Command
13 3854 0 0x6001 0x4004 - 0 0 - Invalid Field in Command
14 3853 0 0x3008 0x4004 - 0 0 - Invalid Field in Command
15 3852 0 0x007a 0x4212 0x028 0 - - Invalid Log Page
... (48 entries not shown)
Critical Update for Western Digital and SanDisk Internal SSDs That Can Cause BSOD on Windows 11 24H2 on the Western Digital sites links to Internal SSD Critical Firmware Update Available for Solving BSOD on Windows 11 24H2 Update on the SanDisk site which reports that for some 2TB NVMe a firmware update is available to fix the BSOD.
Download – Tools & Software has links to downloads for tools which can perform firmware updates on Samsung SSDs. Can see a tool which supports a SM963. Think the SAMSUNG MZVPW256HEGL-000H1 in running HP OEM firmare, so not supported by the Samsung tools.
Followed Create installation media for Windows to create the Windows 11 install media on a SD card.
The install media boots on a HP Pavilion 590-p0053na, and if select recover PC followed by a command line then the Windows version reported when the command line starts is 10.0.26100.2033. October 8, 2024—KB5044284 (OS Build 26100.2033) is the Microsoft page for this version.
The installed OS on the HP Pavilion 590-p0053na is Version 10.0.22631.4602.
Windows 11 Version Numbers Build Numbers Major Minor Build Rev has:
| Windows 11 Versions – Production Release Build Version | Windows 11 Build version | KB | Availability Date | Start of Servicing Date | End of Servicing Date |
|---|---|---|---|---|---|
| Windows 11 24H2 – 10.0.26100.2033 | 10.0.26100.2033 | KB5044284 | 8th October 2024 | 1st Oct 2024 | 12th Oct 2027 |
Attempting to boot the HP Z4 G4 with the Windows 11 24H2 install media, with the SD card in either the built-it SD card slot or a USB to SD card adapter, results in the same symptoms as with the bricked update on the NVMe. I.e. after a few seconds of the spinning circle before getting the same BSOD and the PC only responding to the power button.
Changes to HP Z4 G4 configuration which didn't allow the Windows 11 24H2 install media to boot:
- Disable the NVMe slot in the BIOS. Reverted when had no effect.
- In the BIOS change from "Legacy Support Disable and Secure Boot Enable" to "Legacy Support Disable and Secure Boot Disable". Reverted when had no effect.
- Prevent 3 3 FPGA cards from enumerating on the PCIe bus, by loading bitstreams with no PCIe endpoint. Reverted when had no effect.
- In the BIOS:
- disable Trusted Execution Protection (TXT)
- While leaving Virtualisation Technology (VTx) and Virtualisation Technology for Directed I/O (VTd) enabled.
The following change in the BIOS did allow the Windows 11 24H2 install media to boot, and as expected prevents AlmaLinux from using the IOMMU:
- disable Trusted Execution Protection (TXT) and Virtualisation Technology for Directed I/O (VTd)
- While leaving Virtualisation Technology (VTx) and enabled.
When booted the install media got a Windows Setup dialog which said:
It looks like you started an upgrade and booted from installation media. If you want to continue with the upgrade, remove the media from your PC and click Yes. If you want to perform a clean installation instead, click No.
Removed the media and clicked Yes. The PC rebooted.
At the AlmaLinux grub menu selected to boot Windows (on the NVMe). Windows starts and get a "undoing changes to your PC". After several tens of seconds reboots and starts Windows without the grub menu being displayed.
Can login into Windows. Command Prompt reports Version 10.0.22631.4541 and winver reports Version 23H2 (OS Build 22631.4541).
Selected restart in Windows, and boots back into Windows without the grub menu.
In the BIOS changed the boot order to move SATA0:AlmaLinux to be before M.2 SSD1:Windows Boot Manager. That restored the grub menu at boot. Suspect Windows changed the boot order as part of the "undoing changes".
In the BIOS re-enabled Trusted Execution Protection (TXT) and Virtualisation Technology for Directed I/O (VTd). Windows still boots from the NVMe as Version 10.0.22631.4541.
After the PC was left booted as Windows, an update for 2024-12 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5048685) was automatically installed with a status of Pending Restart. On a search this is 23H2.
Update installed OK. On completion:
- Command Prompt reports
Version 10.0.22631.4602 winverreportsVersion 23H2 (OS Build 22631.4602)- Check for updates finds no available updates.
In the Update History the Features Updates has:
- Windows 11, version 23H2: Successfully installed on 04/11/2023
- Windows 11, version 22H2: Successfully installed on 22/10/2022
- Windows 11: Successfully installed on 14/10/2022
The most recent Quality Updates for Windows 11 are:
- 2024-12 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5048685) : Successfully installed on 20/12/2024 (this is the date on which performed the recovery action)
- 2024-11 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems (KB5046732) : Successfully installed on 24/11/2024
- 2024-11 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5046633 : Successfully installed on 16/11/2024
- 2024-10 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems (KB5044380) : Successfully installed on 26/10/2024
I.e. no mention in the history of the failed attempt to update to 24H2.
Saved the BIOS configuration, since the above investigation had modified some settings:
C:\SWSetup\SP143621>BiosConfigUtility.exe /get:biosconfig_after_24H2_failed_update_recovery.txt
<BIOSCONFIG Version="" Computername="COMPUTERNAME" Date="2024/12/20" Time="11:58:20" UTC="0">
<SUCCESS msg="No errors occurred" />
<Information msg="BCU return value" real="0" translated="0" />
</BIOSCONFIG>
Compared against the previous saved configuration biosconfig_slot5_enable_hot_plug.txt only difference was an additional A physical presence check to modify Secure boot was approved. in the Critical BIOS Event Log. That occurred when temporarily disabled secure boot. It means the BIOS configuration is back to before the temporary changes.
Why is 24H2 no longer available on windows update after cumulative update KB5048685 was installed? contains:
The 24H2 update was pulled from some devices due to bugs and other issues. If you want to force the Windows 11 24H2 update, you can use the Windows 11 Installation Assistant to upgrade.
Haven't found an explict mention of a bug in 24H2 related to the IOMMU.
On 25 Jan 2025 on checking for updates Windows 11, version 24H2 started downloading. Download got to 8 and got a Windows 11 Update dialog with:
This PC doesn't currently meet Windows 11 system requirements
Here'w why:
- We couldn't update the system reserved partition.
Only button enabled was Close.
Need to try and follow the answer to Windows 11 Pro 24H2 update: "We couldn't update the system reserved partition"
The free space after mounting the SRP:
C:\Windows\System32>mountvol y: /s
C:\Windows\System32>dir y:
Volume in drive Y has no label.
Volume Serial Number is 6E63-8558
Directory of Y:\
22/10/2022 16:10 <DIR> EFI
0 File(s) 0 bytes
1 Dir(s) 15,192,064 bytes free
Deleted the font files as suggested:
Y:\EFI\Microsoft\Boot\Fonts>del *.*
Y:\EFI\Microsoft\Boot\Fonts\*.*, Are you sure (Y/N)? y
Y:\EFI\Microsoft\Boot\Fonts>dir y:
Volume in drive Y has no label.
Volume Serial Number is 6E63-8558
Directory of Y:\EFI\Microsoft\Boot\Fonts
14/10/2022 18:42 <DIR> .
14/10/2022 18:42 <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 28,967,936 bytes free
Unmounted the SRP:
C:\Windows\System32>mountvol y: /d
Retried the 22H2 update, this time got a "Almost ready" dialog, which closed itself.
The install completed. Rebooted but got stuck at the same blue screen as before, with no dump taken. Pressed the power button and powered off cleanly.
Power on and disabled Virtualisation Technology for Directed I/O (VTd) in the BIOS. Windows 11 booted, but was still Version 23H2 (OS Build 22631.4751.
Check for Updates reported the install of 24H2, but didn't make a note of the hex error code before selected retry. Got a "We couldn't update the system reserved partition" error again.
Deleted the font files again, and performed a further install of 24H2.
With VTd left disabled, after 3 reboot the update completed and booted into Version 24H2 (OS Build 26100.2894).
Re-enabled VTd (and TXT) in the BIOS. 24H2 then gets stuck at the same blue screen as before.
Disabling TXT, leaving VTx and VTd enabled in the BIOS. 24H2 then gets stuck at the same blue screen as before.
Disabling TXT and VTx, leaving VTd enabled in the BIOS. Got a "Preparing automatic repair" message breifly before getting stuck at the same blue screen as before.
Disabled VTd, TXT and VTx in the BIOS. Went to boot Windows hope to allow any automatic repair to complete. Got a dialog to chose which Windows to boot - both options simply said Windows 11 and were on the same device. On two further attempts to boot Windows 11 from the AlmaLinux grub menu hear the power in the PC cut before restarts. No message on the screen before the power cuts.
BIOS version was 02.94 and the BIOS says 02.95 is available. Updated the BIOS to 02.95 and still boots into AlmaLinux OK. Attempting to boot Windows still cuts the power.
With VTd disabled in the BIOS can boot the 24H2 install media created above but:
- Attempting to repair the PC fails, with no obvious diagnostic message reported.
- Attempting to boot Windows on the NVMe just causes the PC to reboot (the power doesn't cut).
Re-enabled VTd in the BIOS, and the 24H2 install media blue screens as before. I.e. the update to BIOS 02.95 hasn't helped with that problem.