bigboxes
Lifer
- Apr 6, 2002
- 40,256
- 12,219
- 146
Do they expect people to use this in conjunction with the power plans they released earlier to combat instability? A cap of 1.55v wouldn't seem to be sufficient to solve all of the stability problems out there . . .
- The microcode limits the voltage to 1.55V. As far as I can tell, this is the only change.
I have no idea how few milions of 13 and 14 gen users have no issue but some youtuber know best, same as guru3d those ppl have no shame for shilling for $$$
maybe if he had brain could explain the 9950x what is the issue, ohhh no no more dough from AMD, lol, OK move on
Agreed. Still kicking the can down the road, avoiding getting merked badly in the new reviews.Do they expect people to use this in conjunction with the power plans they released earlier to combat instability? A cap of 1.55v wouldn't seem to be sufficient to solve all of the stability problems out there . . .
That guy he mentioned in the Reddit post isn’t using microcode 0x129, MSI BIOS 7E07v1D is microcode 0x125.Video will start at correct time. Daniel-San shared Reddit posts where users are seeing significant performance drops with the new microcode.
Replying to myself ..... Suddely experiencing a couple of days of horrible crashing in Unreal Engine on a codebase ive had for months. No explanation for it. Completely random and very annoying. How am I supposed to develop if I have no idea if its a degraded CPU or something smelling in my code?After some testing on the 14900 non-K, I set the ICCMAX to 275A, limited all my cores to 5300MHz, (Asus Multicore Enhancement Unlimited - 90C)
Running CB23 and HWMonitor, This limits me to 225W permanently and I can score 35000 in CB, which is about 3000 down from the best I can get.
These settings also limit the VCORE to 1.3V which I assume is safe for a 14900.
If I enforce limits or use Baseline, I score 22000 in CB, which is worse than both the 3950x and 12700 non-K I upgraded from. Should have kept it! Zen5 here I come. Intel Crap
That is usually how it begins from what I understand. I would say yes to the RMA and start using an AMD Ryzen for all your coding needs.Replying to myself ..... Suddely experiencing a couple of days of horrible crashing in Unreal Engine on a codebase ive had for months. No explanation for it. Completely random and very annoying. How am I supposed to develop if I have no idea if its a degraded CPU or something smelling in my code?
Tried the same executable on a lesser AMD system and its fine....next day the 14900 is fine as well. Is this how degraded processors behave? Maybe one core is fxxxed and when processor scheduler uses it I get crashes?
Should I RMA this thing?
Replying to myself ..... Suddely experiencing a couple of days of horrible crashing in Unreal Engine on a codebase ive had for months. No explanation for it. Completely random and very annoying. How am I supposed to develop if I have no idea if its a degraded CPU or something smelling in my code?
Tried the same executable on a lesser AMD system and its fine....next day the 14900 is fine as well. Is this how degraded processors behave? Maybe one core is fxxxed and when processor scheduler uses it I get crashes?
Should I RMA this thing?
I suppose you don't live near a major source of cosmic rays, do you?Replying to myself ..... Suddely experiencing a couple of days of horrible crashing in Unreal Engine on a codebase ive had for months. No explanation for it. Completely random and very annoying. How am I supposed to develop if I have no idea if its a degraded CPU or something smelling in my code?
Tried the same executable on a lesser AMD system and its fine....next day the 14900 is fine as well. Is this how degraded processors behave? Maybe one core is fxxxed and when processor scheduler uses it I get crashes?
Should I RMA this thing?
Now that was a complex problem.When Sun folks get together and bullshit about their theories of why Sun died, the one that comes up most often is another one of these supplier disasters. Towards the end of the DotCom bubble, we introduced the UltraSPARC-II. Total killer product for large datacenters. We sold lots. But then reports started coming in of odd failures. Systems would crash strangely. We'd get crashes in applications. All applications. Crashes in the kernel. Not very often, but often enough to be problems for customers. Sun customers were used to uptimes of years. The US-II was giving uptimes of weeks. We couldn't even figure out if it was a hardware problem or a software problem - Solaris had to be updated for the new machine, so it could have been a kernel problem. But nothing was reproducible. We'd get core dumps and spend hours pouring over them. Some were just crazy, showing values in registers that were simply impossible given the preceeding instructions. We tried everything. Replacing processor boards. Replacing backplanes. It was deeply random. It's very randomness suggested that maybe it was a physics problem: maybe it was alpha particles or cosmic rays. Maybe it was machines close to nuclear power plants. One site experiencing problems was near Fermilab. We actually mapped out failures geographically to see if they correlated to such particle sources. Nope. In desperation, a bright hardware engineer decided to measure the radioactivity of the systems themselves. Bingo! Particles! But from where? Much detailed scanning and it turned out that the packaging of the cache ram chips we were using was noticeably radioactive. We switched suppliers and the problem totally went away. After two years of tearing out hair out, we had a solution.
But it was too late. We had spent billions of dollars keeping our customers running. Swapping out all of that hardware was cripplingly expensive. But even worse, it severely damaged our customers trust in our products. Our biggest customers had been burned and were reluctant to buy again. It took quite a few years to rebuild that trust. At about the time that it felt like we had rebuilt trust and put the debacle behind us, the Financial Crisis hit...
Yes, you should RMA it. That one core is likely your "preferred" best core for ST workloads which probably has to work the hardest out of all your cores since it's the one that can boost the highest so every time some sustained ST workload is run, Windows scheduler or the Intel Thread Director will try to schedule that workload onto that poor overvolted core so it's degrading faster than the other cores.Maybe one core is fxxxed and when processor scheduler uses it I get crashes?
Should I RMA this thing?
This is a total train wreck.
Is that guy a FUDSTER or moron, the voltage spikes are limited to 1.55V not the constant voltage used for clock, but he defo look as idiot to start from
gr8 way to get more clicks, 12min video and he show one picture of adobe crash report.... could it be it, sure but if he is some reviewer and not usual user I expected more from him then to rant only for whole videoAnother tech tuber starting to notice their raptor degrade from the looks of it.
gr8 way to get more clicks, 12min video and he show one picture of adobe crash report.... could it be it, sure but if he is some reviewer and not usual user I expected more from him then to rant only for whole video
FYI for those with RPL CPUs. If you turn off Intel Default Settings in the BIOS, the voltage limit in the new microcode gets disabled.
Exactly. Play by Intel's rules, or they'll take their ball and stomp off home (while denying your RMA request along the way). I wonder if this is Intel's idea for planned obsolescence?I mean of course it does. lmao.