[SOLVED] Old ryzen mobos with old ryzen cpus but with new bios for second generation processors

[FrixSuperX]

The question is simple :
If i've a old mobo like a B350 and an old ryzen like a 1600. Is fine to update the bios to a version compatible with ryzen 2 processors and still using the old cpu?
Seems a bit dumb but i've tested with my aorus x370 k7 with my 1800x updating the bios from an f10 to an f23 . What I've got is performances a bit lower in comparison my f 10 a little higher cpu temps and after a serious problem with ram stability (32 gb gskill flare x 3200) . At the end when I shutdowned my pc i noticed a little freeze and when i tried a reboot my system couldn't even get in the bios and even clearing CMOS wasn't helpfull . Debug leds keep jumping between ram and cpu and the only solution for me was using the backup bios to force a downgrade in the corrupted one .
Now is working fine with the f10.
A friend tried an update from f8 to f23 with a gigabyte gaming 3 B350 and a ryzen 1600 to solve some screen tearing issues in linux (he read that in a post somewhere that could be a solution) and now his pc cannot keep xmp profile without giving issues and resetting bios settings (he use 16 gb corsair vengange 3000). Are these stuffs related from using an older cpu with a new bios compatible with ryzen 2 processors?

 

[Darkbreeze]

It's fine. It's actually RECOMMENDED that you do that, because the bios changes are generally NOT only what is listed as the primary change on the release data. Memory compatibility, graphics card support and a variety of other thing such as microcode to support newer CPUs are all potentially things that get addressed in any bios update.

If you find that you have a loss of performance AFTER updating from a bios version that was released prior to January of 2018, then it's likely due to the fact that there were changes to the bios due to potential issues from the Spectre and Meltdown side channel attack vulnerabilities and it is well documented that performance has been affected across the board for AMD, Intel and ARM.

Now, it might NOT be due to that, but it certainly could be if it was a fairly old bios you were updating from.

Furthermore, AFTER updating the bios, I highly recommend starting from scratch by doing a hard reset of the BIOS as follows:

Power off the unit, switch the PSU off and unplug the PSU cord from either the wall or the power supply.

Remove the motherboard CMOS battery for five minutes. During that five minutes, press the power button for 30 seconds. After the five minutes is up, reinstall the CMOS battery making sure to insert it with the correct side up just as it came out.

Now, plug the power supply cable back in, switch the PSU back on and power up the system. It should display the POST screen and the options to enter CMOS/BIOS setup. Enter the bios setup program and reconfigure the boot settings for either the Windows boot manager or for legacy systems, the drive your OS is installed on if necessary.

Save settings and exit. If the system will POST and boot then you can move forward from there including going back into the bios and configuring any other custom settings you may need to configure such as Memory XMP profile settings, custom fan profile settings or other specific settings you may have previously had configured that were wiped out by resetting the CMOS.

If the system will not POST after resetting the CMOS, then there is a hardware problem of some kind.


THEN, if you still have a loss of performance, be sure to check your motherboard product page for updated chipset, audio, network adapter and storage controller drivers and if ANY of them are newer than what you have currently installed, or if you have never manually installed ANY of them previously and were only running on the default Microshaft supplied drivers, it is HIGHLY recommended that you update to the versions offered on your motherboard product page.

Don't make the mistake of thinking that a newer audio driver can't affect something else, because it absolutely can. Any driver can affect ALL other drivers, so update when an update is offered unless there is a very good reason not to. They don't release new drivers just for fun. They do it when problems are found with the code or framework of the current release, which means updating is a wise thing to do.

 

[FrixSuperX]

The problem is that 'ive already did .
Updating bios from a default setting of bios of course after that the first log in in windows completelly stock .Turning off the system and clearing cmon battery logging another time in windwos default . Turning off the system again logging the bios and changing settings like xmp. logging in the os and testing the system(that's the basic for me).
The problem is that the performances are a bit less and after that xmp profile become unstable .
In my case that issue caused a perma loop that I could only solve with the backup bios.
For my friend just keep disabling xmp profile randomly when he turn on his pc.
Btw F10 is the last bios that gigabyte did for the first gen of ryzen so have all ram compatibility and all stuff i need I think that other bios have just something for new cpus.
What i'm asking is if I just messed up with the bios installation why that stuff happens with the bios after f10 (i've already update my bios from f6 to f8 and f10 with no issues), and why i could resfresh the old bios without any issues if i couldn't install bios properly in the first place?
Seems like using a bios for zen2 is usefull just if you need to change cpu gen , using the old one is guaranteed just in stock (basically bcz you will change the cpu immediatly after)

 

[Darkbreeze]

Then it sounds to me as though you have a faulty motherboard or memory module or you have some kind of non-UEFI hardware installed, could be any kind of PCI card or USB device, that is causing the issues.

Also, you don't need to update from F6 to F8 to F10. You can ALWAYS just ONLY update to whatever the latest bios version is UNLESS there are specific instructions on the motherboard bios page indicating you MUST update to an earlier version before updating to the latest version. That is rare, but does occasionally happen. I've seen it maybe twice.

There should NEVER be any issue with running a non-Beta bios version, no matter WHAT the reason for updating is. If you cannot run any motherboard on the latest available bios, unless there are obvious issues with that bios version for MANY people, then something is wrong with either your motherboard or some other hardware component. Or, you need to download the bios fresh to new USB media and try again. Sometimes it's just a bad download.

 

[FrixSuperX]

I see that post.
https://www.google.com/amp/s/amp.reddit.com/r/GAAB350/comments/97jvuc/f23_stable/
Looks like the increase of temps in caused from an increase of vsock.
I've figued one thing the first time i've installed f23 the problem i've find was a lower cinebech score of 5 points (negligible) and how I said before higher temps but if the system was really instable couldn't run a cinebench and a passmark test in the first place.
The second thing that I've figured is the second time I've tried f23 I had Linux installed in dual boot.
Some people reported issues with this BIOS version with Linux (my fried have Linux too). When I've benchmarked the system in that case scores are more less similar with f10 but I've find some issue like clock time incorrect and some error when I tried to open some application (solved rerunning the program a second time) . The system could handle all bench but when I shutdowned it I noticed a freeze and my system couldn't even boot in BIOS after that (how I said before). My friend have issues when he tries logging in windows after a lot time that use just Linux (likes days) and seems related to xmp

 

[Darkbreeze]

I'd get rid of the dual boot, do a CLEAN install of Windows like I suggested before, using this EXACT method, with all other drives disconnected, and see if you still have issues. Could even be that you have a bad drive that is borking the system.

Windows 10 Clean install tutorial