Windows Memory Diagnostic (mdsched.exe) ((hot)) May 2026

Maya didn’t answer. She was already shutting down, case open, screwdriver in hand. Slot A2. She removed the second DIMM—the one that mapped to those addresses. Rebooted. Ran mdsched.exe again , just to be sure.

“I need a diagnosis , not a mantra.” Maya knew the drill. MemTest86 required a USB boot, BIOS tweaks, and patience she didn’t have at midnight. But Windows had its own scalpel—mdsched.exe. The Windows Memory Diagnostic.

The system rebooted without warning.

This was the third crash this week. The first had been a Blue Screen of Death— MEMORY_MANAGEMENT . She’d ignored it. The second was a sudden reboot while rendering a video. Now this: a total catatonic seizure of the machine that held her master’s thesis on astrophysical simulations.

It was 11:47 PM on a Tuesday, and Maya’s cursor was frozen mid-scroll. The screen—a tableau of half-written code and three Chrome tabs playing different YouTube videos—had become a painting. Ctrl+Alt+Delete did nothing. The Caps Lock key’s LED stared back at her, unblinking, like a dead eye. windows memory diagnostic (mdsched.exe)

Maya watched the percentage tick upward with the intensity of a bomb tech. 23%. 47%. Her system had 32GB of Corsair Vengeance DDR4—four sticks, bought on sale last Black Friday. One of them, she suspected, had turned traitor.

A detailed report opened in Event Viewer: MemoryDiagnostics-Results → Error Count: 4 . Below, in the gory details: “The following memory locations contained errors: 0x000000012F4A8C10, 0x000000012F4A8C18...” Four distinct addresses, all within the same physical bank. Maya didn’t answer

A polite dialog box materialized, absurdly calm: “Check your computer for memory problems.” Two options: Restart now and check, or check next time.