Windows Server 2025 Crash with IRQL_NOT_LESS_OR_EQUAL BSOD on HPE Supermicro AMD-Based Servers After Installed July 2025 Updates

Windows Server 2025 faces a serious problem. After installing July 2025 updates, servers crash with a “stop code” message. This issue affects expensive business servers from top companies like HPE and Supermicro. The main update causing trouble is KB5062553. This update came out on July 8, 2025. It makes servers show a blue error screen right after users log in.

Understanding the Frustrating Server Crashes

Have you noticed your server acting strangely after the most recent Windows update? A serious problem is affecting some powerful computers, causing them to suddenly stop working. This issue, known as the “Blue Screen of Death” (BSOD), is a major headache for those who rely on their servers to run smoothly. The specific error message, IRQL_NOT_LESS_OR_EQUAL, points to a deep issue within the operating system itself.

This problem appears to have started after the July 2025 security updates for Windows Server 2025 were installed. Servers that were working perfectly before the update are now crashing, leaving system administrators searching for answers. The crashes seem to happen a few minutes after the server starts up, right after the login screen appears.

Affected Server Hardware

The issue seems to be very specific, mainly affecting certain high-performance servers. If you use one of the following models, you should be aware of this potential problem:

HPE ProLiant Servers

• ProLiant DL325 Gen10 Plus v2 with AMD EPYC 7443P processors
• ProLiant DL325 Gen10 with AMD EPYC 7402P processors

Supermicro Servers

• H12SSL-NT motherboards
• H12SSL-CT motherboards
• H12SSL-i motherboards

All these servers use AMD processors. The issue appears linked to AMD EPYC chips. These are not virtual machines but physical servers running Windows Server 2025 directly on the hardware. Reports from users show a clear pattern: the servers were stable with the June 2025 updates but started crashing immediately after installing the July 2025 cumulative update (KB5062553).

The Search for a Cause

Many smart people have been trying to figure out what is going on. At first, some thought the problem might be related to other hardware components, like special storage cards or network adapters. However, even after removing these parts and reinstalling the operating system from scratch, the blue screen error returned as soon as the July 2025 update was applied.

Further investigation looked into whether the server’s startup mode (UEFI vs. legacy BIOS) or security features like TPM (Trusted Platform Module) were to blame. A test was run by installing Windows Server 2025 in legacy BIOS mode, without any special security settings. Even in this simplified setup, the server crashed after installing the latest update, this time pointing to a file called wof.sys. This file is a part of Windows that helps manage compressed files, but it appears to be involved in the crash. Even though the wof.sys driver is new and signed by Microsoft, it seems to be at the center of the conflict.

The Problem Pattern

Here’s what happens when servers get the July update:

1. Before July updates: Servers work fine with June 2025 updates (KB5060842)
2. After July updates: Blue screen crashes appear within minutes of login
3. Fresh install test: Even clean Windows installations crash after getting the update
4. Driver updates don’t help: New drivers and BIOS updates fail to fix the issue

The error message shows:

Stop Code: IRQL_NOT_LESS_OR_EQUAL
What failed: ntoskrnl.exe

Technical Details

The crashes involve two main system files:

• ntoskrnl.exe – The main Windows system file that manages memory and hardware
• Wof.sys – A Windows file compression driver

Technical analysis shows the problem happens when the system tries to access memory that doesn’t exist. This creates an “invalid memory address” error.

What the Experts Are Saying

The problem has been discussed on several online forums, including Reddit and Microsoft’s own Q&A site. In every case, the story is the same: a perfectly fine server starts crashing after the July 2025 update. Experts have tried to analyze the error logs, but the information is limited. The system is failing to create a complete “memory dump,” which is a detailed snapshot of what the computer was doing at the moment of the crash. Without this file, it is very difficult to pinpoint the exact cause.

The evidence so far strongly suggests that the problem lies within the update itself, likely an incompatibility between the new code in Windows Server 2025 and the AMD processors used in these powerful servers. The core of the operating system, a file called ntoskrnl.exe, is consistently named in the error reports, indicating a fundamental issue.

Immediate Solutions

Unfortunately, there is no easy fix for this problem at the moment. The only known workaround is to uninstall the July 2025 updates. However, this is not a good long-term solution because it leaves your server unprotected from security threats that the update was designed to fix.

If your server crashes after July 2025 updates, here’s what works:

Step 1: Remove the Problem Update

1. Open Control Panel
2. Go to Programs and Features
3. Click View Installed Updates
4. Find KB5062553 and uninstall it

Step 2: Block Future Updates

1. Open Windows Update settings
2. Pause updates until Microsoft fixes the problem
3. Set up Group Policy to block KB5062553 specifically

Step 3: Use Command Line Method

Run this command as administrator:

wusa /uninstall /kb:5062553

Why This Matters for IT Teams

This issue creates serious problems:

• Business downtime: Servers crash without warning
• Data center issues: Multiple servers fail at once
• Security risks: Can’t install security updates safely
• Hardware waste: Expensive servers become unusable

The problem affects both Legacy BIOS and UEFI systems. Tests show it happens regardless of security settings like TPM or Secure Boot.

Current Status

As of August 2025, Microsoft hasn’t released an official fix. The company knows about the problem through user reports. Tech experts recommend reporting the issue through Microsoft’s Feedback Hub to speed up a solution. The issue is being reported to Microsoft so their engineers can investigate and hopefully release a patch that solves the problem without causing these devastating crashes. For now, if you manage one of the affected servers, the best advice is to hold off on installing the latest updates until a reliable solution is found. You should stay informed by checking for updates on technology news sites and official Microsoft channels.

Important: Don’t install KB5062553 or later July 2025 updates on AMD EPYC servers until Microsoft provides a fix. The temporary solution is to avoid these updates, even though this leaves security gaps.

This problem shows how Windows updates can break expensive business hardware. IT teams need to test updates carefully before rolling them out to important servers.