Random crashes? Test your RAM with Windows Memory Diagnostic

The memory checker built into Windows needs one restart, and Event Viewer keeps its verdict for you to read afterwards.

FREE$34.95UpdateStar PremiumShare a link to claimThird blue screen this week. Each time with a different error code, each time in a different app. Yesterday a game froze, this morning Explorer closed itself while you were copying files, and a reinstall of the graphics driver didn't change a thing. When crashes look this random, the memory modules are high on the list of suspects, and testing them costs you nothing but time.

Windows has a RAM tester on board. It's called Windows Memory Diagnostic, the program behind it is mdsched.exe, and it has shipped with Windows since Vista. It runs outside of Windows, so nothing on your desktop can interfere with the test.

Before you start

The test needs a restart, and while it runs you can't use the PC. Plan for at least a few minutes with the default settings, and much longer if you choose the thorough test mode later on.

  1. Save your open documents and close your programs.
  2. If you're on a laptop, plug in the charger.
  3. Keep this article open on your phone, since your PC will be busy.

Step 1: Launch Windows Memory Diagnostic

  1. Click Start.
  2. Type mdsched and press Enter. Alternatively, press Win+R, type mdsched.exe and click OK.

A small window opens with two choices. Restart now and check for problems (recommended) reboots immediately and starts the test. Check for problems the next time I start my computer waits until you restart yourself, which is handy if you want to finish something first.

Pick one. If you chose the first option, Windows restarts straight away, so make sure your work is saved.

Step 2: Watch the test, or make it tougher

After the restart, a blue Windows Memory Diagnostics Tool screen appears instead of the desktop. It shows a progress bar and a Status area. As long as Status doesn't report problems, everything found so far is fine.

The default run is a good first check. If your crashes are rare and you want to dig deeper, press F1 while the tool is running to open its options:

There are three settings. Test mix picks the depth: Basic, Standard or Extended, and Extended runs the most tests, so it takes the longest. Cache sets the processor cache for each test to Default, On or Off; leave it on Default unless you have a reason. Pass count sets how many times the whole test mix repeats, up to 15. Press F10 to apply your choices and start the test.

On a PC with a lot of RAM, an Extended run with several passes can take hours, so start it in the evening. Faulty memory sometimes only misbehaves once it's warm or under constant load, so a long run catches errors a quick one can miss.

When the test is finished, the PC restarts into Windows on its own.

Step 3: Read the result in Event Viewer

Windows may show the result in a notification after you sign in, but it's easy to miss. The reliable place is Event Viewer, where the diagnostic tool writes an entry after every completed run, whether it found errors or not.

  1. Press Win+R, type eventvwr.msc and press Enter.
  2. In the left pane, expand Windows Logs and click System.
  3. Right-click System and choose Find.
  4. Type MemoryDiagnostics-Results and click Find Next.
  5. Close the Find box and look at the details pane at the bottom.

The System log can hold thousands of events, which is why the search is faster than scrolling. You can also use Filter Current Log in the right-hand pane and pick MemoryDiagnostics-Results as the event source, which hides everything except the memory test entries.

If several entries turn up, check the date and time so you're reading today's test and not one from months ago.

Step 4: Make sense of what you found

If the entry says no errors were detected, that's good news, though not a full acquittal: a single Standard pass can miss a module that only fails occasionally. If the crashes continue, run the Extended mix with two or three passes overnight before you look elsewhere. Overheating, a failing drive or a buggy driver can produce similar symptoms.

If it reports that hardware problems were detected, take it seriously. A memory error means data can be corrupted silently, in files you save as well as in programs you run. Back up your important files first.

Then narrow it down. If your PC has more than one memory module and you're comfortable opening the case, test with one module at a time to find the bad one. Unplug the PC before you touch anything inside, and check your manual for how the modules come out. On laptops with soldered memory, or if the PC is still under warranty, contact the manufacturer instead and give them the test result.

And if there's no entry at all, the test probably didn't finish. A power cut or a forced shutdown ends the run early. Start it again from Step 1 and let it complete.

What not to do

Don't keep working on a PC that reported memory errors while hoping it'll go away. Every crash risks damaging the file you had open, and an Office document or photo library that saves corrupted data won't warn you.

And don't replace RAM based on a hunch alone. One restart with mdsched gives you an answer for free.

Our verdict

Anyone with crashes that don't follow a pattern should run Windows Memory Diagnostic before reinstalling Windows or buying parts. It's built in, it needs nothing beyond a restart, and the result sits in Event Viewer for later. Today, save your work, type mdsched into Start and let the PC test itself while you make coffee.

Related on UpdateStar

about author