After I install update KB5062553 geting BSOD - IRQL NOT LESS OR EQUAL, Windows 2025

Question

After I install update KB5062553 geting BSOD - IRQL NOT LESS OR EQUAL, Windows 2025

Zdenek Pikal 25

Hello,

We have a problem with Windows 2025. After we installed the last update (KB5062553), we are getting BSOD (stop code: IRQL NOT LESS OR EQUAL, what failed: ntoskrnl.exe) on the computer. We are experiencing this issue on multiple computers after the update.
I try reinstalling the computer, and it works normally, but when I install the update KB5062553 and reboot the computer, and get, BSOD. I reinstalled the drivers on the computer and updated the bios but it didn't help.

Any idea what I could try or where the problem might be? (yes, not installing the update is a rather common solution)

dumpfile
080325-5250-01dump.zip.txt

hw:

Windows: Windows server 2025 Standard

version: 10.0.26100 build 26100

CPU: AMD EPYC 7443 24-Core

RAM: 8 x 32 GB

Motherboard: GIGABYTE H252-Z10-00 Screenshot from 2025-08-03 05-04-55

HY 0 Reputation points

2025-10-28T07:51:32.0933333+00:00

Hi there, same problem. I've experienced ntokrnl errors as well after the update, particularly on 25th October (I am mentioning the date, as I do not know if many people experienced it after the update). Although I am getting black screens, here are some tips: To check for system file violations, such as corruption, use the command prompt sfc/scannow. Utilise Windows Memory Diagnostics, which kind of take a while; use [Dism /Online /Cleanup-Image /CheckHealth] followed by [Dism /Online /Cleanup-Image /ScanHealth] again followed by [Dism /Online /Cleanup-Image /RestoreHealth]. To limit Windows from repairing using Windows Update, use [Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess]. After that, you can choose to use an even more advanced tool, [chkdsk]. Keep in mind that you'll need to open Cmd Prompt with administrator permissions by clicking "Open with Administrator".

Answer accepted by question author

Smith Pham 2,795 Independent Advisor

Dear Team,

The update KB5062553 for Windows Server 2025 is causing the BSOD IRQL_NOT_LESS_OR_EQUAL (ntoskrnl.exe) on your AMD EPYC-based servers. This is a classic symptom of a bad or incompatible Windows update, especially affecting specific hardware (AMD EPYC in this case).

What you should do right now:

Uninstall KB5062553 on all affected systems.
- wusa /uninstall /kb:5062553
- Or via Control Panel > Programs and Features > View Installed Updates
Pause/Block the update using Group Policy or Windows Update settings until Microsoft releases a fixed patch.
Report to Microsoft via Feedback Hub (important for fast-tracking a hotfix)

Best Regards,

0 comments

2 additional answers

Your answer

HY 0 Reputation points

2025-10-28T07:51:32.0933333+00:00

Hi there, same problem. I've experienced ntokrnl errors as well after the update, particularly on 25th October (I am mentioning the date, as I do not know if many people experienced it after the update). Although I am getting black screens, here are some tips: To check for system file violations, such as corruption, use the command prompt sfc/scannow. Utilise Windows Memory Diagnostics, which kind of take a while; use [Dism /Online /Cleanup-Image /CheckHealth] followed by [Dism /Online /Cleanup-Image /ScanHealth] again followed by [Dism /Online /Cleanup-Image /RestoreHealth]. To limit Windows from repairing using Windows Update, use [Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess]. After that, you can choose to use an even more advanced tool, [chkdsk]. Keep in mind that you'll need to open Cmd Prompt with administrator permissions by clicking "Open with Administrator".

Answer 1

I got also a report from a Swiss blog reader, because his HPE Proliant servers with WinSrv 2025 fails with the BSOD in his data centers. After researching I found 3 cases (also Thoma Krenn reported that issue, but without a solution).

The affected Swiss guy tried to get a full memory dump and made several installation tests. The latest findings are: WinSrv 2025 as a clean install in legacy BIOS mode fails, after August 2025 CU has been installed. In this case Wof.sys (a Windows Overlay Filter driver for compressed install images) was mentioned as a root cause within the BSOD message. But Wof.sys is from July 16, 2025, digitally signed from Microsoft). And WinSrv 2025 didn't create a full memory dump, although this was selected in the system settings, according to the blog reader, before he let install the August 2025 security update. All my compiled findings so fare may be found in the English article below. Don't know, if this thread is still monitored by Microsoft moderators. I suggest, that the issue shall be forwared to the Windows Server 2025 developers!

Windows Server 2025: HPE ProLiant DL325 server drops IRQL_NOT_LESS_OR_EQUAL BSOD after July 2025 update

Answer 2

GNETS 0

The same issue occurred with ProLiant DL325 Gen10 Plus v2 with AMD EPYC 7443P 24-core processor and ProLiant DL325 Gen10 with AMD EPYC 7402P 24-core processor. KB5060842 (OS Build 26100.4349) is no problem. However, starting with KB5062553 (OS Build 26100.4652) and KB5064489 (OS Build 26100.4656) or KB5063878 (OS Build 26100.4946), Stop Code: IRQL NOT LESS OR EQUAL What failed: ntoskrnl.exe

0 comments