Those on Raptor Lake... What is your Vid cap? (Intel's default - or something else? - not updating at all??)

[iameatingjam]

Have you decreased it from intels default of 1.55?

I tried putting 1.4v but I couldn't reach max boost unless idle basically. Maybe if I had a better bin. Lots of people on reddit seem to be doing this.

I tried putting 1.5v and not much changed, passmark cpu test shows a 1-2% loss of performance. So I'm not sure if I should do this or just leave my fate in intel's hands (and maybe get golden sample as an rma replacement?)

 

[chrcoluk]

On my board its not configurable (and also cant be viewed), one thing I noticed with ASRock, is when I compare to buildzoid's bios it seems like about 90% of the settings are missing.

So no idea sorry.

I miss the days when board reviewers also reviewed the actual bios, so one knew what could be configured in the bios before buying the board.

 

[iameatingjam]

On my board its not configurable (and also cant be viewed), one thing I noticed with ASRock, is when I compare to buildzoid's bios it seems like about 90% of the settings are missing.

So no idea sorry.

Oh yeah, lots of people can't pick. Well shouldn't that put you in either the (1.55) or (on some old bios f these new updates).... options, lol.

​

 

[chrcoluk]

Oh yeah, lots of people can't pick. Well shouldn't that put you in either the (1.55) or (on some old bios f these new updates).... options, lol.

​

Yeah I assume if I update my bios it will be 1.55v (enforced via microcode), but on the old bios? who knows.

 

[iameatingjam]

Hmm I see what you're saying, worded a little too harsh? EDIT: Oh well I guess I can't edit it, can only add new options. Oh well.

 

[agent_x007]

CPU-z should be able to show it, you just have to adjust one value in cpuz.ini file (from "Sensor = 1" to "Sensor = 0").
If it works, you should see "Core VID", instead of "Core voltage" :

Yes, my waste of sand also likes to cook itself - but I'm locking it ~1.35V, so it's fine

 

[chrcoluk]

CPU-z should be able to show it, you just have to adjust one value in cpuz.ini file (from "Sensor = 1" to "Sensor = 0").
If it works, you should see "Core VID", instead of "Core voltage" :
View attachment 359364
Yes, my waste of sand also likes to cook itself but I'm locking it ~1.35V so it's fine

Yeah but thats not the cap, here is mine e.g.

Interesting in your newer build it says VID instead of vcore now, I will update it, but I suspect it will show the current VID instead of the max VID.

Updated it, and still shows live vcore for me.

 

[agent_x007]

I'm just locked to max. frequency here (on desktop), nothing in the background.

Main problem for this kind of thing is poll rate, or how fast programs checks voltage.
BZ videos will make it look easy with Oscilloscope, but it's REALLY hard to catch them.

 

[iameatingjam]

I'm just locked to max. frequency here (on desktop), nothing in the background.
Main problem for this kind of thing is poll rate, or how fast programs checks voltage.
BZ videos will make it look easy with Oscilloscope, but it's REALLY hard to catch them.

Right, thats kind of the whole benefit of the vid cap. You dont have to worry so much about having super accurate fast software reporting, if there's a hard limit in the cpu.

I see you're on 11th gen, so I don't think you're affected by this though if memory serves rma rates were still on the high side 11th gen though, correct me if I'm wrong.

 

[chrcoluk]

CPU-z should be able to show it, you just have to adjust one value in cpuz.ini file (from "Sensor = 1" to "Sensor = 0").
If it works, you should see "Core VID", instead of "Core voltage" :
View attachment 359364
Yes, my waste of sand also likes to cook itself - but I'm locking it ~1.35V, so it's fine

Ok switched it, but its the live VID not the VID limit.

 

[agent_x007]

Live VID is fine.
Now, with CPU-z window open, you have to put CPU under single core stress and see what happens to VID value.
If you want monitoring/log to check max/min VID - HWInfo64 is a good place to start.

PS. All core steady workload WILL NOT work for this, also with live view only - you have to do screenshot "in time".
That's why having a log and max/min values is important.

 

[chrcoluk]

Live VID is fine.
Now, with CPU-z window open, you have to put CPU under single core stress and see what happens to VID value.
If you want monitoring/log to check max/min VID - HWInfo64 is a good place to start.

PS. All core steady workload WILL NOT work for this, also with live view only - you have to do screenshot "in time".
That's why having a log and max/min values is important.

Yeah but I think we were talking about viewing the VID limit that is configured in the bios not the reported VID. It seems on some new boards, there is a limit now that can be configured.

As you said we already have tools like hwinfo to monitor the VID activity, and that can be set to a very high polling rate as well. Regardless, thanks for the tip because I do see when VID is configured in CPUZ it uses a fairly high polling rate as standard, Nice to learn something new about these tools.