Why browser memory tests can't measure ECC corrections

You ran a memory test in your browser and want to know whether your computer’s ECC memory is correcting errors. A speed result can be useful, but it cannot show how many errors ECC has corrected, or confirm that correction is working.

The Memory Test (RAM) measures memory read, write and copy speed, response time, and a performance score. Here’s what those results mean, and where to look for ECC information instead.

Measure memory performance in your browser

1. Open the Memory Test (RAM).
2. Close demanding programs and browser tabs that are using a lot of memory. This helps make repeat runs more comparable.
3. Run the test and note the read, write and copy speeds, response time, and score.
4. Run it again under similar conditions. Compare the results, but don’t treat a speed score as an ECC error count.

The test checks how quickly the browser can work with memory it has been given. It does not read the memory controller’s ECC correction counters or inspect individual memory cells.

What the result means

The score and speeds look consistent

Your browser completed its memory workload at a fairly steady rate. That is useful for comparing performance, but it does not prove that ECC is enabled or that no errors are being corrected. A system can correct errors without a noticeable change in the benchmark result.

The result changes between runs

Other programs, browser activity, power settings, heat, and background system work can all affect performance. A change does not by itself point to an ECC problem. Repeat the test with fewer programs open and compare results taken under similar conditions.

You see a low score or a browser crash

A low score can reflect the computer’s memory speed, the processor, browser workload, or other activity. A crash or freeze can have many causes too. The browser test is not a dedicated memory error detector, so use system or manufacturer diagnostics if you suspect a fault.

You want to know whether ECC corrected errors

The browser test cannot answer this. ECC correction is handled by hardware such as the memory controller, with error information sometimes reported to the operating system or a computer’s management system. Whether those reports are available depends on the hardware, firmware, operating system, and drivers.

How to check ECC correction information

1. Confirm the computer supports system-level ECC. Check the computer or motherboard specifications and the memory configuration. A memory module described as ECC-capable does not guarantee the whole system supports or has enabled ECC. Some DDR5 memory has on-die error correction inside the memory chips, which is not the same as system-level ECC reporting.
2. Check the firmware or management interface. Look in the computer’s BIOS or UEFI setup, or its vendor management tools, for memory error or ECC status. Workstations and servers may expose corrected and uncorrected error counts. Some computers show only whether ECC is enabled, not a running count.
3. Look at Windows hardware error logs. On Windows 11, open Start, search for and open Event Viewer, then go to Windows Logs › System. Look for entries from WHEA-Logger, the Windows Hardware Error Architecture. Some systems record corrected hardware errors there, but entries are not guaranteed to count every ECC correction or identify memory as the source.
4. Check Linux error reporting if available. Linux systems with a supported memory-controller driver may expose error counters through EDAC, the Error Detection and Correction subsystem. Tools such as rasdaemon can record hardware error reports when the platform provides them. If those tools or counters are absent, it does not prove that ECC is disabled; the hardware or driver may not expose the data.
5. Use the manufacturer’s diagnostics for a persistent warning. If firmware or system logs show repeated memory errors, follow the computer or motherboard manufacturer’s diagnostic instructions. On a Mac, System Settings › General › About identifies the model, but macOS does not provide a general built-in screen with a live ECC correction count for users. Check model-specific support information or diagnostics instead.

Why a browser cannot read ECC counters

A browser runs websites in a restricted environment. It can request memory for its own tasks and time how long operations take, but it cannot directly inspect physical memory addresses or read privileged memory-controller registers. Those limits protect the operating system and other programs from websites.

The operating system also manages memory through virtual addresses. The memory available to a browser is not a simple view of specific physical chips, and normal browser APIs do not provide corrected-error totals. That is why a browser benchmark can measure speed without seeing what ECC corrected behind the scenes.

For a performance comparison, use the browser test. For ECC status or error counts, rely on a supported firmware, operating-system, or manufacturer reporting path for your computer.