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.
Test your computer RAM for errors using Windows Memory Diagnostic tool. Identify faulty memory modules causing crashes, freezes, and blue screen errors.
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.
Run these in an elevated Command Prompt or PowerShell unless stated otherwise.
mdsched.exe
wmic memorychip get capacity,speed,manufacturer,partnumber
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.
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.
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.
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.
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.
Symptoms include random crashes, blue screens with varying stop codes, file corruption, programs freezing, and failure to boot. Run Windows Memory Diagnostic to confirm.
The extended test can take several hours depending on RAM size. We recommend running the extended test overnight for thorough results.
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.
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.
No reviews yet. Be the first to review!