Announcement

Collapse
No announcement yet.

Memtest show error: [UEFI Firmware Error] Could not start CPU3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Memtest show error: [UEFI Firmware Error] Could not start CPU3

    Hi,

    When using Memtest for CPU multithreading test, [UEFI Firmware Error] Could not start CPU3 is displayed. What is the possible cause? CPU or ram? Or BIOS? Thank you!Click image for larger version

Name:	mmexport1575509933089.jpg
Views:	386
Size:	91.1 KB
ID:	46250

  • #2
    Yes it is probably a UEFI firmware bug.
    Can you send us the log from Memtest86. See
    https://www.memtest86.com/support/index.htm

    Comment


    • #3
      Sorry, I don't seem to see the place where the log is generated, only the things shown in the picture above, thank you!

      Comment


      • #4
        Hi David,

        I found that this phenomenon would not occur if the test U disk was always followed or the test tool was put into the hard disk of the machine. Do you know what happened?thanks!

        Comment


        • #5
          if the test U disk was always followed
          Sorry I don't know what you mean by this.

          Comment


          • #6
            Hi David,

            We usually finish the Memtest86 tool in the U disk, insert the U disk to run Memtest86, and then unplug the U disk. UEFI firewall error will appear, but if the U disk is not unplugged during the process of running Memtest86, it is OK. So what's your opinion on this?

            Comment


            • #7
              If you are unplugging the USB drive while MemTest86 is running, then don't.

              Comment


              • #8
                Do we have any testing techniques to follow when testing with Memtest86? it seems to be no fixed way to test, so do you have? thanks!

                Comment


                • #9
                  Connect drive & boot.
                  Run tests.
                  Remove drive.


                  Edit: To remove any doubt I'll add one more line,

                  Connect drive & boot.
                  Run tests.
                  Wait for tests to finish.
                  Remove drive.

                  Comment


                  • #10
                    Connect drive & boot.
                    Run test.
                    Remove drive
                    --> can the fail phenomenon
                    Connect drive & boot.
                    Run test.
                    Stay connect drive
                    --> The fail phenomenon would disappeared

                    Do you know the difference between the two methods? thank you!

                    Comment


                    • #11
                      Connect drive & boot.
                      Run test.
                      Remove drive
                      --> can the fail phenomenon
                      This make no sense. The screen shot you posted showed an error while testing. But here you are saying the error happened after testing. Contradicting your screen shot.

                      Also you are also using an old version of Memtest86. Can you try the current software.

                      Comment


                      • #12
                        What I described is not contradictory to the content of the screenshot, why? There will be different phenomena between moving device and not moving device, and the latest version of Memtest86 is used

                        If you remove the device test, you will see the picture on the screen. If you do not remove the device test, it will not appear.The error in the screen can disappear with my device with Mem test tool plugged in, so do you know that your tool will affect the test?

                        Comment


                        • #13
                          Screen shot show V7.4.
                          Current release is V8.4

                          Comment


                          • #14
                            Yes, we've tried Memtest86 v8.4 or v8.0, it's the same thing

                            Comment

                            Working...
                            X