Windows Memory Diagnostic Results in Event Viewer Where to Find Them
You ran the Windows memory test, the PC restarted — and the result vanished. It did not vanish. Windows filed it in Event Viewer; you just have to know which drawer.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ Finding the result takes 2 minutes
🎥 mdsched chalana aur Event Viewer me result padhna video me step by step hai
The most common complaint about the Windows Memory Diagnostic is not that it fails — it is that it seems to say nothing. The test runs before Windows loads, so when Windows returns, the verdict is delivered as a log entry. This guide shows the exact place: Event Viewer → Windows Logs → System → source MemoryDiagnostics-Results, and how to tell the no-errors entry from the hardware-errors entry. It also covers the honest limit of this built-in tool: a pass here is a good sign, not a full clearance.
Event Viewer — System log (example)
Filter by source
MemoryDiagnostics-Results
What the entries say
Event 1101No errors detected PASS
Event 1102Hardware errors detected FAIL
Example values — your PC shows its own real entries
The two result events to look for. Green means the test found nothing, the error event means it did.
1
Run the Test First with mdsched
Press Windows + R, type mdsched.exe and press Enter
Choose Restart now and check for problems
On the blue test screen, press F1 to open options. The Extended mix is slower and more thorough than Standard; the pass count can also be raised there
Let it finish. The PC restarts into Windows by itself
Resist judging by the restart screen — many systems show the result notification briefly or not at all. The log is the record that cannot be missed.
2
Find the Result in Event Viewer
Press Windows + R, type eventvwr.msc and press Enter
In the left panel open Windows Logs → System
On the right, click Filter Current Log. In the Event sources list, tick MemoryDiagnostics-Results and click OK
The list now shows only your memory test entries. Open the newest one and read the General tab in plain words
No entries at all usually means the test never actually ran — the restart was cancelled, or the PC booted past the tester. Run mdsched.exe again and watch the restart happen.
3
Read What the Entry Is Telling You
Event ID 1101 reports that the Windows Memory Diagnostic tested the memory and detected no errors. That is a pass — for the depth this tool reaches
Event ID 1102 reports that hardware errors were detected. That is a fail: the memory setup has a real problem, and the next step is isolating stick and slot
Note the date and time in the entry. If you ran the test twice, compare entries — the newest one describes the current hardware state, not the old one
Take a photo or screenshot of the entry. If the PC is under warranty, this log is evidence the service centre respects
4
Know This Tool's Honest Limit
The Windows Memory Diagnostic is a screening test, not the final court. It is known to miss faults that the longer, pattern-heavy MemTest86 catches — particularly borderline sticks that fail only under specific patterns or after warming up.
So read its verdicts asymmetrically. A fail here is trustworthy — the tool does not invent hardware errors. A pass here is provisional: if the crashes continue and the symptoms still point at memory, run MemTest86 for 4 full passes before you clear the RAM.
🔴 Event 1102 means act, not watch. A hardware-errors entry will not heal itself. Back up anything important first — a truly faulty stick can corrupt files silently — then isolate the failing stick before it takes data with it.
🎥 Watch the Full Video Guide
Windows Memory Diagnostic ka result kahan chhupa hota hai — video me live dekho.
I cannot find any MemoryDiagnostics-Results entry. What went wrong?
Most likely the test did not run — the restart was interrupted or you chose the check-on-next-restart option and the PC was later shut down instead. Re-run mdsched.exe, choose restart now, and stay until the blue test screen appears.
The result notification popped up and disappeared. Can I see it again?
Yes — that notification is just a copy of the Event Viewer entry. Follow the filter steps on this page and the same result is there permanently, with its date and time.
Standard or Extended test mix — which should I pick?
Standard is the quick screening. Extended adds harder patterns and takes considerably longer — pick it when Standard passes but the crashes still look like memory, or run MemTest86 instead for the deepest check.
This guide is based on the Technical Anshu RAM testing video linked above • Stuck on a step, ask in the video comments 🙏