I wanted a spooky spooky season but not like this

  • Ftumch@lemmy.today
    link
    fedilink
    arrow-up
    0
    ·
    14 days ago

    And when they opened their computer… the memory was soldered onto the motherboard! 🎃

    • Agent641@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      14 days ago

      4 x 16GB but one of them is fully cooked and isn’t even recognised (leaving 48GB) another module is failing with errors.

      They are also specced at 3200mhz but running at 1066 currently 🤷

      • Dimand@aussie.zone
        link
        fedilink
        arrow-up
        0
        ·
        14 days ago

        I was going to suggest trying them at a lower clock but seems like you might be out of luck.

        It is pretty rare to see multiple fails like this, do a search for your ram, mobo, chipset CPU and bios and see if anything flags. Might even be worth messing with latency settings, XMP can do stupid things.

        Anyone already running memtest probably knows enough to check stuff but just in case.

        Assuming it’s a reputable brand it’s probably worth attempting an RMA, it usually has pretty long warranty.

      • Tja@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        14 days ago

        Yeah, the time of death is a few years ago, they were cooked for a while…

        Have you tried testing one module at a time at the original 3200?

  • OwOarchist@pawb.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    14 days ago

    Excellent argument for having a large number of small RAM sticks, rather than just one or two big ones… If one fails, it’s less of a loss that way.

  • Jiral@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    12 days ago

    Wow, keep it together please, no reason to start posting hard horror like this just because its the season.

  • afk_strats@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    14 days ago

    Tbf this is all kinds of fucky. 3x ddr4 is not a good start. Severly under clocked. The cas timings look very tight to me

  • JackbyDev@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    12 days ago

    This happened to me earlier this year, my friend had some spare ram randomly. I should’ve started the RMA process, but I was too lazy, idk if I still can.

    • dual_sport_dork 🐧🗡️@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      12 days ago

      I have heard tell of people having their warranties on RAM spuriously denied with the explicit justification that the replacement stick is “worth” 600% or whatever of what the original was and therefore the manufacturer can’t afford it. So I would not at all be surprised if you learned retroactively that you can’t. Of course, after already surrendering your RAM stick to the manufacturer.

      I returned a memory card to Sandisk the other week, and I’m fully expecting the same result.

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    13 days ago

    What brand is it?

    G.Skill has a lifetime (sometimes 7 years) warranty on their sticks and they honored mine when it failed almost 3 years after purchase.

    They take the whole kit back though, so you’ll be ramless for about 2 weeks.

    • iocase@lemmy.zip
      link
      fedilink
      arrow-up
      0
      ·
      11 days ago

      I just helped my brother do this last month. He was BSODing for no reason and had ruled everything out. He was reluctant to check for RAM issues for obvious reasons but I convinced him to check.

      He had 4 bad addresses and once he blacklisted them he’s been stable and no BSOD since then. Obviously its better to replace it but this works well enough for now.

      • Beangut@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        13 days ago

        You might have some luck reseating the ram after cleaning the contacts with isopropyl for single bit errors

        If the errors are in the same address range everytime you can definitely reserve that address range in kernel parameters and nothing will be assigned there, you just lose a small amount of memory (Windows can do this too but I can’t remember the process)

        Last ditch effort is to manually adjust your ram timings, take note of what tests your ram fails on because there will be a corresponding setting for certain issues, this is very time intensive though and requires days of memtesting