Si ton système le supporte, tu peux toujours installer les "edac-utils", ils pourront te dire quelle barrette cause tout ce bazar.
Par contre, après constatation, fait un "rmmod edac", car sinon ce sont tes disques durs qui vont morfler :).
++
On 4 June 2017 12:12:26 CEST, Alarig Le Lay alarig@swordarmor.fr wrote:
On m’a conseillé memtester en offlist, ça donne ça :
root@argall:~# memtester 7066669056B memtester version 4.3.0 (64-bit) Copyright (C) 2001-2012 Charles Cazabon. Licensed under the GNU General Public License version 2 (only).
pagesize is 4096 pagesizemask is 0xfffffffffffff000 want 6739MB (7066669056 bytes) got 6739MB (7066669056 bytes), trying mlock ...locked. Loop 1: Stuck Address : testing 0FAILURE: possible bad address line at offset 0xf58ca000. Skipping to next test... Random Value : FAILURE: 0x6b775b1413a73efb != 0x6b775b3413a73efb at offset 0x22f24000. FAILURE: 0x7dbd93e3fbdf6891 != 0x7dbd93c3fbdf6891 at offset 0x22f24010. FAILURE: 0xf17dc2c4ffb758fa != 0xf17dc2c6ffb758fa at offset 0x22f24018. FAILURE: 0xeffbe1ec3fdd9f59 != 0xeffbe1ee3fdd9f59 at offset 0x22f24020. FAILURE: 0x5f5e39ca5fbf89ba != 0x5f5e39c85fbf89ba at offset 0x22f24028. FAILURE: 0x5dcb7ca3fdff6569 != 0x5dcb7ca1fdff6569 at offset 0x22f24030. FAILURE: 0xceffd2c17dd391e5 != 0xceffd2e17dd391e5 at offset 0x22f24078. […]
Je crois que je suis bon pour demander un changement de RAM :)
-- alarig