Core 2 Duo Batch Number threads for overclocking

[sswilson]

Originally Posted by JayDee

I came across that thread at NCIX as well - After I put in an order for a E6600. Too bad that a poor overclock isn't accepted as a vaild RMA reason. For 99% of the buyers (Dell/Gateway/... bulk box buyers) it makes no difference but the OC is a big part of the decision to buy for the other 1%.

Yeah, there are very few venders who will offer to check steppings, and some of those who do will charge a premium for the service.

This used to be a big issue with S939 chips, not sure what the market is like for C2Ds.

This is the kind of service that a local vender can shine at.

[S|nApSE]

One of the Thermalright series - if NCIX ever decides to get stock. :P

At any rate, I can't possibly see it requiring such an extreme increase in voltage to carry this processor a couple hundred mhz higher. So, I either got really lucky in the batch or those guys in that thread are doing something really wrong.

[Supergrover]

Originally Posted by sswilson

Yeah, there are very few venders who will offer to check steppings, and some of those who do will charge a premium for the service.

This used to be a big issue with S939 chips, not sure what the market is like for C2Ds.

This is the kind of service that a local vender can shine at.

Well I have been lucky with my 939 cpu's BUT before I open the packages I ran the stepping's just so I wouldn't get burned. A restocking fee is better than having to flog it on Ebay, of course you run the risk with the replacement.

[ragenrok]

ok, well I finnaly got my case that I have been waiting for about a week now so I can use my new e6600.

Its stepping is L646G510

So far Ive gotten it to 3.32 @ 1.45v

I've run it through a full 3dmark with no error and currently running orthos blend test Priority 9 and cpu temps are holding steady at 55C with my zalman 9700

Running it at 3.4 gave me a BSOD in 3dmark half way through the second CPU test so I'll play wih it more tommorow and see what I can get it to lol.

My new rig arrived yesterday but, unfortunately, I won't have a chance to built till Monday or Tuesday


My batch is L704 A945 Malay. I checked all the links and I didn't see a single "L7" (a 2007 production run I think). From what I've seen the older L6 weeks OC better than the ones later in the year so I hope the L7 breaks that trend. Oh well the proof of the pudding is in the voltage and we'll see what I can get from the L7

[Babrbarossa]

Great news guys! Rag- 55 seems a little high with that voltage and that cooler- maybe the thermal paste just needs to settle. Good news that you were able to break 3GHz though, and without too much juice.

[ragenrok]

check this link out here:

NCIX FORUMS - Recent Steppings - Intel Core 2 Duo E6600 Dual Core Process...

2 guys with L7 chips. One even ha a A batch like you and managed 3.2 at stock voltage. Its to bad he never posted his final OC.

Oh and my G510 ran for 8 hours in orthos last night at 3.32 and no crashes.

Thanks for that info ragenrok

Helps me to have a more positive attitude as I look to the build as I've been thinking newer isn't necessarily better when it comes to C2D production weeks.

[ktown]

I have checked out the C2D lists you were good enough to post but I can't seem to find out what week & code my E6400 is. The lists all insist that the info is on the cpu and box and is listed like ..L6xxA***. But the only info I have is...FPO/Batch#... 7639A235 (Pack Date 01/31/07). So I'm guessing the code is A235 but have no clue as to what week 7636 would be???? CPU-Z shows Stepping 6 & Revn B2.
Any ideas??

[S|nApSE]

7639A235
Okay, this is a little wierd. Generally it's year, week, batch and some other batching markers. As a result, 76 doesn't make a whole lot of sense. Take a look at the processor itself and see if there's a similar number.