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.

    • Otherbarry@lemmy.frozeninferno.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      8 hours 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
      9 hours 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@thelemmy.club
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        3 hours 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.