Recommended Posts

On 20/11/2024 at 10:07, neufuse said:

hence why I posted a 3rd party report too

You should look into Windel from level1techs.

Many of those who have those processors didn't even know they had the issue until Windel contacted them and they started looking into the issue.

On 20/11/2024 at 13:13, Mockingbird said:

You should look into Windel from level1techs.

Many of those who have those processors didn't even know they had the issue until Windel contacted them and they started looking into the issue.

I've seen all their videos back in the summer I saw gamers nexus's videos this is nothing new to me

and the oxidation issue was fixed in what 2023? So that shouldn't stop you from buying a newer Intel CPU neither should problems of the 13th and 14th gen. which is the whole point of this thread

On 20/11/2024 at 10:17, neufuse said:

I've seen all their videos back in the summer I saw gamers nexus's videos this is nothing new to me

You should then know that even with a failing processor, the issue is often sporadic and doesn't show up in every task.

If you recall, the issue only blew up after Unreal Engine threw an "out of video memory" error and NVIDIA pointed the finger at Intel.

 

Edited by Mockingbird
On 20/11/2024 at 13:20, Mockingbird said:

You should then know that even with a failing processor, the issue is often sporadic and doesn't show up in every task.

If you recall, the issue only blew up after Unreal Engine threw an "out of video memory" and NVIDIA pointed the finger at Intel.

 

I am very aware of what errors occurred, and of intel's initial horrible response, but once again this is about is it NOW safe to buy Intel, and I'm saying yes, right now it is

On 20/11/2024 at 10:43, neufuse said:

I am very aware of what errors occurred, and of intel's initial horrible response, but once again this is about is it NOW safe to buy Intel, and I'm saying yes, right now it is

As I previously said...

On 19/11/2024 at 16:47, Mockingbird said:

Previously, the Vcore was going >1.66V.

In the microcode update (0x129), Intel capped the Vcore at 1.55V, which is still very high.

Accelerated silicon degradation could still be happening. We just don't know because the microcode update has only been out for 2 months and silicon degradation is a long-term issue.

 

If you are doubting and you read the news, why keep wanting to continue use Intel, when there's a better option, cheaper, better performance, more power efficient, more stable platform. Its like awarding the one that screw up, and punish the one that its doing a better job, make no sense.

On 20/11/2024 at 10:57, Mockingbird said:

The via oxidation issue is a separate issue.

It's wild that Intel knew about it since 2022 and didn't even acknowledge it until Gamers Nexus went digging.

Hello,

Intel's statement on the issue: https://community.intel.com/t5/Processors/Addressing-Manufacturing-Speculation-on-Intel-Core-13th-14th-Gen/m-p/1620097

While I haven't worked for a semiconductor manufacturer before, I have worked for a hardware manufacturer and, yes, companies do put out buggy hardware from time to time and when they do, they fix them.  In this case, it seems like Intel notified their customers about the issue and took action.  Now to be clear, "customer" in this context probably means something very different from "end user," but they did have the affected CPUs removed.  So, from that perspective, they correctly handled that bad batch of CPUs.

The hardware company I was at many years ago did something similar:  When they put out a bad batch of gear, they notified all resellers who had ordered them, a few customers that had purchased direct, let everyone know how to prevent the bug from occurring, and arranged for replacements of the gear.  This was at a very tiny company with a much smaller base, and they are not even in business anymore, but they did the right thing, which was to replace all the buggy gear from that particular batch with working gear. There was no reason for them to do anything else since it was a minor issue involving a specific batch of gear, and they fixed it for everyone involved (resellers and customers).

While such things are rare, they do happen from time to time.  I've had warranty work done on my current car a couple of times due to recalls.  This would not prevent me from buying the same brand of car again in the future.

Regards,

Aryeh Goretsky
 

 

  • 2 weeks later...

So I am doubtful that it is actually fixed or something is going on. I had a 13900k about 6 - 8 months old when this all started happening and started to run into similar issues. Once Intel released updates I started the refund process and got a 14900k. I installed it with all the updates and since day 1 run it at Intel defaults. There was one more update from Intel which released about a month or so after isntalling the CPU and I applied this update as soon as it was available.

However recently I have started to get issues again, mainly with CRC errors like installing new Nvidia drivers where it does unzip and CRC checks. I've since gone into the BIOS and changed my max turbo boost for the P cores from Auto on the two 6.0ghz to 5.7 to match all the other cores.

Now I did some extensive testing around this. The issues don't always happen and my theory is that whenever the CPU is momentarily boosting to 6ghz this is when the problems happen. So in many use cases like playing games, running stress tests then the CPU is not ever going to reach the 6.0ghz boost on those cores so you don't see the problem.

What I want to do is run a minimal OS and try to stress the cores at 6ghz somehow and see what results I get. But I am not sure how to go about that.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.