I reset the BIOS. I reset the CMOS. I replaced the CMOS. No IDE option in my bios. Thing gets stuck on automatic repair - ill leave it on for hours and nothing.

I removed all additional HDDs and SSDs. I pulled the C drive and backed up the important data. Pulled the GPU and checked it real good. All of the ram as well.

I had gotten a BSOD with the “PNP Driver Watchdog” error. Google is unhelpful as anyone with this BSOD never received nor confirmed a working remedy or solution.

Now, after days of trying I am very rarely able to get to the Windows Install window from my USB. But none of my mice or keyboards work. They’ll work briefly for a few seconds and then stop. Nothing works to get them going again forcing me to shut down yet again.

Only thing I can think of is an unplanned and unannounced power shut off while I was out. Less than a week later my PC is pulling this shit. Refusing to boot.

Im ready to take it to a stupid pc repair shop… which im very hesitant on doing as I built this thing. Not to mention I dont like the thought of transporting this huge and heavy thing.

    • Evil_Shrubbery
      link
      fedilink
      arrow-up
      6
      ·
      3 days ago

      See, it wasn’t that hard to run the test (it didn’t even take hours to find the errors). This could have saved you 10 days.

      But good news, it’s DDR4, you can actually kinda buy that.
      (Or maybe even test individual sticks, maybe they aren’t all faulty, and just run with what works.)

    • Otherbarry@lemmy.frozeninferno.xyz
      link
      fedilink
      English
      arrow-up
      8
      ·
      3 days ago

      Well that’s your answer, you usually won’t get a normal Windows boot up with bad RAM. And if by some miracle Windows manages to make it to the desktop with bad RAM it’s just going to crash out sooner or later.

      You’re not going to be able to do any Windows re-installs with bad RAM either.

      The good news is that’s very unlikely all your RAM is bad. You have 4 sticks - this will take a bit of time but what you can do is take out all RAM sticks. Then install one stick, do a memtest run, if it looks okay take the stick out and repeat with each of the other 3 RAM sticks. That should give you an idea on which RAM stick(s) are bad, the bad ones just keep them aside and don’t re-install them.

      After testing each RAM stick individually you can re-install all the good RAM sticks, do a final memtest run & verify it all works together (it should be fine at this point but sometimes you have to do multiple memtest runs to suss out bad RAM).

      Once you remove all bad RAM your system should be able to boot into a Windows USB install and make it through the entire install normally. Or alternatively you can test if your current Windows 10 can fix itself once the RAM issue is resolved but there’s a good chance it’s pretty broken now.

      • dotCody@lemmy.worldOP
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        Thank you for the assistance!

        OK, now it looks like 1 out of the 4 ram sticks is no good. But now the thing is still refusing to boot. Doesn’t matter if its 1 stick or 2.

        I honestly think my mobo is fucked. The trouble codes on the mobo are erratic as well. I’ve gotten multiple for bad ram and now a bad GPU driver.

        And it doesn’t matter if Booting off of usb, trying to boot normally off of the c drive or trying to get into windows recovery. Everything is simply hanging on the loading screen!

        I think I might have to bite the bullet and buy a replacement mobo… 🥲 id still like to see if a second opinion from a pc repair shop is worth it to confirm my suspicion before shelling out $400 on a used mobo from China express.

  • NaibofTabr@infosec.pub
    link
    fedilink
    English
    arrow-up
    14
    ·
    4 days ago

    But none of my mice or keyboards work. They’ll work briefly for a few seconds and then stop. Nothing works to get them going again forcing me to shut down yet again.

    This sounds like there’s a hardware problem with either the motherboard or CPU, or possibly the power supply. What motherboard model do you have? Is it one of the Asus models with a backup UEFI/BIOS storage? Does it have one of those 2-digit error code displays?

    Is the failure with USB peripherals true for both the fixed USB ports on the back and front USB ports connected via one of the headers? Is it true for both USB 2 and 3 ports?

    It’s possible that a bad component is shorting a signal on your board.

    To troubleshoot:

    1. Strip everything from the motherboard except for the CPU and the PSU connection. Yes even the RAM. Disconnect all external cables.
    2. Connect your monitor to one of the motherboard video outputs (not the GPU, that should be removed).
    3. Connect a keyboard to a USB 2 port on the back of the motherboard.
    4. Power on the motherboard. Does it POST? Can you interact with the UEFI interface?
    5. If not, don’t panic yet - some boards will POST without RAM and some won’t. If yours did not, then insert one RAM stick in the first slot and try powering it on again. We want to define what the bare-minimum startup configuration is.
    6. Is it behaving any differently? Does the keyboard continue to work, or does it stop working after awhile like before?
    7. If everything seems OK at this point, reinstall your OS hard drive and test again.
    8. Continue re-adding components one at a time and testing between each until failure happens.

    The goal is to isolate the source of potential problems. You have to do it systematically. Rushing will make the troubleshooting worthless. Take notes.

    When you have a moment, a list of the system hardware would be helpful. Also if you have the paper manual for the motherboard get it out.

  • Rai@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    8
    ·
    3 days ago

    I was all excited to help at first cuz I had a VERY SIMILAR ISSUE recently and it was the CMOS battery. I’ve never even had to THINK about a CMOS battery in all my years of computer work, and a machine of mine went from working normally to freezing on POST. No BIOS, no boot select, just froze. Tested the voltage of the battery, 1.4v! I put in a 15+ year old battery I had in another old machine and it booted up perfectly.

    I’m sorry that’s not your issue. D: Best luck!

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    7
    ·
    4 days ago

    Unplanned crash like all this tells me RAM. I would say disk, but if you can’t get to even a boot disk (which loads to ram) then I say ram. Watchdog too to me says ram because it sounds like it tried to write and failed. Run memtest and see what happens

      • Otherbarry@lemmy.frozeninferno.xyz
        link
        fedilink
        English
        arrow-up
        4
        ·
        4 days ago

        If you’re at the “Preparing Automatic Repair” screen that means it skipped booting from USB and is trying to boot from internal drive with the messed up Windows install. Maybe try booting without any internal drives connected to see what it does, most computers would boot normally then complain there’s no boot device.

        Also your earlier post mentions you are using an Asus ROG Crosshair Hero VIII Wifi motherboard so some other ideas…

        • According to the manual that motherboard should display a boot menu when you press F8 at the beginning of the boot process when the initial Asus logo appears, it probably won’t work every time but when it works after the BIOS finishes scanning RAM and hard drives it will give you a boot menu listing your bootable SSDs as well as any bootable USB devices it found. (if your boot USB isn’t displaying there then you’ve got a different issue, maybe you formatted it wrong, maybe you need to disable Secure Boot temporarily, etc.)
        • That motherboard has a Q-Code LED in the upper-right of the board, it’s a little LED that displays alphanumeric digits. When the system hangs look at the board & see if it’s displaying anything in particular, that could give you an idea on what the issue is. Cross reference with the manual all the Q-Codes are listed there (see https://rog.asus.com/us/motherboards/rog-crosshair/rog-crosshair-viii-hero-wi-fi-model/helpdesk_manual/)

        Next time you’re in the BIOS I’d suggest making sure Q-Code is enabled (it should be by default but just in case) and probably disable Quick Boot if there’s an option, the boot process might be going too fast for you to catch a USB boot with F8.

        Dunno if any of that helps but hopefully it does… good luck!

      • teft@piefed.social
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        4 days ago

        Download memtest86+ to a thumbdrive, boot from the thumbdrive and run the tests.

        If you can’t get that to boot then either the memory is fucked or your mobo is fucked.

        Do you have a friend with a similar set up pc you could test parts in? That way you can narrow down what part is causing the issue.

        Edit: also you say it won’t boot but that is the recovery screen in your screenshot. Have you tried just booting into safe mode using F8?

        • Evil_Shrubbery
          link
          fedilink
          arrow-up
          7
          arrow-down
          1
          ·
          edit-2
          3 days ago

          We have been giving them this simple advice about memtest86 for 10 days now (they have several posts regarding this issue, you can look it up), they just disregard it.

          (That and live-booting any OS from USB just for diagnostics, to see if the issues are there, maybe stress test it.)

          It seems like an issue a bit complex to diagnose, but with some structure you can always rule out things until you get to the core issue, and then try to fix that or replace it.

          • teft@piefed.social
            link
            fedilink
            English
            arrow-up
            6
            arrow-down
            1
            ·
            3 days ago

            We can only lead a user to the water hole. We can’t make them drink.

              • teft@piefed.social
                link
                fedilink
                English
                arrow-up
                3
                ·
                3 days ago

                I will never understand people ignoring knowledgeable people that they specifically asked questions to but at least OP now has their answer.

                Poor guy is now poor though if he has to replace ram.

                • Evil_Shrubbery
                  link
                  fedilink
                  arrow-up
                  3
                  ·
                  3 days ago

                  Yeah.

                  Tho it’s DDR4 & maybe only one of four sticks went to memory heaven (so they are left with 48GB).

            • Evil_Shrubbery
              link
              fedilink
              arrow-up
              2
              arrow-down
              1
              ·
              3 days ago

              Oh … a water hole of a water cooled PC can leak & cause such symptoms, you are right!
              … we prob should not make them drink it tho.

            • Evil_Shrubbery
              link
              fedilink
              arrow-up
              4
              ·
              3 days ago

              Sorry, I should have said downvote, it’s different to disregard :).

              (I didn’t mean anything that bad by it, just that we do try to help & don’t really get feedback if it worked/what works & what not, which means we can’t help further/move from that point forward. Opening additional posts instead of finishing with what’s left in previous ones is more work for everyone, you included.)

  • bearboiblake@pawb.social
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    4 days ago

    Edit: sorry, my bad, I didn’t see at first you mentioned that USB peripherals weren’t working at all, even in the installer. That’s very strange, it sounds like maybe electrical shorting? Have you installed the IO shield properly?


    Unplanned power off suggests to me that it is likely that you have disk corruption. Boot into a Windows installer and go into the recovery mode, choose command prompt, and use the following tools:

    chkdsk /f /r

    bootrec /fixboot

    X:

    sfc /scannow

    One of those should probably fix it, if that’s the case.

    Consider installing a good operating system in the future :p and good luck!

  • confusedwiseman@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    2
    arrow-down
    13
    ·
    edit-2
    3 days ago

    I know it’s not the ask, but sounds like there’s no better time to try Linux Mint.

    That is provided you don’t have specific software that requires Windows.

    If it’s not for you, that’s fine, and I don’t care if I can only help and convert 1 in 10 . It’s worth it.

    Edit: sorry, I misread this as a corrupted install, not a hardware issue. I must be too tired. So yes, memtest, and cmos battery check are starting points.