Dangman
Ninja Editor SuperMod
- Joined
- Dec 15, 2005
- Messages
- 46,056
press Ctrl-F1 at the bios screen.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Hiya guys, just finished my first build this week and have been playing around with trying to overclock it. Getting couple of errors.
First of all my hardware:
Intel e6600
Bufalo Firestix 4 x 1gb
Gigabyte DS3 rev3.3, F11 bios
PNY 8800GTS 320mb
Corsair 620HX
Barracuda 7200.10 320gb HD
Arctic Freezer 7 pro
Thermalright HR05 SLI
Antec p182 Case
I've been following this guide to OC my DS3
From the many hours lurking these forums I felt that the following overclock was very achievalbe:
CPU @ 3150mhz
350 FSB x 9
Vcore 1.375
RAM @ 437.5mhz (4:5 ratio)
875mhz 4-4-4-12 timings @ 2.2v
So, the above is the OC I was intending to keep. However, something is apparently not stable. I've had a few problems at this speed.
1) sometimes when I boot the computer for the first time that day, the computer would load but the monitor would act like no signal is recieved. This happened a couple of times, I've reseated my vid card. Its has since happened once again but been behaving for the last couple of days.
2) After setting the ram timings and FSB speed, I boot into memtest86+ to check the stability of the ram. I let it run till it gets 1 pass without errors (approx 45 mins). The ram is pretty hot to touch (I can put my finger on the heatsink for 5 secs or so) but looks ok according to memtest86+. I quit the program and reboot. The computer would not post, it attempts to boot a couple of times then reverts to lower FSB/RAM settings.
3) Being stubborn, I reinput same settings to see what temps look like. I start up CoreTemp, SpeedFan, SuperPi, CPUZ, and Orthos. Orthos ran fine the first time at priority1 for about half and hr with no errors. Idle temp is 39o and never goes above 55o under load. Later, I run all the above again and orthos stops about 5 mins in . The following is from the splog file in orthos directory:
Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 3837 Time: 15
CPU: 3150MHz FSB: 350MHz [350MHz x 9.0 est.]
5/1/2007 9:37 AM
Launching 2 threads...
1:Using CPU #0
2:Using CPU #1
1:Beginning a continuous self-test to check your computer.
1ress Stop to end this test.
2:Beginning a continuous self-test to check your computer.
2ress Stop to end this test.
1:Test 1, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.
2:Test 1, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.
2:Test 2, 4500 Lucas-Lehmer iterations of M17432577 using 1024K FFT length.
1:Test 2, 4500 Lucas-Lehmer iterations of M17432577 using 1024K FFT length.
2:Test 3, 4500 Lucas-Lehmer iterations of M17432575 using 1024K FFT length.
1:Test 3, 4500 Lucas-Lehmer iterations of M17432575 using 1024K FFT length.
1:FATAL ERROR: Rounding was 0.5, expected less than 0.4
1:Hardware failure detected, consult stress.txt file.
1:Torture Test ran 4 minutes 50 seconds - 1 errors, 0 warnings.
1:Execution halted.
2:Torture Test ran 4 minutes 50 seconds - 0 errors, 0 warnings.
2:Execution halted.
I cannot find the 'stress.txt' file it refers to.
Any thoughts as to what you think is unstable in this system? Any thoughts are greatly appreciated. (I've also posted this in the OC forums)
KD
Edit: here are the messages from inside orthos (its greek to me)
Test 3, 4500 Lucas-Lehmer iterations of M17432575 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 4 minutes 50 seconds - 1 errors, 0 warnings.
Execution halted.
Test 1, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.
Test 2, 4500 Lucas-Lehmer iterations of M17432577 using 1024K FFT length.
Test 3, 4500 Lucas-Lehmer iterations of M17432575 using 1024K FFT length.
Torture Test ran 4 minutes 50 seconds - 0 errors, 0 warnings.
Execution halted.
1) sometimes when I boot the computer for the first time that day, the computer would load but the monitor would act like no signal is recieved. This happened a couple of times, I've reseated my vid card. Its has since happened once again but been behaving for the last couple of days.
Here goes. 1. What is the purpose of lowering your multiplier from 9 to 8? With a higher FSB you will get higher speed? With a lower multiplier, you have to raise FSB that much higher to get to same speed. What are the advantages of changing from 9 to 8? What am I missing? I am currently at 3ghz with a 9 x 333, 1.375v. 31c on Hyper XT cooling on a e-6600, Giga rev. 3.3. Corsair XMS 4-4-4-12 memory.
Test 3, 4500 Lucas-Lehmer iterations of M17432575 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 4 minutes 50 seconds - 1 errors, 0 warnings.
Execution halted.
Test 1, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.
Test 2, 4500 Lucas-Lehmer iterations of M17432577 using 1024K FFT length.
Test 3, 4500 Lucas-Lehmer iterations of M17432575 using 1024K FFT length.
Torture Test ran 4 minutes 50 seconds - 0 errors, 0 warnings.
Execution halted.
Thanks for this amazing thread but does anyone have a guide on how to set up RAID. I'm a total noob and have no clue how to do it.
Thank you soooooooooo much for this thread. This is so amazing for noobs like me who have never overclocked before! Will you be adding more to this thread is is this all that I will have to know?
Ok I will bite, but please tell me what kind of raid you wish to use first please so I can go right to the point.
If you did not install the Raid/AHCI drivers (called the F6 preinstall drivers on Gigabytes site) during windows install we might be in for a bumpy ride but beleive we can still do it.
Also be aware that to properly do raid you should use drives designed for raid although its not absolutlely necessary i.e WD RE series of drives instead of the SE series but I digress. Be aware that a 2 drive raid 0 with nothing else doubles your chance of loosing ALL YOUR DATA due to a drive failure.
Tell me your OS, and the desired raid configuration,
I hope to start working on it again, but a bit slower, finish section on taking the memory OC info and using it to overclock the CPU in a rational method. ..Raid setup. Then basic updates and repost all in one bunch in proper order. LOL I dont know if this is all you have to know cause I dont know if its is all I have to know. You know ?
Yes! Yes! Yes!
Thanks a lot. I'm thinking raid 0 and in case you needed to know, I'm planning to run vista. Thanks again!
okie dokie, give me a day or two to write it up but do be sure to load the F6 preinstall driver found on gigabytes web site. Actually if you do that you will be in great shape its pretty easy as there is a menu when you boot that allows you to add drives to make the arrary etc. its all in the manual but I will do a quick quide.
Just a note here: I got some 6-32 nylon screws from Home Depot for my DS3 (2.0) yesterday. They did not fit through my holes. I got 4-40's instead and they work like a charm. If you cannot find #4 nylon washers, you can use the #6 ones on the #4 screws.I suggest replacing the push-pins with 6-32 nylon screws washers and nuts found at Lowe's in the specialty hardware drawers.
Just a note here: I got some 6-32 nylon screws from Home Depot for my DS3 (2.0) yesterday. They did not fit through my holes. I got 4-40's instead and they work like a charm. If you cannot find #4 nylon washers, you can use the #6 ones on the #4 screws.
Thanks for this excellent guide, Bill.
BTW, what were your temps like at 400 x 8? What HSF were you using?
Possibly. You may have gotten an E6600 that could only do 3.2Ghz.
Possibly. You may have gotten an E6600 that could only do 3.2Ghz.
That's still good isn't it. That's a 30% increase (faster than an X6800 at 25% the price)
I dont Post. i hear one beep, but i get nothing on the screen, i clear the CMOS, still nothing, I detach all usb, and use 1 stick of ram, still nothing. I just get 1 beep. any ideas? I change vid cards, still nothing on monitor, remove everything, detached power, reseated CPU, clear CMOS, keep just 1 stick of ram, try again.. still nothing. just one beep, then after a minute a single beep, fan spins faster hd cycles, but still nothing on screen- help guys? demmit, i should stayed put at 400x8, i was trying to go 400x9. when this happened.
I am curious is this guide good to go by for a DFI P965-S MB? I am thinking of trying some Overclocking with my new E6600 once I break it in.
Thanks Bill and Danny and everyone for the input, overclocking is a journey and a fun experiment. I am wondering though if my no POST is either, mobo, ram, or cpu, I'll find parts to check..hmm the 1 Beep is good actually, my best guess, and thats all it is, a guess, is that the cpu cant do 9x400, it is posting and then rebooting trying to reset itself to defaults but not being able to for some reason. Clearing the cmos should have got you out of the problem. But it didnt !!! The only thing I can suggest is try clearing the cmos again, even take the battery out and when done, let it cycle at least 5 times. Pray, if it does not come back you might have to RMA it. If it has a floppy you might see if the bios is scrambled and feed it a floppy with a bios file on it in hopes the boot block loader will sense the floppy and reload a bios.