- Mar 3, 2017
- 1,777
- 6,791
- 136
The 32% meme propelled this thread to 662 pages. It's not something that you erase at this pointPls stop
*dons tin foil hat*
Is this because Intel said they would release their microcode update also on August 15th... *rubs chin*
I’m gonna be honest that should up to AMD to test, find and fix. If an YouTuber found an issue and let them AMD know what does that make of AMD’s QA team? Incompetent?I wonder if Youtubers like GamersNexus etc noticed a problem and let AMD know? Either way, better now than a full recall later. It's just two weeks, no lifes will be lost.
I know I been there, it’s been beaten so much at this point it’s annoying.The 32% meme propelled this thread to 662 pages. It's not something that you erase at this point![]()
Well... if they catch it before launch they're about 640 days ahead of the x64 competition.I’m gonna be honest that should up to AMD to test, find and fix. If an YouTuber found an issue and let them AMD know what does that make of AMD’s QA team? Incompetent?
oh you mean Intel. That’s a low bar.Well... if they catch it before launch they're about 640 days ahead of the x64 competition.
No, CPU design and manufacturing is just complicated.oh you mean Intel. That’s a low bar.
First time a race to finish last.Intel: "Our microcode update for our 13th and 14th generation of processors is a tiny bit more complicated than anticipated and as a result the releasedate will slip from August the 15th to the 16th."
Per GN Steve, It was AMD's validation team that identified "something they didn't like".I wonder if Youtubers like GamersNexus etc noticed a problem and let AMD know? Either way, better now than a full recall later. It's just two weeks, no lifes will be lost.
"This is not because AMD’s found any issues with the actual chips, spokesperson Stacy MacDiarmid tells The Verge. Rather, AMD discovered some of its chips didn’t go through all of the proper testing procedures, and the company wants to make sure they do."
Pure speculation, but from the statement, and what we've seen from ES samples, and the fact that the top SKUs are affected more, I would guess hitting spec clock speeds (5.7/5.6 GHz for 9950X/9900X). Maybe some of the retail units only hit 5.5 GHz or so.Well... if they catch it before launch they're about 640 days ahead of the x64 competition.
But I wonder what they weren't testing previously.
an OSAT goof?
I couldn't help it.+32% IPC Zen5 on August 15th!!
Do you remember the launch problems of Zen 4 and burned burned sockets? Maybe AMD simply prefer a launch without bugs, as in September no one will remember if it was a late July or early August launch. They will however remember if their CPU is not working.My decision to get the 7700x is looking increasingly better every day. What a cluster fudge of a launch.
AMD - The Software Company!Maybe AMD simply prefer a launch without bugs
They said that it was about what could be obtained at stock but the chip was under LN2 when they got this number.
Looking at the 55046 pts score at 6.375Ghz then those 42k were performed at 4.86GHz, beside the alleged 7 Zip 214,113 score is only 3.83% better than the 7950X, wich lead me to think that those numbers are not what we ll see in reviews.
The 7950X 7 Zip score can be found here, it s 206,214 :
![]()
Intel Core i9-14900KS im Test: Anwendungs-Benchmarks, Leistungsaufnahme & Temperatur
Intel Core i9-14900KS im Test: Anwendungs-Benchmarks, Leistungsaufnahme & Temperatur / Testsystem und Testmethodik für Anwendungenwww.computerbase.de
I doubt that. Having out of stock products for a few months has never been an issue before.My best guess is that the Yields just aren't there. 5.4 and 5.5GHz kinda works, so the 2 small SKUs can Release on 8th, but the number of 5.6 and 5.7GHz CCDs is so low that it would've been a paper launch. That's the only reason I could imagine where this launch window makes sense.
It's still stock, just a non-thermally limited one (and slightly more efficient operating condition).