To test your RAM from within Windows, run Windows Memory Diagnostic, restart when prompted, then read the saved result in Event Viewer. This guide applies to supported editions of Windows 11 and Windows 10. A completed test that reports no hardware errors is a useful first check; an error result should be treated as a hardware or memory-configuration problem until proven otherwise.

Prerequisites and compatibility​

  • Save any open work. Windows Memory Diagnostic must restart the PC and runs before Windows loads.
  • Allow 20–60 minutes for the default Standard test and restart cycle. Systems with large amounts of RAM can take longer.
  • You normally do not need an administrator account just to launch the tool, but User Account Control may request administrator credentials on managed or restricted PCs.
  • Disconnecting external devices is not required for the test, but if you are troubleshooting crashes, leave the PC in its usual hardware configuration for the first run. That makes the result easier to compare with the problem you are experiencing.
  • Windows Memory Diagnostic checks physical memory while Windows is offline. It does not repair RAM, replace a failed module, or identify the exact failing DIMM by itself.

Run Windows Memory Diagnostic​

  1. Save your work and close applications.
  2. Open the diagnostic tool.
    Windows 11
    • Select Start.
    • Type Windows Memory Diagnostic.
    • Select Windows Memory Diagnostic from the search results.
    Windows 10
    • Select Start.
    • Type Windows Memory Diagnostic.
    • Select Windows Memory Diagnostic from the search results.
    If search does not find it, use the Run dialog:
    • Press Windows + R.
    • Type:
      mdsched.exe
    • Select OK.
  3. In the Windows Memory Diagnostic dialog, select:
    Restart now and check for problems (recommended)
    The other option, Check for problems the next time I start my computer, only schedules the test. Select it if you must delay the restart, then perform a normal Restart later.
    Warning: Selecting the recommended option immediately restarts Windows. Unsaved documents, open remote sessions, downloads, and work in virtual machines can be interrupted. Save work and ensure any device encryption, remote-management, or business application requirements are satisfied before continuing.
    Click to expand...
  4. Let the PC restart. Before the sign-in screen, a blue Windows Memory Diagnostic screen appears and the test begins automatically.
    Expected result:
    • A progress percentage appears.
    • Windows runs the default Standard test mix.
    • Do not turn off the PC or press the reset button while the test is running.
  5. Wait for the test to complete. Windows should restart automatically and return to the normal sign-in screen.
  6. Sign in to Windows.
    Windows may display a notification near the clock stating the test result. The notification can take a few minutes to appear and is easy to miss, so verify the result in Event Viewer even if you saw a notification.

Run the more thorough Extended test when needed​

Use the default Standard test first. Run the Extended test when:
  • The Standard test reports no errors but you still have repeated blue screens, random restarts, application crashes, corrupted archives, or unexplained file corruption.
  • You recently changed RAM speed, timings, voltage, or an XMP/EXPO memory profile.
  • You installed, replaced, or upgraded memory.
  • A technician or PC manufacturer asks for a longer memory test.
  1. Start Windows Memory Diagnostic again using the earlier steps.
  2. Select Restart now and check for problems (recommended).
  3. When the blue diagnostic screen appears, press F1.
  4. Under Test Mix, use the arrow keys to select Extended.
  5. Press F10 to apply the setting and continue the test.
    Expected result:
    • The test resumes using the Extended mix.
    • It can take substantially longer than the Standard test. Leave the device connected to AC power if it is a laptop.
If you accidentally select a different test mix, restart the diagnostic and select the intended option again. The test does not alter Windows settings or data.

Verify the result in Event Viewer​

The most reliable confirmation is an event from the Microsoft-Windows-MemoryDiagnostics-Results provider.

Method 1: Find the result in the System log​

  1. Right-click Start and select Event Viewer.
    You can also press Windows + R, type the following command, and select OK:
    eventvwr.msc
  2. In the left pane, expand:
    Code: 
    Event Viewer (Local)
> Windows Logs
> System
  3. Select System.
  4. In the right Actions pane, select Find….
  5. Type:
    MemoryDiagnostics-Results
  6. Select Find Next.
  7. Open the newest matching event. Check the General tab for the result message.
    Typical successful result:
    The Windows Memory Diagnostic tested the computer's memory and detected no errors.
    Typical error result:
    The Windows Memory Diagnostic tested the computer's memory and detected hardware errors.
Do not judge the result solely by whether Event Viewer labels the event as Information, Warning, or Error. Read the message itself. Event IDs can vary by Windows version and the kind of result recorded.

Method 2: Filter the System log​

Use this method when the System log contains many events.
  1. In Event Viewer, go to:
    Code: 
    Event Viewer (Local)
> Windows Logs
> System
  2. In the right pane, select Filter Current Log….
  3. In Event sources, select:
    Microsoft-Windows-MemoryDiagnostics-Results
  4. Select OK.
  5. Open the newest event and read the General tab.
To remove the filter afterward, select Clear Filter in the right pane.

Method 3: Check the dedicated diagnostic log​

Some Windows builds also expose a dedicated Memory Diagnostics event channel.
  1. In Event Viewer, expand:
    Code: 
    Event Viewer (Local)
> Applications and Services Logs
> Microsoft
> Windows
> MemoryDiagnostics-Results
  2. Select Debug, if it is present.
  3. Open the newest result entry.
If this channel is empty or unavailable, return to Windows Logs > System and use the provider filter in the previous method. The System log is the practical fallback when a dedicated channel does not show a readable result.

Verify the result from PowerShell​

This alternate method is useful on remote-support sessions, servers, or systems where navigating Event Viewer is inconvenient.
  1. Right-click Start.
  2. Select Terminal (Admin) in Windows 11, or Windows PowerShell (Admin) in Windows 10.
  3. Run:
    Code: 
    Get-WinEvent -FilterHashtable @{
    LogName='System'
    ProviderName='Microsoft-Windows-MemoryDiagnostics-Results'
} -MaxEvents 10 | Format-List TimeCreated, Id, LevelDisplayName, Message
  4. Read the newest entry’s Message field.
Expected result:
  • A completed no-error test reports that no memory errors were detected.
  • A detected-error result reports hardware errors.
If PowerShell returns no matching events, do not assume the test passed. Use the troubleshooting steps below and rerun the test if necessary.

Troubleshooting and escalation​

The PC restarts but no blue memory-test screen appears​

The test may have been scheduled but not started, or the restart may have been interrupted.
  1. Start Windows normally.
  2. Run mdsched.exe again.
  3. Select Restart now and check for problems (recommended).
  4. Wait for the blue diagnostic screen before leaving the PC unattended.
If the diagnostic screen still does not appear, test after temporarily disconnecting nonessential USB storage devices and docking stations, then retry. Do not disconnect the keyboard on a desktop if you may need F1 or F10.

Windows Memory Diagnostic is missing from Start search​

Use the Run command instead:
mdsched.exe
If Windows reports that it cannot find mdsched.exe, run an elevated Command Prompt or Terminal and check whether the file exists:
dir %windir%\System32\mdsched.exe
If it is missing, do not download a replacement executable from an untrusted site. Repair Windows system files first with an elevated Terminal:
Code: 
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Restart after both commands finish, then try mdsched.exe again.

The test appears frozen or does not complete​

Give the test time, particularly with large RAM configurations or the Extended mix. If the percentage and test status do not change for an unusually long period:
  1. Record the percentage and any on-screen error text.
  2. Hold the power button only if the machine is genuinely unresponsive and cannot complete the test.
  3. Start Windows and inspect Event Viewer for a partial or failed result.
  4. Run the Standard test again before trying Extended.
A repeatable freeze during the offline memory test is itself meaningful. Escalate to the PC or motherboard manufacturer if the diagnostic cannot complete under default firmware settings.

There is no result notification after sign-in​

A missed notification does not mean the test failed. Check Event Viewer:
Windows Logs > System
Then filter for:
Microsoft-Windows-MemoryDiagnostics-Results
If there is no result event, confirm that the blue diagnostic screen actually appeared and that Windows completed the second restart. Run the test again and wait for the sign-in screen without forcing a shutdown.

Event Viewer shows only scheduling events, not results​

Events from MemoryDiagnostics-Schedule confirm that Windows scheduled the test, not that it completed successfully. Look specifically for the Microsoft-Windows-MemoryDiagnostics-Results provider in the System log.
If no result exists after a confirmed completed test:
  1. Restart Windows normally once more.
  2. Reopen Event Viewer and repeat the provider filter.
  3. Check the dedicated channel:
    Code: 
    Applications and Services Logs
> Microsoft
> Windows
> MemoryDiagnostics-Results
> Debug
  4. Run the diagnostic again if the result still is not recorded.

The test reports hardware errors​

Treat this as a real hardware or memory-configuration issue. Do not dismiss it because Windows still starts.
First, if you recently enabled overclocking or an XMP/EXPO memory profile, restore the firmware’s default memory settings and repeat the test. A result that disappears at default settings indicates that the memory configuration may be unstable even if the modules are not physically defective.
If errors remain at default settings, contact the system, motherboard, or memory manufacturer for model-specific diagnostics and warranty guidance.
Warning: Reseating or testing RAM modules individually requires opening the PC. Shut down Windows fully, unplug AC power, follow the manufacturer’s service instructions, and protect components from static electricity. On laptops, internal access can affect warranty coverage or damage fragile connectors.
Click to expand...
If you must return to the prior hardware state, reinstall each original RAM module in its original slot, ensure the retaining clips are fully engaged, reconnect power, and confirm that the expected memory amount appears in Task Manager > Performance > Memory after startup.
A no-error Windows Memory Diagnostic result does not completely rule out RAM instability. If crashes continue, repeat the test using Extended, return firmware memory settings to defaults, and use the PC or memory manufacturer’s approved diagnostic procedure before replacing hardware.

References​

  1. Official source: support.microsoft.com
    support.microsoft.com

    How to fix Error 0xA: IRQL_not_less_or_equal | Microsoft Support

    Actions to take when receiving the error Error 0xA: IRQL_not_less_or_equal including running Windows Update and running memory diagnostics.
    support.microsoft.com
  2. Official source: learn.microsoft.com
    learn.microsoft.com

    MemoryDiagnostics-Results - Microsoft Q&A

    hello, this is my Memory Diagnostics Results: can anyone tell me what the problem is?? [-] <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**"> [-] <System> <Provider…
    learn.microsoft.com
  3. Official source: learn.microsoft.com
    learn.microsoft.com

    I can't find memory diagnostic results in Event viewer. - Microsoft Q&A

    I ran the memory diagnostic. You are supposed to be able to find them in the event viewer. Is it the case that there is simply no output if the tool finds no errors? That does not seem very good, one would want to see "no errors found" or…
    learn.microsoft.com
  4. Official source: support.microsoft.com
    support.microsoft.com

    Troubleshooting Windows unexpected restarts and stop code errors | Microsoft Support

    Resolve Windows blue screen errors with tips and resources to do your own troubleshooting, or contact the Microsoft support if you need more help.
    support.microsoft.com
 

Click to expand...
You must log in or register to reply here.