HL's E6850 OC Experience

[Quakindude]

If the problem is systemic throughout the production run, it won't be long before other sites start confirming Rich's findings. You can bet your ass other sites are scrambling to test this issue out on their own hardware.

The more I've thought about this, the more I find the hard FSB wall of 415 to be upsetting. No matter the multiplier, the CPU should still hit it's rated core clock.

[Capper]

It could very easily be an isolated incident......who knows.....but my concern was the Rep I've dealt with experienced the EXACT same issue.

If it were something I saw with a variety of processors, as I'm working on three different CPUs, then I'd look at the boards.....but I pop the E6850 out, put an E6600 in with the exact same settings....and theres no problem at all.

[Lead Head]

Originally Posted by Quakindude

If the problem is systemic throughout the production run, it won't be long before other sites start confirming Rich's findings. You can bet your ass other sites are scrambling to test this issue out on their own hardware.

The more I've thought about this, the more I find the hard FSB wall of 415 to be upsetting. No matter the multiplier, the CPU should still hit it's rated core clock.

I agree that it SHOULD hit its rated speed, but that is just one part of the core, the one you get the rated speed of. Some parts operate at FSB speeds, other operate that the "core" speed. On the P4s, one part, im not sure, I think it was the SEE or ALU operated at DOUBLE the rated core speed.

[Quakindude]

Originally Posted by Capper

It could very easily be an isolated incident......who knows.....but my concern was the Rep I've dealt with experienced the EXACT same issue.

That's also what has me thinking the flaw could be related to a production run of CPU's. I've seen where some folks have overclocked their E6850's to 433FSB, but when an Intel rep has the same issue, that should draw some much needed attention to the issue and at the very least, Intel should be asking you some pointed questions about your CPU. Like serial #.

[Capper]

You would think, huh?

You would also think that knowing who i am, and that the processor is part of our test bench, INTEL would have said "Hey, we'll make this right, and get you a working processor".....but true to their shitty, arrogant reputation, all i got was a big "F U" from them.


They always say to be kind and respectful to people on your way to the top, as those are the same people you'll pass on your way down.

[Elysium]

So, are you going to get a new CPU? What are you going to do about this?

[Capper]

What can you do? Not recommend the processor? Possibly, we'll see how a new one works. Not recommend INTEL? No, they are the best option around. Does this mean I'm happy? NO..... I am really disappointed with how the situation was handled from their end....but to be honest, its about what I expected. I wish I could say the response was an isolated incident, but its not.

I'll continue working on the review, and share my thoughts. Hopefully, this is an isolated incident, and nothing widespread......If you are one of those people who don't tweak the FSB to optimize the memory and motherboard, then the E6850 is a great option.....but from my experience, I won't recommend the CPU to anyone who already has a C2D processor.

[RA1D]

have you had a chance to play around with the qx6850?

[Capper]

Awesome processor, I'm running it right now at stock, with 1.265V right now....33C. I've had it at 370x10 (3.7GHz) 12 hrs Prime Stable, and 333X11 (3.66GHz) 12 hrs Prime stable.

In all honesty, I'd recommend the Q6600 to everyone....much cheaper, and the results are much closer than the price.

[garetjax]

The fact of the matter is that Intel, a company with a net worth of billions of dollars, would not replace a lousy $320 processor that they themselves admit to be bad. This is a prime example of how not to run a business. I don't care if Intel is worth billions of dollars; they have a responsibility to their customers. They can either get on board, or suffer the wrath and bad publicity of threads like this.