[German]I'm going to include a post here in the blog that a blog reader described to me a few days ago. An HPE ProLiant DL325 Gen10 Plus v2 running Windows Server 2025 triggers IRQL_NOT_LESS_OR_EQUAL blue screens (stop code 0x0000000a) in ntoskrnl.exe as soon as the July 2025 updates (KB5062553 ff.) are installed. This does not appear to be an isolated case, as I have received two further reports from readers via the Internet. The cause could be incompatibilities with AMD processors, but nothing is known yet.
Advertising
Reader tip about BSOD in Windows Server 2025
Blog reader Marco M. from Swiss had already contacted me in July 2025, but due to vacations and other circumstances, the issue was put on hold. He had serious issues with BSOD on Windows Server 2025, caused by July 2025 updates.
Initial situation with Windows Server 2025 on HPE servers
The initial situation involves the following HPE server models, which are operated in the reader's data center:
- ProLiant DL325 Gen10 Plus v2 with "AMD EPYC 7443P 24-core processor"
- ProLiant DL325 Gen10 with "AMD EPYC 7402P 24-core processor"
Windows Server 2025 is installed directly on the hardware on the HPE servers, so these are not virtual servers.
Everything fine until the June 2025 updates
In the initial report, the reader stated that all machines running Windows Server 2025 that had been patched up to update KB5060842 (OS Build 26100.4349) from June 10, 2025, were running smoothly and had no problems.
July 2025 updates trigger BlueScreen
After installing cumulative update KB5062553 (OS Build 26100.4652) from July 8, 2025, the server starts normally until the login screen. But then, after a few minutes, a BSOD appears with the following error message (stop code 0x0000000a):
Advertising
Stop Code: IRQL_NOT_LESS_OR_EQUAL
What failed: ntoskrnl.exe
Installing the out-of-band update KB5064489 (OS Build 26100.4656) from July 13, 2025 did not change this situation – the BlueScreen continues to appear.
Reinstallation, update, and BSOD again
The blog reader then reinstalled Windows Server 2025 on a machine without configuring any parameters. The installation was successful, and the machine ran without errors. The reader then started Windows Update and reinstalled the cumulative update KB5062553 (OS Build 26100.4652) from July 8, 2025. The process ran smoothly and without errors, so the server was restarted. Shortly after the user logged in, a BlueScreen appeared again:
Stop Code: IRQL_NOT_LESS_OR_EQUAL
What failed: ntoskrnl.exe
After the July 2025 update KB5062553 at the latest, Windows Server 2025 crashes with BSOD on the above-mentioned HPE servers. This does not appear to be an isolated case.
First report on reddit.com
The blog reader wrote to me in his initial email that he had only found one article on reddit.com titled Potential Issues with Windows Server 2025 June 2025 Update that described the same problem. In the case described, Windows Server 2025 was installed on a Supermicro H12SSL-i, AMD EPYC 7313. This installation of Windows Server 2025 worked flawlessly until build 26100.1742.240906-0331.
After the user upgraded to the cumulative update from June 2025, Windows Server 2025 could no longer boot because a BSOD occurred in ntoskrnl.exe. Here, the affected party also attempted to reinstall Windows Server 2025, but again received a BSOD. At first, the affected party thought it might have something to do with an additional RAID card, Mellanox Connectx-5, or 2 x U.2 NVMe's. These were removed and reinstalled. Windows Server 2025 was installed on a Samsung PM983 M.2 NVMe.
The person affected writes that he has seen Proxmox users report a similar problem with Server 2025 VMs (see also Windows 11/Server 2025 June 2025 updates cause BSOD in Proxmox/KVM/QEMU), but nothing about bare metal installations. So far, there has been no indication of the cause in this thread, at least from what I have seen from skimming through it.
Report at Microsoft Q&A
On August 14, 2025, the blog reader contacted me again by email and pointed me to the next hit with the title After I install update KB5062553 geting BSOD – IRQL NOT LESS OR EQUAL, Windows 2025 from August 4, 2025 on Microsoft Q&A.
There is also a problem with Windows Server 2025, which triggers a BSOD with the stop code: IRQL NOT LESS OR EQUAL in ntoskrnl.exe after installing the latest update (KB5062553 from July 8, 2025). According to the person affected, this problem occurs on several computers after the update.
Here, too, it is said that reinstalling Windows Server 2025 helps and the system runs until the June 2025 update KB5062553 is installed. Then the BSOD reappears after a restart. Reinstalling the drivers and updating the BIOS did not help.
The Q&A post contains a link to a mini dump, which I viewed using Nirsoft BlueScreen Viewer. However, this does not provide any further information. A complete dump will probably need to be extracted and analyzed in Windows Debugger in order to narrow down the cause.
Report in the Thomas Krenn Wiki
After I finally posted this article online, a reader pointed me to a wiki article by Thomas Krenn on BlueSky (thanks for the tip).
An undated post titled Windows Update KB5062553 causes IRQL NOT LESS OR EQUAL it is confirmed, that on Supermicro H12 motherboards:
- Supermicro H12SSL-NT
- Supermicro H12SSL-CT
- Supermicro H12SSL-i
since installing the July 2025 updates (KB5062553, ff.), the above BSOD occurs. An unofficial workaround is to uninstall the relevant updates – but this isn't ideal, as it doesn't fix the vulnerabilities. I'll try to report the problem to Microsoft.
Similar article:
Patchday: Windows Server-Updates (June 10, 2025)
Windows 11/Server 2025 June 2025 updates cause BSOD in Proxmox/KVM/QEMU
Windows 11 24H2: Out-of-Band Update KB5063060
Windows 11 22H2 – 24H2 Preview-Updates verfügbar
Windows 10/11 and Server: Known issues (early July 2025)
Advertising
