When does memtest86+ stop?












56















I'm running memtest now for over 60 hours and don't really understand when it stops. As per the web it runs 12 tests. But are these tests run per memory slot? I have 6 slots and currently passed 21, but it is still going. To get a pass, the 12 tests are run. So I'm a bit confused when this will end.










share|improve this question





























    56















    I'm running memtest now for over 60 hours and don't really understand when it stops. As per the web it runs 12 tests. But are these tests run per memory slot? I have 6 slots and currently passed 21, but it is still going. To get a pass, the 12 tests are run. So I'm a bit confused when this will end.










    share|improve this question



























      56












      56








      56


      2






      I'm running memtest now for over 60 hours and don't really understand when it stops. As per the web it runs 12 tests. But are these tests run per memory slot? I have 6 slots and currently passed 21, but it is still going. To get a pass, the 12 tests are run. So I'm a bit confused when this will end.










      share|improve this question
















      I'm running memtest now for over 60 hours and don't really understand when it stops. As per the web it runs 12 tests. But are these tests run per memory slot? I have 6 slots and currently passed 21, but it is still going. To get a pass, the 12 tests are run. So I'm a bit confused when this will end.







      memtest86+






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 4 '18 at 4:33









      Peter Mortensen

      8,371166185




      8,371166185










      asked Sep 2 '18 at 20:10









      user8user8

      38636




      38636






















          2 Answers
          2






          active

          oldest

          votes


















          99














          It stops when you press Esc, I mean it loops until you stop it.



          The number N of completed passes is indicated as Pass: N (it was Pass: 0 when the very first pass was running). I guess after 60 hours your N is relatively huge.



          The message Pass complete, no errors, pres Esc to exit appears when the very first pass finishes without errors. If consecutive passes finish without errors, the message stays.



          If there were errors, the program also loops. Either way it's your job to stop it. In case of errors there's almost no point of running additional passes. If there are no errors, running multiple passes is advised because there's non-zero probability that a faulty memory module successfully passes all tests. The more passes without errors, the more certain you may be your RAM is fine. In this case you stop the program when you think it's enough.






          share|improve this answer





















          • 10





            Thx for your answer. It passed 21 with no errors, so think thats more than fine

            – user8
            Sep 2 '18 at 21:19






          • 2





            @user8: yes, 2 or 3 passes is usually fine for memtest86+. If you're looking for errors like data corruption while transferring, do Prime95 stress tests with large block sizes to stress cache and the interconnect between CPU and DRAM (at high temperature), rather than looking for a specific DRAM cell or address/data line that's bad.

            – Peter Cordes
            Sep 3 '18 at 23:47



















          5














          Also be aware that there is MemTest86 (the original version) and the MemTest86+ fork (which is not being maintained at the moment). They aren't the same software.



          The current MemTest86 V7 release auto-terminates after 4 passes. It is a good idea to do at least 2 passes, as the first pass is a quicker less intense pass. This was a design choice done with the goal of picking up gross errors faster.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1354648%2fwhen-does-memtest86-stop%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            99














            It stops when you press Esc, I mean it loops until you stop it.



            The number N of completed passes is indicated as Pass: N (it was Pass: 0 when the very first pass was running). I guess after 60 hours your N is relatively huge.



            The message Pass complete, no errors, pres Esc to exit appears when the very first pass finishes without errors. If consecutive passes finish without errors, the message stays.



            If there were errors, the program also loops. Either way it's your job to stop it. In case of errors there's almost no point of running additional passes. If there are no errors, running multiple passes is advised because there's non-zero probability that a faulty memory module successfully passes all tests. The more passes without errors, the more certain you may be your RAM is fine. In this case you stop the program when you think it's enough.






            share|improve this answer





















            • 10





              Thx for your answer. It passed 21 with no errors, so think thats more than fine

              – user8
              Sep 2 '18 at 21:19






            • 2





              @user8: yes, 2 or 3 passes is usually fine for memtest86+. If you're looking for errors like data corruption while transferring, do Prime95 stress tests with large block sizes to stress cache and the interconnect between CPU and DRAM (at high temperature), rather than looking for a specific DRAM cell or address/data line that's bad.

              – Peter Cordes
              Sep 3 '18 at 23:47
















            99














            It stops when you press Esc, I mean it loops until you stop it.



            The number N of completed passes is indicated as Pass: N (it was Pass: 0 when the very first pass was running). I guess after 60 hours your N is relatively huge.



            The message Pass complete, no errors, pres Esc to exit appears when the very first pass finishes without errors. If consecutive passes finish without errors, the message stays.



            If there were errors, the program also loops. Either way it's your job to stop it. In case of errors there's almost no point of running additional passes. If there are no errors, running multiple passes is advised because there's non-zero probability that a faulty memory module successfully passes all tests. The more passes without errors, the more certain you may be your RAM is fine. In this case you stop the program when you think it's enough.






            share|improve this answer





















            • 10





              Thx for your answer. It passed 21 with no errors, so think thats more than fine

              – user8
              Sep 2 '18 at 21:19






            • 2





              @user8: yes, 2 or 3 passes is usually fine for memtest86+. If you're looking for errors like data corruption while transferring, do Prime95 stress tests with large block sizes to stress cache and the interconnect between CPU and DRAM (at high temperature), rather than looking for a specific DRAM cell or address/data line that's bad.

              – Peter Cordes
              Sep 3 '18 at 23:47














            99












            99








            99







            It stops when you press Esc, I mean it loops until you stop it.



            The number N of completed passes is indicated as Pass: N (it was Pass: 0 when the very first pass was running). I guess after 60 hours your N is relatively huge.



            The message Pass complete, no errors, pres Esc to exit appears when the very first pass finishes without errors. If consecutive passes finish without errors, the message stays.



            If there were errors, the program also loops. Either way it's your job to stop it. In case of errors there's almost no point of running additional passes. If there are no errors, running multiple passes is advised because there's non-zero probability that a faulty memory module successfully passes all tests. The more passes without errors, the more certain you may be your RAM is fine. In this case you stop the program when you think it's enough.






            share|improve this answer















            It stops when you press Esc, I mean it loops until you stop it.



            The number N of completed passes is indicated as Pass: N (it was Pass: 0 when the very first pass was running). I guess after 60 hours your N is relatively huge.



            The message Pass complete, no errors, pres Esc to exit appears when the very first pass finishes without errors. If consecutive passes finish without errors, the message stays.



            If there were errors, the program also loops. Either way it's your job to stop it. In case of errors there's almost no point of running additional passes. If there are no errors, running multiple passes is advised because there's non-zero probability that a faulty memory module successfully passes all tests. The more passes without errors, the more certain you may be your RAM is fine. In this case you stop the program when you think it's enough.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Sep 2 '18 at 21:00

























            answered Sep 2 '18 at 20:52









            Kamil MaciorowskiKamil Maciorowski

            26.2k155680




            26.2k155680








            • 10





              Thx for your answer. It passed 21 with no errors, so think thats more than fine

              – user8
              Sep 2 '18 at 21:19






            • 2





              @user8: yes, 2 or 3 passes is usually fine for memtest86+. If you're looking for errors like data corruption while transferring, do Prime95 stress tests with large block sizes to stress cache and the interconnect between CPU and DRAM (at high temperature), rather than looking for a specific DRAM cell or address/data line that's bad.

              – Peter Cordes
              Sep 3 '18 at 23:47














            • 10





              Thx for your answer. It passed 21 with no errors, so think thats more than fine

              – user8
              Sep 2 '18 at 21:19






            • 2





              @user8: yes, 2 or 3 passes is usually fine for memtest86+. If you're looking for errors like data corruption while transferring, do Prime95 stress tests with large block sizes to stress cache and the interconnect between CPU and DRAM (at high temperature), rather than looking for a specific DRAM cell or address/data line that's bad.

              – Peter Cordes
              Sep 3 '18 at 23:47








            10




            10





            Thx for your answer. It passed 21 with no errors, so think thats more than fine

            – user8
            Sep 2 '18 at 21:19





            Thx for your answer. It passed 21 with no errors, so think thats more than fine

            – user8
            Sep 2 '18 at 21:19




            2




            2





            @user8: yes, 2 or 3 passes is usually fine for memtest86+. If you're looking for errors like data corruption while transferring, do Prime95 stress tests with large block sizes to stress cache and the interconnect between CPU and DRAM (at high temperature), rather than looking for a specific DRAM cell or address/data line that's bad.

            – Peter Cordes
            Sep 3 '18 at 23:47





            @user8: yes, 2 or 3 passes is usually fine for memtest86+. If you're looking for errors like data corruption while transferring, do Prime95 stress tests with large block sizes to stress cache and the interconnect between CPU and DRAM (at high temperature), rather than looking for a specific DRAM cell or address/data line that's bad.

            – Peter Cordes
            Sep 3 '18 at 23:47













            5














            Also be aware that there is MemTest86 (the original version) and the MemTest86+ fork (which is not being maintained at the moment). They aren't the same software.



            The current MemTest86 V7 release auto-terminates after 4 passes. It is a good idea to do at least 2 passes, as the first pass is a quicker less intense pass. This was a design choice done with the goal of picking up gross errors faster.






            share|improve this answer






























              5














              Also be aware that there is MemTest86 (the original version) and the MemTest86+ fork (which is not being maintained at the moment). They aren't the same software.



              The current MemTest86 V7 release auto-terminates after 4 passes. It is a good idea to do at least 2 passes, as the first pass is a quicker less intense pass. This was a design choice done with the goal of picking up gross errors faster.






              share|improve this answer




























                5












                5








                5







                Also be aware that there is MemTest86 (the original version) and the MemTest86+ fork (which is not being maintained at the moment). They aren't the same software.



                The current MemTest86 V7 release auto-terminates after 4 passes. It is a good idea to do at least 2 passes, as the first pass is a quicker less intense pass. This was a design choice done with the goal of picking up gross errors faster.






                share|improve this answer















                Also be aware that there is MemTest86 (the original version) and the MemTest86+ fork (which is not being maintained at the moment). They aren't the same software.



                The current MemTest86 V7 release auto-terminates after 4 passes. It is a good idea to do at least 2 passes, as the first pass is a quicker less intense pass. This was a design choice done with the goal of picking up gross errors faster.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 27 '18 at 22:43









                Kamil Maciorowski

                26.2k155680




                26.2k155680










                answered Sep 6 '18 at 6:35









                user312931user312931

                811




                811






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1354648%2fwhen-does-memtest86-stop%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Список кардиналов, возведённых папой римским Каликстом III

                    Deduzione

                    Mysql.sock missing - “Can't connect to local MySQL server through socket”