Here:
Download Intel's Thermal Analysis Tool (TAT):
http://www.techpowerup.com/downloads/392/Intel_Thermal_Analysis_Tool.html
Click on "TAT.exe in that link.
That should give you and us some reference to you temps.
What was you last stable settings (FSB X mulit @ Vcore)?
What are you using to test stability?
What do you consider stable?
Here's a stability utility that many of us use:
http://www.techpowerup.com/downloads/search.php?q=orthos
Click on Orthos Stress Prime 2004
I use one instance of Orthos for each core....but I need very stable machines for Distributed computing. You may want to just try 2 instances to get going.
Here's a link to CPU-Z, if you don't already have it, to confirm you BIOS settings once back in Windows:
http://www.techpowerup.com/downloads/search.php?q=cpu-z
Just for the record: All links above were linked via "techPowerUp.com". You can also find them on the original developer's sites, with possible problems finding TAT from Intel.
OK
Use those tools I linked. Get to somewhere stable, If not sure where stable, go back to stock settings. Decide how stable you would like your machine to be. Then use Orthos to test accordingly, while monitoring temps in TAT, and using CPU-Z to confirm your basic CPU and memory setting to be sure what you set in the BIOS is there when booting in Windows.
Lets's first get a baseline run on stock settings. Then take it from there.
Try two instances of Orthos at stock settings for 45 mins, and see how your system reacts. Then you can increase the clockspeeds slowly, whiling keeping Vcore stock, all the while stopping to test stability and temps under load.
I'll try to pop in when I can. Hopefully some of the other fine knowledgeable overclockers here will keep an eye out too. Let us know how it goes. And don't panic or get worried. Take it nice and easy, one thing at a time, slowly. Overclocking is generally a reiterative process, involving small changes, stability and thermal testing, then more changes, and more testing. This goes in spades if your new to overclocking.
K
Take care.
~ Srat ~
<edit>
BTW, I hope I haven't insulted your untelligence or your technical expertize...I'm starting with the very basics. I see your a new member, and not sure of your abilities, or knowldge in the s/w tools and methodology comon to overclocking. If you're already past this point in you roverclocking learning curve, let us know where your at, and we'll proceed from there.