Heya!

This is something I haven’t seen much, especially when I see YouTubers like JayzTwoCents, GamersNexus etc when they do CPU reviews and other CPU related content.

But they always seem to have reasonable voltages when they show HWINFO and their board BIOS, like 1.35 -1.45 depending.

But I can’t get a stable system unless the voltage is cranked this high.

The P-core SP is apparently 113 and the E-core SP is 85.

The board is a MATX ASUS Z690-G.

VRM LLC is set to 6 at the moment with DC IA at auto (0.49) and AC IA at 0.68.

I do have an OC applied at the moment, P-cores @ 56x and E-cores @ 45x.

When I reset everything the system won’t boot at stock/defaults unless I at least bump up the IA AC to around 0.78 to increase the voltage to at least around 1.5+ to be stable at stock with LLC 4 (DC IA 0.98).

Anyone else running a ASUS board have this issue? Or is it that common that it’s not really something to talk about as it’s part of why it runs so hot?

Capture while working in Unreal Engine 5 Editor

  • Sononeo@alien.topOPBEnglish
    1·
    1 year ago

    MCE is enabled, I even tried it off and this morning I actually did a CMOS clear again after the replies here just to be sure it’s not a bug in software.

    With MCE on and MCE off with everything at auto I can’t get into Windows. The BIOS voltage readout was at around 1.42.
    Which from the comments yesterday is about normal and what’s expected.

    I then made the changes back to what I had as stable (1.5+) and I can boot into Windows at least.

    It’s really weird and I also feel like for my setup I shouldn’t get a ton of throttling, but on heavy workloads it will frequently go down to 5GHz or 4.9GHz and stay there.

    • nhc150@alien.topBEnglish
      1·
      1 year ago

      I’d keep MCE off to enforce the stock power limits and make sure its not doing black box stuff to the voltage. For testing purposes, you can manually do everything MCE does.

      • Sononeo@alien.topOPBEnglish
        1·
        1 year ago

        Yeah this I’ve seen said before. I have thought to do that as a better way to keep track of changes and what causes an issue and what doesn’t.

        Except I kinda have this issue either way, but yeah I’ll probably do so for the added safety. Though it does suck, as far as features go, you’d hope it’d just work.