|
|
|
|
|
by jackblack8989
3222 days ago
|
|
Any experts here care to tell how does one check for RAM quality? Does CPU-Z do it? (Writing from work, don't have admin perms to use) Not talking about this particular case, but maybe case of a RAM not working in general. |
|
On the other hand I've seen memory module with sufficiently unfortunate pattern of broken bits, that it could not be detected by memtest86. Even such tools need some part of memory that they run from and thus does not get tested (also some memory is reserved for BIOS). The problem manifested itself by completely unusable Windows and occassionally flipped bits in files downloaded from network on Linux (I assume that on Linux the faulty bit ended up in DMA bounce buffer, while on windows in something significantly more critical). To confirm my hunch, that it was memory related I netcat'ed few GB worth of CHARGEN output and analyzed the pattern of bit errors, which were perfectly aligned on some boundary. Finding which module was faulty then involved rearranging modules, running memtest86 and repeating the CHARGEN experiment.
Edit: actually diagnosing this took about month and half. memtest86 was passing and there was unrelated known hardware bug in used network card which I though might be related to observed behavior. Experiment with chargen was motivated by finding out whether the bit errors were somehow aligned to TCP segment boundaries, instead I found out they were aligned on some quite large power of two, which clearly pointed to memory issue.