CPU-Z reporting the core speed at 2997.7 MHz

modez · 2 Apr 2009 at 12:24

Hi

CPU-Z reporting the core speed at 2997.7 MHz and the bus speed at 333.4 MHz, rated fsb at 1332.6, the multiplier x9.0 and I have disabled in the bios EIST Mode and the CIE Function. I have changed the CPU clock instead of 333MHz bus speed to 334MHz. The Dram Speed has gone to 1069. I get a report now on the CPU-Z my core speed at 3000.6 MHz and the multiplier has stayed the same and the bus speed is showing 333.4MHz and rated FSB is showing 1333.6MHz.
Temp reporting
Core0 34
Core1 41
My question is as I increase from the bus speed 333MHz to 334MHz, is this going to damage the board or CPU?

Any advice would be appreciated.

Motherboard Lanparty UT x48-T3RS
Bios:03/26/2009
CPU: E8400 C0
Memory:OCZ3P13331G
Timings:7 7 7 16
PSU:650W
GPU:8800GTS (640MB)
Seagate 500 GB SATA II at 7200rpm
Operating systems:WIn VISTA 32sp1

magicroundabout · 2 Apr 2009 at 13:38

Take a read of this

http://forums.overclockers.co.uk/showthread.php?t=17612922

RJC · 2 Apr 2009 at 21:46

Nope you will not damage the board or cpu, You could proberly overclock that cpu to around 3.8 - 4.2ghz.
I have my E8600 @ 440MHZ fsb.

JeremyW · 4 Apr 2009 at 00:18

A 1Mhz overclock aint going to do too much damage. As RJC says you can probably overclock your E8400 by a lot more before you run into grief. And if it hangs try again at a lower clock rate or with more volts!!

modez · 4 Apr 2009 at 11:38

Thanks for all the advice.

I thought with a board like this it would go further overclocking without damage. It is only my first time I am doing this as I usually don't bother to overclock. On my previous board Gigabyte, I didn't have to adjust the bus speed it just automatically came up with a CPU-Z core speed at 3000MHz . Basically, I wanted it to stay at 3000MHz as the specification stated on CPU.

Motherboard Lanparty UT x48-T3RS
Bios:03/26/2009
CPU: E8400 C0
Memory:OCZ3P13331G
Timings:7 7 7 16
PSU:650W
GPU:8800GTS (640MB)
Seagate 500 GB SATA II at 7200rpm
Operating systems:WIn VISTA 32sp1

Meridian · 5 Apr 2009 at 10:19

You would have to try really hard - like take the cooling fan off - to damage a CPU while overclocking, as long as (see the example) the cooling is still working. CPUs become unstable long before they get damaged, and you would turn it down below the danger point just to get it working. I've run heavily overclocked, air-cooled, CPUs for literally years (over four years for a 1.A Northwood at 1.65V!) with no damage that I could see. If the rig is 100% stable, you're OK.

M