Help with Booting Issues After Hardware Changes

0
8
Asked By TechieWalter92 On

I'm having trouble booting my PC and I suspect it might be a hardware issue. Here's what I've got: CPU is an AMD 9600x, motherboard is an MSI Pro B850M-A, I've got an RTX 3080 for a GPU, and I'm using two sticks of T-Force 16GB RAM at 6000MHz CL30. I keep getting an error that says 'The digital signature for this file couldn't be verified' with a status code of 0xc0000428. It initially pointed to winload.efi when I had Windows installed on my NVMe drive, which I've since wiped, hoping to fix the problem. I'm also having a tough time booting from a Windows 11 media creation USB stick and get the same error. I've experimented with different USB ports and sticks, confirming they all work on another PC. I even tried booting from a Ubuntu stick, but that freezes at the splash screen in safe graphics mode. I've tried moving my RAM around and even switched to onboard graphics by removing the GPU. All my components are under warranty except for the GPU, but I'm starting to think the CPU might be at fault. Any thoughts or suggestions on what else I could check?

2 Answers

Answered By HelpDeskHero42 On

Have you checked your BIOS settings? Sometimes, changes there can mess with the boot process. Also, since you wiped your NVMe, make sure your BIOS is set to boot from the correct device. If your Windows installation is completely gone, that could be part of the problem too. Just a heads up, always back up your data before messing with hardware settings.

Answered By MemoryMaster88 On

So, just to clarify, do you have Windows installed anywhere now? Since you wiped your NVMe drives, it might be time for a fresh install. Also, I recommend running memtest86 to check your RAM. Even though the error doesn't scream bad RAM, it's worth double-checking. Let us know what you find!

TechieWalter92 -

I don't have Windows anywhere at the moment. I wiped both NVMe drives via UEFI, which was kind of a last resort after trying various things. I'm currently running memtest86; seems to be clear so far. Thanks for the tip!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.