Kursah, i got a better OC now. 3.24Ghz!!! Its kind of weird though. I'll explain later. For start, i'll tell you bout the settings. The voltage is set to around 1.35V but because of voltage droop, CPU-Z only detected 1.312V. Its normal i think. The core speed is 3240Mhz
Yeah, that ammount of vDroop is normal...I run my e6300 up to 3.36 stable with bios set to 1.32...reads (in bios and windows) 1.28v, and under load droops to 1.26. You may try upping it to 1.375 or 1.4 for a better oc. I've heard that 4300's may require 1.5v+ to maintain 3.5 speeds or more...some don't..it's kind of a crapshoot that way.
(360Mhz X 9 multiplier). FSB : DRAM is 1 : 1. My memory latency is set to 5-6-6-17(auto). I didn't set it to 5-5-5-15 as advised because whenever i set to that latency, vista can't boot up properly. It came out a blue screen saying something bout physical dump memory and restarted. So i set it to auto. And the DRAM voltage is 2.1V(+0.3V). When i set to 2.2V(+0.4V) the same blue screen appears again.
Well what is your memory's rated voltage? Your MB will stock run at 1.8v..but my memory is recommended to be ran at 2.0-2.1v for the rated 4-4-4-12 at DDR2 800 speeds, and that is perfectly normal to have to up your voltage as per MFG specs. I am at 2.25v, DDR2 960, 4-4-4-5 timings with my memory, it's good stuff.
I read on some sites that when overclocking on a 667Mhz DDR2 RAM, the memory muliti plier should set to 2.5 as 553Mhz to 2.0 and 800Mhz to 3.0. But the thing is, if it set to 2.5, the frequency of the memory would be too high. Will that affect my OC? I also plus another 0.2V for my motherboard (Gigabyte 965P-DS3).
Well you want to have your memory set to match 1:1 to your CPU at STOCK speeds for 1:1 OC, which for my ddr2 800 memory I had to set it to 533 (my cpu stock bus speed is 266), your bus speed is 200, so see if you can set it lower (Possibly 400?, I haven't OC'd with lower than DDR2 800 memory). It depends on your memory quality as far as how high you can OC it, look up specs on your RAM, find reviews, read forums about what other users were able to get and what they had to adjust to get there.
For my system's temp its quite cool, because i am using Artic cooling Freezer 7 pro which has a big heatsink. And a cooler master 12cm fan is placed just behind the heatsink, so airflow is excellent. SpeedFan recorded around 38C during idle and when i stress test my system, running 3DMark06, it around 45C.
I use the same CPU heatsink..it is great. I have my bios set to Performance mode so it doesn't kick on 100% till about 48C, but it will progressively increase speeds once I hit about 38C, so it stays very quiet and is very effective for the price! I idle around 33-35c, and load around 52-54c. Do you have front intake fans? A 12 cm fan in the rear is definately a posotive boost in cooling.
What are your load temps with ORTHOS set to Priority 9? Also if you want to see some high temps, load up TAT, intel made it to run the CPU hotter than anything else out there, and you'll never be able to get those kind of temps under gaming or anything else. If i use TAT I'll it about 62C in a hurry, but it stays there. Not recomended for a lot of stress testing/burn in though, but do try Orthos and let me know what you get.
Here comes the weird thing, i dont know how to explain, but please try to understand ok.
When i OC to 3.0GHz, vista is fine. After 3.05Ghz, vista still boots up normally, BUT my intergrated network adapter cannot connect to the network as i'm using a broadband router, and vista can't detect my clock speed, CPU-z cant be started. Now come the interesting part. WHEN, i unplug the cable from the router and plug it back again, the intergrated network adapter connects to the network that i wnated perfectly and vista could detect all the settings that i changed and CPU-Z pops up showing me the new clock speed...
Read up on your board for a "dead spot" in the FSB. It may cause issues like this, you may have to skip 10-20+mhz of FSB to alleviate that issue, as you'll be stable below that range and stable above that range, dunno why this is, and I have heard Gigabyte has implementations in new bios releases to solve this, but not completely. But do a search on your board for the FSB range you are having problems with.
If you want to skip that range, the best way is to up all of your voltages by 1 or 2 notches..some set up all but CPU on the highest and then OC to their top and start backing off voltages until it becomes unstable to know what kind of power it takes them to maintain that OC level with stability. I do the reverse route, I only increase once I see instability or failed tests in ORTHOS/Prime 95. But with your issue it may help you to OC further, and yes your system will run a lot warmer most likely so it's best to ensure you have enough airflow to help dissapate all of that extra heat. But you may have to keep voltages higher than you want to maintain a higher OC, and if you're not kosher with that or don't have enough cooling to maintain good temps, then you may be stuck at your current OC.
Good luck! I hope I have been of some help to ya! If you really want some help, get a P5B Deluxe as I have that board currently, I love it, and I know it very well now!