I think somebody has been smoking somthing naughty. DS3 generally top out around 450-500 so its about right, though i can run my mem at 500+ on a 4/5 divider which is nice. Anything around the 60's load is fine imo, it will crash before it burns
I think we're both right, just a half sine wave apart. Sync on the Striker = 1:1 in CPU-Z and clocks it all the way down to 266. 1:1 on the Striker = 2:1 in CPU-Z and clocks it at 533, which reads as 1066 in the BIOS. This is also why memory was rated in PC-numbers, so as people we weren't like "WTF is with the clocks!? I have DDR400 here and DDR2... 400? 800? I think we should also talk in PC numbers from now with memory on to avoid confusion.
So the bios is reporting things right, it's just doing wierd things with the dividers. Talk in the "base" non DDR speed. Avoids any confusion with people having to divide by 8 to get the DDR speed, then work out the base FSB speed from there. If you say memory's running at 400 FSB, then you know it means 400 FSB. Dunno, up to personal preferences I guess, whatever you feel comfortable with - just make sure people know which you're working in!
Alright I have my histroy correct now: Dual DDR400 on the 875P chipset allowed the data to run on a P4-C with "800MHz" FSB to run in sync because they were both "3200MB/s" So, the increase to 266 = "1066" = 4200MB/s from the CPU, so if dual channel DDR2 533 was running at 100% efficiency it would work at the full 4200. Right. So PC8500 is twice as fast as it needs to be. Im with it! This DDR/DDR2 nonsense has me in loops. Which is good to get my head sorted now since I have a Memory article to write for next week And there was me thinking the Intel CPUs had increased more than I thought, but really we've only gone from 66-100-133-(166)-200-266. :/
trig take it off of auto and set it to 1.38, see if it boots up, if not keep raising the voltage up. I know on my board if you set the voltage to auto it will fluctuate depending on how much power is needed and it caused me a pile of trouble when i first started overclocking. Thats what i would do anyway, dunno about the more experienced users.
ive taken the cpu voltage off auto when i was trying this...knocked it all the way to 1.4...didnt seem to help...all the other settings are +0.1, +0.2...etc...
hm i found on my board that it really didnt like +0.1v on fsb and pci, so if you have any of them get rid. Then try mch on +0.1 and put the memory up to +0.3 vdimm. Running out of ideas why you have hit a wall. Could just do what i did: Return everything to stock, make sure all the extra bios features are disabled and any on board turbo boost stuff is off. Leave the vcore on stock add +0.2vdimm with 5 5 5 15 timings then just keep raising the fsb until it wont post. Then give it an extra 0.1vdimm to get 0.3. If it boots up to windows then everything should be good, give it a quick check with super pi 1M. Restart and raise the fsb once again until it wont boot and up the vcore until it does. Just keep doing this, if you push past where you got stuck before then it was one of your settings holding it back and not hardware. However going for stability.. is another story
I gave it all another go to try and take my e6300 further and once again no luck, i can boot it at 470 no problems and runs uper pi and tighten timings. But theres is zero chance of me hittin 3.30ghz it just wont happen i have tried everything. Id like to say its the memory but im really unsure as when i loosen it stupid amounts it still wont budge
Sounds like the boards maxing perhaps? Try dropping the multi and see what affect that has. If you can push the FSB further with the lower multi then it's probably not the board maxing. If you can't or the board has issues reaching the same FSB as before then its probably the board maxing. Dropping the multi pushes the internal NB frequency up, if there's more room in the chipset then this should highlight it.
just dropped the multi to 6x and tried fsb 480 and it wouldnt post. I have loosened mem timings to 5 5 5 15 and 1:1 with fsb
After reading this: http://www.xbitlabs.com/articles/mainboards/display/ga-965p-s3_6.html maybe worth going back to a previous bios?
