Question Win10 will not boot in after CPU change

[Ka3el]

Hi folks, I have just changed CPU Ryzen 3700X -->5800X3D on my Asus TUF X570 MLB, but computer cant start windows (10). I updated bios before new CPU installation and I believe there is no problem how new CPU was assembled, I can get to BIOS etc., windows starting and show message that there is problem to launch the PC, windows is trying to repair it but no success.

Windows error message is: inaccessible boot drive (bellow screen), I dont have drives encrypted, I have just TPM module but didnt do anything with it and even dont have win version which would support it encryption, nevertheless when new CPU installed there was some message regarding TPM and I clicked yes to confirm I dont use TPM If I remember well.

I tried to search the solution (seems many have this problem) and found clearing CMOS could be solution, I did with MLB jumper (short-circuit) method but no success. I read better method could be to also remove the battery and then again use jumper but so far I was not able to remove the battery, its udder GPU and not easy to access.

Do you please think take out battery could help?ANy other solution or only one will be reinsall windows? Will it be possible to reinstall keeping applications or at least data?

Note: Strange thing, before new CPU installation, when PC turn on or restart fans started to spinning fast for short moment, but that is now not happening.

 

[mikeymikec]

Can you confirm that the boot drive isn't encrypted by for example connecting it as an additional drive to another system and seeing whether it can be read, or starting the problematic PC from Windows USB setup media, Shift+F10 at the setup welcome screen, and get a directory listing of the boot volume?

I've seen Win10 encrypt a boot drive without asking once before, and on the same computer a fresh install of Windows 10 wasn't encrypted. I have no idea why it decided to encrypt it on one occasion.

If you go down the route of USB setup media, doing chkdsk /f /v /r on the partition containing the Windows folder wouldn't go amiss.

Having said all of this, I wonder whether something else might have happened, like a storage protocol change in the BIOS. How is the boot SSD connected (SATA/M.2)?

 

[igor_kavinski]

Having said all of this, I wonder whether something else might have happened, like a storage protocol change in the BIOS. How is the boot SSD connected (SATA/M.2)?

Yeah. Seems like the BIOS settings might have gotten reset to default, causing the SSD mode to change or something.

 

[Ka3el]

Can you confirm that the boot drive isn't encrypted by for example connecting it as an additional drive to another system and seeing whether it can be read, or starting the problematic PC from Windows USB setup media, Shift+F10 at the setup welcome screen, and get a directory listing of the boot volume?

I've seen Win10 encrypt a boot drive without asking once before, and on the same computer a fresh install of Windows 10 wasn't encrypted. I have no idea why it decided to encrypt it on one occasion.

If you go down the route of USB setup media, doing chkdsk /f /v /r on the partition containing the Windows folder wouldn't go amiss.

Having said all of this, I wonder whether something else might have happened, like a storage protocol change in the BIOS. How is the boot SSD connected (SATA/M.2)?

Hallo, drives are not encrypted, I checked that recently with "manage-bde -status", system is installed on M2/NVME.

Before installing new CPU I had some issues with NVMe. after I updated bios before CPU change. After power on system went to bios as didnt see bootable device, it didnt see NVME at all, after bios exit,all was ok, after restart all ok, after power off, issue back but always fixed then just leaving bios. THis issue was now fixed after new CPU installed (no more to bios after power on)Let me add here that the issue with NVME appeared after after bios update but I also updated chipset in windows. I tried to to go back to original bios but issue persisted so one could say it was chipset issue.

 

[mikeymikec]

It sounds to me like your problem here is very much linked to your other thread:

Question - PLEASE HELP - After bios update PC goes to bios after every power on

Hi folks, so few days ago I updated MB bios 3603 to 4802 (ASUS TUF gaming X570) and also updated AMD chipset in windows, I think there was also some windows update same time. After that whenever I power ON PC it goes to bios, once I just leave the bios (no changes made) and system restart all...

forums.anandtech.com

I almost invariably use ASUS boards myself and the business of the computer going to the BIOS screen rather than booting an OS sounds a lot to me like the board isn't/wasn't seeing the SSD on the first boot attempt.

You could verify which boot method Windows is expecting by booting from USB setup media, Shift+F10, diskpart, list disk. I think it'll have a star/asterisk in the 'Gpt' column if it's meant to boot from UEFI. By all means lose secure boot because it's not a requirement to manage to boot Windows (Windows will just list the secure boot state as off in msinfo32).

I was looking into a booting issue this morning on a customer's PC I built and one thing I encountered was that when I enforced UEFI only on a boot device that apparently I originally set up without UEFI, the BIOS spawned a message saying that I would have to enable CSM in order to boot. I would have thought the opposite scenario would be true too, so I don't think it's a straight UEFI/CSM issue (also if it was, you wouldn't be getting INACCESSIBLE_BOOT_DEVICE because the Windows boot process wouldn't start if the wrong mode was selected). Once you've verified that it's meant to be UEFI/GPT, I'd disable CSM completely for the sake of simplicity (Asus boards in my experience will do a little boot/reboot dance routine to switch between one mode and the other).

I think this is a BIOS bug too. There's no configuration reason why a SSD would not be detected in the first boot attempt by the board but detected the second time around, IMO that screams faulty SSD or board acting wonky.

 

[Tech Junky]

On Intel it's usually defaulting back to RST which borks how Windows boots after the update and you have to disable RST and reboot.

I think it's an issue where on older setups it's looking for a GPT disk vs MBR which most are setup as. With UEFI it doesn't seem to rear its head tough as far as I've seen lately w/ a couple of rebuilds / MOBO swaps .

 

[Ka3el]

Hallo, just for those who would tried to find solution and find this post. I solved this with windows reinstall which I was trying to prevent, but that was wrong. I spent much more time trying to find and implement solution than I spent reinstalling windows which also have its advantages. I did full reinstall (not repair) but I didnt format the drive so installation program created folder windows.old where I could get some data I wanted (Firfox bookmarks, etc.)