Last edited by malice19; 19-12-2012 at 05:39 PM.
I'm still worried about your version of CPUz reading the FSB all wrong - something is definitely up there.
Still, if you can get it to do 400x8 I'd stick with that - decent CPU clock and excellent on the FSB![]()
333 x10 Gets into windows then BSOD : (
So even though CPU z is saying im only getting a core clock of 2.5Ghz its still worth it as im getting higher FSB?
Only worry i have with this setting is Prime 95 when testing all cores errors on
[Dec 19 16:55] Worker starting
[Dec 19 16:55] Setting affinity to run worker on logical CPU #0
[Dec 19 16:55] Beginning a continuous self-test to check your computer.
[Dec 19 16:55] Please read stress.txt. Choose Test/Stop to end this test.
[Dec 19 16:55] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.
[Dec 19 16:55] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Dec 19 16:55] Hardware failure detected, consult stress.txt file.
[Dec 19 16:55] Torture Test completed 0 tests in 0 minutes - 1 errors, 0 warnings.
[Dec 19 16:55] Worker stopped.
Does this mean even though it has not crashed is not working correctly with 8x 400?
Cheers
Hmmm, not sure about the Prime95 test - you might be best googling that one.
As to CPUz, if the setting in BIOS is 400x8 you should be getting 3.2GHz, but CPUz seems to be reporting it as 8*320. Might be worth reinstalling CPUz and checking again, because either the OC tools are showing it wrong or CPUz is, and either that way that suggests that something's up. Along with the Prime95 test as well, it could indicate that there's a problem with some item of hardware... might be worth going back into the BIOS, setting *everything* to AUTO, and then doing a CPUz shot (while running something like Prime95 or wPrime) to check what CPUz reports as the default settings. You CPUz shot in the first post is way off what I'd expect the default settings to show as (should be core speed 2666MHz, multiplier x10, Bus speed 266MHz, rated FSB 1066MHz). If CPUz shows something different from that with all the BIOS settings at AUTO, there's something wrong (and personally I'd be pointing me finger at the motherboard...).
malice19 (19-12-2012)
malice19 (19-12-2012)
Yeah - go back to stock settings and test everything - including running Prime95. That'll help you work out if the overclock is the problem, or if it's something else. Like I said, I'm not entirely happy about your CPUz readings at stock: it might be that you've got something that's starting to show its age![]()
There are currently 1 users browsing this thread. (0 members and 1 guests)