Announcement

Collapse
No announcement yet.

F3-12800CL7D-4GBRH stability problems with Asus M4A89TD

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

    F3-12800CL7D-4GBRH stability problems with Asus M4A89TD

    I am currently having significant stability problems with a pair of 2GB F3-12800CL7D-4GBRH DDR3 modules in my new Asus M4A89TD motherboard. I have an AMD Phenom II X2 processor and use Linux 2.6.35.5.

    So far I have been plagued with both hard and soft lockups, process crashes, kernel oopses and other badness, such as bellyaching from the IOMMU (!!!!!). I have run the x86_64 version of Prime95 for Linux twice; once, it ran for seven hours and then hard locked the system, and the other time it ran for only an hour before exiting with a mathematical error. I have tried to configure and run Memtest86+ version 3.5 on this system using my bootloader (GNU GRUB 0.97) but every time I try to start it the system hard resets.

    When I first installed this motherboard I immediately upgraded to BIOS version 1006, then went in and checked the settings. To my surprise the SPD EEPROM did not emit the correct settings for the BIOS to configure the memory, so I had to manually configure the BIOS for 7-7-7-24-2T with 1.65V and 1600MHz. I did some research on here and also verified that the CPU-NB voltage is set to 1.2V. Interestingly though the BIOS reports a base clock speed of 1333MHz when it POSTs.

    I have since taken out one of the 2GB sticks (serial # 10360640052063) and will try Prime95 again on a soak run to see if the system hard locks once more. Can anyone on here give me some advice on how to proceed before I request an RMA?

    Here are some examples of the IOMMU complaints:

    Code:
    AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad1000 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad10c0 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad1080 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad1140 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad1100 flags=0x0030]
...
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad2b80 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad2e40 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad2b40 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad2f40 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad2f80 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000070ad2fc0 flags=0x0030]
    Code:
    AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x00000000608932c0 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893280 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893040 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893180 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x00000000608930c0 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893240 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893140 flags=0x0030]
...
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893600 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893500 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893400 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893380 flags=0x0030]
AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0014 address=0x0000000060893540 flags=0x0030]
    Here is an example of one of the kernel oopses; the fact that it splattered in exit_mm() in the core VM smells an awful lot like severe memory corruption, especially given that CR2 is near the top of kernel space:

    Code:
    BUG: unable to handle kernel paging request at ffffffffffffff89
IP: [<ffffffff810555d0>] exit_mm+0x4d/0x11c
PGD 1619067 PUD 161a067 PMD 0 
Oops: 0002 [#1] SMP 
last sysfs file: /sys/devices/virtual/block/dm-7/stat
CPU 0 
Modules linked in: ipt_LOG xt_state xt_helper iptable_nat iptable_mangle iptable_filter nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack fglrx(P) snd_usb_audio snd_usbmidi_lib snd_seq_midi pwc snd_rawmidi [last unloaded: scsi_wait_scan]

Pid: 21485, comm: plugin-containe Tainted: P            2.6.35.5-BET #1 M4A89TD PRO USB3/System Product Name
RIP: 0010:[<ffffffff810555d0>]  [<ffffffff810555d0>] exit_mm+0x4d/0x11c
RSP: 0000:ffff88006922dcf0  EFLAGS: 00216d12
RAX: ffff8801363918a0 RBX: ffff880108793cf8 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000015 RDI: ffff8801363918a0
RBP: ffff880118306d30 R08: 0000000000000000 R09: 0000000000000000
R10: ffff880123221108 R11: 000000000000000b R12: ffff880136391840
R13: ffff8801363918a0 R14: ffff880123221108 R15: ffff880137de7400
FS:  00007fd935fc96f0(0000) GS:ffff880001800000(0000) knlGS:00000000f3967b90
CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
CR2: ffffffffffffff89 CR3: 0000000105b87000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process plugin-containe (pid: 21485, threadinfo ffff88006922c000, task ffff880118306d30)
Stack:
 00000000082ae000 ffff880136391840 0000000000000714 0000000000000000
<0> 000000000000000b ffff880118306d30 ffff880118306d30 ffff880118306d30
<0> ffffffff81057034 0000000000000081 00000000ffffffff 0000000000000000
Call Trace:
 [<ffffffff81057034>] ? do_exit+0x1c2/0x625
 [<ffffffff8107357a>] ? futex_wake+0xdb/0xec
 [<ffffffff81057507>] ? do_group_exit+0x70/0x97
 [<ffffffff81061676>] ? get_signal_to_deliver+0x30e/0x32c
 [<ffffffff81021e1a>] ? do_notify_resume+0x87/0x734
 [<ffffffff81075d20>] ? compat_sys_futex+0x10d/0x12b
 [<ffffffff81022b0b>] ? int_signal+0x12/0x17
Code: 00 00 00 4d 8d 6c 24 60 4c 89 ef e8 4e 60 32 00 49 8b 9c 24 60 03 00 00 48 85 db 74 68 4c 89 ef e8 d4 52 01 00 48 89 2c 24 48 8d <43> 10 48 89 e2 48 87 10 48 89 54 24 08 f0 ff 0b 0f 94 c0 84 c0 
RIP  [<ffffffff810555d0>] exit_mm+0x4d/0x11c
 RSP <ffff88006922dcf0>
CR2: ffffffffffffff89
---[ end trace f7a1950e457b2592 ]---
Fixing recursive fault but reboot is needed!
    Tags: None
  • #2
    Is there an option in the BIOS to disable IOMMU? Otherwise, test each stick separately in different slots too. It could be the motherboard's fault as well.

    Comment

    • #3
      What CPU are you using? You may need to use 8-8-8-24 timings as not all CPUs are capable of CL7 at DDR3-1600.

      Thank you
      GSKILL TECH

      Comment

      • #4
        He said he is using a Phenom II X2 although we don't know its revision.

        Comment

        • #5
          AMD Phenom II X2 C3 stepping

          Originally posted by GSKILL TECH View Post
          What CPU are you using? You may need to use 8-8-8-24 timings as not all CPUs are capable of CL7 at DDR3-1600.

          Thank you
          GSKILL TECH
          Originally posted by mrcmtl View Post
          He said he is using a Phenom II X2 although we don't know its revision.
          It's the C3 stepping of the X2.

          I actually tried backing off the timings to 8-8-8-24 with a command rate of 1T, but that made things much worse.

          So far though my Prime95 soak test seems to be running just fine with a single stick.

          Comment

          • #6
            Bad mobo or CPU if each stick passes Prime on rated specs. Also, double check that you have the latest BIOS.

            Thank you
            GSKILL TECH

            Comment

            • #7
              Originally posted by GSKILL TECH View Post
              Bad mobo or CPU if each stick passes Prime on rated specs. Also, double check that you have the latest BIOS.

              Thank you
              GSKILL TECH
              Well, at this point I'm disinclined to blame the motherboard or the CPU, since the Prime95 settings I'm using would have caused the CPU to explode well before now. Plus, I have a Corsair Hydro Series H70 attached, and even with Prime95 saturating the CPU the motherboard temperature monitor for the CPU socket reads 95 degrees F (the CPU itself reads 83 degrees F).

              I will test out the other stick tomorrow with Prime95, and if the system hard resets again I'mm have to RMA it.

              Comment

              • #8
                Verified - the second stick is bad

                Serial #10360640052063 is definitely bad. I started a Prime95 soak run and it halted only eight minutes in with another mathematical error. I'm going to request an RMA.

                Comment

                • #9
                  Test it in another slot and with the other stick in the same slot that stick A failed, just to make sure it's not the motherboard.

                  Comment

                  • #10
                    Originally posted by mrcmtl View Post
                    Test it in another slot and with the other stick in the same slot that stick A failed, just to make sure it's not the motherboard.
                    I will try that out, and I will be interested to see if it makes a difference - the broken stick fails both in DIMM slot A1 on the M4A89TD and in DIMM slot B2 with the good stick in DIMM slot A2 (recommended for two-stick-only installations by Asus).

                    Comment

                    Previous template Next
                    Working...
                    X