AQUASTEVAE wrote:
what I think is happening, is if you don't make sure to compliment your overclock among all the important settings, it will automatically readjust to a lower base number.
First, thanks for replying here. Well, it's not that. Like OJR already said, it's just the multiplier which is stuck at 15.5, whenever I try to set a multiplier any higher than 37.
[EDIT: At this point, it didn't even fail to POST. It's just not applying them corretly!] I didn't touch BLCK yet, and it sits at 100 MHz as it should be. A multiplier of 15.5 is actually AMDs P2-state, it seems that it's stuck there for some reason.
However, I found a workaround. I reverted all my OC to default and just tried PState overclocking. I simply adjusted the P0 state to work with a multiplier of 37 which worked fine. Don't remember if I changed anything else in that step because I wanted to dig deeper. So, again I adjusted P0 state to a multiplier of 38. To be fully stable, I also needed to dial in a VCore offset of +0.05625. When trying to get 39 stable, I put some more VCore to it, reaching higher temps than I want it to be (remember, I'm still on a small tower air cooler) and it was not stable at all. At this point I just went back to my stable 3800 MHz OC using pstates.
I also tried these settings again with stock pstates, resulting in getting stuck at a multiplier of 15.5 again. Since I benefit of lower idle temps when using pstate oc, I'll stick to that. But still, that's something which needs to get fixed. I also assume that you are overclocking with pstates as well, right?
I already figured out my way to go, but I would like to see your settings. I'm curious how you did that. I'd also appriciate if you could provide information about your cooling solution and your temps.
🙂AQUASTEVAE wrote:
In one instance, I had my ram set at 3466mhz and it was running great, and then I tried to push the cpu higher, and the ram would go back down to 2200mhz. You have to have all of your ducks in a row with all complimentary settings.
When doing my initial overclocks, I just had a cheap 2133 RAM in it. I didn't even try to overclock it. But now I have my Trident Z RGBs. Running at 2933 for now. Didn't push higher there as well, since it also puts heat to the cpu. I also had my RAM @2933 when trying to push the CPU to 3900 MHz. I was reaching like 67°C on the CPU without being stable at all. Now with pstates maxing out at 3800MHz and RAM@2933 being fully stable, my CPU doesn't get higher than 61.5°C, which is still okay. Didn't have the time to fully stabilze higher memclocks, yet, but I actually don't wanna push my temps higher on air, so for now, I'll just leave my settings like that. But I'll try to push higher when switching to a full custom water cooling loop later this year.
'[OJR wrote:
;672955']1. I can have everything on AUTO and simply change VCORE to 1.35V for example. I reboot, go into Windows and the multiplier is stuck at 15.5
2. This exact issue is documented on the Crosshair VI HERO motherboard, and it is fixed in the latest BIOS 1501.
I also figured out those two things. The VCore gets applied, no matter what. But as you mentioned, you just get stuck at 15.5 when applying "too much" VCore or a multiplier higher than 37.
'[OJR wrote:
;672955']I am sure there is NOTHING wrong with the board, but the UEFI has an issue with certain Ryzen 7 1700 CPUs.
There have been no BIOS updates for this board in over 2 months.
The BIOS is still the initial release for this board. I think, it's not on the same status as the C6H is, yet. Neither do I think that's a faulty board. It's just the BIOS. They already fixed it for the C6H, so they just should release a fix for C6E as well.