Tuesday, November 25th 2025
Memtest86+ 8.0 Gets Support for Latest Intel/AMD CPUs and More Improvements and Fixes
The popular RAM testing utility, the memtest86+, has been updated to the new 8.0 version, adding support for latest AMD and Intel CPUs as well as plenty of other improvements and fixes, like temperature reporting for DDR5 DIMMs, faster detection of CPUs with high core count, optional Dark Mode, fixed DDR5 XMP 3.0 issue, improved Loongson architecture support and more.
The newest memtest86+ 8.0 version also adds CLang/LLD support, and now ships as a single binary for both UEFI and legacy boot. It also brings better BadRAM support and reporting as well as better SPD detection for early ICHs, and better support for VTxxx serial console. The complete changelog can be found below.memtest86+ v8.00 Changelog
Sources:
Memtest, via Phoronix
The newest memtest86+ 8.0 version also adds CLang/LLD support, and now ships as a single binary for both UEFI and legacy boot. It also brings better BadRAM support and reporting as well as better SPD detection for early ICHs, and better support for VTxxx serial console. The complete changelog can be found below.memtest86+ v8.00 Changelog
- Add support for latest Intel CPUs
- Add support for latest AMD CPUs
- Faster detection for many-cores CPUs
- Added Temperature reporting on DDR5
- Added optional Dark Mode
- Fix DDR5 XMP 3.0 issue
- Better BadRAM support and reporting
- Better SPD detection on early ICHs
- Better support for VTxxx serial console
- Various refinements for Loongson µarch
- Bug fixes & optimizations

11 Comments on Memtest86+ 8.0 Gets Support for Latest Intel/AMD CPUs and More Improvements and Fixes
replaced it with TestMem5 and OCCT
If you are catching issues in windows but not MemTest, there's a good probability that one of your non-isolated variables is causing that. Testing in an isolated environment is very important to limit, as much as possible, the issue down to just the memory. Windows adds a billion other headaches wherein it becomes extremely difficult to narrow down issues just to one component. I've had instances where memory was fine in MemTest but crashed in windows under TestMem and the issue turned out to be Windows Power Management after a boat load of testing. That one I almost gave up on and was ready to replace the parts given how much I had tested.
Same goes memory timings overclock, my memtest missed almost all problems on secondary timings, especially tRFC.
And even memtest cant narrow down problems, it can crash coz of bad cpu memcontroller, or bad VRM on memory or some interference and etc. Not the sticks itself.
Otherwise, this is more useful for deciding if a module should be returned. In other words, a quick good test to determine the floor rather than potential ceiling. If a module fails this, it will fail everything else.
What the hell do people use these days, and is this some kind of modern trend to switch testing programs for another flavour of the month every so often? lol