I have Arch Linux on Ryzen 7 3700X, 32gb of ram, and some Gigabyte motherboard with updated bios.

Few weeks ago my computer would startet crashing (screen would freeze) soon after login or even at boot about 50% of the time. I was lazy so when it crashed I just forced rebooted it (the power button). Then crashes became more common untill my system wouldn’t even boot.

So I reinstalled and I had some trouble generating dracut bundles, because some zstd copression was corrupted. After booting freshly installed os it would crash again right before the login should show up. Switching kernel (from hardened to zen) fixed the problem. Then I installed basic apps (browsers, office, crypto stuff, steam, etc.) I rebooted and when I typed the password for my encrypted root it was wrong (Im sure I typed it correctly).

I have no idea wtf went wrong with my system. I have almost the same everthing on my laptop (hardened, btrfs, luks encrytped drives, systemd boot, etc.) and it works great. And I never experienced any crashes on live usb on my pc.

I ran some random test (its passmark memtest86 v9.3 pro) on my medicat usb. Right now its 92% finished with 1070 errors. This just can’t be good :(

Now I will play with some bios settings (like disable xmp), reflash other version, maybe switch a ssd… I will also try other distro, but I can’t daily drive them. Arch gives me a ton of flexibility and I don’t want to lose it. Maybe NixOS or Gentoo, but gentoo doesnt have systemd (I want to use Mullvad as my vpn and their app reqires it).

Do you maybe know what could be wrong and how to fix it. Thank you for reading this post and thank you very much for answering.

I don’t know if this is arch bug or its something wrong with my system. If this is not right community to ask this, plese direct me to the right one (just please not reddit).

Edit: I ran memtest again without one ramstick and it gave me no errors! Thank you for all help and suggestions :)

Edit: I also tried only the faulty ram stick and the PC wouldn’t even boot.

Edit: Booting PC with only the faulty ram stick corrupted my bios… I guess I will have to reflash bios anyway.

  • lemmyreader
    8·
    10 months ago

    I ran some random test (its passmark memtest86 v9.3 pro) on my medicat usb. Right now its 92% finished with 1070 errors. This just can’t be good :(

    Not familiar with medicat. Are you saying memtest86 gave you 1070 errors ? Then one of RAM modules is faulty. Or is this about the hard disk and bad blocks ?

    gentoo doesnt have systemd (I want to use Mullvad as my vpn and their app reqires it).

    If I recall correctly it is technically possible to run Mullvad and OpenVPN manually without systemd for example on a SBC (pi4 etc.) as your LAN router, and feed it to your devices, but yeah this is a bit cumbersome.

    • chevy9294@monero.townOPEnglish
      5·
      10 months ago

      Medicat is like a Ventoy (USB that can have multiple iso files).

      Now I disabled XMP (makes ram faster) and ran test again and still errors. I noticed that all errors give same mesaage: expected “address”, actual “wrong address” and wrong address is the same as expected address but 1 byte different. For example expected is FFFFFFF7, actual is FFFDFFF7. And this error is always on CPU core 6.

      I have 2x 16gb of ram, so I will try test again with only one stick and then with other one.

      • mozz@mbin.grits.dev
        4·
        10 months ago

        Are you overclocking / doing any other unusual hardware thing? That one-bit flip is clearly pointing to broken memory, but it could be either the system RAM or the CPU cache memory (which would be real sad, but if it’s always on core 6 sounds pretty likely).

        • chevy9294@monero.townOPEnglish
          2·
          10 months ago

          XMP is somekind of overclocking, but I disabled it.

          Its not only one bit flip but at leats two (in a single byte), I figured out using addresses in the errors.

          I was also scared that it’s the cpu, because it was the most expensive part when I build the PC. Thankfully I think it’s not, now I’m running memtest again with no errors without one ram stick.

          • Aniki 🌱🌿@lemm.eeEnglish
            4·
            10 months ago

            Was it just one bad stick? When you’ve identified one slot that’s acting up, shuffle the remaining sticks around to rule out the socket going bad.

          • mozz@mbin.grits.dev
            2·
            10 months ago

            Hey, that’s wonderful! Good to hear. Yeah I would just throw away the memory and do a certain amount of double-checking of what’s on your disk, as some of it may have been corrupted during the time the broken memory was in there. But yeah if you can run and do stuff without errors after taking out the bad stick then that sounds like progress.