GoKawiilMicrosoft confirms Windows Server 2025 memory bug crashing SQL Server apps
Microsoft has acknowledged that a memory-management change in Windows Server 2025 is causing crashes, memory corruption, and access violations in applications using Address Windowing Extensions (AWE), including SQL Server instances with Lock Pages in Memory enabled. Affected systems may show error code 0xC0000005, failed database maintenance tasks, crash dumps, and unexpected service restarts.
GoKawiil's interpretation of the reporting above, not reported fact.
SQL Server is widely deployed in enterprise environments, so unexpected crashes or memory corruption can disrupt critical business operations and databases. Until Microsoft ships a permanent fix, administrators must choose between disabling LPIM—potentially hurting performance—or risking instability, forcing a tradeoff during migration to the new server OS.
- Windows Server 2025's new memory-management behavior breaks compatibility with older AWE-dependent apps.
- SQL Server with Lock Pages in Memory enabled is a major affected use case, risking crashes and corruption.
- Microsoft offers only a temporary workaround—disabling LPIM or AWE—while it develops a permanent fix.
Kingston Server Premier DDR5 ECC RDIMM — When memory management is the culprit, reliable server RAM is the foundation you want under SQL Server workloads. Kingston's Server Premier ECC registered DIMMs are built for enterprise boxes running Windows Server, with error correction that helps catch corruption before it takes an app down. A solid upgrade for admins provisioning or expanding a Windows Server 2025 host.
See Kingston Server Premier DDR5 ECC RDIMM on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.Source: bleepingcomputer.com, 2026-09-08
Published there as: “Microsoft: Windows Server 2025 changes causing app crashes”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.