Failing RAM? In this economy?

Now to go beg to the RMA gods

  • digilec@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 hour ago

    You can edit the grub config (assuming you’re using Linux) and add reserved ranges for the affected physical address.

    find the linux boot command and add a memmap=<size>$<start> argument This tells the kernel to avoid the bad parts.

    In your case it looks like a relatively small chunk of bad memory so… memmap=64K$0x130FE0000

    I’ve used this trick to stabilise systems with faulty RAM and it works.

  • dangrousperson@feddit.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 hours ago

    Seems like its always the same core that is creating the error. Could be a bad overclock. Try reseting the bios to default. Also try reseating the RAM (and clean out the slots with compressed air) and rerunning the test. I’ve had similar issues in the past that were fixed by this.

    Once stable overclocks can fail after many years as it slowly wears out some transistors.

  • Treczoks@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 hours ago

    Not good. The pattern is not consistent.

    Take the RAM out and carefully clean the contacts with e.g. alcohol and a piece of lint-free cloth.

  • 0xDREADBEEF@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 hours ago

    I’ve got two 16GB sticks that I bought in 2020 pullin me through—I’m praying they last long enough til prices go back down haha

  • juipeltje@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    8 hours ago

    Dang, i’m a bit worried for my own RAM as well. I keep getting random reboots on my pc every now and then. I initially suspected my distro to be the problem since it started happening after i hopped, but after feeling like i checked everything on the software side, i’m checking hardware now just to be safe anyway. Started with removing the OC from my RAM. I also have my 5800X3D undervolted though since i saw it recommended at the time. Now that it’s a few years old i might just not be stable anymore at that voltage.

  • loric@piefed.social
    link
    fedilink
    English
    arrow-up
    13
    ·
    14 hours ago

    Remove the sticks, blow out your sockets with some compressed air and re-test. I had something similar recently and a full memtest pass ran clean after that.

      • AllHailTheSheep@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 hour ago

        you’d be surprised. it’s not even a about dust. chip creep is still a thing in modern ddr and pcie slots, and can absolutely show up as a bad part. I’ve saved a few gpus and ram sticks from being declared dead after a bad test by just cleaning contacts and reinstalling.

    • Shayeta@feddit.org
      link
      fedilink
      English
      arrow-up
      8
      ·
      13 hours ago

      Also, disable any OC. I had my ram fail tests because it is not supported by my mobo. After reducing speed to factory stock it would pass flawlessly.

      • halcyoncmdr@piefed.social
        link
        fedilink
        English
        arrow-up
        27
        ·
        16 hours ago

        If it’s still under warranty, why wouldn’t you try to RMA it first?

        You can try… but several manufacturers are opting to refund you what you paid for the product, instead of replacing it, per their warranty terms. Terms that never were an issue before. And obviously what you paid years ago won’t get you anywhere near a similar product now.

        • zdanger@lemmy.world
          link
          fedilink
          English
          arrow-up
          36
          ·
          18 hours ago

          Return Merchandise Authorization. Return it to the manufacturer for a replacement

          • adarza@piefed.ca
            link
            fedilink
            English
            arrow-up
            13
            ·
            edit-2
            18 hours ago

            to add… (mainly for the benefit of others who may come across this)

            most ram, purchased new at retail from a legit or ‘authorized’ merchant or store should be covered by a manufacturers warranty. those sellers on amazon marketplace with random ‘kdfguuugggu’ names probably not selling warranty-eligible products. you would more than likely need a proof of purchase receipt to show when and from where you purchased the ram.

            if it was in a prebuilt or major oem (dell, hp, lenovo, etc) system you’re usually at the mercy of the builder and its system warranty. if purchased direct, the seller should have record of the system purchase. if purchased at retail, same deal as above–need the receipt.

            if the ram was acquired as used product, you’re probably out’a luck.

        • NateNate60@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          15 hours ago

          Return Merchandise Authorisation. It means to return a product to the seller or to the manufacturer because it is defective, and ask for a replacement.

  • Zonefive@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    22
    ·
    18 hours ago

    Don’t know what brand you’ve got but I had two 16GB sticks of G.Skill DDR4 go bad a few months back and their RMA process worked a treat.

    Wishing you success as well.

    • bdonvr@thelemmy.clubOP
      link
      fedilink
      English
      arrow-up
      15
      ·
      18 hours ago

      GSkill yep. Should be good. I originally built in 2020 with 2x8gb and then in October 2024 I got another 2x8gb because it was only $35USD why not lol

      The exact same set is currently $135…

      And go figure the new sticks were the ones that failed.

      • call_me_xale@lemmy.zip
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        9 hours ago

        Just to be clear: are you trying to add the new set of two to the existing set? I.e., 4x8GB?

        That can sometimes cause problems due to timing variations between batches. Make sure to memtest each stick individually, to make sure that isn’t the issue.