mdsched.exe /? No direct switches? Instead: Run → after restart, press F1 before test starts → choose Extended (not Standard or Basic). Takes hours but catches subtle timing errors. 7. Pro tip: The pagefile is your canary If you suspect intermittent memory failure but diagnostics pass, disable pagefile temporarily :
Get-WinEvent -FilterHashtable @LogName='System'; ID=19 | Select-Object TimeCreated, Message Event ID 19 = “WHEA-Logger” memory corrected error — early warning of flaky RAM. Windows 11 compresses memory aggressively. If your Memory Diagnostic passes but you still get crashes, check memory pressure : windows 11 memory check
mdsched.exe Or for advanced control:
System Properties → Advanced → Performance Settings → Advanced → Change → No pagefile → reboot. mdsched
Then run heavy apps. If system crashes only then — your RAM is faulty but was being masked by pagefile usage. Would you like a one-line PowerShell script to automate logging memory diagnostic results every boot? Takes hours but catches subtle timing errors
Task Manager → Performance → Memory Look at vs “Available” — if Committed > RAM size, you’re oversubscribed, and compression/pagefile is hiding a memory leak. 6. Ultimate test: Run mdsched.exe in extended mode Most people run standard mode. But:
wmic memorychip get status If it returns OK or Status OK , your RAM is passing basic electrical self-checks. If blank or error — deeper issue likely. Get-WmiObject -Class Win32_MemoryDevice | Select-Object Status, Availability Better yet — check for corrected memory errors (ECC RAM or reported by firmware):