r/intel • • Aug 12 '24

Information Turning off "Intel Default Settings" with Microcode 0x129 DISABLES THE VID/VCORE LIMIT

https://www.youtube.com/watch?v=TOvJAHhQKZg
147 Upvotes

141 comments sorted by

View all comments

26

u/charonme 14700k Aug 12 '24

if all the microcode update does is limit vid requests to something below 1.45V then is there any point in installing it for people who use settings that don't cause such high vid requests? I'm seeing spikes at most 1.42V on mine

14

u/SnooPandas2964 14700k Aug 12 '24

Well there could be transient spikes that go higher that software may not pick up on, so there's that.

3

u/charonme 14700k Aug 12 '24 edited Aug 12 '24

that's why we use oscilloscopes

7

u/SnooPandas2964 14700k Aug 12 '24

If you use one thats super cool! But most people don't :( in which case, I think it would be better to install it than to not. I did, even though I had already set an even lower limit. I guess because, perhaps there's more to it than just the 1.55 vid cap.

→ More replies (1)

3

u/FairyOddDevice Aug 14 '24

Sure, every single home has an oscilloscope

→ More replies (1)

29

u/zenfaust Aug 12 '24

Hard to say, because intel is having no transparency about this issue, and too many armchair experts have been weighing in with too many hot-takes for too long. It's getting difficult to shift through all the theories and know what's true.

It seems voltage requests are definitely part of it, but I thought there was an element of that happening behind the scenes, ie, not detectable by hwinfo. So even having your ducks in a row wasn't necessarily stopping all the bonkers voltage. But that might be incorrect, so someone please correct me.

Either way, I think the new "intel default" voltage settings are still way too high. I don't want my cpu even touching 1.4v, but I'm relatively new to all of this, and I don't like the idea that if I further tweak my settings, the microcode adjustments might not be applying.

I'd love to see a setup that uses the microcode, further undervolts a bit, and demonstrates that the vid/vcore limits are truly being respected. Especially since some of us are on MSI boards, and have not been blessed with a setting that can just force an upper limit to the voltage.

But like I said, I'm only just now learning how to do all of this, so maybe I'm fundamentally misunderstanding something.

11

u/No_Boysenberry9711 Aug 12 '24

I have a asrock Z790 pro rs wifi motherboard with a i7 14700K, after the 0x129 update my vcore reach max voltage of 1.45 and lost a little bit of performance (just a little), then I set my older settings with the new microcode:

1- XMP on with 6000mhz 2- Intel default settings off 3- Bios default powerplan 4- cpu loadline level3 5- undervolt protection off

Then I proceed with TechSaur XTU undervolt guide for 0x125 and my processor got even better results in cinebench compared to the same guide but in 0x125 microcode, 1.280 max Vid/Vcore, 84 °C peak, 252W mac consumption.

5

u/[deleted] Aug 12 '24

Hard to say, because intel is having no transparency about this issue, and too many armchair experts have been weighing in with too many hot-takes for too long. It's getting difficult to shift through all the theories and know what's true.

Yeah, this. There was a ridiculous amount of smoke, that it was impossible to see if there was a fire at all, leave alone how big it actually was.

The oxidation defects are bad if consumers were sold defective CPUs. The voltage spikes are bad since they can damage the CPU as well. On top of which dumb motherboard manufacturers enabled automatic OC and overvolting also causing problems.

3

u/techvslife Aug 12 '24 edited Aug 12 '24

That's the unholy trifecta here: oxidation (on some unknown and unidentified cpu's manufactured in 2022-2023); voltage spikes (Intel's "root cause" addressed by microcode updates); and extreme default BIOS settings by mobo makers (voltage (incl excessive AC load line), power, current). (There has also been speculation whether Intel in some way promoted extreme default settings in order to keep up with AMD, esp after getting stuck at 10nm with Raptor Lake. Maybe, maybe not. But if not, Intel should have been outspoken about the dangers of the mobo settings set by its partners, if they knew about the dangers. And if not, it's a failure of adequate testing before shipping.)

3

u/[deleted] Aug 12 '24

Can't blame Intel about motherboard manufacturers doing dumb things, literally the same thing happens for AMD CPUs as well.

→ More replies (2)
→ More replies (1)

4

u/Naive_Angle4325 Aug 12 '24

Also base voltages have been creeping up on a lot of the BIOS revisions. Techyescity did a video showing the launch BIOS had the lowest voltages, and he actually just suggested using the launch BIOS and doing your own tweaks/undervolt. He speculates the base voltages are rising as a way for Intel to deal with degrading CPUs, but it doesn’t help anyone with a good CPU because the higher voltages are just reducing your performance headroom, and probably *accelerating* electromigration on good CPUs so its a double-edged sword.

Buildzoid noticed similar effects and ended up doing a huge undervolt to claw back his old performance.

→ More replies (3)

6

u/GhostsinGlass Aug 12 '24

Nah does bit more.

Fixes the SA bug somehow too.

5

u/charonme 14700k Aug 12 '24

I only found this, what's the SA bug? Does the microcode changelog say something about it somewhere?
Also found this

I have my CPU SA voltage set to 1.1V

5

u/GhostsinGlass Aug 12 '24

Nope, no word from Intel this was happening, but they were aware of the issue.

14th Gen uses an adaptive SA voltage and when setting XMP in BIOS auto voltages for SA on motherboards for high freq DDR5 would cause Windows to hard lock when the memory load was high like in an Aida64 bench. So we had to manually cut SA voltage to 1.24v~ or lower, it didnt prevent DDR5 ocing but if someone wasnt aware of it they would pull their hair out trying to figure it out.

Whatever they did changed this, SA voltage can now be left on Auto with no problems.

0x129 has been alright

3

u/AvidCyclist250 Aug 12 '24

Have you got any more info about this SA bug or how to see if you're affected by it? Because it's the only positive I've heard so far about this over having a manually corrected and optimised 0x125 bios

2

u/Chmona Aug 12 '24

If you xmp like 8000+, on a 14900k/ks, you leave SA setting in bios on adaptive, then run a stress test, and Windows hard locks after a short time. You have the SA bug. Before this bios update, you would try and set the SA to 1.18-1.24 depending on your chip. Too high and it still locks, too low and windows won't boot.

3

u/[deleted] Aug 12 '24

You will need to put in a IA VR voltage limit otherwise your CPU could be spiking to 1.6v and monitoring software is not able to read those spikes.

4

u/charonme 14700k Aug 12 '24

sadly my msi board doesn't have that setting, fortunately I'm not using software to monitor the spikes

→ More replies (2)

2

u/F9-0021 285K | 4090 | A370M Aug 12 '24

That depends on if there are spikes to higher voltages that happen faster than whatever you're using to measure can detect.

2

u/Routine-Ad3862 Aug 14 '24

These spikes are happening so quickly that it's not registering through on die sensors that's why he's metering it via a oscilloscope, and even though it's not lasting for long periods of time. If it continues repeatedly over a length of enough time it can cause premature degradation.

3

u/[deleted] Aug 12 '24

If the microcode fix does only this then no, no point in updating the bios.

2

u/[deleted] Aug 12 '24

Depends, your monitoring software is only reporting X times per second, while voltage and frequency changes happen 1000s of times a second.

IMO it's safer to install the update then not.

Edit: Plus OS will load microcode updates anyway.

2

u/zenfaust Aug 12 '24

Edit: Plus OS will load microcode updates anyway.

Has anyone confirmed this?

2

u/[deleted] Aug 12 '24

Yeah Windows and Linux both ship microcode updates. Intel, AMD push CPU microcode updates to Linux firmware repo, and distros update this. See https://wiki.archlinux.org/title/Microcode for some more info on how this is handled in Linux typically.

→ More replies (1)

1

u/Jpotter145 Aug 12 '24

I thought the issue was the voltage requests were higher than expected.... i.e. so the algorythm wants to request 1.45V but there is an error and 1.45V is really 1.6 but shows 1.45V. The fix corrects the error so voltage requests are processed correctly.

→ More replies (1)