Intel's weapon against motherboard companies... will it work?

preview_player
Показать описание
As you can imagine, everyone is pretty concerned about the next generation of Intel CPUs given the way things turned out for 13th and 14th gen CPUs... so what is Intel doing to keep this from happening again?! Let's talk about DLVR...
 
Sponsored Links:

○ Join this channel to get access to perks:

○○○○○○ Items featured in this video available at Amazon ○○○○○○

••• Follow me on your favorite Social Media! •••
Рекомендации по теме
Комментарии
Автор

Back when I bought my 8700k, I didn't even consider Ryzen. Now I'm getting a 9800x3d and I'm not even considering Intel. Something about turntables.

MeatNinja
Автор

I dislike the narrative that the motherboard vendors were the only problem. The 13th and 14th gen CPUs have a voltage table and Intel pushed the 1 and 2 core values too high in microcode. All so they could have reviews with improved gaming benchmarks.

scott-
Автор

It is not only the fault of the motherboard manufacturers, I remember a video GN made in conjunction with Level1 Techs where they commented that 50% of Intel CPUs failed in game servers where the CPUs had never been run at high voltage or wattage, in other words CPUs that were never overclocked.

germang.
Автор

You also didnt mention that even at the 125w profile due to microcode errors it caused the voltage to shoot up to over 1.6v . It was not just the board vendors. Intels own voltage curve was borked.

Intel reps somehow gaslit you into believing it was the motherboard vendors only.

RadialSeeker
Автор

This is all good, but def important to remember motherboard companies were doing whatever for decades and we almost never had these issues. This was still on Intel at the end of the chain of failure. Just want to mention that so the buck doesn't get passed too much.

Garage
Автор

It’s funny how Intel never had a problem with motherboard manufacturers increasing the power profiles for years because it helped them sell their CPU’s at unrealistic performance numbers. This is not a motherboard manufacturer issue, it has always been an Intel issue.

blackbirdpctech
Автор

Sounds to me like Intel is trying to shift the blame. How come these issues were not in 12th gen?

petrescuserban
Автор

Nah, Jay. Mobo venders were A problem, but the real issue is Intel’s own microcode allowed their CPU’s to ask for voltages that excessive to begin with.

Corpo spent weeks concocting funny power mode graphs, pointing fingers and covering their faults up, and it worked on you. Everyone is to blame, but it’s MOSTLY Intel here.

zf
Автор

To sum the video up. "intel blaming motherboard manufactures for their own defects."

ligerstripe
Автор

When a company wont ackknowledge their own mistake, then that company is not trustwhorty.

joserosa
Автор

Don't let Intel gaslight us into thinking this was just a "motherboard vendor problem."
Intel owns the engineering of the CPUs and how much power they let them draw.
Board vendors wouldn't have been incentivized to compete in ways that led to burning up and destabilizing CPUs if Intel hadn't enabled them to do so in ways that incentivized that kind of dangerous envelope-pushing. "More stringent motherboard oversight" is all well and good, but Intel put board partners in that position in the first place. Don't let them off the hook.

wasd____
Автор

Yesterday, the local branch of a chain shop was running a promotion, you could get a 14700KF for $300 (tax included, it's in Europe). I decided to give it a try and see what happens.

The first processor was DOA and was replaced under warranty the same day with another one from the same batch. The second one even worked for a while but was so unstable that it still caused BSODs, going to RMA it tomorrow.

I can safely say that my credit of trust in Intel has been exhausted, and that for my next upgrade I will buy an AMD processor.

Edit: Forgot to mention that all of this happened with an updated BIOS, with Intel's "Performance Mode" enabled by default.

dartimon
Автор

Intel lost me when they started doing "generations" that were more like facelifts and you also needed new motherboards like every other "generation". That and their pricing taking advantage of there being little competition, to me that just showed greed - something illustrated that when AMD was competitive again Intel lowered their prices 40-50% and pushed OEM in all sort of ways to keep AMD out (look up Intel anti-trust fines).
The recent quality issues and frankly them doing all sorts to up core count, using extreme amounts of power and so, to try and look good on the boxes rather than really delivering has not made me consider Intel again.
Intel is a sick giant gorilla and those should be put to sleep.

bzdtemp
Автор

Nobody should be blamed for this besides Intel.

chunk
Автор

What's all this talk of motherboard vendors? Intel could just dictate the limits. And in the end it was the CPU's asking for the too-high-voltage anyway, no?

intermarer
Автор

The warmer room temps of those e-cafe's may play a role, but humidity only matters if you're using evaporative cooling with water, which I've not seen in the wild, and certainly wouldn't expect in an e-cafe.

kaseyboles
Автор

I don't agree with your take here Jay. It sounds like the board partners are at fault for Intel's issues. It is actually Intel who basically pushed them to compete in that way. And the board partners ofcourse had to, otherwise the reviews would show the other boards are faster.
Intel set this whole thing like this, and they got the profit from it for many years (because the cpus performed better with the board partners settings). They also used benchmarks with board partner settings to showcase how fast the cpus were.

Perrajajaja
Автор

This iFix it ad is still hilarious... The minnow!

kayakMike
Автор

I don’t think you are seeing the whole story with the voltage, cpus in servers with low limits were dying. There’s also the fact that the microcode is an intel problem and it was calling for extreme voltage because of an Intel error.

Nh_audios
Автор

All good except this wasn't really a mother board problem but a microcode defect.

audiodemos
visit shbcf.ru