cancel
Showing results for 
Search instead for 
Did you mean: 
316 Views
1,118 REPLIES 1,118

Ravwyn wrote:
Thanks for this! Where did this come from?


An user posted it(link). Who have installed it says that fix 07 error and cpuz/aida showing it as "AGESA Version Combo-AM4 1.0.0.3". So i think the fix made by Shamino is included and we'll find this version on mobo support pages soon.

Oh boy, replaced the 2700X with a 3600 today, on the 2602 beta bios got a couple of BSODs immediately, then no mouse and keyboard in windows but worked in BIOS, then reversed and no keyboard during boot up so couldn't get into bios except from windows. Done some 3Dmark benchmarks with quite good results, all core OC to 4.2ghz at 1.35v + GPU overclock got me a comfortable 1st place, when i tried all core 4.3ghz at 1.4v got a crash, Ryzen Master doesn't work anymore, got a lot of BSODs just browsing. Now flashed back to 2501, getting CL14 RAM tomorrow, hope it stays at least stable for normal use. Using the latest chipset drivers but the windows balanced plan, in BIOS just DOCP for 3200 CL16 at the moment, IF speed set to auto.

Nikon985 wrote:
Try with bios v7304


So I tried bios 7304, same problem as beta bios 0001. What seems to happen is that the mobo randomly doesn't recognize my boot drive.
I think I've found a fix (it works thus far) and that is to change what sata port my boot drive is using, this is a kinda tedious fix tho as I have to do it every time my pc won't boot.
I also found out that disabling CSM fixed the unresponsive bios problem, but that seems to be because the mobo doesn't recognize a drive and just instantly boots into the bios (what else can it do?), CSM has to be enabled if I want to boot into windows. So I'm guessing something is bugged with the CSM module.
My boot drive is a 250GB Samsung 850 EVO btw.

@Shamino, any ideas to what is wrong?

Cursecut3r wrote:
@Shamino
The 0001 beta BIOS fixed the 07 code for me, but it just boots into an unresponsive BIOS (without me pressing anything) or a
responsive BIOS though safemode. I can't get into Windows. When I swap back to the R7 1700 the problem is still there and I have to
flashback to a BIOS that doesn't have Zen 2 (the ones prior to the 7000 bios) support for it to work again.
This is on a C6H with 16GB (2×8GB) of Crucial Ballistix 3000CL15 RAM.
I've tried twice to flash the beta BIOS but it still happens.


This one sounds like it might be an actual hardware issue since you're reverting the hardware back and the issue persists. When I was swapping my 1800x to my 3900x and having 07 issues it would immediately go away when I'd swap the 1800x back in. I would try re-seating everything on the board (a pain I know) and maybe changing up the slots that the RAM is installed into.

xeizo wrote:
Confirms Shamino saying it has weak boost, AMD is putting out less than great AGESA:s now. Looks like us using C7H will be staying on bios 2501 with AGESA 1.0.0.2 for quite some time, it's the best performing AGESA for Ryzen 3000 so far. Plenty of bugs, but better than slow and hot performance.

Regarding the chipset driver, best performance is rolling back to old driver from 7/7 and then install only the new Ryzen Power Plan on top of it. Not all the other stuff, works great best of both worlds!


Does anyone have the original BIOS for Crosshair hero x570 VIII? I am trying to track it down but i am unable to find it.

xeizo
Level 12
Should be a about time to see a 1.0.0.3ABB bios for X470 now, would be interesting even if it turns out worse than the 1.0.0.2:s
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

xeizo wrote:
Should be a about time to see a 1.0.0.3ABB bios for X470 now, would be interesting even if it turns out worse than the 1.0.0.2:s


More like Monday bet ya fiver

Dukat
Level 7
AMD is saying idle cpu voltage of 1.45 is perfectly fine as w're not really seeing the true voltage due, as long as it drops to 1.35v under load when all cores are active it's working as intended.

Assuming that is correct I decided instead of worrying about idle temp I should watch load temp.

Ryzen 3800x (Stock Speed)
Asus Crosshair VIII Hero x570
RAM: DDR4 3200
MSI RTX 2080Ti Trio (Overclocked)
Power Profile: Ryzen Balanced (Latest AMD release)
I tweaked fan curves to prevent fans from maxing out at random when mouse is moved.

Running Assassins Creed Odyssey benchmark, 2560x1440, max settings CPU temp jumps between 67-70C.
Would you consider that perfectly normal/safe temp?

Fan's ramp up less than before but still louder than any PC I've had in the past.
I'd like to further tweak the fan curve to only hit high RPM when temp passes 70C but wanted to make sure 67-70C is safe & not throttling before I make any other changes.

Dukat wrote:
AMD is saying idle cpu voltage of 1.45 is perfectly fine as w're not really seeing the true voltage due, as long as it drops to 1.35v under load when all cores are active it's working as intended.

Assuming that is correct I decided instead of worrying about idle temp I should watch load temp.

Ryzen 3800x (Stock Speed)
Asus Crosshair VIII Hero x570
RAM: DDR4 3200
MSI RTX 2080Ti Trio (Overclocked)
Power Profile: Ryzen Balanced (Latest AMD release)
I tweaked fan curves to prevent fans from maxing out at random when mouse is moved.

Running Assassins Creed Odyssey benchmark, 2560x1440, max settings CPU temp jumps between 67-70C.
Would you consider that perfectly normal/safe temp?

Fan's ramp up less than before but still louder than any PC I've had in the past.
I'd like to further tweak the fan curve to only hit high RPM when temp passes 70C but wanted to make sure 67-70C is safe & not throttling before I make any other changes.


You have to rely on the latest version of Ryzen Master for a more accurate temperature reading, according to AMD. Until the rest of monitoring sofware gets updated accordingly, what you're seeing is not representative of the current temperature of your CPU.
In space no one can hear you scream.

bruno_ro
Level 7
Great. Thank you!