Yeah, it calculates a total aggregate based on latencies and NB clocks so indeed it would definitely make a large difference to the DCT performance. I've tried 40ns vs 50ns at 1066 5-5-5-15 2T, good gains.
As for NB DID, my BIOS gives the following options:
Bits - Divisor
000b Divide-by 1
001b Divide-by 2
010b Divide-by 4
011b Divide-by 8
100b Divide-by 16
Anything chosen >1 doesn't POST (clear CMOS needed).
IDK if what applies to K8 applies to K10h number decoding since they are totally different. One thing does apply, the year/week and the stepping '0747' and 'CAAWB' for instance.
But so far one other member says "MPMW is crap" based on 2 results. That's not right to do, it's too early to say this or if the latter letters make any difference at all.
-Firstly you'll need to have a database of similar week different last 4 letters to compare them.
-Secondly you need to have records of 'MPMW' and some other of any one particular week.
-Thirdly you need other week batches.
-Fourthly you need to match and variate steppings.
-Fifthly you need many samples of each chip to get a close to accurate rough idea.
So far we don't have these. 9600 BE could in itself be just a bad clocker. How do we know? Based on retail user results so far, it looks like a bad clocker, worse than locked Phenoms. Especially on HT ref. Jack looks to have a similar week/step to me, so we'll wait to compare chip potential.
I mean, how many users have you seen get more oc out of 9600BE than the standard edition?
How many retail users have you seen 2.55GHz stable on 9600BE?
Many have this with 9500/9600 though.![]()
When I see ES/PR junk like this it really ticks me off because they're try to get the feeling across that one one random sample they received reached 2.8GHz stable easy and yet that's totally untrue for retail so far. I'm sorry but not talking to any AMD reps for which step/week to buy and just going out and picking any one sample of the shelf is what we do and what applies as user centric results. I mean even Fudzilla reported on 18th November something far more accurate than most I've seen around: No plus 2.3GHz parts until B3. The >2.4GHz B3 Q1 part is where what I've heard doesn't agree but the rest has been true for a while.
Also, I'm not sure if I've mentioned it but you'll need to know K10 (AM2+, and AM3 actually) are limited to providing a maximum 110A to the cores and 20A to the northbridge. Not very healthy for oc if you start at 2.2GHz at 1.232V 95W TDP.
Generally 9500/9600 are clocking far better than 9600BE so far. My 9500 did 265HT ref but this 9600BE struggles over 210. Though I haven't yet underclocked the NB/HT to test max (BIOS problem), I have enough to show me the basics when 1.504V 1.48VID 220x11 fails bootup and destroys the Windows registry.But the "MPMW" seems to be weak for OC'ing. I've been reading these threads for a few weeks now and was really confused by some of the numbers you guys were getting, when I couldn't even get close regardless of how many V's I gave the chip... (I have a 9600, 0745MPMW)
I kept thinking I was losing my touch, or missing something....
At least I don't feel quite so bad now.
If you folks should find a magic bullet for MPWM, I'd sure like to know!![]()
If not, this may at least give some of you a rough point for a stable OC...
EDIT: Oh BTW, this is with 9x NB (1962Mhz) and 8x HTT (1744Mhz)... HTT may run at 9x but I haven't tried upping it yet, I was just looking for something solid...
KeZzZu: Its better to either post thumbs when its not something everyone passing-by will need if they miss it, or just to crop only the info you need to show in the pics (the tools/values).
9500s are going very good so far... in comparison to the rest.
Bookmarks