• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Ryzen bclk confusion

Soulkeeper

Soulkeeper

Diamond Member
I just went into my bios and I can't seem to make it lock my bclk to 100MHz.
It shows frequencies in realtime and they are fluctuating wildly from 100-112+
The memory speed is also fluctuating above the 2400MHz that I have it set to.

Any ideas how to lock the bclk at 100 ?
 
That is odd, and definitely not normal behavior for any of the bclk OC-capable motherboards. Are you getting any instability or major voltage fluctuations associated with this behavior?
 
My motherboard does the same thing inside the BIOS as well. I think it's incorrect information being detected by the motherboard sensors because it says my CPU is hopping from 3.7GHz to 3.85GHz, memory jumps from 3200MHz to 3511MHz, and BCLK jumps from 99.88 to 112MHz all at the same time without crashing (all back and forth).
 
Unfortunately I can't verify voltages or temperatures in my operating system yet.
The stable software doesn't yet support the ITE87 chip version yet (i'll look into this more).
Also CPB/turbo does not seem to work.
The bios randomly shows/removes settings as well .... one time CPB was there, then it wasn't. The tRCDWR mem setting also disappears randomly.
Any memory speed over 2400 results in a single beep on boot and won't work regardless of other settings.

I currently have 4GHz running as the base, without cpb and +0.1v vcore/soc, memory at "normal" voltage/speed
So it runs max at 4GHz in my os and idles at 2.2GHz (voltages unknown).
I was getting mce errors reporting uop cache parity as the culprit on cores 8/9 when I set the vcore to 1.2-1.3v manually, also +0.05 offset was doing that.

I'm flying blind here, I guess dialing things in might have to wait for bios updates and software updates.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top