Announcement

Collapse
No announcement yet.

Error Verifying data in RAM HELP

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

  • Error Verifying data in RAM HELP

    Hi there,

    I have been struggling to find a solution to the problem with my machine. The problem is that a lot of applications crash e.g the Internet Explorer or Firefox as well as casually getting the blue screen of death. I have read that this might be caused by the RAM, so i tested the PC with BurnInTest. I have 2 sticks of DDR2 RAM 1 ghz each, with both of the sticks in the program gives out the Error Verifying data in RAM, with only one stick of RAM in the PC it works fine (both sticks on their own work fine). I'm now confused whether it is the RAM or the motherboard causing this error, also the next step I'm about to take is to test the other RAM slot with one RAM stick to check if it's whether the one RAM slot in the motherboard. Here is the test log after the test has been completed with the two RAM slots in.

    System summary:
    Windows 7 Home Premium Edition build 7600 (32-bit),
    1 x Pentium(R) Dual-Core CPU E5200 @ 2.50GHz,
    2.0GB RAM,
    Intel(R) G33/G31 Express Chipset Family,
    233GB HDD,


    General:
    System Name: HENRY-PC
    Motherboard Manufacturer: ASUSTeK Computer INC.
    Motherboard Name: P5KPL-AM
    Motherboard Version: x.xx
    Motherboard Serial Number: MT708BK03104958
    BIOS Manufacturer: American Megatrends Inc.
    BIOS Version: 0518
    BIOS Release Date: 07/08/2009

    CPU:
    CPU manufacturer: GenuineIntel
    CPU Type: Pentium(R) Dual-Core CPU E5200 @ 2.50GHz
    Codename: Wolfdale
    CPUID: Family 6, Model 17, Stepping 6, Revision R0
    Socket: LGA775
    Lithography: 45nm
    Physical CPU's: 1
    Cores per CPU: 2
    Hyperthreading: Not capable
    CPU features: MMX SSE SSE2 SSE3 SSSE3 DEP PAE Intel64
    Clock frequencies:
    - Measured CPU speed: 2500.1 MHz
    - Multiplier: x12.5
    - Scalable Bus Speed: 200.0 MHz
    - Front Side Bus: 800.0 MHz
    Cache per CPU package:
    - L1 Instruction Cache: 2 x 32 KB
    - L1 data cache: 2 x 32 KB
    - L2 cache: 1 x 2 MB
    - L3 cache: Not applicable

    Memory
    Total Physical Memory: 2038MB
    Available Physical Memory: 1131MB
    Memory devices:
    DIMM 1:
    - 1GB DDR2 SDRAM PC2-6400
    - Corsair CM2X1024-6400
    - SSTL 1.8V, Clk: 400.0MHz, Timings 5-5-5-18 (@ Max. freq.)
    DIMM 3:
    - 1GB DDR2 SDRAM PC2-6400
    - Corsair CM2X1024-6400
    - SSTL 1.8V, Clk: 400.0MHz, Timings 5-5-5-18 (@ Max. freq.)
    Virtual memory: C:\pagefile.sys (allocated base size 2038MB)

    Graphics
    Intel(R) G33/G31 Express Chipset Family
    Chip Type: Intel(R) GMA 3100
    DAC Type: Internal
    Memory: 256MB
    BIOS: Intel Video BIOS
    Driver provider: Intel Corporation
    Driver version: 8.15.10.1930
    Driver date: 9-23-2009
    Monitor 1: 1920x1080x32 60Hz (Primary monitor)

    **************
    RESULT SUMMARY
    **************
    Test Start time: Mon Jul 02 14:11:42 2012
    Test Stop time: Mon Jul 02 14:26:44 2012
    Test Duration: 000h 15m 02s
    Temperature HDD 0 (ST3250410AS ATA Device) (Min/Current/Max): 41.0C / 42.0C / 42.0C

    Test Name Cycles Operations Result Errors Last Error
    CPU 54 239 Billion PASS 0 No errors
    Memory (RAM) 35 65.164 Billion FAIL 2931 Error verifying data in RAM
    2D Graphics 1554 12435 PASS 0 No errors
    3D Graphics 0 3531 PASS 0 No errors
    Temperature - - PASS 0 No errors
    Sound 9 15.501 Million PASS 0 No errors
    Video Playback 6 206 PASS 0 No errors
    Disk (C 2 14.505 Billion PASS 0 No errors
    TEST RUN FAILED

    ******************
    DETAILED EVENT LOG
    ******************
    LOG NOTE: 2012-07-02 14:11:42, Status, Main Tests started
    LOG NOTE: 2012-07-02 14:11:43, CPU, 3DNow! SSE4.1 SSE4.2 SSE4a test(s) selected, but CPU feature not detected
    LOG NOTE: 2012-07-02 14:11:43, 3D Graphics, 3D test starting: Duty cycle = 50. Test on primary monitor (0). (x,y) = (0,600). WxH = 300x200.
    LOG NOTE: 2012-07-02 14:11:45, Video, Video test starting: Duty cycle = 70. Test on primary monitor (0). (x,y) = (310,0). WxH = 300x200.
    SERIOUS: 2012-07-02 14:11:59, RAM, Error verifying data in RAM
    LOG NOTE: 2012-07-02 14:11:59, Memory (RAM), Process 2, Data verify error: 0x01E1500C, read 0x2a9401, expected 0x2a9403
    SERIOUS: 2012-07-02 14:11:59, RAM, Error verifying data in RAM
    LOG NOTE: 2012-07-02 14:11:59, Memory (RAM), Process 2, Data verify error: 0x01E1501C, read 0x2a9405, expected 0x2a9407
    SERIOUS: 2012-07-02 14:11:59, RAM, Error verifying data in RAM
    LOG NOTE: 2012-07-02 14:11:59, Memory (RAM), Process 2, Data verify error: 0x01E1508C, read 0x2a9421, expected 0x2a9423
    SERIOUS: 2012-07-02 14:11:59, RAM, Error verifying data in RAM
    LOG NOTE: 2012-07-02 14:11:59, Memory (RAM), Process 2, Data verify error: 0x01E1510C, read 0x2a9441, expected 0x2a9443
    SERIOUS: 2012-07-02 14:11:59, RAM, Error verifying data in RAM
    LOG NOTE: 2012-07-02 14:11:59, Memory (RAM), Process 2, Data verify error: 0x01E1518C, read 0x2a9461, expected 0x2a9463
    SERIOUS: 2012-07-02 14:12:00, RAM, Error verifying data in RAM
    LOG NOTE: 2012-07-02 14:12:00, Memory (RAM), Process 2, Data verify error: 0x01E1519C, read 0x2a9465, expected 0x2a9467
    SERIOUS: 2012-07-02 14:12:00, RAM, Error verifying data in RAM
    LOG NOTE: 2012-07-02 14:12:00, Memory (RAM), Process 2, Data verify error: 0x01E1520C, read 0x2a9481, expected 0x2a9483

    The same error keeps repeating about 3000 times.

  • #2
    I work at a repair depot, managing our test software package. We use PassMark and we see this issue every now and then. Most of the time, it's RAM. But every now and then it's the board.

    In this case, it seems like the board.

    Comment


    • #3
      If you have the Data verify error then there is definitely something wrong.

      It could be motherboard, but it still could be the RAM.

      When you test with both sticks of RAM you have 2GB of RAM. The operating system, drivers and background services might use up 500MB+ of this. BurnInTest can't test this RAM that is in use by the O/S. So maybe 1.5GB is available for testing.

      When you test with 1 RAM stick, you have only 1GB of RAM. But the operating system takes up the same amount of RAM. Meaning the free RAM available to test is much less and the problem might be missed.

      My advice would be to borrow a couple of sticks of compatible RAM from another PC or a friend for a quick test (at least 2GB in total). If you still have a problem with the new RAM then it is almost surely the MB or CPU at fault.

      Comment


      • #4
        Error Verifying data in RAM - not a RAM / Mobo problem but a DRIVER problem!

        A friend of mine has a Dell Latitude D630 laptop which had random BSOD's all pointing to either RAM or a driver problem.

        I focused on RAM problems. I know this laptop should detect bad RAM automatically, but it did not complain.

        So I did an MS Ramcheck. Again, no problems found.

        With BurnInTest I did find RAM errors (error verifying data: expected 0x0, got 0xRANDOM).

        Strange. Especially because I could not easily reproduce it - when just running PassMark there would be no errors. But sometimes there were errors, and a lot. Re-fitting the RAM seemed to help at first. After few days of testing / using the laptop I figured it could be caused by sound - for when I played Youtube in Chrome I got errors more quickly, I thought). Again, reproducing the RAM problem appeared to be tricky.

        After some stress test WITH errors, I noticed that everytime another RAM memory address was at fault. That just didn't made sence! Within a Passmark session, the memory address failing would be constant (as you would expect). Only when running a new test, the bad RAM appears to move to a new location... And stays consistent for that address until the next test session.... :s

        So I downloaded the official driver for sound from the Dell site and installed their driver (the sound device did change its name in device manager). Now, after half a day of testing and playing videos, I did not encounter any RAM errors anymore.

        SO IN SHORT: Error reading RAM COULD be caused by defective driver too... Try to change drivers to test if you have the same symptons I described above...

        Peace!

        Devvie


        ~~~ notemail@facebook.com ~~~

        Cuisvis hominis est errare, nullius nisi insipientis in errore persevare
        ——
        All spelling mistakes are my own and may only be distributed under the GNU General Public License! – ( 95-1 by Coredump; 2-012 by DevNullius)

        Comment

        Working...
        X