How to fix Error 3624 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 3624 — “A System Assertion Check Has Failed”

Why This Error Happens

Error 3624 indicates that an internal SQL Server assertion has failed, meaning the Database Engine detected an unexpected internal state while executing a code path and halted to prevent further damage. This is typically triggered by severe memory corruption, a corrupted database page, a bug in a specific build of SQL Server 2025, or incompatible/outdated hardware drivers (storage or network) causing data integrity issues. It can also surface after an abrupt system crash, faulty RAM, or when running unsupported trace flags that destabilize internal engine logic.

Step-by-Step Resolution Guide

Step 1: Capture and Review the Full Error Context

  • Open the SQL Server Error Log located at C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG.
  • Look for the full assertion text, including the file name, line number, and stack dump reference (e.g., SQLDump0001.txt) generated in the LOG folder.
  • Note the exact SPID, database ID, and page ID (if listed) involved at the time of the crash.

Step 2: Run Database Consistency Checks

  • Open SQL Server Management Studio (SSMS) or a command prompt and run:
  • DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • If corruption is found, review repair options carefully (avoid REPAIR_ALLOW_DATA_LOSS unless a verified backup exists).
  • Restore from the most recent clean backup if corruption is confirmed on critical system or user pages.

Step 3: Validate Hardware and OS-Level Stability

  • On Windows Server 2025 / Windows 11, open Event Viewer and check the System log for disk, memory, or controller-related warnings (Event IDs 7, 9, 11, 51).
  • Run chkdsk C: /f /r (adjust drive letter) and reboot to repair file system-level issues.
  • Run Windows Memory Diagnostic (mdsched.exe) to rule out faulty RAM.
  • Update storage controller and network adapter drivers via Windows Update or OEM support site.

Step 4: Apply the Latest SQL Server 2025 Cumulative Update

  • Download the latest Cumulative Update (CU) from the Microsoft Update Catalog for SQL Server 2025.
  • Install the CU during a scheduled maintenance window, as many assertion failures are resolved in engine patches.
  • After installation, restart the SQL Server service via services.msc or net stop MSSQLSERVER && net start MSSQLSERVER.

Step 5: Disable Non-Standard Trace Flags

  • Check startup parameters in SQL Server Configuration Manager under SQL Server Services → Properties → Startup Parameters.
  • Remove any undocumented or community-sourced trace flags (e.g., -T flags not recommended by Microsoft support).
  • Restart the SQL Server service and monitor the error log for recurrence.

Alternative or Verification Steps

  • Re-run DBCC CHECKDB and monitor the ERRORLOG for 24–48 hours to confirm the assertion does not reoccur under normal workload.
  • If the issue persists after patching and hardware validation, collect the generated SQLDumpXXXX.txt and .mdmp files from the LOG directory and open a Microsoft Support (CSS) ticket, as this may indicate an unreported engine defect requiring a hotfix.