Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Diagnostics & reliability · reviewed troubleshooting

Windows Memory Diagnostic: when to run it and how to read the result

Use the built-in memory test when repeated stop errors or instability make RAM plausible, then read the recorded result instead of assuming a clean test proves all hardware is healthy.

Applies to: Windows 11Change risk: LowReviewed: 2026-09-17
Do this first
  1. Save work because the diagnostic requires a restart.
  2. Run mdsched and choose Restart now and check for problems when you are ready.
  3. Allow the test to finish without interrupting the restart cycle.
  4. After sign-in, preserve the result notification or review MemoryDiagnostics-Results in Event Viewer.

What this problem usually means

Microsoft includes Windows Memory Diagnostic in current blue-screen troubleshooting. The test runs after a restart; standard testing is the default and an extended test is available. Results can be reviewed after Windows returns, including through the MemoryDiagnostics-Results log.

Ordered repair path

Work from the narrowest fix to the broader one.

1

Run the built-in memory test before replacing RAM

Low risk

Why this belongs here: The diagnostic provides direct evidence that is more useful than guessing from a generic crash.

  1. Open Run with Windows + R.
  2. Enter mdsched and choose the restart/test option.
  3. Use the default Standard test first; use F1 and Extended when a deeper pass is justified.
  4. After Windows restarts, review the recorded result.
2

Treat a positive result as a hardware branch, not a Windows repair branch

Low risk

Why this belongs here: Memory errors shift the next step toward module/slot/vendor testing rather than repeated SFC, browser resets or app reinstalls.

  1. Record the exact result.
  2. Return overclock/XMP/EXPO settings to supported defaults for diagnosis when applicable.
  3. Use the PC/memory vendor hardware test or service path before replacing unrelated Windows components.
Stop condition

When this guide stops being the right path

A clean Windows Memory Diagnostic result does not prove every memory, CPU, board or power fault is impossible. Keep the result as one piece of evidence.

If the problem is still not fixed

If the memory test reports errors, move to hardware/vendor diagnosis; if it is clean, continue with the exact stop code, driver timeline, Event Viewer and storage evidence.

Evidence

Sources reviewed for this page

Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

CommandWindows Memory Diagnostic

Schedule the built-in Windows memory test, which restarts the PC and tests system memory before Windows loads normally again.

GuideNo memory dump after a Windows blue screen: verify capture settings before blaming the crash

A missing MEMORY.DMP or Minidump can reflect dump configuration, paging-file requirements, disk space or an incomplete write—not proof that no bugcheck occurred.

ErrorEvent ID 41 — Kernel-Power: Windows restarted without a clean shutdown

Event ID 41 confirms an unexpected shutdown/restart occurred; it does not by itself name the failed component.

ErrorEvent ID 6008 — EventLog unexpected shutdown: a timestamp clue, not a root cause

Event ID 6008 records that the previous shutdown was unexpected; correlate it with Event ID 41, bugcheck records and the failure timeline.

GuideFind Windows crash dump files: Minidump vs MEMORY.DMP and what each tells you

Locate the dump that matches a Windows stop error and verify dump configuration before assuming Windows failed to capture the crash.

GuideUnexpected restart in Windows 11: use Event ID 41 as a timeline clue, not the diagnosis

Kernel-Power Event ID 41 confirms Windows detected an unclean restart; correlate its fields with bugcheck, power and recent-change evidence before deciding why.