🆓 Free Forever ⚡ Instant Results

Windows Memory Diagnostic Guide

Test your computer RAM for errors using Windows Memory Diagnostic tool. Identify faulty memory modules causing crashes, freezes, and blue screen errors.

✓ Free ✓ Fast ✓ No Login Required ✓ Instant Results
Last updated: November 21, 2026
☆ ☆ ☆ ☆ ☆

Test RAM with Windows Memory Diagnostic

Faulty RAM causes random blue screens, application crashes and silent data corruption. The Windows Memory Diagnostic runs outside Windows and tests the physical memory directly. For a definitive result, run an extended pass or a dedicated tool such as MemTest86 overnight.

Common symptoms

  • Random blue screens with different stop codes each time.
  • Applications crash or close without an error message.
  • Files or downloads are corrupted intermittently.
  • The PC fails to start after adding or reseating a memory module.

Step-by-step fix

  1. Save your work and start the test: Run mdsched.exe and choose Restart now and check for problems. The test runs before Windows loads, so unsaved work is lost.
  2. Choose the extended test: Press F1 during the test to select the extended pass. The basic pass finishes quickly but misses marginal faults.
  3. Let the test complete: An extended pass can take several hours depending on capacity. Do not interrupt it. Results are shown after Windows restarts.
  4. Test modules one at a time: If errors are reported, power off, remove all but one module, and test each stick in each slot. This identifies the faulty module or slot rather than condemning all the RAM.
  5. Reseat and retest: Clean the contacts, reseat the modules firmly, and confirm the BIOS is running the memory at a supported speed. Retest before replacing hardware.

Commands used in this guide

Run these in an elevated Command Prompt or PowerShell unless stated otherwise.

mdsched.exe
wmic memorychip get capacity,speed,manufacturer,partnumber
Important: Power off and unplug the PC before touching memory modules. Hold the module by the edges and discharge static electricity first.

When to stop and get help

Escalate if any test reports errors, if a module is not detected, or if the machine will not POST with a known-good stick. Replace the faulty module.

Disclaimer: These guides are for educational purposes. Back up important data and create a restore point before making system changes. Consult a qualified IT professional for critical or business-critical systems.

How To Use Windows Memory Diagnostic Guide

  1. Find the symptom that matches your problem in the symptoms list on this page.
  2. Create a system restore point and back up important files before changing any settings.
  3. Open Command Prompt or PowerShell with Run as administrator so the repair commands can run.
  4. Work through the step-by-step fix in order and read the output of each command.
  5. Stop and follow the escalation advice if the machine becomes unstable or the problem persists.
  6. Repeat the original task to confirm the problem is fixed, then remove any temporary changes.

What is Memory Diagnostic Guide – Test RAM for Errors & Fix Crashes?

Faulty RAM causes random blue screens, application crashes and silent data corruption. The Windows Memory Diagnostic runs outside Windows and tests the physical memory directly. For a definitive result, run an extended pass or a dedicated tool such as MemTest86 overnight.

The checks run in this order: Save your work and start the test, Choose the extended test, Let the test complete, Test modules one at a time, Reseat and retest. Work through them in sequence instead of jumping to the last step, because each check rules out a layer of the problem and makes the next result easier to interpret.

Before you make changes, back up important data and create a system restore point. Run the commands in an elevated Command Prompt or PowerShell, read the output of each one, and stop if a result looks worse than the original symptom.

Benefits of Using Windows Memory Diagnostic Guide

  • Explains the symptoms that point to this specific Windows problem, so you can confirm the diagnosis before changing settings.
  • Lists the exact commands and the order to run them in, instead of a vague list of suggestions.
  • Separates safe read-only checks from changes that need a backup and a restore point.
  • Tells you when to stop and escalate rather than continuing to change an unstable system.
  • Uses built-in Windows tools, so you do not need to install a third-party repair utility.

Best Practices

  • Create a restore point and back up important data before running repair commands.
  • Run commands in an elevated prompt and read the output before moving to the next step.
  • Change one thing at a time so you can tell which step fixed or caused the problem.
  • Do not install third-party "fixer" tools for problems Windows can diagnose itself.
  • If the machine becomes less stable, stop and use Safe Mode or recovery media.

Practical Examples

Symptom: Random blue screens with different stop codes each time

Start at step 1 of the guide and work down. The first check either confirms the cause or rules it out, so you do not skip straight to a destructive repair.

Symptom: Applications crash or close without an error message

Start at step 1 of the guide and work down. The first check either confirms the cause or rules it out, so you do not skip straight to a destructive repair.

Symptom: Files or downloads are corrupted intermittently

Start at step 1 of the guide and work down. The first check either confirms the cause or rules it out, so you do not skip straight to a destructive repair.

Who Should Use This Tool

  • Windows 10 and Windows 11 users diagnosing a problem on their own PC.
  • IT technicians who want a consistent checklist for a common fault.
  • Help-desk staff who need the exact command sequence to give a user.
  • Home users deciding whether a problem is safe to fix or needs a professional.

FAQs

What are signs of bad RAM?

Symptoms include random crashes, blue screens with varying stop codes, file corruption, programs freezing, and failure to boot. Run Windows Memory Diagnostic to confirm.

How long does a memory test take?

The extended test can take several hours depending on RAM size. We recommend running the extended test overnight for thorough results.

Do I need administrator rights for this guide?

Most repair steps need an elevated prompt. Open Command Prompt or PowerShell with Run as administrator before running commands such as sfc, DISM, chkdsk, netsh or net stop. Read-only checks can often run without elevation.

When should I stop and get professional help?

Escalate if any test reports errors, if a module is not detected, or if the machine will not POST with a known-good stick. Replace the faulty module.

User Reviews

No reviews yet. Be the first to review!

Write a Review

☆ ☆ ☆ ☆ ☆
We Value Your Privacy

We use cookies to improve your browsing experience, analyze traffic, and display relevant advertisements.