Saturday, August 10th 2024

Intel Ships 0x129 Microcode Update for 13th and 14th Generation Processors with Stability Issues

Intel has officially started shipping the "0x129" microcode update for its 13th and 14th generation "Raptor Lake" and "Raptor Lake Refresh" processors. This critical update is currently being pushed to all OEM/ODM partners to address the stability issues that Intel's processors have been facing. According to Intel, this microcode update fixes "incorrect voltage requests to the processor that are causing elevated operating voltage." Intel's analysis shows that the root cause of stability problems is caused by too high voltage during operation of the processor. These increases to voltage cause degradation that increases the minimum voltage required for stable operation. Intel calls this "Vmin"—it's a theoretical construct, not an actual voltage, think "speed for an airplane required to fly". The latest 0x129 microcode patch will limit the processor's voltage to no higher than 1.55 V, which should avoid further degradation. Overclocking is still supported, enthusiasts will have to disable the eTVB setting in their BIOS to push the processor beyond the 1.55 V threshold. The company's internal testing shows that the new default settings with limited voltages with standard run-to-run variations show minimal performance impact, with only a single game (Hitman 3: Dartmoor) showing degradation. For a full statement from Intel, see the quote below.
Microcode (0x129) Update for Intel Core 13th and 14th Gen Desktop ProcessorsIntel is currently distributing to its OEM/ODM partners a new microcode patch (0x129) for its Intel Core 13th/14th Gen desktop processors which will address incorrect voltage requests to the processor that are causing elevated operating voltage.

For all Intel Core 13th/14th Gen desktop processor users: This patch is being distributed via BIOS update and will not be available through operating system updates. Intel is working with its partners to ensure timely validation and rollout of the BIOS update for systems currently in service.

Instability Analysis Update - Microcode Background and Performance Implications

In addition to extended warranty coverage, Intel has released three mitigations related to the instability issue - commonly experienced as consistent application crashes and repeated hangs - to help stabilize customer systems with Intel Core 13th and 14th gen desktop processors:
1. Intel default settings to avoid elevated power delivery impact to the processor (May 2024)
2. Microcode 0x125 to fix the eTVB issue in i9 processors (June 2024)
3. Microcode 0x129 to address elevated voltages (August 2024)

Intel's current analysis finds there is a significant increase to the minimum operating voltage (Vmin) across multiple cores on affected processors due to elevated voltages. Elevated voltage events can accumulate over time and contribute to the increase in Vmin for the processor.

The latest microcode update (0x129) will limit voltage requests above 1.55V as a preventative mitigation for processors not experiencing instability symptoms. This latest microcode update will primarily improve operating conditions for K/KF/KS processors. Intel is also confirming, based on extensive validation, all future products will not be affected by this issue.

Intel is continuing to investigate mitigations for scenarios that can result in Vmin shift on potentially impacted Intel Core 13th and 14th Gen desktop processors. Intel will provide updates by end of August.

Intel's internal testing - utilizing Intel Default Settings - indicates performance impact is within run-to-run variation (eg. 3DMark: Timespy, WebXPRT 4, Cinebench R24, Blender 4.2.0) with a few sub-tests showing moderate impacts (WebXPRT Online Homework; PugetBench GPU Effects Score). For gaming workloads tested, performance has also been within run-to-run variation (eg. Cyberpunk 2077, Shadow of the Tomb Raider, Total War: Warhammer III - Mirrors of Madness) with one exception showing slightly more impact (Hitman 3: Dartmoor). However, system performance is dependent on configuration and several other factors.

For unlocked Intel Core 13th and 14th Gen desktop processors, this latest microcode update (0x129) will not prevent users from overclocking if they so choose. Users can disable the eTVB setting in their BIOS if they wish to push above the 1.55V threshold. As always, Intel recommends users proceed with caution when overclocking their desktop processors, as overclocking may void their warranty and/or affect system health. As a general best practice, Intel recommends customers with Intel Core 13th and 14th Gen desktop processors utilize the Intel Default Settings.

In light of the recently announced extended warranty program, Intel is reaffirming its confidence in its products and is committed to making sure all customers who have or are currently experiencing instability symptoms on their 13th and/or 14th Gen desktop processors are supported in the exchange process. Users experiencing consistent instability symptoms should reach out to their system manufacturer (OEM/System Integrator purchase), Intel Customer Support (boxed processor), or place of purchase (tray processor) further assistance.
Source: Intel
Add your own comment

119 Comments on Intel Ships 0x129 Microcode Update for 13th and 14th Generation Processors with Stability Issues

#76
chrcoluk
vMax65For me it has always been Vcore. You can also look at VROUT (which is probably a little more accurate). VID when everything is on auto is what is being requested but gets modified by a few parameters including LLC, Power states like EIST/C1E temps etc which when looking at vcore is the actual voltage being used. As soon as you start changing settings like fixed, adaptive, offsets etc, then VID becomes less relavent. For both Intel and AMD VID is just a value that the CPU pulls from a programmed table of Multiplier/Voltage, and the mobo uses this to determine what Auto voltage it should set.

Can be real confusing and I am not any sort of expert so if there are any CPU engineers on TechPowerUp please jump in to help...
My understanding is the same as you, the reason I showed VID in the screenshot was because Jay used VID in his video so was kind of apples to apples, and I knew that I was undervolting so was showing what my CPU is requesting, I did later post my actual vcore values though.

I can use vcore moving forward on TPU, not a problem for me, as I agree with what you said.
Posted on Reply
#77
vMax65
#22This is the thing I don't get, I mean people concerned about VID being high. Isn't VID exactly what you say, so voltage CPU asks for, but one it gets being Vcore, so Vcore should be the one to concern? Btw what exact voltages are the ones to be concerned in the matter of this whole instability drama?
In terms of what to be concerned about, any voltages over 1.5v (okay even 1.45v for me would be too much! but some don't mind and like pushing to see what max they can get) would be a concern and I believe the issue was that up to 1.6v was being pushed under certain circumstances. For me limiting to 1.350v was a good middle ground (no loss in performance for me) and fingers crossed no issues and I monitor via HardwareInfo to make sure my voltage spikes do not go above 1.4v and since I have gone for an override/fixed voltage, this has been the case.
Posted on Reply
#78
ShrimpBrime
vMax65In terms of what to be concerned about, any voltages over 1.5v (okay even 1.45v for me would be too much! but some don't mind and like pushing to see what max they can get) would be a concern and I believe the issue was that up to 1.6v was being pushed under certain circumstances. For me limiting to 1.350v was a good middle ground (no loss in performance for me) and fingers crossed no issues and I monitor via HardwareInfo to make sure my voltage spikes do not go above 1.4v and since I have gone for an override/fixed voltage, this has been the case.
Not an engineer, but you worry too much seeing a v-core reading.

The problem is you state certain loads. But never say which one.

Oh no 1 core utilized 1.5v to obtain a frequency of 5.6ghz through 6.0ghz depending on the cpu model. This does not mean 250w man.

The issue is from heavy loads like all cores and the wattage. So Volt x Amp = wattage.

1.35v limited while under all core load drooping to 1.288v. That's a big droop. Why not just set 1.288v with a higher LLC and keep a sustained v-core? You'd still be at nearly 250w peak consumption....

People really should look at the amps. Lower that. V-core isn't a big deal. Well it is to those that don't understand it I suppose.

OK - Sorry for double post.

This is TWO cores at 1.682v Cpu-z reading with High LLC so keeping fairly stead 1.68v observed during the benchmark as minimum.

This is only 60w...... Edit: (Only 1 core utilized for the benchmark.)

Degradation?
Posted on Reply
#79
Dr. Dro
stimpy88Yeah, it's possible. I think they pushed the 14 a few megahertz higher.

Are you monitoring your CPU vids in HWInfo during a few different games to see what the vids are doing? And did you do this before the flash to be able comparison of behaviour?
No need for further speculation - Buildzoid hooked his 14900K/Master X on the oscilloscope


Looks like there's a whole mess with the settings going on - and looks like my setup is affected too. Video showed me how to improve on the situation. Might have changes coming with newer BIOSes
Posted on Reply
#80
chrcoluk
Dr. DroNo need for further speculation - Buildzoid hooked his 14900K/Master X on the oscilloscope


Looks like there's a whole mess with the settings going on - and looks like my setup is affected too. Video showed me how to improve on the situation. Might have changes coming with newer BIOSes
Buildzoid seems to have got an improvement out of the updates, his CPU at the start of all these events couldnt even run cinebench now he is running it undervolted.

In the end the mess I think was just his cinebench being detected as a background app and limited to e-cores only by windows I think, he said it at the end.
Posted on Reply
#81
ShrimpBrime
chrcolukBuildzoid seems to have got an improvement out of the updates, his CPU at the start of all these events couldnt even run cinebench now he is running it undervolted.

In the end the mess I think was just his cinebench being detected as a background app and limited to e-cores only by windows I think, he said it at the end.
Have the same problem with Z790 Gaming wifi. Can't pass a benchmark to show a screenshot.

Turns out, cpu runs fine on my B660-G board with first release ME firmware. Which is sad cause I'd like to get back to overclocking.

The problem Intel has is that once ME updates, you can't roll it back. They fucked themselves with that.
Posted on Reply
#82
starfals
Finally, intel is forced to go back to earth lol. THey have been pushing temps, speeds and voltages too hard to compete and win lol.
Posted on Reply
#83
phanbuey
I just tested my unpatched 13700kf and max volts at stock with LLC offset was 1.317v at 5.4Ghz -- i think ill sit this one out since I like the bios version I'm on for ram subtimings.

Chip has been running great since release and at this point, and
Posted on Reply
#84
Minus Infinity
Dr. DroNo need for further speculation - Buildzoid hooked his 14900K/Master X on the oscilloscope


Looks like there's a whole mess with the settings going on - and looks like my setup is affected too. Video showed me how to improve on the situation. Might have changes coming with newer BIOSes
I was just wondering what builzoid had to say on the matter. He's the go to guy IMO.

I've not really owned an Intel cpu since 3570K days, so not really been into this stuff much, but I do watch buildzoid for MB/memory recommendations and have followed his videos since these issues first started popping up.
Posted on Reply
#85
iameatingjam
phanbueyI just tested my unpatched 13700kf and max volts at stock with LLC offset was 1.317v at 5.4Ghz -- i think ill sit this one out since I like the bios version I'm on for ram subtimings.

Chip has been running great since release and at this point, and
chrcolukI am using stock clocks, not touched them, so 5.4ghz on the two best cores and 5.3 the rest, as I said I think I have a good chip.

The VIDs I pasted here are also using Intel spec'd AC/DC.

Here is pic of my configured undervolt, although actual undervolt seems a bit lower.

I swear I backed these off to 50mv for daily o_O. Guess I didnt.





Your test is not surprising as I think the microcode is not making any adjustment with your current voltages.
Yeah I think you do have a good sample.

So I took the shackles off my cpu ( haven't decided if I'm going to keep it that way)

I'm getting a maximum of 1.43 vcore (as per hwinfo) after running the passmark cpu test (includes multi and single core). And... I even turned off turbo 3 off so there'd be no 5.6 cores. Put ac at 90 instead of the 110 it was at originally. And left the 253 limit on, so otherwise still 'intel defaults= high performance' which includes 307 iccmax so its not 100% unbound.

Really goes to show how the 14700k is just an overclocked 13700k, its not better binned or, at least in my case. Guess that was just me fooling myself when I made the purchase.

On one hand its like should I just go back down to 5ghz and turn off some ecores? Turn down the power limits.... Pretend its like a 13600k/13700k and hope it lives a long life? Its not like that extra 10% of performance really matters for daily tasks. On the other its like, because I damn well paid for it whats why, and rma has been extended so if something goes wrong, maybe I'll get a better sample?


I just don't know ='(


Can always go back to 104 and do offsets but that corrupted my os last time I tried so I don't think I have much wiggle room (even though I did in January..... not a comforting thought) then again thats also when I found a couple pieces of something in my socket so that could have been what was causing issues. Also don't want to lose these new ucode protections...

On the bright side, I can confirm the vid limit (1.4) in my bios works as before turning it off all my pcores could not hit 5.5 unless they were basically idle. (Actually for some reason, vid was showing not going higher than 1.37... but thats software reporting for you I guess)

Perhaps setting a vid limit of 1.5 would be enough to allow me to hit 5.5 consistently enough while also offering a bit more protection than what intel is offering. Does intels vid limit vary by sku or is it just 1.55 across the board? I would really like to know.

Too much choices, giving me a headache. Anyway sorry for venting.
Posted on Reply
#86
chrcoluk
You could try emulating a 13700k and see what voltage you end up with either a all core 5.3/5.4 or 5.4 on 2 best cores and 5.3 for rest, that has me curious how well the voltages are in that configuration. If you curious my e-cores cap at 4.2ghz, I assume they got boosted on 14th gen as well. Also dont know how open you are to undervolting, the risk is instability if your chip cant handle it but there should be no risk to the health of the chip as you lowering voltage load on it.

I do have my power limits conservative and even lowered my tjmax from 100C to 95C might drop it later to 90C. My power limits are 175w for short and 125w for long. I ran a quick and dirty CPUZ bench yesterday which hit the 175w limit, but still outscored the 12900k reference on it.
phanbueyI just tested my unpatched 13700kf and max volts at stock with LLC offset was 1.317v at 5.4Ghz -- i think ill sit this one out since I like the bios version I'm on for ram subtimings.

Chip has been running great since release and at this point, and
Yeah similar situation for me.
Posted on Reply
#87
iameatingjam
chrcolukYou could try emulating a 13700k and see what voltage you end up with either a all core 5.3/5.4 or 5.4 on 2 best cores and 5.3 for rest, that has me curious how well the voltages are in that configuration. If you curious my e-cores cap at 4.2ghz, I assume they got boosted on 14th gen as well. Also dont know how open you are to undervolting, the risk is instability if your chip cant handle it but there should be no risk to the health of the chip as you lowering voltage load on it.

I do have my power limits conservative and even lowered my tjmax from 100C to 95C might drop it later to 90C. My power limits are 175w for short and 125w for long. I ran a quick and dirty CPUZ bench yesterday which hit the 175w limit, but still outscored the 12900k reference on it.
Yeah I was kinda curious about that too. Only thing is... I'm not sure how I can turn turbo 3 back on, but make those two core boosts go to 54 instead of 56 in the bios. Maybe throttlestop could help me with that. Anyway, I'll look into it. Would be very interesting if the results turned out to be the same.

So, if you haven't updated, does that mean your ac/dc loadline is at 110? (since the default just changed for me, not sure if thats a gigabyte or intel thing) Should be in hwinfo>summary>Motherboard under 'ai ac loadline' and ''ai ad loadline.' As of now my other loadlines are all on auto. Just to get it as close as possible.
Posted on Reply
#88
chrcoluk
Ahh I see you have a B760, so you probably cant do it, is possible on Z chipsets.

How did you get it down to 5ghz then?
Posted on Reply
#89
iameatingjam
chrcolukAhh I see you have a B760, so you probably cant do it, is possible on Z chipsets.

How did you get it down to 5ghz then?
I can still access the multiplier. It just wont take if I put it higher than the default boosts. So underclocking the all cores is no problem. Just not sure how to do it with the two 5.4 cores, separate from the rest of the 53x cores is what I mean. I'm sure I can figure it out though. Just... right now I need some game time. Been reading text and looking at numbers for too long. I'll get back to you though. I am interested in the result.
Posted on Reply
#90
Lesha
Does anyone else think that "incorrect voltage requests to the processor that are causing elevated operating voltage" is just an excuse for pushing the voltage to be able to compete with AMD?
Posted on Reply
#91
Caring1
zmeulASUS' BIOS release for Z790 Creator is broken in some way

with Intel profile I get around 13k score in R23 (13700K) and it should've been around 29-30k
No, that's how it is supposed to work, Asus made the error by giving it "all the power" and people assumed that was the norm.
Posted on Reply
#92
Dr. Dro
Caring1No, that's how it is supposed to work, Asus made the error by giving it "all the power" and people assumed that was the norm.
13k in R23 is not normal for a 13700K. It's less than half what it should be.
Posted on Reply
#93
chrcoluk
iameatingjamI can still access the multiplier. It just wont take if I put it higher than the default boosts. So underclocking the all cores is no problem. Just not sure how to do it with the two 5.4 cores, separate from the rest of the 53x cores is what I mean. I'm sure I can figure it out though. Just... right now I need some game time. Been reading text and looking at numbers for too long. I'll get back to you though. I am interested in the result.
Ok then try all core 5.3.

I had a look at my notes for AC/DC, so basically I equalised them as intel now recommends, 1.10/1.10 is set in bios, and this bumped my voltages up a bit so thats why my undervolt increased to -75mv. I think it might be ok to reduce them, but they both should be same value.
Posted on Reply
#94
zmeul
Caring1No, that's how it is supposed to work, Asus made the error by giving it "all the power" and people assumed that was the norm.
highly doubtful as other reviewers with MSI, GB mobo have 29-30k score
Posted on Reply
#95
phanbuey
zmeulhighly doubtful as other reviewers with MSI, GB mobo have 29-30k score
This happens when you have voltage protection enabled and undervolt too far. For instance, if I run my chip at 1.3v flat, it's actually stable but I get like 12K cinebench score, and 8K MT CPU-z score instead of the 27K (@190W) and 12.6k i usually get.

That's been the case since basically day 1 bios -- they released a bios later where you could turn off the undervolt protection, and that let the chip crash but rip at full performance with an undervolt. I think the undervolt protection just underclocks the chip if the voltage fed is below the vid table and it's just a flat 50% underclock.
Posted on Reply
#96
iameatingjam
chrcolukOk then try all core 5.3.

I had a look at my notes for AC/DC, so basically I equalised them as intel now recommends, 1.10/1.10 is set in bios, and this bumped my voltages up a bit so thats why my undervolt increased to -75mv. I think it might be ok to reduce them, but they both should be same value.
Alright, that sounds close enough. So I moved ac/dc up to 110. Reduced ecores to 8. pcores 53x and ecores 42x. pl1 125 pl2 175 (is that right? I like to keep them the same personally). The only difference is I can't apply that offset (not without doing things I don't want to do anyway)... And I wasn't sure what you usually do for load testing but I saw you mentioned cpu-z so I tried that and this is what I got: (should I have pressed stress cpu instead? I'm not really that familiar with this one).




Max vcore of 1.35. See that seems more normal to me. If a -75mv offset were stable on here ( don't know, don't want to try, since it involves ucode 104 which I've had bad luck with - twice! That thing is cursed). That would put us roughly around the same, right? If I were to jump to conclusions, it would almost seem like 13700k and 14700k aren't even binned that differently. I guess I assumed that was the whole point of the new gen. No new silicon, but move the bins up a tier.

Anyway yeah thats why I do have to use the ac/dc loadline as other than frequency its pretty much my only tool to affect vcore while staying up to date. But I can only get so far with it. 90 seems to have the same performance as 110 at least as far as I can see. Somebody on reddit suggested 60 but my performance nosedived. I guess some people increase llc to make up for this but w/e. Intel's whole system is just too complicated as far as I'm concerned. I'm just gonna run intel defaults with ac/dc at 90 and turbo 3 off, vid limit of 1.5 and try to forget about it.
.
.
.
.
.
.
.
Off topic but last time I ran this test on my 14700k, the score was 14700, I'm not even kidding... I think I still have the pic.....


lol!
Posted on Reply
#97
Moofachuka
This needs a re review... 13 and 14 gen
Posted on Reply
#98
Caring1
zmeulhighly doubtful as other reviewers with MSI, GB mobo have 29-30k score
Yes, they all allowed too much power to be given to the CPU until now.
There are plenty of videos online as proof they exceeded the 253W Intel specification.
Posted on Reply
#99
chrcoluk
iameatingjamAlright, that sounds close enough. So I moved ac/dc up to 110. Reduced ecores to 8. pcores 53x and ecores 42x. pl1 125 pl2 175 (is that right? I like to keep them the same personally). The only difference is I can't apply that offset (not without doing things I don't want to do anyway)... And I wasn't sure what you usually do for load testing but I saw you mentioned cpu-z so I tried that and this is what I got: (should I have pressed stress cpu instead? I'm not really that familiar with this one).




Max vcore of 1.35. See that seems more normal to me. If a -75mv offset were stable on here ( don't know, don't want to try, since it involves ucode 104 which I've had bad luck with - twice! That thing is cursed). That would put us roughly around the same, right? If I were to jump to conclusions, it would almost seem like 13700k and 14700k aren't even binned that differently. I guess I assumed that was the whole point of the new gen. No new silicon, but move the bins up a tier.

Anyway yeah thats why I do have to use the ac/dc loadline as other than frequency its pretty much my only tool to affect vcore and stay up to date. But I can only get so far with it. 90 seems to have the same performance as 110 at least as far as I can see. Somebody on reddit suggested 60 but my performance nosedived. I guess some people increase llc to make up for this but w/e. Intel's whole system is just too complicated as far as I'm concerned. I'm just gonna run intel defaults with ac/dc at 90 and turbo 3 off, vid limit of 1.5 and try to forget about it.
.
.
.
.
.
.
.
Off topic but last time I ran this test on my 14700k, the score was 14700, I'm not even kidding... I think I still have the pic.....


lol!
Your pretend 13700k score probably about right as you dont have two 5.4 clocking scores. Although that isnt a stress test.

Everyone has their own way of stress testing, I prefer to not go overboard so for me, its usually a few runs of each cinebench, asusbench 30 minutes, and 5 minute run of each xtu stress test (standard, avx, avx2, memory), and also the xtu bench, as I have in the past had bench cause instability. Also memory testing but no need in your case as you only adjusted the cpu params. Then just using the machine, as transient loads always have the potential to throw something up. Keep an eye on WHEA counter as well, hwinfo does log the counter for conveniance. I think with the loadline you set, I dont see why the chip would be unstable though as you still on the stock v/f curve.

Now intel have confirmed wattage isnt the root cause but its voltage, I may change my pl1/pl2 back to 175/175. Although I dont anticipate any workload I would run that would need that wattage, as I have only ever exceeded 125w in a benchmark or stress application. 175 is about right for my cooler/ambient/case airflow combination.

I seen your post in the other thread as well, and i do agree with the other guys, your chip is 5 year warranty now, and even at stock you are well within Intel's guidelines. But if you are uncomfortable above 1.4v, it looks like this 13700k config might be an acceptable middle ground for you.
Posted on Reply
#100
vMax65
LeshaDoes anyone else think that "incorrect voltage requests to the processor that are causing elevated operating voltage" is just an excuse for pushing the voltage to be able to compete with AMD?
As a 14900K user (no issues as I limited mine to 1.350v from the start), yes! Sadly Intel I think did decide to push these CPU's to the max to compete with the X3D CPUs' and they also wanted to keep the highest Ghz victory as well....In doing so they and the Motherboard manufacturers also had a huge hand in this, really pushed the CPU's especially the i9 series way to high without thinking or fine tuning the voltages. The worst part is that they did not need to and could have still got great perforamnce with some fine tuning. Anyway this is a lesson for both AMD and Intel and I think AMD have limited there new 9000 series already showing the underwhelming performance figures.

Intel have extended the warranty for a further two years for all 13th and 14th gen which is a start and I believe RMA's are going through a bit more smoothly though losing your CPU for a week or two cannot be a nice thing.
iameatingjamAlright, that sounds close enough. So I moved ac/dc up to 110. Reduced ecores to 8. pcores 53x and ecores 42x. pl1 125 pl2 175 (is that right? I like to keep them the same personally). The only difference is I can't apply that offset (not without doing things I don't want to do anyway)... And I wasn't sure what you usually do for load testing but I saw you mentioned cpu-z so I tried that and this is what I got: (should I have pressed stress cpu instead? I'm not really that familiar with this one).




Max vcore of 1.35. See that seems more normal to me. If a -75mv offset were stable on here ( don't know, don't want to try, since it involves ucode 104 which I've had bad luck with - twice! That thing is cursed). That would put us roughly around the same, right? If I were to jump to conclusions, it would almost seem like 13700k and 14700k aren't even binned that differently. I guess I assumed that was the whole point of the new gen. No new silicon, but move the bins up a tier.

Anyway yeah thats why I do have to use the ac/dc loadline as other than frequency its pretty much my only tool to affect vcore while staying up to date. But I can only get so far with it. 90 seems to have the same performance as 110 at least as far as I can see. Somebody on reddit suggested 60 but my performance nosedived. I guess some people increase llc to make up for this but w/e. Intel's whole system is just too complicated as far as I'm concerned. I'm just gonna run intel defaults with ac/dc at 90 and turbo 3 off, vid limit of 1.5 and try to forget about it.
.
.
.
.
.
.
.
Off topic but last time I ran this test on my 14700k, the score was 14700, I'm not even kidding... I think I still have the pic.....


lol!
I use to have a Gigabyte motherboard and all I can say it the bios was a mess and once you start making any voltage changes things can go off very quickly. In fact even wwhen I made changes the old changes were not removed and only a hard bios reset. removing battery would get oit back to normal...I was pulling out my hair...changed to ASUS which was also just another painful experience as the voltage they ware pushing on anything auto or 'multicore enhancment' was a joke. On MSI now which has been better but they too were pushing too much but in terms of fine grained control, it seems a lot better. Only manufacturer I have not tried is AS Rock.
Posted on Reply
Add your own comment
Sep 16th, 2024 08:32 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts