OC old man C2D E6600 + Asus Commando

[Sylver]

@Rober-García It was too strange that with underclock it raised the temperature so much...

Now it is at more normal values, of course it had dust to stop a ship

You can already try the 3DMark to see what results it gets.

The Brisbane is a great processor, it has given me great joys, although right now it is not with me. In the future I hope to recover it, when I have space

Greetings!

[Rober García]

Hello again.
With everything clean I have run the tests again... with the same results. I rule out the temperature issue because they are really stable.
I have monitored the voltages during the tests in case there was any peak, but nothing, stable.
I am starting to think it is the motherboard.
Sometimes when I start up I get an error in Overclock, and it loads the default configuration... but I haven't done any OC now ?...
Does any of you know of a situation where this happens, or any way to check it?

[Sylver]

Man, it reminds me a lot of an Asus K8V-X I had, which got worse over the years until it finally died, and gave that error from time to time... I have no idea about the specific reason, I'm convinced that some guru who occasionally stops by should know, but it's just speculation. The battery I imagine is fine, right? To rule out the most basic thing... Regards

[cobito]

I don't remember if I got a message or not, but my P5B Deluxe had a pin bent on the socket that was precisely used to define the bus frequency. This meant that sometimes, the processor would not be configured at its nominal frequency even when a clear cmos was done. Perhaps if dirt has entered the socket, a pin has been bent, thermal paste has entered, or anything else, something similar might be happening to it.

[Rober García]

Thanks for the replies. I'll check the battery and the dirt. I think I changed the battery recently, but it can't hurt to check.

More tests: I've lowered the HLBM and I'm doing tests and something weird is happening or I don't understand the results, because no matter what FSB I set on the e6600, I get almost the same results. It only cares about the multiplier

FSBxX CPU  Mem Timmings MonoThread MultiThread 375x6 2250 1:1 4-4-4-12 9.48k      15.43k 325x6 1900 1:1 4-4-4-12 9.42k      15.25k 182x6 1090 1:1 4-4-4-12 9.69k      14.97k  375x9 3375 1:1 4-4-4-12 13.52k     22.16k 182x9 1642 1:1 4-4-4-12 13.83k     22.55k 

[Rober García]

@cobito No dirt or paste, but the processor was full of a gelatinous substance that I don't remember seeing before. I didn't remove it because I thought "if it has been there for more than 10 years it can't be harmful"

[cobito]

@Rober-García Those results don't make sense. I've been reviewing the validations you've sent and the only one under 2Ghz gives a multi-core score of just over 12k (which matches the frequency), but I don't see validations at 1090 and 1642Mhz that give those 14.97 and 22.55k respectively. If you could repeat those two configurations and validate the results, I could look more closely at what might be happening in the performance charts. So far, in the 6 submissions you've made with the micro both over and underclocked, I don't see anything out of the ordinary.

[Rober García]

@cobito You are right. I was overclocking from Windows with clockgen and cpu-z recognized it, but it seems that the FSB was not being modified... as is evident from the results. I have done the OC from BIOS and it does vary the results accordingly. Also with superpi I had the same behavior.
When I have time I will check the pin you mention

[cobito]

@Rober-García If it was a failure in the CPU-Z frequency measurement and you can make the modifications via BIOS, I don't think you have any pin problems. In fact, I don't recommend removing that micro if it has been placed for a few years, because that's where a pin can bend no matter how careful you are.

[jordiqui]

@Rober-García what memories those coolers. Have air solutions changed much?