With the 1226v bios, vanderpool is enabled but grayed and will not give an option of disabling it.
Would you know why this is happening?
Should it matter much if I let it enabled since I'm not running virtuals?
Printable View
With the 1226v bios, vanderpool is enabled but grayed and will not give an option of disabling it.
Would you know why this is happening?
Should it matter much if I let it enabled since I'm not running virtuals?
That's normal actually. You can only enable/disable it from a cold boot. I don't think leaving it off will affect you in any way. I believe it's only there if needed but I could be mistaken.... why don't you run virtuals? They are the ultimate tool for testing new/unknown software before hosing your "main" system.
Microsoft virtual PC 2007 is freeware now, just google it. You can make a fresh XP or Vista or etc. install to a virtual HD and then save that file to always has a fresh system image for testing purposes.
Thanx for the tip. ;) Maybe I'll give MS vPC a try.
By cold boot, you mean booting after restoring factory defaults in bios?
---
I noticed you added the E8000 series in the Intel offerings list.
I recently purchased an intel E8200 and wanted to warn E8000 series owners about temps that are reported by coretemp or speedfan regarding these cpus.
These utilities can't be trusted on the 45nm series.
Just for reference I originally had mine at stock cooling and no tower fans.
Coretemp reported 55C idle/ 65C prime25 load.
After installing a scythe mugen cooler and 4 tower fans, coretemp still reports 55C idle but 58C prime25 load.
I came across this theory http://www.xtremesystems.org/forums/...d.php?t=179044 that might give a logical explanation as to why this is happening.
Just wanted to share the link so that other newbies like me don't panic on their first coretemp reporting as I did.
Cheers.
@javaneze - no, a cold boot means power on the machine from an off state. A warm boot means to simple restart the machine (hitting reset or an o/s restart).
Thanx for the tip, I finally disabled it.
After numerous tries to achieve 8*400, I never got it stable at max vcore 1,1265v.
Not wanting to go higher on voltage, I gave the exact given in this topic configuration for the cpu, but running 4:5 833 MHz the memory @4-4-4-8 2.1v. (I'm still to stop thinking like that :D about the 6400 sticks)
I get an error in prime25 in about 2hours n 20 minutes.
I just did the vdroop mod and am running a smallfft's test with prime, waiting for the results. If I get an error again I'll loosen memory timings and ratio before giving any more voltage.
I'll post again when I finally get a stable system.
As far as you know, could it be the memory that's causing the errors? I mean since I'm running the smallfft's test that doesn't test memory as prime25 says.
Could be the memory, but it's tough to say... it could also be one of your MB vcores is a touch too low... 1.1265 V @ 8x400 is VERY LOW! My B3 Q6600 needs 1.3375 V to boot @ 8x400 and +1 level on the NB and +1 on the FSB term. voltages. I dunno if that's p95 stable or not. 9x333 is fast enough for me on this system.
Sorry for the typo, I meant to write 1,2625v but it's still far to low from the 1.3375 voltage you used.
Anyway also sorry for not being clear, what I meant by "the exact given in this topic configuration for the cpu" is that I'm now running @ 9*333 @1,2625v as you. All other voltages are one click up from auto too.
With this configuration and the memories in the quoted sync, I get the prime25 errors.
Btw I'm now at 2hours & 33 minutes stable. Maybe the vdroop mod was all I needed.
I pray it lasts for 6 hours :D
@javaneze - so did it last?
succinct guide, well done.
OK, just got finished upgrading the guide to version 1.6!
• Added a detailed section to help you find the minimum stable CPU and MB vcore settings. Check it out (near the bottom of the guide entitled, “Stress Testing and Minimizing Your Vcores”)!
• Updated the CPU table
• Provided a less than $5 method you can use to shave off some NB load temps (in the thermal management section at the end of the guide).
Any chance you could add a section on GTLref voltages? I havent seen much if any info on them...especially like max GTLref votlages etc.
Therein lies the problem... I don't feel comfortable writing about GTL's since I don't have a good handle of them, and what might happen to your system long-term if you use values that are above the rumored 67 % of VTT that is the default. As I said in the guide:Quote:
Originally Posted by graysky
Version 1.6.1 is up. Totally re-wrote the section on memory which now includes a discussion on both DDR2/DDR3 and formulas you can use to calculate max supported FSB of a given module based on it's DDRX-Y and PCX-Y designations. Also re-ordered the first part of the guide.
graysky, this guide is great, one of the best guides I have read. One suggestion, you provide an example where random cores fail and you diagnose/fix the problem. Could you post some other common issues that encountered when OCing Intels. For example, what if the same core keeps failing, which most of us know is most likely a weak core and the CPU may need more voltage. Thanks and great work again.
Thanks for the praise and the suggestions. I might add some additional discussion to the next version of the guide, but I didn't wanna make a fictitious stability log to demonstrate the point. What's in there is my real data.
I agree a fictitious log is not the way to go, but you could post some common Intel OCing issues and tips to resolve them.
Edited on 08-Jun-2008: Guide is now version 1.7 – added a 2nd example minimizing the vcores on my system.
nice guide gray , was a brave move
regards
I'm an Intel overclocking noob and would very much like to have the guide on paper so I could read and tweak at the same time. I think it's a great guide btw!
^^ Print it! ^^
First post was unclear indeed. What I meant was graysky to make a pdf or doc
or whatever to people to print. I would like to print it indeed but didn't want to
start copying and making it nicer looking. I'm lazy I know it...the first overclocking manual I read was from the dfi-street and they had it as a pdf.
If it was too much to ask I'll make one myself then. Just thought it would be great to be able to print it without a hassle.
hereya go... easy enough...
1MB PDF http://scootplace.net/fah/C2DOC.pdf
Just found this guide while searching for something, just had to read it, very good guide and very well written.
Awesome guide :up: really helpful for a noob like myself