MacBook Pro reports memory errors on installing the OS. Memtestx86 seemingly never gets to report an error, but instead after about an hour of testing the screen goes dark and displays this electrical noise on the left side.
You can see it the "noise" at https://www.youtube.com/watch?v=3gr9zF3y_zo&feature=youtu.be
MacBook Pro Retina
There's lots of misinformation in Galt's post.
The first statement is just absurd. MemTest has been testing memory reliably for decades and it's proven its worth probably on millions of occasions.
Then the second statement, "if you wish, you can.." contradicts the first statement.
The third statement, "MacBook Pro reports..." also contradicts the first statement but there's not really any truth to it. If there happens to be a memory error during the installation, something may go awry and that may lead one to suspect a memory error, but it's not as if it's doing the same function as Memtestx86.
The last statement is also false given that the third statement is false. (I suspected a memory error, but the current version of memtestx86 led me to think something else was the cause.)
The error I'm reporting here appears to be due to a bug in the old version of Memtestx86 I had initially been using. It appears that initial kernel memory error is due to a faulty SATA cable and had nothing to do with the memory further confirming the falseness of the third statement.
There's lots of misinformation in Galt's post.
The first statement is just absurd. MemTest has been testing memory reliably for decades and it's proven its worth probably on millions of occasions.
Then the second statement, "if you wish, you can.." contradicts the first statement.
The third statement, "MacBook Pro reports..." also contradicts the first statement but there's not really any truth to it. If there happens to be a memory error during the installation, something may go awry and that may lead one to suspect a memory error, but it's not as if it's doing the same function as Memtestx86.
The last statement is also false given that the third statement is false. (I suspected a memory error, but the current version of memtestx86 led me to think something else was the cause.)
The error I'm reporting here appears to be due to a bug in the old version of Memtestx86 I had initially been using. It appears that initial kernel memory error is due to a faulty SATA cable and had nothing to do with the memory further confirming the falseness of the third statement.
It is technologically impossible to reliably test or evaluate memory installed on a device that relies upon that memory to function.
If you wish, you can certainly use "Memtestx86" to confirm what you already know:
MacBook Pro reports memory errors on installing the OS.
That's all you need to know.
Can a memory error tank the screen in MemTestx86?
