This past weekend, my laptop decided it’s had enough and has given me the blue screen of death. I’ve put it in recovery mode, tried to reinstall windows, the works, and it refuses. I have no idea why. I was logged on, looking something up, and it went kaput. I wasn’t downloading anything, the computer was in it’s sleeve prior, not too wet, cold, hot, etc. Battery is fine, the laptop it’s self is maybe two years old.

My understanding is that Linux is a kind of system that you download the components to a USB or what not and then install it on your machine. Is that something I could do in this case? Or do I need to take it somewhere?

Edit: it seems I may have to check if it’s a hardware problem. The error code is Bad_system_config_info, but it changed to something else at one point but I didn’t write that one down. :(

    • rudyharrelson@lemmy.radio
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      23 days ago

      Gotcha. You mentioned you put the PC into Recovery Mode and tried to reinstall Windows, but it didn’t work. What happened that prevented the re-installation of Windows? Did the PC just shutdown during installation, or were you wholly unable to get the Windows installer to run?

      If you’re still able to boot into Recovery Mode/Safe Mode, try opening up a Command Prompt and running the SFC Scan and DISM commands outlined here: https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/

      • 2ugly2live@lemmy.worldOP
        link
        fedilink
        arrow-up
        4
        ·
        23 days ago

        When I was trying to reinstall, it stopped in the middle and gave me. The blue screen. I can trick it into the recovery ry mode, so I’ll give the command a try. Thank you

        • gravitas_deficiency@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          22 days ago

          One of the first hardware things I check when a system starts getting a bit fucky is the memory. Check out memtestx86. Depending on how beefy your system is, you may have to let it run for a day or so, but it will do a rather thorough series of bitwise checks of your entire memory space, and let you know if there are any hardware faults, and indicate which physical module is the problem. If that gives you any hits (and assuming the RAM is swappable/upgradeable), just swap out your memory with some new ones (I generally go with factory-paired modules, unless it’s a system I don’t care much about, but you should absolutely used matched speed and timing on the modules you swap in).