Constant blue screens with different errors

[Hattto]

I recently upgraded to am5 and everything worked the first few days but I had a small issue where my pc wouldn’t boot to windows the first time I powered my pc on but would after turning it off and trying again. When this happened I had xmp enabled and thought that was the issue but after disabling it I received blue screens with error codes 0xc0000098 and 0xc0000428. Then after a day or so, the blue screens were so bad that I’d received them seconds after starting windows. When entering safe mode, I’d get sihost unknown hard errors after putting in my pin and blue screens when trying to restore to a previous point.

My pc is practically unusable and I have no idea if it’s a hardware or software issue.

[veeg]

Hello

You could have some corrupted files. You could do a system restore to a earlier state to see if this fixes the issue.

[Hattto]

Hello

You could have some corrupted files. You could do a system restore to a earlier state to see if this fixes the issue.

I’ve tried to do a system restore but I keep getting blue screens some time after starting the process.

[Rustys]

AM5 motherboard or the CPU

[Hattto]

AM5 motherboard (MSI MAG B650 Tomahawk) with the Ryzen 7 7700x

[Rustys]

Here is a possibility why you are seeing the issues that you are as posted by @phillpower2

A new MB means a clean install of Windows and for two reasons **

Once Windows has been installed before doing anything else you must install the chipset drivers for the MB, the SATA/storage device drivers for any SSD and/or HDD followed by the drivers for any add on GPU that may be present, these steps are a must and have to be done before Windows is allowed to check for updates as it has a habit of downloading the wrong drivers on you.

Second reason is down to the Windows product key, ever since Windows 8 the Microsoft servers have stored the licence key and corresponding MB details on their servers, this means that should a user ever need to do a clean install the servers check that the licence key and MB details correspond and if they do the user does not need to enter a product key number, if the MB and licence key do not match the user gets asked for a new product key, see my canned info below;

Unless your present product key is the full retail version you cannot use it with a new MB as an OEM product key is tied to the original MB it was paired with, to use an OEM key with a new MB is detected by the Microsoft servers as software piracy and therefore you get on screen warnings etc..

Exceptions to the above are 1: If your MB is replaced under warranty and 2: If your MB is replaced out of warranty with an alternative type but same brand due to the original model no longer being available, an upgraded MB however will require the purchase of a new OS licence.

If you have a full retail disk and a product key that is not in use on another computer the OEM restriction/s is/are not the same.

** It is possible to uninstall the previous MB drivers while the drive is still in that PC, the Windows licence key info provided remains the same though so the workaround is not worth the hassle.

Windows is trying to install the drivers for the previous MB and that is most likely what is causing the system to fall over.

[Hattto]

Here is a possibility why you are seeing the issues that you are as posted by @phillpower2

A new MB means a clean install of Windows and for two reasons **

Once Windows has been installed before doing anything else you must install the chipset drivers for the MB, the SATA/storage device drivers for any SSD and/or HDD followed by the drivers for any add on GPU that may be present, these steps are a must and have to be done before Windows is allowed to check for updates as it has a habit of downloading the wrong drivers on you.

Second reason is down to the Windows product key, ever since Windows 8 the Microsoft servers have stored the licence key and corresponding MB details on their servers, this means that should a user ever need to do a clean install the servers check that the licence key and MB details correspond and if they do the user does not need to enter a product key number, if the MB and licence key do not match the user gets asked for a new product key, see my canned info below;

Unless your present product key is the full retail version you cannot use it with a new MB as an OEM product key is tied to the original MB it was paired with, to use an OEM key with a new MB is detected by the Microsoft servers as software piracy and therefore you get on screen warnings etc..

Exceptions to the above are 1: If your MB is replaced under warranty and 2: If your MB is replaced out of warranty with an alternative type but same brand due to the original model no longer being available, an upgraded MB however will require the purchase of a new OS licence.

If you have a full retail disk and a product key that is not in use on another computer the OEM restriction/s is/are not the same.

** It is possible to uninstall the previous MB drivers while the drive is still in that PC, the Windows licence key info provided remains the same though so the workaround is not worth the hassle.

Windows is trying to install the drivers for the previous MB and that is most likely what is causing the system to fall over.

Thanks for response, I’ll try this when I can.

[Rustys]

Let us know how things go.

[Hattto]

Let us know how things go.

I got the installation media and set it up for a usb drive on a Mac running Parallel. I put the drive in my pc and began the process, selecting custom install, choosing my main drive but it gives me an error saying there’s missing files. Shortly after that, I got a blue screen for a PFN list corrupt error. I’ll try again with a new installation media but I’m doubting it’s a coincidence.

[Hattto]

I got the installation media and set it up for a usb drive on a Mac running Parallel. I put the drive in my pc and began the process, selecting custom install, choosing my main drive but it gives me an error saying there’s missing files. Shortly after that, I got a blue screen for a PFN list corrupt error. I’ll try again with a new installation media but I’m doubting it’s a coincidence.

Follow up, I deleted everything in my C: Drive and still receive errors then blue screens. Can this be a hardware issue?

[Hattto]

Second follow up, I may have fixed the issue. Enabling XMP actually allowed me to install Windows without blue screens then I immediately updated my BIOS which set the RAM speed to default and it’s been fine so far. I’m guessing there was a bug or corruption in the BIOS version where enabling XMP would cause issues after disabling it.

[Rustys]

Thank you for letting us know