There's a guy 30mhz shy of 3ghz with a 9500 with 1.37v's right now. He is currently trying for more...
Is that supposed to be an impressive overclock on a Phenom? Seems a rather high voltage to get 3GHz, but then again what do I know, I've only been overclocking C2Ds...
There's a guy 30mhz shy of 3ghz with a 9500 with 1.37v's right now. He is currently trying for more...
I know this doctor named Brown who is almost done working on a flux capacitor.
---------------
E6600 (B3)-HD4850 512MB GDDR3-2GB DDR2-800
"You figured it out. All new CPU's are nothing but overclocked Pentium 1's with a few bells and whistles added, ask any ol timer whose been around."
Wasn't the TLB Errata only suppose to affect Phenoms above 2.4ghz in a select benchmark?(Locking up I believe) I have to go back and research when the errata first came to light but that would explain how you can have phenoms clocked higher then 2.4. Found an Inquirer link http://www.theinquirer.net/gb/inqu [...] hz-due-tlb about the TLB Errata. I can put up with dealing with the errata if what the inquirer says is true.
Unlocked Phenoms...mmm..that might just make me finally upgrade. Since I plan on gaming at 1400x900 for a while to come I don't need xtreme anything.
Current Rig: AMD 3800x2@ 2.4(939)-a8r32-mvp 3 gigs-x1900xtx-80gighd-500gighd-audigy2-samsung 19inch wide
Message edited by Pepethebandit on 12-18-2007 at 06:28:51 PM
TLB Errata affects all Phenoms and Barcelona chips
---------------
E6600 (B3)-HD4850 512MB GDDR3-2GB DDR2-800
"You figured it out. All new CPU's are nothing but overclocked Pentium 1's with a few bells and whistles added, ask any ol timer whose been around."
But I think what he's saying is that it's almost impossible for an end user to reproduce the error, ie it basically can only be done in a lab setting. Anandtech and the enthusiasts haven't been able to cause the crash, so I'm sure most average joe overclockers and such will be fine I thought I had read on the NCIX boards that the QX9850 had a FSB error in it that's basically the same idea, virtually no home user would ever trigger it?
If AMD could produce chips that stable at those speeds, they would and try to sell them.
The only reason Intel does not sell faster chips is they are not being pushed.
I read the thread and I saw nothing about stable chips at those speeds.
A few talking about booting. A few saying briefly "Prime Stable".
Not really much of any good news.
And to those curious about steppings, AMD already said they do not expect to have the B3 available until late Q1. So, no, this is not a chip that has the L3 erratta fixed. I'm not sure they have even figured out how to do that well yet. Remember, this erratta is one of the main reasons they kept reducing speeds.
They also cut the NB speed to try and fix it.
The linked article talks alot about how the chip really suffers under NB under 2.0.
Now, by supplying lots of power and lots of chipset cooling, they did get higher NB speeds, but again this is more along the lines of extreme cooling.
You are going to need to spend lots on the Phenom to make it match a 6400+ X2.
As far as overclocking goes, prime stable is stable.
Could be good for AMD if it offers the increase in performance that Phenom has so far lacked. Of course, if it turns out to be less than expected, another disappointment would be really bad right now...
Wow. This thread's come quite a long way. Some moments of sadness, some of laughter, and some of...well...utter ridiculousness.
We now see one more "confirming" report of immanent Phenom BEs, but is this all legit? Will we really see such a release this week? Ever? Or is it smoke and mirrors? Testing the water?
As far as overclocking goes, prime stable is stable.
Running a CPU-intensive program like Prime95 for many hours without errors is a general predictor of overall stability. However, it is not the end-all, be-all and I'd suggest running other programs that are stressful but sensitive to errors like Orthos and Folding@Home or even games (to check for locking up and gross instability, not the occasional hiccup that does not cause a program to segfault.) FAH is probably the most sensitive program I have run across and I recommend its usage, especially if you complete a work unit or two as that takes several days.
Oh, one more thing: watch those temps. "If it's too hot, it's not stable."
---------------
UNIX is user-friendly- it's just picky who its friends are.
DRM is slowly killing personal computing, one Sony rootkit and TPM chip at a time.
Agreed, I've had completely prime stable systems (8+ hours on both cores) that locked up during everyday browsing. It was my memory, and for some reason Prime wasn't effected by it.
Look at the TechReport website where they review Phenom twice - one with the TLB fix workaround and the other without.
---------------
E6600 (B3)-HD4850 512MB GDDR3-2GB DDR2-800
"You figured it out. All new CPU's are nothing but overclocked Pentium 1's with a few bells and whistles added, ask any ol timer whose been around."
Kyle Bennette at hardocp has his oc to 3Gigs with no errata patch along with other folks that bought the Phenom.The question I ask was statement,so I pose it as a question here ,which so far I have no answers.Everyone talks about the bug but nobody has shown it,reviewers have shown the penalties of the errata patch but thats it
Kyle Bennette at hardocp has his oc to 3Gigs with no errata patch along with other folks that bought the Phenom.The question I ask was statement,so I pose it as a question here ,which so far I have no answers.Everyone talks about the bug but nobody has shown it,reviewers have shown the penalties of the errata patch but thats it
I can kind of see where you're going with this, but stop and ask yourself this... Would AMD put the (punishing) errata patch in place if it wasn't absolutely necessary? Errata that tank every processors off the production line, all the time, in every computer in which they are installed, are usually caught in the modelling or simulation phase of CPU design/manufacture. Be content that this is likely a very rare bug, but one which AMD realized needed a fix in place. Add on to that the "PR factor" which Intel learned the hard way...
(Likelihood of bug)*(impact of occurrance)*(negative press impact of bug) = probability of implementing a "fix"...
Kyle Bennette at hardocp has his oc to 3Gigs with no errata patch along with other folks that bought the Phenom.The question I ask was statement,so I pose it as a question here ,which so far I have no answers.Everyone talks about the bug but nobody has shown it,reviewers have shown the penalties of the errata patch but thats it
If "The Bug" does not exist, as you suggest, then why has AMD released a patch for it? AMD also acknowledged its existence during it analysts meeting.