1.7v is too high no matter what your cooling method is. Temporary is fine for benchmarking, but it's not good to run that chip at 1.7v for extended periods.Originally Posted by kempez815
1.7v is too high no matter what your cooling method is. Temporary is fine for benchmarking, but it's not good to run that chip at 1.7v for extended periods.Originally Posted by kempez815
And what was i doing? Benchmarking (well testing) now is anyone goign to tell me if i am correct about how to test how OC friendly my RAM is?Originally Posted by StormPC
(\__/)
(='.'=)
(")_(")
Memtest86+ tests 5 and 8 (at least 5 loops of each)
Then SuperPI 32mil, then maybe sandra and man I can't remember the name of the other one that I use a lot
Also generally playing games is a good indication
i find playing strategy games is good for testing ram stability.
When i had a dodgy stick of BH6 (and i mean super dodgy) it would play CSS for any period upto an hour before crashing (typical 30-45mins) but homeworld 2 would crash within about 5-10 mins.
Checking how far your ram will overclock just means putting your CPU multi to something ridiculously low such as 5 and upping the HTT until it will no longer work, you'll most likely hit your RAM barrier before your mobo barrier as DFI are just legendary for high HTT's.
I dont think you guys are getting what i mean:
Is this how i overclock including the ram, and therefore see how far my RAM will go without errors?
Take the HTT to 215 and the the memory mhz to auto, then it would automatically match the HTT and so would be 1:1 right? Then if i went faster that the ram could go then it would then start to get errors on memtest and super pi?
EDIT: Just saw what DW said, should i take it down to 5x or should i keep it at 10x cause thats what i did for testing the cpu?
(\__/)
(='.'=)
(")_(")
Read, smartass!Originally Posted by nvening
http://www.xtremesystems.org/forums/...verclock+guide
Basically, find your HTT and CPU limits and run them at the speed you like. Turn the DDR volts up as high as your motherboard will allow. Don't run your CPU volts over 1.55 on air. Set the system to boot from a floppy and boot memtest. If it completes a pass, raise the overclock. Keep going until it fails. Then back it down until a couple MHz from there.
A couple of things to remember:
Run the tightest timings possible. Also, only use a 1T command rate. You have good memory so it should do 1T to a pretty high speed. I like to run my TCCD at 2.5-3-3-8 1T at 276MHz x 2 (DDR552) at 2.9v. Gets great framerates at this speed, and it's 100% stable.
One problem, i havnet updated my system (will do know) and if you read smartass my first post i am running geil value 2 gb so i am not aiming high but would hope to get 218 (same as a 4000+) stable.
(\__/)
(='.'=)
(")_(")
There are currently 1 users browsing this thread. (0 members and 1 guests)