cancel
Showing results for 
Search instead for 
Did you mean: 

My experience with C7H UEFI 2406 & R5 3600

gupsterg
Level 13
Last update: 10/07/19 16:00 UK BST

I have a C7H given to me by ASUS at launch. It has had 3x 2700X used on it and lost count how many UEFI flashes I have done testing things. It is also the early board which has bugged chipset voltage readout in SW monitoring, ~+50mV from actual. So in UEFI screenie/HWINFO you will see ~1.1V when actually it is 1.05V.

From having read others posts I thought I would have a mare with swap over to R5 3600, to my delight my experience was to the contrary of what I had read :cool: .

As the current 2700X had been in the rig since Jan 19, I was expecting it to come out of the socket with the water block :eek: , but no it did not pull the CPU :cool: . I had ran the system up prior to warm her up 🙂 .

Any how quick painless remove and swap out to R5 3600. I did not even reflash UEFI, did clear CMOS from rear IO and BOOM! first time she booted! :cool: .

The Hero everyone wants is the C7H! :cool:

This album link has some screenies from UEFI 2406, continuing now with other bits of testing, etc 🙂

OS was freshly installed yesterday when on 2700X, I just had a screen doing some updates once booted on R5 3600. Seems AOK so far and will update benches, etc here ASAP 🙂 .

HW in use:-

- R5 3600 Batch Code: BF 1922 SUT
- C7HWIFI
- F4-3200C14D-GVK
- Sapphire HD 5850 Toxic 1GB
- Intel 660P 1TB
- Cooler Master V650

Cooling used:-

- EK Supremacy EVO (Acetal+Copper)
- Magicool 360 G2 Slim radiator
- 3x Arctic Cooling P12 PWM
- 1x Arctic Cooling F12 PWM
- EK DDC 3.2 PWM
- Coolant is distilled water with ~20% mix of Mayhems XT-1 clear concentrate
- Arctic Silver 5 spread by hand using plastic strip from a plastic card (OFC 😄 )

All fans are using a 4 in 1 cable, connected to CHA_FAN2 and powered by molex. The water pump is powered by molex and gains PWM from H_AMP header. All fans/pump run a UEFI based profile, based on water temperature, T_Sensor1 is used.

Image

Here HWINFO shows some idle stats, etc, room ambient temp is ~24C.

Windows 10 Pro x64 1903 with AMD Chipset driver 1.07.07, power plan is Ryzen one which has UEFI CPP2 link.

So far benches in this album are at base settings stated in ZIP above, room ambient ~24C.

Done an image of system to SATA SSD over USB adapter, now to scratch the OC itch of Matisse! 😉 .

Overall so far experienced smooth POSTs on mobo (done a few) and usage in OS for tests/uploading images/posting here, etc all nice. PWM on headers is behaving, so not having any issues with the SIO (ITE IT8655E), so fans/pump reacting as they should. OS has only had whatever updates it wanted via web, only driver so far installed is AMD Chipset from AMD site. Aspects of Wifi, NVMe, etc all working as they should.

Setting up 3533MHz using The Stilt 3466MHz timings has not been an issue so far. I have done some warm POSTs (ie restart from OS) and then some POSTs from shutdown, but with board having standby power (ie PSU wall plug still had power).

As Elmor had on OCN highlighted an issue on current UEFI I set up voltages first, saved settings, set timings and saved settings. When FCLK (ie fabric clk) was left [Auto], even with 3533MHz MEMCLK it did not maintain 1:1 ratio until I manually set it. FCLK not being 1:1 can have severe affect on RAM performance depending upon how far out it is from 1:1. This 3533MHz without 1:1 FCLK, link, then here is with 1:1, link. Below ZIP has settings used txt.

Image

Just like on 1xxx/2xxx gear down mode must be disabled for odd CAS not to be rounded to nearest even. Just like previous gen again tRDWR on [Auto] does train to differing values (link), I left it on [Auto] as The Stilt's preset do this.

I set SOC manually to match what I saw at stock via with DMM, so I could see what RAM MHz gains I could get at stock SOC, link. CLDO_VDDG is explained here by The Stilt link. I should have perhaps used 0.950, but set it ~40mV less than SOC, CLDO_VDDG does accept 1mV steps, at complete UEFI defaults RM shows 0.950V, link.

Today I have ended on 3600MHz, FCLK & MEMCLK 1:1, using The Stilt's 3466MHz timings, 1T, Gear Down Mode: [Disabled], AIDA64 bench result link. Latency is ~7ns behind 2700X for same RAM MHz & timings, strangely.

Stability testing album link, 3533MHz passed 1100% even though screenie shows 750%, same settings failed with 3600MHz, even though I encountered no POST issues, etc. Bumping VDIMM to 1.355V seems to have solved it as gained 1200% PASS. Just as a comparative I needed 1.385V VDIMM on same RAM kit & mobo, but using 2700X. This IMO shows clearly RAM & MOBO was not what held back 1xxx/2xxx, but IMC quality. Room ambient was ~26C for the tests stated.

Settings for 3600MHz using The Stilt 3466MHz timings in below ZIP.

Image

This has now been tested for 2400% in RAM Test and then on same POST I did 1200%, link 1, link 2.

3666MHz I have gained pass in RAM Test ~1100% so far, this was by increasing SOC/CLDO_VDDG/VDIMM and CAD Bus needed to be 30 A A A. Link 1 , Link 2, RM is showing some things incorrectly, but a lot is correct and currently only util showing as much as it does on Matisse.

So using The Stilt 3466MHz timings, Gear Down Mode: Disabled, 1T, below is so far what has passed stability testing in RT reasonably well.

3533MHz SOC: 1.025V CLDO_VDDG: 0.985V VDIMM: 1.35V
3600MHz SOC: 1.025V CLDO_VDDG: 0.985V VDIMM: 1.355V
3666MHz SOC: 1.043V CLDO_VDDG: 1.003V VDIMM: 1.365V CAD Bus: 30 A A A

UEFI 2406 does had PMU Training menu (aka IMC), link, further info ref Elmor's post here.

*** more to come soon 😉 , so stay tuned peeps 😄 ***
Intel Defector :eek: AMD Rebel


R9 5900X - Custom WC - ASUS Crosshair VII Hero WiFi - Ballistix Sport LT 2x16GB 3800MHz C16 - RX 6800 XT - WD SN770 2TB - 2x 870 EVO 4TB


24/7 OC: i5 4690K @ 4.9GHz CPU@1.255v 4.4GHz Cache@1.10v - Archon SB-E X2 - Asus Maximus VII Ranger
Sapphire Fury X (1145/545 ~17.7K GS 3DM FS)

:eek: CPU Validation 5.198GHz@1.314v with 4.4GHz cache + RAM 2400MHz@1T :eek:
Da Music video
410 Views
51 REPLIES 51

xeizo
Level 12
Bios 2501 performs very well, it's only the known bugs disturbing the experience.

But Yesterday AMD said they will have a new AGESA with all possible fixes delivered to vendors on Tuesday, so we have a much better bios possibly incoming first half of August.

New Ryzen Dram Calculator also incoming tomorrow!
R9 7950X - ASUS X670E Crosshair Extreme (bios 0803) - 32GB HyperX Fury Beast @6200c32 - Corsair H150i Pro - ASUS RTX3080 TUF OC V2 - Phanteks P400A - Corsair RM850 - WD SN850

gupsterg
Level 13
Yes 2501 performs well.

Even better is 0068 if I disregard how on 1st POST after flash chipset gets ~1.35V, when default is ~1.05V.

Why 0068 is better is it has better training process at POST and changes of settings.

For example I can go from stock to PBO+150MHz 3800MHz C16 whilst on 4x8GB in one go on UEFI 0068, but UEFI 2501 will Q-Code: C5. UEFI 2406/2501 need to be coaxed into that profile, they can jump from stock to PBO+150MHz 3800MHz C16 whilst on 2x8GB in one go.

There are a few other factors which make also UEFI 0068 best IMO. UEFI 2602 was pants IMO, I was hoping that would gain the training process UEFI 0068 had, but didn't look like it did. I'm hoping next release is more like UEFI 0068.

I also like changes in PBO on Extreme Tweaker of UEFI 0068 is better reflected in RM.

https://youtu.be/CLEopLPNoJw
Intel Defector :eek: AMD Rebel


R9 5900X - Custom WC - ASUS Crosshair VII Hero WiFi - Ballistix Sport LT 2x16GB 3800MHz C16 - RX 6800 XT - WD SN770 2TB - 2x 870 EVO 4TB


24/7 OC: i5 4690K @ 4.9GHz CPU@1.255v 4.4GHz Cache@1.10v - Archon SB-E X2 - Asus Maximus VII Ranger
Sapphire Fury X (1145/545 ~17.7K GS 3DM FS)

:eek: CPU Validation 5.198GHz@1.314v with 4.4GHz cache + RAM 2400MHz@1T :eek:
Da Music video

My board on 2501 and 3600 running G.Skill Ripjaws V 3200 CL14 2x8gb keeps forgetting the VBOOT setting on every cold boot, gives C5 error like when VBOOT is set to AUTO. Any idea how to solve this, it's getting really annoying, i have to clear CMOS and load up my profile every time i use the PC for the first time that day. Luckily it's stable and works fine otherwise.
2602 was an absolute BSOD fest. Previous 3200 CL16 ram worked fine though with DOCP.

gupsterg
Level 13
When you mean cold boot, you mean you turned off power to PC power supply?
Intel Defector :eek: AMD Rebel


R9 5900X - Custom WC - ASUS Crosshair VII Hero WiFi - Ballistix Sport LT 2x16GB 3800MHz C16 - RX 6800 XT - WD SN770 2TB - 2x 870 EVO 4TB


24/7 OC: i5 4690K @ 4.9GHz CPU@1.255v 4.4GHz Cache@1.10v - Archon SB-E X2 - Asus Maximus VII Ranger
Sapphire Fury X (1145/545 ~17.7K GS 3DM FS)

:eek: CPU Validation 5.198GHz@1.314v with 4.4GHz cache + RAM 2400MHz@1T :eek:
Da Music video

gupsterg wrote:
When you mean cold boot, you mean you turned off power to PC power supply?


Yes, i turn off the APC overnight or when i go out for some time, like now, i came home, turned on, C5. It's like Vboot rolls back to the previous value, which was 1.2v i guess. I've now just set dram in vboot voltage to 1.35v, will now restart into BIOS and set the DOCP profile and all other stuff, maybe it'll work.

Another bizarre problem is i can't get into BIOS except from windows, the keyboard doesn't work until the it's too late to press DEL or F2.

KeithMyers
Level 7
BIOS 2501 is totally broken. Turns off all the motherboard fan headers at least a couple times a day leading to cpu overtemp error and a reboot. All fans stop spinning. This is with all fan output controls disabled in the BIOS for nothing but solid +12V to all the fans all the time for 100% fan rpms. I've been dealing with this aggravation ever since upgrading to the 3900X and the 2501 BIOS on the C7H. Never a problem before for the 2700X and the 1001 BIOS that was installed previously. I have had over half a dozen reboots to cpu overtemp errors so far. Adjusted clocks and voltages to no effect. I am on custom loop cooling with the pump powered by SATA. But the radiator fans were connected to the cpu fan header. Every time I found the system waiting on the BIOS splash screen to have F1 key pressed to enter Setup, all the fans are spinning. Finally had it happen while browsing the forums, and noticed the cpu temp at 92° C. and all five fan outputs at 0 rpm. Got the side panel off to look and finally found all fans actually completely stopped. Moved the radiator fan cable to the cpu opt header to see if that did anything. It did not. At that point the computer rebooted at 95°C. on the monitor and then all the fans started spinning again once the display arrived at the BIOS splash screen with the cpu overtemp error.

I have moved the radiator fans to a molex direct connection and have ordered a fan controlle hub powered by SATA. ASUS needs to fix this BIOS ASAP.

KeithMyers wrote:
BIOS 2501 is totally broken. Turns off all the motherboard fan headers at least a couple times a day leading to cpu overtemp error and a reboot. All fans stop spinning. This is with all fan output controls disabled in the BIOS for nothing but solid +12V to all the fans all the time for 100% fan rpms. I've been dealing with this aggravation ever since upgrading to the 3900X and the 2501 BIOS on the C7H. Never a problem before for the 2700X and the 1001 BIOS that was installed previously. I have had over half a dozen reboots to cpu overtemp errors so far. Adjusted clocks and voltages to no effect. I am on custom loop cooling with the pump powered by SATA. But the radiator fans were connected to the cpu fan header. Every time I found the system waiting on the BIOS splash screen to have F1 key pressed to enter Setup, all the fans are spinning. Finally had it happen while browsing the forums, and noticed the cpu temp at 92° C. and all five fan outputs at 0 rpm. Got the side panel off to look and finally found all fans actually completely stopped. Moved the radiator fan cable to the cpu opt header to see if that did anything. It did not. At that point the computer rebooted at 95°C. on the monitor and then all the fans started spinning again once the display arrived at the BIOS splash screen with the cpu overtemp error.

I have moved the radiator fans to a molex direct connection and have ordered a fan controlle hub powered by SATA. ASUS needs to fix this BIOS ASAP.


Actually I've noticed such behavior with AI Suite, so I've uninstalled it and no problems with fans for now.

DJATOM wrote:
Actually I've noticed such behavior with AI Suite, so I've uninstalled it and no problems with fans for now.


Yup, all motherboard software like AI Suite is complete garbage, there are no exceptions. Why people continue to install this utter crap and wonder why they're having issues is beyond me. Installing this bloatware is one thing but if your first instinct when you run into problems isn't to uninstall it I don't know what to tell you.

DJATOM wrote:
Actually I've noticed such behavior with AI Suite, so I've uninstalled it and no problems with fans for now.


I don't do Windows. I have no fan control software running. Only have every fan control setting in the BIOS set to disabled to get nothing but +12V.

Except the BIOS is still turning off all the fan headers twice each day on average.

igralec84 wrote:
Yes, i turn off the APC overnight or when i go out for some time, like now, i came home, turned on, C5. It's like Vboot rolls back to the previous value, which was 1.2v i guess. I've now just set dram in vboot voltage to 1.35v, will now restart into BIOS and set the DOCP profile and all other stuff, maybe it'll work.

Another bizarre problem is i can't get into BIOS except from windows, the keyboard doesn't work until the it's too late to press DEL or F2.


I believe this is a UEFI bug. Hopefully release after 2602 fixes it.

UEFI 0068 (link) does seem to have this bug fixed. It is AGESA ComboPi-AM4 1.0.0.2, be aware though on some boards chipset voltage on first POST after flashing can be ~1.35V, link.

Once you manually set chipset voltage as 1.05V it will be that value even if you used "SAFE BOOT" button or make board enter "SAFE MODE" by holding down power button on board/case, the only time it can be ~1.35V is if you do CLEAR CMOS or on initial post after flashing.

I find getting into UEFI can be difficult when a restart is done from OS. I watch the Q-LED, just as I see it get to boot LED and here post beep I hit DEL to get into UEFI. When the board is posted from shutdown then there is enough delay on initial UEFI screen to enter UEFI with ease.

KeithMyers wrote:
BIOS 2501 is totally broken. Turns off all the motherboard fan headers at least a couple times a day leading to cpu overtemp error and a reboot. All fans stop spinning. This is with all fan output controls disabled in the BIOS for nothing but solid +12V to all the fans all the time for 100% fan rpms. I've been dealing with this aggravation ever since upgrading to the 3900X and the 2501 BIOS on the C7H. Never a problem before for the 2700X and the 1001 BIOS that was installed previously. I have had over half a dozen reboots to cpu overtemp errors so far. Adjusted clocks and voltages to no effect. I am on custom loop cooling with the pump powered by SATA. But the radiator fans were connected to the cpu fan header. Every time I found the system waiting on the BIOS splash screen to have F1 key pressed to enter Setup, all the fans are spinning. Finally had it happen while browsing the forums, and noticed the cpu temp at 92° C. and all five fan outputs at 0 rpm. Got the side panel off to look and finally found all fans actually completely stopped. Moved the radiator fan cable to the cpu opt header to see if that did anything. It did not. At that point the computer rebooted at 95°C. on the monitor and then all the fans started spinning again once the display arrived at the BIOS splash screen with the cpu overtemp error.

I have moved the radiator fans to a molex direct connection and have ordered a fan controlle hub powered by SATA. ASUS needs to fix this BIOS ASAP.


I have only experienced fan PWM going bad once on UEFI 2501. The board had been in use ~3 days without power off, only reboots had been done.

The other two times PWM went bad when I had Ryzen Master open with other monitoring tools, I have to have RM and other tool concurrently open for few minutes and then board headers have an issue.

I know your not on MS OS, perhaps something in Linux is sending Super IO chip wacko. I have yet to use Linux with R5 3600+C7H.
Intel Defector :eek: AMD Rebel


R9 5900X - Custom WC - ASUS Crosshair VII Hero WiFi - Ballistix Sport LT 2x16GB 3800MHz C16 - RX 6800 XT - WD SN770 2TB - 2x 870 EVO 4TB


24/7 OC: i5 4690K @ 4.9GHz CPU@1.255v 4.4GHz Cache@1.10v - Archon SB-E X2 - Asus Maximus VII Ranger
Sapphire Fury X (1145/545 ~17.7K GS 3DM FS)

:eek: CPU Validation 5.198GHz@1.314v with 4.4GHz cache + RAM 2400MHz@1T :eek:
Da Music video