Name: Windows Server 2025's SQL Server crash bug, explained
Uploaded: 2026-09-08T09:00:00+00:00
Duration: 54 s
Description: Microsoft confirms a Windows Server 2025 memory-management change can crash SQL Server with access-violation dumps when the Lock Pages in Memory policy is enabled, and it has no fix yet.

Windows Server 2025's SQL Server crash bug, explained.

Software · 2026-09-08 · 54s

Microsoft confirms a Windows Server 2025 memory-management change can crash SQL Server with access-violation dumps when the Lock Pages in Memory policy is enabled, and it has no fix yet.

Read the full story: Windows Server 2025 Memory Change Is Crashing SQL Server →

Transcript

Microsoft has a Windows Server 2025 bug it can't fix yet, and the trigger is a setting it told database admins to turn on. If SQL Server runs with Lock Pages in Memory enabled, a change to how Windows Server 2025 handles that locked memory can crash the instance outright, an access violation, error 0xC0000005. The tell is one line in the startup log: using locked pages in the memory manager.

Microsoft's own known issues page confirms it, and the only workaround right now is disabling that memory protection, which brings back the exact performance risk it was there to prevent. No KB number, no release date for a real fix. If you're running SQL Server on Windows Server 2025 with LPIM on, check your logs today.