10-04-2022 06:30 AM - last edited on 04-01-2025 02:13 PM by Silent_Scone
ill use this thread to collect some new test bioses for the boards, maybe also to explain some less understood options
to disable cores ccd go here and choose ccd xx bit map down core.
each ones stand for an enabled core
best to disable from the back, ie:
110000
instead of 0011000
after selection press downcore apply changes or discard if made mistake
ocpak/octools
FAQ:
7950x not boosting pass 5.5G -> check that CStates is not disabled
Detailed Explanation on CState Boot Limiter
Test BIOSes:
new:
X3D OC Preset for those MB with asynch BCLK Support: (for simple slight perf boost for X3D)
DOCP/EXPO Tweaked: (for simple timings tightening)
strixe-e 1515
for crosshair and strix e-e:
explanation of segment2 Loadline:
customize a heterogenous loadline for a dual segment workload range.
example above shows loadline=L6 when current is in range of 0~40A, and Level4 when current is above 40A.
Adds for x3d
dynamic ccd priority switch with core flex, os / driver agnostic so win10 win11 ok
Algo as follows:
If condition reached and ccd0 specified, then check current mem/cache activity > threshold and hysteresis reached, if fulfilled then switch
If condition reached and ccd1 specified, then check current mem/cache activity <=threshold and hysteresis reached,, if fulfilled then switch
Default hysteresis =4
Can combine multiple algos for ccd priority so combinations are wide
works on non x3d too but of course senseless on it. detailed explanation here.
a month ago
Well, if anyone cares I got my PC to boot by jumping the CMOS then fixed all the rest of the issues by uninstalling the PCI Express Root Complex and rebooting then getting rid of all ghost devices.
As for the BIOS, I am looking forward to checking out 1.2.0.7 when it comes out as a stable BIOS for the TUF X670E-Plus Wifi. Until then, which is likely going to be a while, all is back to good and working on the latest 3287.
a month ago - last edited a month ago
I never used UEFI 1801, but UEFI 9912 started showing option to save profile as CMOS file. Comparing same profile saved as CMO & CMOS the files differ.
I am starting to save my profiles as CMOS file. Any insight you can give why saving profile as CMOS file has been created in UEFI?
a month ago
CMO will save current BIOS setting as .CMO file
CMOS will save all exist profiles to single .CMOS file
So if you save it as a cmos file, you can import all presets with one file
a month ago
Okay, so redoing the PCI Express Root Complex made the enumeration issues almost be gone but I got one this morning. I then decided, at the behest of some fellow Gurus on Guru3D, to completely wipe any and all trace of the more up to date chipset drivers that gigabyte has released for their mobos and use the more up to date than the official AMD site ones on the support page for my mobo (TUF X670E-Plus Wifi). I uninstalled the chipset then rebooted, then I used DriverStoreExplorer to delete every single AMD driver on my PC, I installed the chipset drivers from my mobo's support site v7.06.24.2226, then rebooted and haven't had an enumeration issue yet but that's what I said last time so I guess I will report back if that was not the final fix. I am also disabling get the latest updates as soon as they are available now that MS has fired to many people and are probably relying on LLMs for QA which we all know is a horrible idea as I find all of them to be wrong about things about half the time so replacing a human QA team while using LLMs and unpaid beta testers in the canary and insider's build tracks looks like it is going to start producing some terrible preview updates and I'll have none of that anymore. I have been running Win 11 Pro on my three computers since 23H2 dropped, all of them had latest updates enabled so preview updates installed, and not a single issue until this last preview Oct 29th driver and only on my main PC that has the TUF X670E-Plus Wifi at the heart. Oh well, I guess I know better now to stick to either the official AMD chipset drivers or the ones posted for my mobo specifically if they are newer and not to dabble with the latest ones out on the internet, though it has never been a problem before, now that Microsoft has basically thrown out almost all semblance of professional QA done on the Windows operating system. I learned a lot which was cool but I've never experienced a windows update absolutely brick and trash a PC before which sucks.
Anyways, good luck to everyone here! Patiently awaiting the 1.2.0.7 stable for my board but, as I said before, I am sure that's not going to happen any time soon considering how slow the updates have been for just a few boards from Asus lately. I guess they changed a lot in the new AGESA and Asus is having a hard time with it or something as this is the longest I think I have gone without at least a test BIOS for my board. Though, I am sticking to stable only now and am going to try and play it safe with this PC as I don't ever want this thing to get bricked again and then have eleven days of troubleshooting to hopefully get back to normal.
a month ago - last edited a month ago
For me on AGESA 1.2.7.0 well determined profiles have same stability and I can use same settings.
This is 9400C44 on ASUS ROG Crosshair X870E APEX with KingbankDark 2x24GB 6800C32 SK Hynix M die kit.
HWINFO was not running during LinpackXtreme run, it is in screenshot to capture VMISC in use for my records and sharing, as no other SW shows VMISC on Ryzen 8000 series.
This is 3 of 6 8700F / 4 of 7 8000 series I have, it has a crazy SOC/VDDP voltage curve for MEMCLK in use, this is a BIN'd CPU example on show. None of the 8700F I have tested do not do 9400MT/s, they just do not do it with +50mV to stock VSOC and +0mV to VDDP.
Those that think VMISC does nothing on Ryzen 8000 series, I suggest test more.
I have seen a 8700F that could not POST FCLK 2550MHz, complete POST if VMISC is bumped. I have seen stability improve in LinpackXtreme and other test loads with bumped VMISC with CPU shown in above screenshots.
On Ryzen 8000 series there is no VDDG, which is used to improve FCLK stability on Ryzen 7000 / 9000 series, instead VMISC seems to do this from my experience.
Settings txt in ZIP attached to post.
a month ago
I have kept my ASUS ROG Crosshair X670E HERO for a number of reasons. One reason it is a board that tends to be classed by ASUS as a "development" board.
Dev boards tend to get the beta first, will also have features in UEFI that others may not, how useful those features are tends to depend on what you do with board, some of these options can stop working as they worked on CPUs/AGESA when these boards were in use to test the platform before release to public.
In Tweakers Paradise there are two settings which maybe of interest to those that push things.
BCLK1 Amplitude
BCLK1 Slew Rate
I picked up on this whilst watching a video by Sugi0lover, link to video, the test for settings.
a month ago - last edited a month ago
a month ago
Which TurboV Core Version do you use?
Mine looks like that on X670E Extreme: (only a few Settings available - Ver 1.10)
3 weeks ago
Newer versions don't pull as many values, try the one linked in this post.