Announcement

Collapse
No announcement yet.

Serious Errors in Ram Test!

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

  • Serious Errors in Ram Test!

    Hi! Can someone help me trough this, I would really appreciate it!?

    Here are my PC Specs....

    **************
    SYSTEM SUMMARY
    **************
    Windows 7 Ultimate Edition Service Pack 1 build 7601 (64-bit),
    1 x AMD Phenom(tm) II X6 1100T Processor [3296.3 MHz],
    6.0GB RAM,
    AMD Radeon HD 6950,
    1863GB HDD

    GENERAL
    Motherboard Manufacturer: ASRock
    Motherboard Name: 890GX Extreme4

    CPU
    CPU manufacturer: AuthenticAMD
    CPU Type: AMD Phenom(tm) II X6 1100T Processor
    Codename: Thuban
    CPUID: Family 10, Model A, Stepping 0, Revision PH-E0
    Socket: AM3
    Lithography: 45nm
    Physical CPU's: 1
    Cores per CPU: 6

    MEMORY
    Total Physical Memory: 6143MB
    Available Physical Memory: 4473MB
    Memory devices:
    0: - 2048MB, 800MHz,
    1: - Not populated
    2: - 2048MB, 800MHz,
    3: - 2048MB, 800MHz,
    Virtual memory: C:\pagefile.sys (allocated base size 2000MB)

    GRAPHICS
    AMD Radeon HD 6950 1GB

    --------------------------------------------------------------------------
    I've got 289 Serious Errors in 1 Cycle.....PLS HELP... I'm very new to this...
    --------------------------------------------------------------------------
    DETAILED EVENT LOG
    LOG NOTE: 2011-07-21 11:17:22, Status, PassMark BurnInTest V6.0 Std 1030
    LOG NOTE: 2011-07-21 11:17:22, Status, Main Tests started
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 0, Data verify error: 0x0000000012CA7CD8, read 0x44b5f36, expected 0x44f5f36
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 0, Data verify error: 0x00000000130A3CD8, read 0x45b4f36, expected 0x45f4f36
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 0, Data verify error: 0x0000000013611ED8, read 0x47107b6, expected 0x47507b6
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 0, Data verify error: 0x000000001380FED8, read 0x478ffb6, expected 0x47cffb6
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 0, Data verify error: 0x0000000013A99CD8, read 0x4832736, expected 0x4872736
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 1, Data verify error: 0x00000000136FFED8, read 0x4707fb6, expected 0x4747fb6
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 1, Data verify error: 0x00000000138FDED8, read 0x47877b6, expected 0x47c77b6
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 1, Data verify error: 0x0000000013CE9CD8, read 0x4882736, expected 0x48c2736
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 1, Data verify error: 0x0000000013EE7CD8, read 0x4901f36, expected 0x4941f36
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 1, Data verify error: 0x0000000013EF7ED8, read 0x4905fb6, expected 0x4945fb6
    SERIOUS: 2011-07-21 11:18:02, RAM, Error verifying data in RAM
    LOG NOTE: 2011-07-21 11:18:02, Memory (RAM), Process 2, Data verify error: 0x0000000014CCEED8, read 0x4c3fbb6, expected 0x4c7fbb6

  • #2
    Your RAM is very likely to be bad. (there is a small chance it is motherboard, or CPU)

    In binary for the last 2 errors,

    100110001111111101110110110 <== Value written to RAM
    100110000111111101110110110 <== Value read from RAM

    100100101000101111110110110 <== Value written to RAM
    100100100000101111110110110 <== Value read from RAM

    The same single bit is wrong each time.
    It's a pretty serious error as the consequences are likely to be unpredictable.

    Comment


    • #3
      The Ram is new, 2-3 months old "Corsair for Triple Channel" but my MOBO is for Dual.
      Could it be because of the timming 9-9-9-28?

      I've tried one by one, and the 1-st showed (~80 errors), the 2-nd stick showed less, and the 3-rd showed nothing(very surprising).

      Could they be incompatible with my MOBO?
      (didn't tried them on another pc, but I got 1 BSOD "MEMMORY MANAGMENT"!!)
      thx.....

      Comment


      • #4
        Also , can you tell me what to try to see if the ram is realy bad, before I return it!?!?

        Comment


        • #5
          If it was the MB or CPU at fault, then one would expect the faults to remain constant for each stick of RAM. So it is more likely that it is the RAM at fault.

          There should be no problem running 1 stick, 2 sticks, or 3 sticks at a time.

          I assume the machine has a variety of stability problems. It would almost have to have with this many errors.

          You should let the MB decide on RAM timings

          Comment


          • #6
            As you sad , it's definitely the RAM! I've put the only one that's "error free", and the computer is stable now ) I'll return the 2 bad sticks these days.Thx alot for the help.))

            Comment


            • #7
              I know this is after the fact, but you could try a standalone memory test to see if it sees errors also. MemTest86+ is a good one. The last I checked they were up to version 4.2.

              I have found the BurnIn test to be very reliable but I always like to double check errors with another utility.

              Comment


              • #8
                As he was getting a blue screen of death with the bad sticks, and BurnInTest reported an RAM error, then the PC became stable when the bad RAM was removed I would say it was conclusive in this case. We have never seen a case where BIT reported a RAM error that wasn't a real fault of some type.

                Comment


                • #9
                  Hi again I'm still waiting for the ram to be returned to me but the guy's there use memtest and they say that the program doesn't show errors(runing 20hours) (14 passes), and again I tell them that I used it too and nothing!

                  When I started Windows Memory Diagnostic after the first 30-45min ,before I returned the ram ,WMD showed a hardware issue and the removing of the two bad sticks, the pc started to act normally and WMD didn't showed any problems at all.Played games one after another and no BSOD, no errors in BurnInTest , everything was OK.

                  I seriously cant believe that the ram isn't bad or there's a MB or CPU problem, because why when I put ram stick #2 or #3 in slot #1 and there's and error in BurnInTest and WMD, and when I put ram stick #1 in slot #1 and both programs show good results....Simple logic, don't you think!?!

                  Comment


                  • #10
                    Hi again.The service guy's used WMD too and didn't found any errors, and they'll return me the old ram....... I can't f***ing believe it....

                    Comment

                    Working...
                    X