Memory test unstable after a Windows update

Did a memory test start freezing, closing the tab, or showing very different scores after a Windows update? That change does not automatically mean your RAM is failing. An update can leave background work running, change power or driver behavior, or expose a browser problem.

Use the Memory Test (RAM) to compare read, write, and copy speeds and response time under repeatable conditions. The test runs in your browser, so treat it as a performance check, not a complete memory error diagnosis.

Check the memory test again

1. Open the Memory Test (RAM) on the same computer and in the same browser you used before the update.
2. Save your work, close demanding apps and extra browser tabs, and wait until Windows has finished any visible update or restart activity.
3. Run the test once. Note whether it completes, which results it shows, and whether the page freezes, reloads, or closes.
4. If it completes, restart Windows and run it one more time under similar conditions. Compare read, write, and copy speeds, response time, and the score out of 100.
5. If the page fails, try one other up-to-date browser. Change only one thing at a time so you can tell what affected the result.

A browser memory benchmark uses temporary work and shares the computer with Windows and other open programs. A score can vary even when the RAM is healthy. For more on changing results, see Why browser memory test scores keep changing.

What the result means

The test completes, but the score is different

A different score alone is not proof of a fault. Background updates, antivirus scans, browser tabs, power mode, and changes to Windows scheduling can all affect a short benchmark. Compare repeated runs on the same computer with similar apps open, rather than treating one score as a pass or fail.

The test completes, but one result is consistently lower

Repeatedly lower read, write, or copy performance may point to a different power setting, system load, or browser environment. It does not identify a bad memory stick by itself. Record which result changed and check whether the computer also feels slower in everyday use.

The test freezes or the browser closes

This may be a browser crash, a lack of available memory, an extension conflict, or a system problem. It is more concerning if other apps also freeze, Windows restarts unexpectedly, or the same failure happens in multiple browsers after a clean restart. If the page stalls during a heavy workload, do not keep repeating it; see Memory test stalls under load: what to check.

The test works in another browser

The problem is more likely tied to the original browser, its extensions, profile, or settings than to the RAM itself. If both browsers fail in the same way, investigate Windows, drivers, and system stability next.

How to fix it

1. Restart Windows once. A restart finishes some update tasks and clears temporary processes left running after installation. Use Start › Power › Restart, then wait a few minutes after signing in before testing.
2. Let update work finish. Open Settings › Windows Update and check whether Windows is still downloading or installing updates. Restart if Windows requests it, then test again after the computer settles.
3. Close background workloads. Pause large downloads, game launchers, cloud file sync, and other heavy apps. Open Task Manager with Ctrl + Shift + Esc and check whether another process is using a large amount of memory or processor time. Do not end unfamiliar system processes.
4. Check the browser. Update it, then try a private window or a fresh browser profile to rule out extensions. If the test works there, disable extensions in the regular profile one at a time. You can also try the other browser as a comparison, not as proof that the hardware is fine.
5. Check the power mode. On Windows 11, open Settings › System › Power & battery › Power mode. For a fair comparison, keep the same mode for each run. On a laptop, compare results while plugged in if that is how you normally use it, and check that the device is not overheating.
6. Check display or chipset drivers if more than the memory test is affected. Windows updates can coincide with driver changes. Use Settings › Windows Update › Update history to see what was installed recently. Get drivers from your computer or component maker, and avoid removing a driver just because the test score changed.
7. Use Windows Memory Diagnostic if there are wider symptoms. Save open work, search Windows for Windows Memory Diagnostic, and choose the option to restart and check for problems. The computer will restart to run the check. If it reports memory errors, note the result and contact the device maker or a repair technician.

When it may be a hardware problem

Suspect a memory or system fault when Windows reports memory errors, crashes recur across different apps, or the computer restarts or shows blue screens after the update. A browser benchmark cannot identify which memory module is faulty, and a normal score cannot certify the RAM as error-free.

If the computer has recently had RAM installed, power it off and have a qualified person check that the modules are seated and compatible. If errors persist, use the computer maker's support process or a repair shop. Avoid repeatedly running heavy tests on a machine that is already overheating or crashing.

Why a browser test can change after an update

The Memory Test (RAM) measures performance through browser features and temporary data. It cannot read every hardware detail or replace a dedicated memory diagnostic. Windows updates may also change browser versions, drivers, background services, or power behavior around the same time. That is why repeatable conditions and a second source of evidence matter more than a single score.

If the test is the only thing behaving differently and it completes consistently after a restart, keep using the computer and watch for other symptoms rather than assuming the RAM is damaged.