Announcement

Collapse
No announcement yet.

Finished pass #4 (of 4) (Cumulative error count: 2) Help?

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

  • Finished pass #4 (of 4) (Cumulative error count: 2) Help?

    2020-10-06 03:33:24 - MtSupportRunAllTests - Setting random seed to 0x24403430
    2020-10-06 03:33:24 - MtSupportRunAllTests - Start time: 14170245 ms
    2020-10-06 03:33:24 - MtSupportRunAllTests - Enabling memory cache for test
    2020-10-06 03:33:24 - MtSupportRunAllTests - Enabling memory cache complete
    2020-10-06 03:33:24 - Start memory range test (0x0 - 0x86F000000)
    2020-10-06 03:35:04 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 598604298, Expected: FEFFFFFF, Actual: FEFDFFFF
    2020-10-06 03:35:04 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 59A604278, Expected: FEFFFFFF, Actual: FEFDFFFF
    2020-10-06 03:36:00 - MtSupportRunAllTests - Test execution time: 153.435 (Test 6 cumulative error count: 2)

    2020-10-06 03:36:00 - GetIA32ArchitecturalTemp - MSR(0x19C) = 88280800 (Vendor ID: GenuineIntel 6 9E C)
    2020-10-06 03:36:00 - MapTempIntel - MSR(0x1A2) = 640E0D
    2020-10-06 03:36:00 - Running test #7 (Test 7 [Moving inversions, 32-bit pattern])
    2020-10-06 03:36:00 - MtSupportRunAllTests - Setting random seed to 0x7851F05A
    2020-10-06 03:36:00 - MtSupportRunAllTests - Start time: 14323784 ms
    2020-10-06 03:36:00 - MtSupportRunAllTests - Enabling memory cache for test
    2020-10-06 03:36:00 - MtSupportRunAllTests - Enabling memory cache complete
    2020-10-06 03:36:00 - Start memory range test (0x0 - 0x86F000000)

    2020-10-06 04:48:59 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x840000000 - 0x860000000]
    2020-10-06 04:49:00 - Memory range 0x1000 - 0x90000 was not locked. Ignoring...
    2020-10-06 04:49:00 - Memory range 0x91000 - 0x9F000 was not locked. Ignoring...
    2020-10-06 04:49:18 - Memory range 0x1000 - 0x90000 was not locked. Ignoring...
    2020-10-06 04:49:18 - Memory range 0x91000 - 0x9F000 was not locked. Ignoring...
    2020-10-06 04:49:35 - Memory range 0x1000 - 0x90000 was not locked. Ignoring...
    2020-10-06 04:49:35 - Memory range 0x91000 - 0x9F000 was not locked. Ignoring...
    2020-10-06 04:49:53 - MtSupportRunAllTests - Test execution time: 2190.897 (Test 13 cumulative error count: 0)
    2020-10-06 04:49:53 - Finished pass #4 (of 4) (Cumulative error count: 2)
    2020-10-06 04:49:53 - Cleanup - Unlocking all memory ranges...
    2020-10-06 04:49:53 - All memory ranges successfully unlocked
    2020-10-06 05:40:40 - Enabling graphics mode
    2020-10-06 05:40:40 - Get screen size
    2020-10-06 05:40:40 - Current screen size: 1024 x 768
    2020-10-06 05:40:40 - GetIA32ArchitecturalTemp - MSR(0x19C) = 88340800 (Vendor ID: GenuineIntel 6 9E C)
    2020-10-06 05:40:40 - MapTempIntel - MSR(0x1A2) = 640E0D

    " Was not locked. Ignoring.." What does that mean?

    When I turned my screen on this morning while the memtest was running the screen was blank and needed to restart my pc to get it signal back.

    Does this mean my CPU is failing or RAM about the errors?

    Can I return my cpu by telling memtest is giving errors I still got warranty?

    Specs:

    CPU: i9-9900K Default and not overclocked.

    Motherboard: ASUS ROG Maximus XI Hero WIFI

    RAM: G.Skill Trident Z Neo DDR4 3600Mhz 32GB with XMP 2 profile on.

    PSU: Corsair RM850X V2 850W

    GPU: MSI GeForce RTX 2080 SUPER GAMING X TRIO

    Air Cooling: Corsair Hydro H150i PRO

    NVMe: Samsung SSD 970 EVO PLUS 1TB

    Windows 10 Pro, latest updates.





  • #2
    RAM is probably bad.

    See this page to start with
    https://www.memtest86.com/troubleshooting.htm

    Comment


    • #3
      After turning off xmp profile there is no errors, only when I turn on XMP 1/ Asus recommended or XMP 2 Profile

      Comment


      • #4
        Sometimes slowing down the access speeds (for example by turning off XMP) can help hide the errors.

        Comment


        • #5
          Originally posted by David (PassMark) View Post
          Sometimes slowing down the access speeds (for example by turning off XMP) can help hide the errors.
          yes indeed, thanks for fast answer
          Ive returned them warranty.

          Comment

          Working...
          X