What is Memtest86+ “failsafe” mode for?












3















When starting Memtest86+ version 5.01, there is a blinking message:




==> Press F1 to enter Fail-Safe Mode <==




If I hit F1 there is the usual progression screen, except that the RAM information (freq, timings ...) is replaced by the message:




**** FAIL SAFE **** **** FAIL SAFE ****



No Detection, same reliability




So I understand that memory errors are not detected and that the computer is only stress-tested (which could be useful to test if CPU is good when we now that the RAM is faulty). Am I right ? There is little information about this on the website.










share|improve this question



























    3















    When starting Memtest86+ version 5.01, there is a blinking message:




    ==> Press F1 to enter Fail-Safe Mode <==




    If I hit F1 there is the usual progression screen, except that the RAM information (freq, timings ...) is replaced by the message:




    **** FAIL SAFE **** **** FAIL SAFE ****



    No Detection, same reliability




    So I understand that memory errors are not detected and that the computer is only stress-tested (which could be useful to test if CPU is good when we now that the RAM is faulty). Am I right ? There is little information about this on the website.










    share|improve this question

























      3












      3








      3








      When starting Memtest86+ version 5.01, there is a blinking message:




      ==> Press F1 to enter Fail-Safe Mode <==




      If I hit F1 there is the usual progression screen, except that the RAM information (freq, timings ...) is replaced by the message:




      **** FAIL SAFE **** **** FAIL SAFE ****



      No Detection, same reliability




      So I understand that memory errors are not detected and that the computer is only stress-tested (which could be useful to test if CPU is good when we now that the RAM is faulty). Am I right ? There is little information about this on the website.










      share|improve this question














      When starting Memtest86+ version 5.01, there is a blinking message:




      ==> Press F1 to enter Fail-Safe Mode <==




      If I hit F1 there is the usual progression screen, except that the RAM information (freq, timings ...) is replaced by the message:




      **** FAIL SAFE **** **** FAIL SAFE ****



      No Detection, same reliability




      So I understand that memory errors are not detected and that the computer is only stress-tested (which could be useful to test if CPU is good when we now that the RAM is faulty). Am I right ? There is little information about this on the website.







      memtest86+






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 3 hours ago









      Gabriel DevillersGabriel Devillers

      1366




      1366






















          1 Answer
          1






          active

          oldest

          votes


















          4














          According to the source code:



                  /* F1 */
          if(c == scs) { v->fail_safe |= 1; break; }


          Pressing F1 sets the fail_safe 1 bit (same variable is used for other things as well), and then...



          /* Find Memory Specs */
          if(v->fail_safe & 1)
          {
          cprint(LINE_CPU, COL_SPEC, " **** FAIL SAFE **** FAIL SAFE **** ");
          cprint(LINE_RAM, COL_SPEC, " No detection, same reliability ");
          } else {
          find_controller();
          get_spd_spec();
          if(num_cpus <= 16 && !(v->fail_safe & 4)) { coretemp(); }
          }


          ...it skips the "find memory specs" step. Basically this detects what type of memory you have (DDR3, DDR4, ECC, clock speed, etc.) which memtest86+ usually displays on the right hand side.



          Why is it called failsafe? My guess it's because memtest86+ operates on a very low level and a single wrong step would cause it to crash entirely. So maybe doing this detection step crashes some systems, and by pressing F1 maybe you can get past that crash and still use the program.



          I have also found some old posts in the Memtest86 forums asking about failsafe but zero answers.



          http://forum.canardpc.com/threads/83104-Memtest86-5-01-(finally)-released?p=7066673




          Tips : F1 will enable fail-safe mode, F2 will enable SMP Mode (disabled by default) and F3 will trigger an hidden alternative SMP Mode.




          (From reading the source code, those are mutually exclusive, you can only pick one of them or wait for input timeout to commence regular operation.)



          As long as the program works for you, I guess there is no need to worry about it.






          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%2f1399461%2fwhat-is-memtest86-failsafe-mode-for%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            4














            According to the source code:



                    /* F1 */
            if(c == scs) { v->fail_safe |= 1; break; }


            Pressing F1 sets the fail_safe 1 bit (same variable is used for other things as well), and then...



            /* Find Memory Specs */
            if(v->fail_safe & 1)
            {
            cprint(LINE_CPU, COL_SPEC, " **** FAIL SAFE **** FAIL SAFE **** ");
            cprint(LINE_RAM, COL_SPEC, " No detection, same reliability ");
            } else {
            find_controller();
            get_spd_spec();
            if(num_cpus <= 16 && !(v->fail_safe & 4)) { coretemp(); }
            }


            ...it skips the "find memory specs" step. Basically this detects what type of memory you have (DDR3, DDR4, ECC, clock speed, etc.) which memtest86+ usually displays on the right hand side.



            Why is it called failsafe? My guess it's because memtest86+ operates on a very low level and a single wrong step would cause it to crash entirely. So maybe doing this detection step crashes some systems, and by pressing F1 maybe you can get past that crash and still use the program.



            I have also found some old posts in the Memtest86 forums asking about failsafe but zero answers.



            http://forum.canardpc.com/threads/83104-Memtest86-5-01-(finally)-released?p=7066673




            Tips : F1 will enable fail-safe mode, F2 will enable SMP Mode (disabled by default) and F3 will trigger an hidden alternative SMP Mode.




            (From reading the source code, those are mutually exclusive, you can only pick one of them or wait for input timeout to commence regular operation.)



            As long as the program works for you, I guess there is no need to worry about it.






            share|improve this answer




























              4














              According to the source code:



                      /* F1 */
              if(c == scs) { v->fail_safe |= 1; break; }


              Pressing F1 sets the fail_safe 1 bit (same variable is used for other things as well), and then...



              /* Find Memory Specs */
              if(v->fail_safe & 1)
              {
              cprint(LINE_CPU, COL_SPEC, " **** FAIL SAFE **** FAIL SAFE **** ");
              cprint(LINE_RAM, COL_SPEC, " No detection, same reliability ");
              } else {
              find_controller();
              get_spd_spec();
              if(num_cpus <= 16 && !(v->fail_safe & 4)) { coretemp(); }
              }


              ...it skips the "find memory specs" step. Basically this detects what type of memory you have (DDR3, DDR4, ECC, clock speed, etc.) which memtest86+ usually displays on the right hand side.



              Why is it called failsafe? My guess it's because memtest86+ operates on a very low level and a single wrong step would cause it to crash entirely. So maybe doing this detection step crashes some systems, and by pressing F1 maybe you can get past that crash and still use the program.



              I have also found some old posts in the Memtest86 forums asking about failsafe but zero answers.



              http://forum.canardpc.com/threads/83104-Memtest86-5-01-(finally)-released?p=7066673




              Tips : F1 will enable fail-safe mode, F2 will enable SMP Mode (disabled by default) and F3 will trigger an hidden alternative SMP Mode.




              (From reading the source code, those are mutually exclusive, you can only pick one of them or wait for input timeout to commence regular operation.)



              As long as the program works for you, I guess there is no need to worry about it.






              share|improve this answer


























                4












                4








                4







                According to the source code:



                        /* F1 */
                if(c == scs) { v->fail_safe |= 1; break; }


                Pressing F1 sets the fail_safe 1 bit (same variable is used for other things as well), and then...



                /* Find Memory Specs */
                if(v->fail_safe & 1)
                {
                cprint(LINE_CPU, COL_SPEC, " **** FAIL SAFE **** FAIL SAFE **** ");
                cprint(LINE_RAM, COL_SPEC, " No detection, same reliability ");
                } else {
                find_controller();
                get_spd_spec();
                if(num_cpus <= 16 && !(v->fail_safe & 4)) { coretemp(); }
                }


                ...it skips the "find memory specs" step. Basically this detects what type of memory you have (DDR3, DDR4, ECC, clock speed, etc.) which memtest86+ usually displays on the right hand side.



                Why is it called failsafe? My guess it's because memtest86+ operates on a very low level and a single wrong step would cause it to crash entirely. So maybe doing this detection step crashes some systems, and by pressing F1 maybe you can get past that crash and still use the program.



                I have also found some old posts in the Memtest86 forums asking about failsafe but zero answers.



                http://forum.canardpc.com/threads/83104-Memtest86-5-01-(finally)-released?p=7066673




                Tips : F1 will enable fail-safe mode, F2 will enable SMP Mode (disabled by default) and F3 will trigger an hidden alternative SMP Mode.




                (From reading the source code, those are mutually exclusive, you can only pick one of them or wait for input timeout to commence regular operation.)



                As long as the program works for you, I guess there is no need to worry about it.






                share|improve this answer













                According to the source code:



                        /* F1 */
                if(c == scs) { v->fail_safe |= 1; break; }


                Pressing F1 sets the fail_safe 1 bit (same variable is used for other things as well), and then...



                /* Find Memory Specs */
                if(v->fail_safe & 1)
                {
                cprint(LINE_CPU, COL_SPEC, " **** FAIL SAFE **** FAIL SAFE **** ");
                cprint(LINE_RAM, COL_SPEC, " No detection, same reliability ");
                } else {
                find_controller();
                get_spd_spec();
                if(num_cpus <= 16 && !(v->fail_safe & 4)) { coretemp(); }
                }


                ...it skips the "find memory specs" step. Basically this detects what type of memory you have (DDR3, DDR4, ECC, clock speed, etc.) which memtest86+ usually displays on the right hand side.



                Why is it called failsafe? My guess it's because memtest86+ operates on a very low level and a single wrong step would cause it to crash entirely. So maybe doing this detection step crashes some systems, and by pressing F1 maybe you can get past that crash and still use the program.



                I have also found some old posts in the Memtest86 forums asking about failsafe but zero answers.



                http://forum.canardpc.com/threads/83104-Memtest86-5-01-(finally)-released?p=7066673




                Tips : F1 will enable fail-safe mode, F2 will enable SMP Mode (disabled by default) and F3 will trigger an hidden alternative SMP Mode.




                (From reading the source code, those are mutually exclusive, you can only pick one of them or wait for input timeout to commence regular operation.)



                As long as the program works for you, I guess there is no need to worry about it.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 3 hours ago









                frostschutzfrostschutz

                33438




                33438






























                    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%2f1399461%2fwhat-is-memtest86-failsafe-mode-for%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

                    CARDNET

                    Boot-repair Failure: Unable to locate package grub-common:i386

                    Aws NAT - Aws IGW- Aws router