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

by

Troubleshooting Guide: SQL Server Error 540 – Insufficient System Memory to Run RAISERROR

Why This Error Happens

This error occurs when SQL Server 2025’s internal memory manager cannot allocate the small amount of reserved memory needed to construct and raise an error message, typically because the server is already under severe memory pressure. This often happens when the max server memory setting is misconfigured too high relative to available physical RAM, causing contention with the Windows Server 2025 / Windows 11 OS and other processes. It can also be triggered by memory leaks in extended stored procedures, CLR integration objects, or a corrupted memory-resident query plan cache.

Step-by-Step Resolution Guide

Step 1: Verify Current Memory Pressure and Configuration

  • Open SQL Server Management Studio (SSMS) and run EXEC sp_configure 'max server memory (MB)'; to check the current cap.
  • Cross-reference this value with Task Manager on Windows Server 2025 to see if the OS itself is starved for RAM (Available Memory should never drop below 10-15% of total).
  • Query the DMV sys.dm_os_memory_clerks ordered by pages_kb DESC to identify which internal component (e.g., MEMORYCLERK_SQLBUFFERPOOL) is consuming excessive memory.

Step 2: Adjust the Max Server Memory Ceiling

  • Navigate to SSMS > Right-click Server > Properties > Memory.
  • Ensure Maximum server memory is set to leave at least 4GB (or 10% of total RAM, whichever is higher) free for the Windows 11/Server 2025 OS and other services.
  • Apply the change using T-SQL if preferred:
  • EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'max server memory', 24576; RECONFIGURE; (Example sets cap to 24GB).

Step 3: Clear Cache and Restart the Service

  • Flush the procedure cache to release memory tied up by inefficient execution plans using DBCC FREEPROCCACHE;.
  • If the error persists, restart the SQL Server service via the Services console (services.msc) or Server Configuration Manager to force a full memory reset.
  • Check the SQL Server Error Log (default path: C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) for “Failed Virtual Allocate Bytes” warnings preceding the crash.

Step 4: Inspect for Memory-Consuming Third-Party Modules

  • Check if any linked servers, CLR assemblies, or extended stored procedures (xp_ processes) are running that might be hoarding unmanaged memory outside the SQL Server buffer pool.
  • Disable CLR strict security temporarily to test if a specific assembly is the root cause: EXEC sp_configure 'clr strict security', 0; RECONFIGURE;.

Alternative or Verification Steps

  • Verify the Fix: Monitor the Windows Performance Monitor (PerfMon) counter SQLServer:Memory Manager - Total Server Memory (KB) for 24 hours to ensure it stabilizes below the new max server memory cap without hitting 100% utilization spikes.
  • Alternative Solution: If the error continues despite configuration changes, increase the physical RAM allocated to the Virtual Machine/Host or enable “Lock Pages in Memory” for the SQL Server service account via the Windows 11/Server 2025 Local Security Policy (secpol.msc) to prevent the OS from paging out SQL Server’s working set.