own^Shady
Legacy Member
sry voor de nieuwe post maar ik vond men oude post niet
ik heb memtest gedaan met memtest82 v 3.2
en ik had 532 errors maar alleen in test 5, in de andere 8 test nix van errors
wat wil dat dan precies zeggen dat men ram werkt maar als er te lang gestressed wordt niet ofwa?
den de volgende vraag kannek zien welk van men 2 latjes dat kapot is?
nog es opnieuw doen met 1 latje en kijken wat dat geeft?
er stond ook iet op van ECC disabled wasda?
http://www.memtest86.com/#download0
Test 5 [Block move, 64 moves]
This test stresses memory by using block move (movsl) instructions and is based on Robert Redelmeier's burnBX test. Memory is initialized with shifting patterns that are inverted every 8 bytes. Then 4mb blocks of memory are moved around using the movsl instruction. After the moves are completed the data patterns are checked. Because the data is checked only after the memory moves are completed it is not possible to know where the error occurred. The addresses reported are only for where the bad pattern was found. Since the moves are constrained to a 8mb segment of memory the failing address will always be less than 8mb away from the reported address. Errors from this test are not used to calculate BadRAM patterns.
ik heb memtest gedaan met memtest82 v 3.2
en ik had 532 errors maar alleen in test 5, in de andere 8 test nix van errors
wat wil dat dan precies zeggen dat men ram werkt maar als er te lang gestressed wordt niet ofwa?

den de volgende vraag kannek zien welk van men 2 latjes dat kapot is?
nog es opnieuw doen met 1 latje en kijken wat dat geeft?
er stond ook iet op van ECC disabled wasda?
http://www.memtest86.com/#download0
Test 5 [Block move, 64 moves]
This test stresses memory by using block move (movsl) instructions and is based on Robert Redelmeier's burnBX test. Memory is initialized with shifting patterns that are inverted every 8 bytes. Then 4mb blocks of memory are moved around using the movsl instruction. After the moves are completed the data patterns are checked. Because the data is checked only after the memory moves are completed it is not possible to know where the error occurred. The addresses reported are only for where the bad pattern was found. Since the moves are constrained to a 8mb segment of memory the failing address will always be less than 8mb away from the reported address. Errors from this test are not used to calculate BadRAM patterns.
) kheb nu ook een uurke een half gespeeld met uber lagstoten en maar 512 ram maar nu had ik geen crashes to desktop