Announcement

Collapse
No announcement yet.

Error Verifying Data in RAM

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Error Verifying Data in RAM

    Dear Experts,

    Performed at least 2 or more successful 12-hour BurnIn Test on the Dell Latitude E5470 (i7-6820HQ, 2x8GB 2133MHz DDR4 Memory, 512GB Samsung SED) with various loads enabled such as CPU, RAM, SSD Disk Drives, Network, Optical Disk, USB, and 3D Graphics running. No Error was detected.

    Used similar test configurations and ran test today on the laptop, but started to receive "Error Verifying Data in RAM". Noticed that the bad error always occurred at position 10th of the 16bit streams. Please find the error logs at below.

    Could you please advise if there is anything I should perform to troubleshoot such error? Do you have any idea what could be the possible cause(s)?

    LOG NOTE: 2016-06-08 09:26:17, Memory (RAM), Process 3, Data verify error: 0x00000000B3B95E00, read 0xffffffefffffffff, expected 0xffffffffffffffff

    LOG NOTE: 2016-06-08 09:28:41, Memory (RAM), Process 3, Data verify error: 0x00000000D06AEE00, read 0x5555554555555555, expected 0x5555555555555555

    LOG NOTE: 2016-06-08 09:30:04, Memory (RAM), Process 3, Data verify error: 0x00000000D06AEE00, read 0xffffffefffffffff, expected 0xffffffffffffffff

    LOG NOTE: 2016-06-08 09:32:11, Memory (RAM), Process 3, Data verify error: 0x00000000D06AEE00, read 0x5555554555555555, expected 0x5555555555555555

    LOG NOTE: 2016-06-08 09:33:37, Memory (RAM), Process 3, Data verify error: 0x00000000D06AEE00, read 0xffffffefffffffff, expected 0xffffffffffffffff

    LOG NOTE: 2016-06-08 09:35:34, Memory (RAM), Process 3, Data verify error: 0x00000000D06AEE00, read 0x5555554555555555, expected 0x5555555555555555
    Tags: ram fail
  • #2
    Do you have any idea what could be the possible cause(s)?
    Yes, if it fails the RAM test, the most likely cause is bad RAM.
    Try replacing it, then retest.

    Comment

    • #3
      I just sign in this forum to share how i fix problem with "Error Verifying Data in RAM" in Burnin test , on Aida64 hardware problem stop system stability test and Memtest86 no error.
      I got 4 modules 2x Mushkin 991778 (99677 and 2x Mushkin 996946, speed is 1333, XMP 1600, Mbo is ASRock P55 Deluxe3 and Intel I5-650 no OC.

      1.Mushkin 991778 (99677 native voltage is 1.5v up to 1333Mhz and 1.65v in 1600Mhz.

      2.Mushkin 996946 native voltage is 1.5v up to 1333Mhz and 1.60v in 1600Mhz.

      1.Mushkin 991778 got error on any speed and 1.6v or 1.65v both Burnin and Aida64 both modules dual or single.

      2.Mushkin 996946 no error on any combination.

      Latency is 9-9-9-24-74 default.

      My suspicion is start because both modules got same error.

      Default voltage in bios if put only 1. modules single or dual is 1.65v but if put all 4 bios down to 1.6v and got "Error Verifying Data in RAM" no matter if is 1.6,1.65 or 1.699.

      To fix problem i try down voltage on 1.59 and after i down voltage no error on any combination, single,dual, four, 1333 or 1600 default timings 9-9-9-24-74-1T in Burnin or Aida64 or MemTest.







      Comment

      • #4
        You shouldn't need to manually adjust voltage levels. The motherboard's BIOS should autoset the correct voltage level for the RAM that is in use. So either the RAM is bad or the BIOS is buggy.

        Original poster also had consistent 1 bit errors, which is a characteristic of bad RAM. So voltage level adjustments probably wouldn't fix it in that case.

        Comment

        • #5
          I,m not post any log here.
          But how long i need run test to be safe a ram is ok?
          If no error in the test that means ram is ok?

          Comment

          • #6
            Here i put default settings in bios 1.65v and test single module.
            Modules is dual ram or same Mushkin 991778.

            1.
            DETAILED EVENT LOG
            LOG NOTE: 2017-02-03 10:56:12, Status, Main Tests started
            SERIOUS: 2017-02-03 10:56:54, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:54, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000062383D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:54, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:54, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:54, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000064D33D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:54, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:54, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:54, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000069CC3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:54, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:54, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000069D03D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000069E93D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000006A1A3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000006AEF3D0, read 0x0000100000000000, expected 0x0000000000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Data verify error: virtual address 0x00000000064323D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Data verify error: virtual address 0x000000000646E3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Data verify error: virtual address 0x00000000064983D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:55, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000006B2F3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Data verify error: virtual address 0x0000000006C6A3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:55, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000077AF3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000007A983D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000007B793D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 1, Data verify error: virtual address 0x0000000006DC33D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 1, Data verify error: virtual address 0x00000000077C93D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 1, Data verify error: virtual address 0x000000000786C3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:56, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:56, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000007BD73D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:57, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 0, Data verify error: virtual address 0x000000000830F3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            SERIOUS: 2017-02-03 10:56:57, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 0, Data verify error: virtual address 0x000000000834F3D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 0, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 1, Data verify error: virtual address 0x0000000007BA33D0, read 0x0000100000000000, expected 0x0000000000000000
            LOG NOTE: 2017-02-03 10:56:57, Memory (RAM), Process 1, Current pattern: 64-bit Zeros (00000000), bits in error 0x0000100000000000
            LOG NOTE: 2017-02-03 10:57:03, Status, Test run stopped

            2.
            DETAILED EVENT LOG
            LOG NOTE: 2017-02-03 11:01:37, Status, Main Tests started
            SERIOUS: 2017-02-03 11:01:47, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:47, Memory (RAM), Process 0, Data verify error: virtual address 0x000000000434BF68, read 0x00000000014557ed, expected 0x00000000004557ed
            LOG NOTE: 2017-02-03 11:01:47, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x00000000014557ed
            SERIOUS: 2017-02-03 11:01:48, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:48, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000005101610, read 0x000000000040c2c2, expected 0x000000000060c2c2
            LOG NOTE: 2017-02-03 11:01:48, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x000000000060c2c2
            SERIOUS: 2017-02-03 11:01:49, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000007BBF610, read 0x0000000000963ec2, expected 0x0000000000b63ec2
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000000b63ec2
            SERIOUS: 2017-02-03 11:01:49, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Data verify error: virtual address 0x0000000008A92F68, read 0x0000000001d3e5ed, expected 0x0000000000d3e5ed
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000001d3e5ed
            SERIOUS: 2017-02-03 11:01:49, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Data verify error: virtual address 0x000000000942F610, read 0x0000000000c71ec2, expected 0x0000000000e71ec2
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000000e71ec2
            SERIOUS: 2017-02-03 11:01:49, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000098F5F68, read 0x0000000001f0abed, expected 0x0000000000f0abed
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000001f0abed
            SERIOUS: 2017-02-03 11:01:49, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Data verify error: virtual address 0x000000000999DF68, read 0x0000000001f1fbed, expected 0x0000000000f1fbed
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000001f1fbed
            SERIOUS: 2017-02-03 11:01:49, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 1, Data verify error: virtual address 0x0000000009654F68, read 0x0000000001ebe9ed, expected 0x0000000000ebe9ed
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 1, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000001ebe9ed
            SERIOUS: 2017-02-03 11:01:49, RAM, Error verifying data in RAM
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 1, Data verify error: virtual address 0x000000000980AF68, read 0x0000000001ef55ed, expected 0x0000000000ef55ed
            LOG NOTE: 2017-02-03 11:01:49, Memory (RAM), Process 1, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0000000001ef55ed
            LOG NOTE: 2017-02-03 11:01:56, Status, Test run stopped


            Comment

            • #7
              Like i say i down voltage to 1.559v after burnin test and aida64 error and now i install and update win10 without problem or lag i use 2 bad modules , i compile in linux without any error.

              Comment

              • #8
                Hi Passmark,
                Would you please check the error log which captured from v9.2.1009?
                Thanks~
                Attached Files

                Comment

                • #9
                  From your log.

                  LOG NOTE: 2022-06-17 12:06:50, Memory (RAM), Process 0, Data verify error: virtual address 0x00000000341D9218, read 0x020000000001fe05, expected 0x000000000001fe05
                  LOG NOTE: 2022-06-17 12:06:50, Memory (RAM), Process 0, Current pattern: 64-bit Sequence (0,1,2...), bits in error 0x0200000000000000

                  It is a 1 bit error. So very likely the RAM is bad.

                  Comment

                  Previous template Next
                  Working...
                  X