- Mar 6, 2013
- Gigabyte X299X Designare 10G
- Vega 64
- Mobile Phone
Nice, 4.8 at 1.19 is pretty good. Above average anyway, from what I've been told.Currently running Mesh at 30, Core at 48, with a voltage of 1.19 and VCCIN of 2.0. LLC is Medium, so everything's quite close to what you've been experimenting with as well.
I briefly tried going 49, but I think that may require me to increase my LLC, which I currently don't want to do. Maybe something to check later.
Out of interest, what's your concern regarding increasing LLC? Heat? I've not yet really got my head around the interactions of VCCIN and LLC with main vcore and its effect on overclock. Interesting that you're as high as 2.0 on VCCIN - did you try lower VCCINs and found 2.0 gave better results? I've not gone above 1.92 yet. There's one expert on overclock.net who sets his VCCIN to 1.74 - underclocking it - and uses minimal or no LLC, because he says some voltage droop is good. Then I found a guide on another site that set VCCIN to 3.0!
I have experimented with various VCCINs, but haven't yet spotted any clear pattern. High VCCINs didn't seem to enable lower VCore, which was the main thing I was hoping for, though I haven't yet tried as high as 2.0. And of course I'm quite limited until I get proper cooling; I've stopped experimenting with new overclock settings until I do.
I'm going to order the MO-RA3 radiator soon, maybe today. I'll likely get that TechN block as well, despite the lack of reviews, as I don't think I want to pay the high delivery prices that an Optimus would involve. It's working well for you so that's a good sign
OK thanks. I'm thinking there must be some OpenCore setting that affects this.Yeah, I'm seeing the same behavior as you, entering without "Save and Exit" or resetting leads to an OpenCore boot failure. Seems like the SMBIOS does not affect this particular behavior.
Today I learned
1. It happens the same when I boot Windows from OpenCore. Exactly the same: if I launch OpenCore having been in the BIOS, I get a shutdown and restart very early in the Windows boot process, and when it comes back up CPU and RAM are at stock. So it's definitely OpenCore in general and not macOS specifically.
2. It's not, as I thought before, specific to overclocking. I prepared a BIOS profile with all CPU and RAM frequencies and voltages at Auto, and it happened just the same. It wasn't a complete stock setup, eg I still had my power and current overrides in place, and a couple of other non-default settings in the Advanced CPU Options menu.
3. It even happens when I use the F12 Boot menu. So it's not specific to having accessed the BIOS. It happens in any scenario except normal straight-through booting.
I'm going to keep investigating it as it's a bit of a pain when testing other OpenCore settings using a USB stick. In that scenario it's very convenient to be able to just select the USB from the Boot Override or F12 menu rather than messing around with boot orders, and this reset issue rather gets in the way of that.