Vengeance Pro - Memtest Warning

Pc is experiencing BSOD's so I am currently stress testing all components to rule out hardware issues.

Ram: Corsair 16GB DDR3 2400Mhz Vengeance Pro Kit

Test: Memtest86

Memory ran for 8 passes (approx 20hrs) and completed with 0 errors however during the 13th test (Hammer Test) of each pass a note would appear.

"Note: ram may be vulnerable to high frequency row hammer bit flips"

What does this mean? Could this be the cause of the BSOD's or is this a fault with ALL Corsair memory?

Thanks in advance.

Background info on the rowhammer vulnerability in memory: https://en.wikipedia.org/wiki/Row_hammer

There also is an explanation about the warning message @ passmark: http://www.memtest86.com/technical.htm#algorithm

Test 13 [Hammer Test]

 

The row hammer test exposes a fundamental defect with RAM modules 2010 or later. This defect can lead to disturbance errors when repeatedly accessing addresses in the same memory bank but different rows in a short period of time. The repeated opening/closing of rows causes charge leakage in adjacent rows, potentially causing bits to flip.

 

This test 'hammers' rows by alternatively reading two addresses in a repeated fashion, then verifying the contents of other addresses for disturbance errors. For more details on DRAM disturbance errors, see Flipping Bits in Memory Without Accessing Them: An Experimental Study of DRAM Disturbance Errors by Yoongu Kim et al.

 

Starting from MemTest86 v6.2, potentially two passes of row hammer testing are performed. On the first pass, address pairs are hammered at the highest possible rate. If errors are detected on the first pass, errors are not immediately reported and a second pass is started. In this pass, address pairs are hammered at a lower rate deemed as the worst case scenario by memory vendors (200K accesses per 64ms). If errors are also detected in this pass, the errors are reported to the user as normal. However, if only the first pass produces an error, a warning message is instead displayed to the user.

Unless you are actually targeted with a rowhammer attack, your BSODs are not related to that warning.

Usually for any memory related problem, you will only get some very specific and well known memory related stop codes (like 0A, 1E, 50). It is worth checking that in the event viewer logs, maybe the actual culprit is something else entirely.

Thanks for the links guys,

Well that's 1 component down several more to go :D