whadda i need to run for 1:1 ?![]()
-
-
Last edited by a moderator: May 7, 2015
-
-
i could do it in Ntune .....
So mandrake i should set my Mem to 1066
Imma try it -
not likely -
-
If you increase your FSB in ntune the divisor will stay the same so (99% sure...)... You need to use 1600 FSB but in BIOS
-
This is how my old Quadcore destkop used to run Linked and synced 1600 fsb 800 ram. had total stability this way only.
-
cookinwitdiesel Retired Bencher
@Quadzilla
That would be with DDR2 ram. The number reported in CPU-Z will be same for DDR2 and DDR3 but for DDR3 just multiple it by 2 again to get the actual RAM frequency
This is that 1:1 argument I was trying to make last week.
FSB: DDR2: DDR3
1066:533:1066
1333:667:1333
1600:800:1600
I am pretty sure these are the right values for "linked" at those FSB's -
No it's not scook... I already explained 3 times.
DDR-3 and DDR-2 are both dual pumped. -
cookinwitdiesel Retired Bencher
That is why I referred to what CPU-Z will report vs what the ram actually runs at (for a given FSB). Them both being dual pumped is what is represented by CPU-Z reporting the ram frequencies as the same isn't it?
I am just pointing out that at a given FSB, DDR3 will run twice the speed of DDR2 (while I think what you were saying is that DDR3 can run at same speed as DDR2 with only half the FSB = same thing? just different wording)
(sorry if this double posts.....NBR is NOT doing well today....server wise) -
CPU-Z reports the right clock and you don't need to do anything.
DDR-3 533 would be 1:1 with 1066 FSB just as DDR-2 is.
DDR-3 have twice the Bus speed but the modules have less clock compared with DDR-2 so basically it's the same -
cookinwitdiesel Retired Bencher
I see, a little confusing, but ok
As you can see, I am still trying to understand this haha -
-
What?, lol!
-
What? What?
-
Tests were not encouraging. I used OCCT and the Crysis benchmark to test. Both these tests seem to fail quickly if it doesn't like the CPU OC.
Keep in mind my default multiplier is 11.5.
Clock: 3547.5 | Mult: 11x | FSB: 1290 | Memory: 1032 | Divisor: 4:5
-no boot (OC failed error)
Clock: 3547.5 | Mult: 11x | FSB: 1290 | Memory: 860 | Divisor: 2:3
-BSOD during boot
Clock: 3553 | Mult: 11x | FSB: 1292 | Memory: 807.5 | Divisor: 5:8
-no ".5" option rounded down. BSOD during boot
Clock: 3547.75 | Mult: 11.5x | FSB: 1234 | Memory: 987.2 (used 987) | Divisor: 4:5
-Booted. OCCT failed immediately, Crysis failed immediately.
Clock: 3550.625 | Mult: 11.5x | FSB: 1235 | Memory: 988 | Divisor: 4:5
-Booted. OCCT failed immediately, Crysis failed immediately.
Clock: 3553.5 | Mult: 11.5x | FSB: 1236 | Memory: 824 | Divisor: 2:3
-Booted. OCCT failed immediately, Crysis failed immediately.
Clock: 3549 | Mult: 12x | FSB: 1183 | Memory: 946.4 (used 946) | Divisor: 4:5
-BSOD during boot
Clock: 3552 | Mult: 12x | FSB: 1184 | Memory: 947.2 (947 used) | Divisor: 4:5
-BSOD during boot
Clock: 3555 | Mult: 12x | FSB: 1185 | Memory: 948 | Divisor: 4:5
-BSOD during boot
Clock: 3546.875 | Mult: 12.5x | FSB: 1135 | Memory: 908 | Divisor: 4:5
-BSOD during boot
Clock: 3552.25 | Mult: 13x | FSB: 1093 | Memory: 874.4 | Divisor: 4:5
-BSOD during boot
Clock: 3550.5 | Mult: 13.5x | FSB: 1052 | Memory: 1315 | Divisor: 5:4
-BSOD during boot
Clock: 3553.875 | Mult: 13.5x | FSB: 1053 | Memory: 842.4 (842 used) | Divisor: 4:5
-BSOD during boot
Clock: 3545.5 | Mult: 14x | FSB: 1013 | Memory: 810.4 (810 used)| Divisor: 4:5
-BSOD during boot
Clock: 3549 | Mult: 14x | FSB: 1014 | Memory: 811.2 (811 used) | Divisor: 4:5
-BSOD during boot
Clock: 3549 | Mult: 14x | FSB: 1014 | Memory: 1267.5 (1268 used) | Divisor: 5:4
-BSOD during boot
Clock: 3552.5 | Mult: 14x | FSB: 1015 | Memory: 812 | Divisor: 4:5
-BSOD during boot
Clock: 3545.25 | Mult: 14.5x | FSB: 978 | Memory: 1222.5 (1222 used)| Divisor: 5:4
-BSOD during boot
Clock: 3552.5 | Mult: 14.5x | FSB: 980 | Memory: 1225 | Divisor: 5:4
-BSOD during boot
Clock: 3547.5 | Mult: 15x | FSB: 946 | Memory: 1182.5 (used 1183)| Divisor: 5:4
-BSOD during boot
Clock: 3555 | Mult: 15x | FSB: 948 | Memory: 1185 | Divisor: 5:4
-BSOD during boot
Clock: 3549.5 | Mult: 15.5x | FSB: 916 | Memory: 1145 | Divisor: 5:4
-BSOD during boot
Clock: 3548 | Mult: 16x | FSB: 887 | Memory: 1330.5 (used 1331) | Divisor: 3:2
-BSOD during boot
Clock: 3552 | Mult: 16x | FSB: 888 | Memory: 1110 | Divisor: 5:4
-BSOD during boot
Clock: 3552 | Mult: 16x | FSB: 888 | Memory: 1332 | Divisor: 3:2
-BSOD during boot -
Looks like the processor doesn't like non default multiplier
.
I'm wondering about more options... It may take some time
EDIT: Can you try 3550 with 1:2 ? (11.5x multiplier). Just to check the difference. -
As soon as I get my QX9300 I should be able to see if it a limitation of the proc. BTW the tests were done with the 1333 memory.
-
I'm curious if the more stability was due the lower memory clock or due the multiplier. Pretty interesting anyway
-
I'll try 3550 in a little bit. I know when I have 3.47 w/1:2 OCCT fails after 20 minutes and Crysis doesn't fail. Regular gaming and benchmarking seem to be stable at that speed also.
-
At 3550 w/ 1:2 Boots fine, OCCT fails almost immediately (lasted a few seconds longer) and Crysis fails immediately.
-
hi
my cpu runs now on 3.06Ghz at 11.5x multiplier ddr3 at 1333mhz FSB 1066mhz
if i set in bios on unlinkt ddr3 go on 1313mhz ?? why is that
and even if i set FSB 1070ghz with multiplier of 11.5x cpu stil be 3.06ghz
so what am doing wrong ? i wand to get cpu on 3.1Ghz because multiplier cant go higher or i get BSODso i hope to get last mhz out my cpu with FSB
hope you ppl can help me -
1070 x 11.5 is 3076 so... Have you tried 1080? 3105.
-
i have try it onlye it dont work
i set clock mode on unlinked in bios en set FSB on 1080mhz and cpu stil 3.06ghz -
Where are you reading 3.06? The bios? Did you try seeing what reading you get from cpu-z?
-
i got him now on 3.1ghz with FBS 1070 and DDR on 1350mhz ( CPU-z ) -
1350 DRAM speed?
-
yep 2x 675mhz in CPU-z
run now burn CPU progam and cpu is now 66c after 30min -
1350... r u using NST right? lol
-
You can't even do that in NST. I have no idea how he's doing it.
-
in bios i can set in over clock > clock mode > unlinked then i can set FSB and can set Mhz of DDR my DDR runs now on 1396Mgz and cpu 11.5x 1085FSB 3.12Ghz
-
Yeah but the max in bios is 1333 lol
-
yea i have tried to go higher ...
-
MOOOOO
the new BIOS supports the ram to run higher then 1333 but not the FSB -
Damn aw...
-
evidentally my RAM can't handle 1500 on the ram .....
but it can handle 1400 -
DDR-2/3 don't like overclock...
Good old days of DDR-1 glory. I miss my OCZ REV2 @ DDR-1 780
-
well my caps lock was blinking as my error code which is the same as when i left my CPU unlock (weird)
the error codes on dell's site are messed up
anyway Mandrake needs to try to 1333 ram to see what it can do -
-
they don't want to allow to much overclocking ....
-
-
why ?
the new BIOS OC'd quads better -
For testing comparisons with the x9100.
-
O ok well update soon
-
K well i think someone deleted my thread about BIOS numbers and other system numbers so ill post here. Id like if someone could post max setting for all configurations of m17x. like with 1333mhz ram with a p8600. and any other lil tweaks or anything that people know. I cant do math. im a 2nd year college student and im still in elementary algebra
... sooo if we could save that math and just have timings/and or basically answers then im sure alot of people would be happy. Thankss
-
i already ansered you
just run it @ 1333
1333
simple as that -
if i go to 1400mm DDR my CAS Latency gets very high is there way to set CAS Latency in bios ? dont wand to us ntunes
-
No.
1 2 3 4 5 1000 vai pra... -
another impressive feat.
11-10-10-26
M17x - FSB:DRAM Ratio & CAS Latency
Discussion in 'Alienware' started by Mandrake, Jul 27, 2009.