AB350 Gaming K4 WIN10 BSOD NVMe after updating

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I've been with my current build for a couple of years without a problem, even though running with stock bios, as follows.

Ryzen 7 1700 (Summit Ridge) at stock settings
2x Crucial 2133mhz CL14 RAM
2x Raid 0 Toshiba P300 1TB HDDs
XFX RX 580 8GB GTS XXX
Adata SX6000 Pro 256GB NVMe

Planning updating with a 3700X in upcoming months, I just ordered a GSkill 2x8 3200mhz kit and they're still on the way. Those old kits were below acceptable treshold.

As plenty of reports stated, early bios'es for AM4 platform are horrible for memory support, so I decided to update my mobo's prior receiving and installing my new DDR kits, that's when my problems began. My target is getting all the way to 5.80, which supports Zen2 archictecture. Yet I could not go past 5.40 due NVMe compatibility. This is what I did.

- Loaded default profile for stock BIOS
- Flashed successfully 3.40 Bridge BIOS
- Loaded default profile for 3.40 BIOS
- All devices recognized inside BIOS without issues, including NVMe
- Successfully booted from NVMe into Windows10
- Flashed successfully 5.40 BIOS (Pinnacle Ridge support)
- Loaded default profile for 5.40 BIOS
- All devices recognized inside BIOS without issues, including NVMe
- Failed to boot from NVMe into Windows 10: target boot partition not found

I can't figure out why I am able to boot my old Windows install from Raid HDDs but not from NVMe since there was no hardware change whatsoever during all this process, didn't touch a single component inside my case. Maybe there is something about how the IO adrresses the PCIe lanes, as there's no PCIe4 *support* yet.

Tried to enable/disable Raid and force booting from NVMe, no luck.

As soon as I flashed back the 3.40 Bridge BIOS everything comes out well and Win10 boots from NVMe as before.

I've seen many people facing that kind of problems when switching a Zen/Zen+ with a Zen2 CPU, but not keeping the platform unchanged. This seems to be a problem not related to the new environment, as also happens in a pre-Zen2 scenario. I couldn't relate any of the Chipset IO settings and options to this issue.

I'll be very upset if I'm compelled to buy a X570. It translates to spending  close to another 3700X, for negligible gain. Feature-wise, I find that X570 mobos are either too anemic or unfathomable expensive compared to the K4, sometimes both. I fail to understand why this happens and can't come up with a solution, so I wish someone could give me some guidance or few insights.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ramax Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jul 2019 Status: Offline Points: 6	Post Options Post Reply Quote ramax Report Post Thanks(0) Quote Reply Topic: AB350 Gaming K4 WIN10 BSOD NVMe after updating Posted: 22 Jul 2019 at 11:33pm
	I've been with my current build for a couple of years without a problem, even though running with stock bios, as follows. Ryzen 7 1700 (Summit Ridge) at stock settings 2x Crucial 2133mhz CL14 RAM 2x Raid 0 Toshiba P300 1TB HDDs XFX RX 580 8GB GTS XXX Adata SX6000 Pro 256GB NVMe Planning updating with a 3700X in upcoming months, I just ordered a GSkill 2x8 3200mhz kit and they're still on the way. Those old kits were below acceptable treshold. As plenty of reports stated, early bios'es for AM4 platform are horrible for memory support, so I decided to update my mobo's prior receiving and installing my new DDR kits, that's when my problems began. My target is getting all the way to 5.80, which supports Zen2 archictecture. Yet I could not go past 5.40 due NVMe compatibility. This is what I did. - Loaded default profile for stock BIOS - Flashed successfully 3.40 Bridge BIOS - Loaded default profile for 3.40 BIOS - All devices recognized inside BIOS without issues, including NVMe - Successfully booted from NVMe into Windows10 - Flashed successfully 5.40 BIOS (Pinnacle Ridge support) - Loaded default profile for 5.40 BIOS - All devices recognized inside BIOS without issues, including NVMe - Failed to boot from NVMe into Windows 10: target boot partition not found I can't figure out why I am able to boot my old Windows install from Raid HDDs but not from NVMe since there was no hardware change whatsoever during all this process, didn't touch a single component inside my case. Maybe there is something about how the IO adrresses the PCIe lanes, as there's no PCIe4 support yet. Tried to enable/disable Raid and force booting from NVMe, no luck. As soon as I flashed back the 3.40 Bridge BIOS everything comes out well and Win10 boots from NVMe as before. I've seen many people facing that kind of problems when switching a Zen/Zen+ with a Zen2 CPU, but not keeping the platform unchanged. This seems to be a problem not related to the new environment, as also happens in a pre-Zen2 scenario. I couldn't relate any of the Chipset IO settings and options to this issue. I'll be very upset if I'm compelled to buy a X570. It translates to spending close to another 3700X, for negligible gain. Feature-wise, I find that X570 mobos are either too anemic or unfathomable expensive compared to the K4, sometimes both. I fail to understand why this happens and can't come up with a solution, so I wish someone could give me some guidance or few insights.

glenb77 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jul 2019 Location: us Status: Offline Points: 8	Post Options Post Reply Quote glenb77 Report Post Thanks(0) Quote Reply Posted: 23 Jul 2019 at 1:25am
	i would try regenerating the efi boot files from a windows install or repair cd. i found that changing the bios will change the way drives and hardware is identified. as experiment, boot windows install or rescue, select repair, get to command prompt. use diskpart. on the efi partition (system) erase it. format quick fs=fat32 label="System" assign letter=S then make sure your windows is seen and note the driver letter; in diskpart use list volume command. exit diskpart and regenerate efi files with: bcdboot c:\windows /s s: /f UEFI if your windows is not c: then change that part to the drive identifier of what you saw under list volumes for your windows on the nvme drive. worth a try..

ramax Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jul 2019 Status: Offline Points: 6	Post Options Post Reply Quote ramax Report Post Thanks(0) Quote Reply Posted: 23 Jul 2019 at 8:24pm
	It is worth a try indeed. Thanks for your reply! Couldn't dive into it yesterday, but I may have some time to sort it out tonight. If you're right, and I really hope you are, this isn't a great issue after all and a fresh OS install might be able to solve it ultimately in a straightforward way. As long as I still need to get all the way to the AMD AGESA Combo-AM4 1.0.0.1, it won't solve my problem entirely yet though, but I'm starting to think that waiting a few days for new BIOSes before blindly ordering a 3700X to pair with this mobo is the safest option. Good riddance that I don't have the bucks right now after all. I'll keep this updated just in case, so it could serve as guidance to anyone in the future. Thanks again for the help!
	AB350 K4 R7 1700 Stock Crucial 2x8 2133 CL14 XFX RX 580 8GB GTS XXX

glenb77 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jul 2019 Location: us Status: Offline Points: 8	Post Options Post Reply Quote glenb77 Report Post Thanks(0) Quote Reply Posted: 23 Jul 2019 at 10:33pm
	you should not need a fresh install of windows. if you see the drive with windows when you use a windows install or repair usb then you are ok. this guide in the link below has the complete instructions which you need to adapt to your situation. i find that simply reformating the efi partition is the way to go so you don't wind up with 2 bootloaders in the system. so use dispart select your efi/system partition, format it. then locate the drive letter of your windows on your hard drive. exit dispart and execute command to generate efi files on the efi partition. reboot. ignore part about msr partition that should be there already.

glenb77 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jul 2019 Location: us Status: Offline Points: 8	Post Options Post Reply Quote glenb77 Report Post Thanks(0) Quote Reply Posted: 23 Jul 2019 at 10:33pm
	forgot link. it is this: https://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installation-to-uefi.aspx