Honestly, how hard can it be to troubleshoot? I don't have a 14900k anymore - had no issues when I had it - but this should be relatively easy to solve. Cap the clockspeeds, see if the issue continues. Cap the power, test again. Cap the amp limits, test again. I don't understand what the heck is intel doing taking that long, unless the issue isn't with the CPU itself this should have been solved alreadyIntel i9-13900K/14900K Highly Unstable in The First Descendant: Crashes Every 5 Mins | Hardware Times
We recently reported on the continued instability of Intel’s 13th and 14th Gen K-series processors in gaming. We’ve RMA’d three Core i9-13900KF (one still in progress), and a Core i7-14700KF in the last couple of months. Ergo, the RMA of the first chip failed, and then the RMA of the RMA...hardwaretimes.com
Literally, problem is still there.
I assume future UE5 game would have same fate on Raptor CPU.
Maybe that site can now receive legal "threats" or "incentives" to take that VERY damning article down?Intel i9-13900K/14900K Highly Unstable in The First Descendant: Crashes Every 5 Mins | Hardware Times
We recently reported on the continued instability of Intel’s 13th and 14th Gen K-series processors in gaming. We’ve RMA’d three Core i9-13900KF (one still in progress), and a Core i7-14700KF in the last couple of months. Ergo, the RMA of the first chip failed, and then the RMA of the RMA...hardwaretimes.com
The problem could be that their very best engineers are fully engaged on validating their upcoming CPUs for launch. We've seen with MTL that they find it very hard these days to maintain their launch schedules so making do with half baked launches where the firmware still isn't up to snuff.Honestly, how hard can it be to troubleshoot?
Small company issues, tough luck.The problem could be that their very best engineers are fully engaged on validating their upcoming CPUs for launch. We've seen with MTL that they find it very hard these days to maintain their launch schedules so making do with half baked launches where the firmware still isn't up to snuff.
The other possibility is that someone very high up is to blame for all these problems but that someone is also instrumental for Intel's future so they are trying to wait out the storm and just hoping that not a lot of people will run UE5 games.
Make this same offer on their community forums. You might get lucky. I once got lucky benching their Ice Lake server platform for free.How much manpower is needed to solve this? I mean seriously, give me a 14900k and a motherboard from each vendor and I'll find out the cause for Intel, free of charge.
Why each vendor ? never been reported on AMD. Unless you mean everybody that sells Intel.Small company issues, tough luck.
How much manpower is needed to solve this? I mean seriously, give me a 14900k and a motherboard from each vendor and I'll find out the cause for Intel, free of charge.
Pretty sure big media outlets have been leaned on to keep this quiet.Maybe that site can now receive legal "threats" or "incentives" to take that VERY damning article down?
Motherboard from each vendor. Meaning all AIBS, asus / msi / giga/ asrock etc. What does AMD have to do with anything?Why each vendor ? never been reported on AMD. Unless you mean everybody that sells Intel.
I did not understand what you mean,t, you just said vendor, not motherboard vender, there is a big difference,Motherboard from each vendor. Meaning all AIBS, asus / msi / giga/ asrock etc. What does AMD have to do with anything?
The problem is that the issue only happens under heavy overclock with all safeties removed with settings that are way beyond anything that intel allows.Honestly, how hard can it be to troubleshoot? I don't have a 14900k anymore - had no issues when I had it - but this should be relatively easy to solve. Cap the clockspeeds, see if the issue continues. Cap the power, test again. Cap the amp limits, test again. I don't understand what the heck is intel doing taking that long, unless the issue isn't with the CPU itself this should have been solved already
You seem to think Intel wants to solve it. If they solve it they have to admit there was a problem. And they don't seem to want to do that. After all they tried to pin it on board partners already.Honestly, how hard can it be to troubleshoot? I don't have a 14900k anymore - had no issues when I had it - but this should be relatively easy to solve. Cap the clockspeeds, see if the issue continues. Cap the power, test again. Cap the amp limits, test again. I don't understand what the heck is intel doing taking that long, unless the issue isn't with the CPU itself this should have been solved already
Are you being serious right now? Have you ever overclocked any part of your PC? How do you make sure it's stable after you overclock? That's exactly how I'd go about figuring out the issue. Isolating all the probable causes one at a time. Stock CPU with XMP off, check if it still crashes. Underclock the cache , check if it still crashes. Push some extra voltage, see if it still crashes. It's really, really, really not that hard.The problem is that the issue only happens under heavy overclock with all safeties removed with settings that are way beyond anything that intel allows.
And if they do heavily overclock a (any number of) CPU and notice that it crashes, how do they make sure that it was the CPU and not anything else in the system?!
How would you do that, since you offered?!
I can confirm that The First Descendant thrashes your CPU on shader compilation (and also decently during game). Despite having overkill water cooling on my 7800X3D it will briefly send fans full blast and hit 77°C.
View attachment 102307
I have however had 0 crashes. Unlike the author in the article who had 7 in less playtime.
You can't do that, master brain, every time you reduce the performance of any of the components you also take off some of the pressure from every other component.Isolating all the probable causes one at a time
The problem is that the issue only happens under heavy overclock with all safeties removed with settings that are way beyond anything that intel allows.
The experts at detecting and fixing instability are in chip validation at Intel.Okay, guess I'm wrong, it's impossible to detect and fix instability.
Well regardless of what intel allows, running power and Amp unlimited is flirting with degradation, especially at tasks like cbr, ycruncher or shader compilations that are causing these crashes. Is intel at fault for allowing aibs to ship their cpus with these settings? Maybe, but at the end of the day, if you are buying a k cpu and a z mobo, you should have the common sense to not be running ycruncher on a loop at 400 watts cause your chip will just die.Hmmm, so what settings exactly does Intel allow?
How did you notice that the CPU degraded? Did you RMA it afterwards or still using that degraded CPU?From my testing, even very light loads (under 100 watts) at 1.4 volts cause immediate and obvious degradation within a couple of minutes. I did not expect it at all cause I thought amps and not voltages are the main chip killers but it wasn't the case.
OH it was pretty obvious. My 24/7 settings were 4.9 / 4 / 4 at 1.06 voltages. Been runing them for around 2 years now.How did you notice that the CPU degraded? Did you RMA it afterwards or still using that degraded CPU?
First. Yes Intel has been stable for many years in the past. UNTIL Alter lake and later( 12xx,13xx,,14xx series) and thats because those are all factory overclocked to some degree. Intel had to, to keep the crown for most things.Are you being serious right now? Have you ever overclocked any part of your PC? How do you make sure it's stable after you overclock? That's exactly how I'd go about figuring out the issue. Isolating all the probable causes one at a time. Stock CPU with XMP off, check if it still crashes. Underclock the cache , check if it still crashes. Push some extra voltage, see if it still crashes. It's really, really, really not that hard.
Or to flip the question, Intel has been shipping CPUs that haven't been crashing for 30 years. How did they manage that before?
There are no issues AFAIK on alderlake. They weren't even particularly highly clocked, the highest clocked alderlake was at 4.9 ghz.First. Yes Intel has been stable for many years in the past. UNTIL Alter lake and later( 12xx,13xx,,14xx series) and thats because those are all factory overclocked to some degree. Intel had to, to keep the crown for most things.
As to your suggestions on Overclocking, here is the root of the issue. 99% or more of all users, buy or assemble their PC, then run it. They don't know how or care to overclock. But in the case of these, thats already a factory "feature". So 99% of all users see a problem with these under heavy sustained load. (percent having the problem was using those who don't adjust BIOS, not the actual number of users)
my 12700F would run as high as 300 watt usage at time, and I got rid of it before I could find out, so yes, that one is only a maybe. BUT the point of my post of that definitely, the 13xx and 14xx are WAY overclocked. from the factory and thats the center of the problem. If there was ANY motherboard that had reasonable bios defaults, they would not sell, as they would be so far in performance compared to the other MFG's.There are no issues AFAIK on alderlake. They weren't even particularly highly clocked, the highest clocked alderlake was at 4.9 ghz.
I get that most people don't dwell into the bios, but then they shouldnt be buying k, ks and z mobos.
That is the crux why months after this came to light, Intel have not been "able" to provide a fix.my 12700F would run as high as 300 watt usage at time, and I got rid of it before I could find out, so yes, that one is only a maybe. BUT the point of my post of that definitely, the 13xx and 14xx are WAY overclocked. from the factory and thats the center of the problem. If there was ANY motherboard that had reasonable bios defaults, they would not sell, as they would be so far in performance compared to the other MFG's.