...Does DxDiag report the correct CPU clock speed, even if you've OC's your CPU? I've got a odd issue on my Q6600 that I "thought" I'd OC'd to 3.5ghz, where upon running BC2 in single player mode if I let the intro run its course and just land on the beach, without moving at all Fraps reckons I've got 39fps. (this is with my Q6600 clocked at 3.5ghz and a 5970 in tow). If I remove the overclock, so the CPU is at stock speed (2.4ghz) and run the same single player on BC2, without moving as I land on the beach Fraps reckons 39fps - Same thing happens if I adjust the overclock to 3.0ghz. Odd? My question returns to DxDiag, where I've currently got the CPU OC'd to 3.1ghz, but DxDiag reckons its 2.4 - Now is it reporting the original clock speed from somewhere? Or is my CPU simple not clocking as the FSB suggests? CPUz reports the OC's clock speed, as does my Win7 gadget which is monitoring CPU load and speed etc. I'm a bit confused, as I don't get why BC2 doesn't achieve better frames with a clock speed change from 2.4 to 3.5! Not sure whether I should sit-up and take notice of DxDiag, or simply ignore it. Cheers for any advice.