Announcement

Collapse
No announcement yet.

DFI LanParty NF4D Ultra and 2x1GB Issue

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

  • DFI LanParty NF4D Ultra and 2x1GB Issue

    Athlon 64 X2 3800+
    DFI NF4 Ultra-D
    2x F1-3200PHU2-2GBNS (2x1Gb either orange or yellow slots)
    Nvidia Geforce 8600
    Ubuntu Linux 10.04 64-bit / Windows XP SP3 (32-bit)

    Advanced Chipset Features:
    Errata 94: Disable
    Errata 123: Disable
    CPU Spectrum: Disable
    Sata Spectrum: Disable
    PCIE Spectrum: Disable
    SSE/SSE2: Enable
    CPU Thermal-Throttling: Disable
    Memory Hole PCI MMIO: Disable (Enable if 4Gb)
    System BIOS Cacheable: Disable
    ACPI SRAT: Disable
    SLI Broadcast: Disable

    Genie BIOS Settings:
    FSB: 200
    LDT/FSB: X3
    LTD BUS: 16/16
    CPU/FSB: X10
    PCI Express: 100Mhz
    K8 Cool'n'Quiet: Auto
    CPU VID StartUp Value: StartUp

    LTD Voltage: 1.20v
    Chipset Voltage: 1.50v
    DDRAM Voltage: 2.80v
    DRAM +.03v if not 3.2v: Disable

    DRAM Configuration:
    DRAM Freq Set: 166=RAM/FSB:05/06
    CPC: Enable
    TCL: 3.0
    TRCD: 4 Bus Clocks
    TRAS: 8 Bus Clocks
    TRP: 4 Bus Clocks
    TRC: 7 Bus Clocks
    TRFC: 13 Bus Clocks
    TRRD: 2 Bus Clocks
    TWR: 2 Bus Clocks
    TWTR: 2 Bus Clocks
    TRWT: 3 Bus Clocks
    TREF: 3632 Cycles
    Odd Divisor Correct: Disable
    DRAM Bank Interleave: Enable

    DQS Skew Control: Auto
    DQS Skew Value: 0
    DRAM Drive Strenght: Level 7
    DRAM Data Drive Strength: Auto
    Max Async Latency: 8.0 Nano Seconds
    DRAM Response Time: Normal
    Read Preamble Time: 5.5 Nano Seconds
    IdleCycle: 256 Cycles
    Dynamic Counter: Enable
    R/W Queue Bypass: 16x
    Bypass Max: 07x
    32 Byte Grabularity: Disable (4 Bursts)


    Memtest 4.0 always gives me the same result: An error occurs on address line 0x00100000. I've tried the memory in both Auto modes and the modes listed above. This memory was working at 400MHz for approximately 2 months before it failed. Operating systems run on this computer include MS Windows XP (32-bit), Ubuntu Linux 9.10 (32-bit), Ubuntu Linux 10.04 (64-bit). There were no severe problems with previous Corsair XMS Memory, but the motherboard didn't autodetect it properly, so I removed it and shelved it.

    Memory operates in pairs, how do I determine the bad Memory for RMA?

  • #2
    You'll have to test each one by itself using the memtest boot disk.
    In other words, you don't have to run both at the same time for testing purposes.
    You also may want to set the memory timings and voltage to what the manufacturer suggests.

    Good luck!

    Comment


    • #3
      Is there a link? I didn't see anything in the box.

      Comment


      • #4
        Test them individually to see if one may be different than the others.

        Thank you
        GSKILL TECH

        Comment


        • #5
          Okay, I have identified the bad memory. One of the pair has errors between the 512MB point and the 768MB point, which leads me to believe that 1) four memory chips failed simultaneously or 2) one of the buffer lines in that range is shorted to Vcc. For reference, Memtest tells me that the err-bits is 00100000. What I see is that for every pattern sent to the memory, the read pattern has an extra 1 in it. For instance: if the test pattern is 01010101, then the read pattern is 01110101.

          Comment


          • #6
            Send them in for new replacements and all should be well.

            http://www.gskill.com/rma.php

            Thank you
            GSKILL TECH

            Comment

            Working...
            X