Windows command guide
Run Windows Memory Diagnostic
Some PC problems look like software issues at first but are actually caused by unstable memory. Random blue screens, sudden reboots, app crashes, and corrupted files can all happen when RAM is failing or running outside stable conditions. Windows includes a built-in memory test launcher so you can schedule a diagnostic without third-party tools.
This guide is written around the specific symptom-command match for run memory diagnostic, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
mdsched.exe
Best place to run it
Command Prompt is the right execution context for this page. Even when elevation is not always required, using the right shell prevents syntax mistakes and makes the output easier to trust.
Fast repair workflow
- Start from the exact symptom on this page: The PC crashes randomly under different workloads
- Run the primary line exactly as shown: mdsched.exe.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Test the original trigger again and compare the result with the problem description on this page.
- Move to the next repair family only after reading the output and deciding what actually changed.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
@echo off
echo Run this CMD sequence in the matching terminal window.
echo Starting targeted repair sequence...
mdsched.exe
echo.
echo Review the output before closing this window.
pause
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
systeminfo
whoami /groups
What problem this command is trying to solve
This command targets suspected memory instability rather than a specific Windows service or cache issue. It is meant to help rule out hardware-related RAM faults.
- The PC crashes randomly under different workloads.
- Blue screens appear without one clear software trigger.
- Files or apps seem to corrupt for no consistent reason.
How the command works
The command opens the Windows Memory Diagnostic scheduler, which lets you reboot and run a memory test before Windows fully loads. That allows the system to check RAM outside a normal desktop session.
When it makes sense to run it
Use it when crashes feel random and cross many different apps or system areas. Memory testing is especially worth considering after hardware changes, overclocking, or recurring blue screens.
Before you run this command
- Open the shell that matches mdsched.exe before you paste it.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: the pc crashes randomly under different workloads.
- Read the command once from start to finish so you know whether it scans, resets, or changes a stored setting.
What result to expect
After running mdsched.exe, compare the result against the symptom that brought you here. The most useful checkpoint is whether the pc crashes randomly under different workloads becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after mdsched.exe is to repeat the action that previously triggered the problem. If blue screens appear without one clear software trigger still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Shell and execution context
This command usually does not need a full elevated repair context, but it still works best when you run it in the shell it was written for and read the output carefully.
Before you run it
The actual test happens after a restart, so save your work first. A clean memory test does not prove every crash is software-related, but it does remove one major hardware suspicion.
When this is probably the wrong fix
This is not the right first fix for every random Windows problem. Use it when the symptom and command target on this page clearly line up with what your PC is actually doing.
What to do if it does not help
If mdsched.exe does not improve the pc crashes randomly under different workloads, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about the specific Windows behavior described on this page.
Frequently asked questions
Should I use mdsched.exe for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets suspected memory instability rather than a specific Windows service or cache issue. It is meant to help rule out hardware-related RAM faults.
What should I check right after mdsched.exe?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether the pc crashes randomly under different workloads becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on mdsched.exe alone?
This is not the right first fix for every random Windows problem. Use it when the symptom and command target on this page clearly line up with what your PC is actually doing.