hello all,
I recently purchased a 14900k and I am running it on Gigabyte AORUS Elite AX mobo. I have 6800 MHz RAM from GSkill and 4090 as well.
I'm having an issue where, with all stock settings, Cinebench r23 always crashes on a multicore run (screenshot attached). However, single core completes just fine. I also don't have stability issues anywhere else. I can complete a 3Dmark timespy extreme run just fine with XMP 6800 enabled. I can play Halo Infinite with 6Ghz all cores + XMP without any other changes (e.g. no voltage changing) without any crashes at all. But with Cinebench my system isn't ever stable on stock settings.
I saw this other post that seemed to be the same, but the actual error log from Cinebench is different. I do notice that I share a mobo with this user. This is the Cinebench error:```Exception
{
ExceptionNumber = 0xC0000005
ExceptionText = "ACCESS\_VIOLATION"
Address = 0x00007FFBE514B3FD
Thread = 0x00000000000027F0
Last\_Error = 0x00000000
}
```
I know there probably isn't much good information in this post, so I will try to answer questions as quick as I can. I'm new to overclocking and dealing with instability so I don't really know where to go from here to achieve stability. Did I just loose the silicon lottery or something? Or are Gigabyte mobos trash for 14th gen? All help is greatly appreciated!
(as a side note, I'd love to learn actual overclocking. All the guides that I can find seem to only go into the detail of increasing Performance Active-Core tuning. So if any of you know of a resource where I can learn what everything does [e.g. AVX2 ratio offset or any of the other knobs in XTU] then I would be very grateful).
EDIT:
I'm continually experimenting, and I'll continue to post information as I get it.
- Not all of the Passmark CPU tests complete correctly either, so there is an issue there.
- In XTU, I boosted the voltage offset to +.05 and cinebench finished. I then returned the voltage back to .000 and cinebench was able to complete again. So I'm even more confused now.
I haven't done either. I'll try CMOS. Everywhere one said to only update the BIOS if it is known to fix this issue, and none of the updated bios seem to address this at all.