brians

We have had confirmation from Microsoft that this is now indeed fixed.

"The fix went out in KB5077179, OS Build 28000.157. It rolled out over time starting mid-Feb, but should be generally available to everyone now. It specially covers the bug in the VirtualMemory allocator in dxgmms2.sys"

You can read more here:
https://support.microsoft.com/en-us/topic/february-10-2026-kb5077179-os-build-28000-1575-74e81d2f-48db-4322-8bd7-8633f8d4d079 [support.microsoft.com]

We have tested internally and can confirm we no longer get the crash.

Thanks all for your patience

An update of sorts:
We are in communication with Microsoft, and they have identified a problem in dxgmm2.sys and have a fix in the works, but have yet to supply a date/KB. We'll update here once we know more.
Thanks for your patience.

rourkepalmer
January 24, 2026—KB5078127 ← Works (as far as I can tell?)

even KB5078127 crashes for me
attached is a repro kit that we've passed on to Microsoft. Are you able to repro the issue with this?