The memory dividers are in the cell menu under Dram configuration. 200 = 1:1 166=5:6 etc etcQuote:
Originally Posted by BobTheDinosaur
http://www.rhcf.com/sisubb/ultimateb...pic/21/87.html
Printable View
The memory dividers are in the cell menu under Dram configuration. 200 = 1:1 166=5:6 etc etcQuote:
Originally Posted by BobTheDinosaur
http://www.rhcf.com/sisubb/ultimateb...pic/21/87.html
Hi all, I have a question:
In MemTest 3.2 (cdrom ...) , my chipset is detected as nForce3 250 ??
It's normal ? sure I have the socket 939 msi neo2 platinum ...
thanks for secure me :bounce:
Goodbye.
thanks side-effect
soooo 200 is 1:1
166 5:6
and the rest? (sorry i'm unfamiliar with mem dividers)
thanks!
Dont use 1.52 mod bios with a san diego or venice it doesnt work at all need to hotflash now :)
Best to use the official 1.8 for venice / sandiego IMO.
200 = 1:1
166 = 5:6
133 = 2:3
100 = 1:2
You can also get the 183 divider (9:10) using A64 Tweaker :)
changing the divider will result in tighter RAM timing which are not accessible thru BIOS settings.... e.g TRC TRFC TWTR... that is why some rams out there won't be able to run the K8N neo2 divider.... e.g like my Corsair PC3200LL which i bought 2+ years ago...
A64 is the way to go.... until MSI do something about locking the RAM timing regardless of dividers.... (why didn't they do that in the first place?.. )
I run my Venice 3000+ @ 9x311 for 24/7 usage @ 1.53v :)
I use 2x256 BH5 and the 166 divider, ~255 is the result.
No problems there, however when I pop in my UTT 2x512 sticks (they can do 260, I've tested them) then I cannot run a HTT over 270... :( and it doesn't matter if I use a divider or what :(
It must be the MSI board, since an acquaintance of mine can run his Venice @ over 300 HTT with the 166 divider with Mushkin Redline sticks (2x512) with his DFI...
Anyone else encountered this problem?
Might be a problem as mentioned above with the memory timings. If you can boot into windows ok using the 166 divider (or which ever divider you need to get your memory under 260mhz, since that is its max speed), use A64 Tweaker to set the 2nd and 3rd values to 12 and 14 respectively (Trc & Trfc)...then you might be able to run the memory at an HTT of over 270. :)
Maybe a modded bios could help me ;) *hint* lol :D
I'm sure a bios guru could mod those timings for me? :thumbsup:
I'm goning to by a venice can i use the 1.36b bios or do I need a later one ?
From what i heard the 1.36 is the earliest bios that will work with a san diego. Bios files i have tried and work are 1.36mod 1.40 official 1.5xmod 1.8mod 1.8 official.Quote:
Originally Posted by Jacke2k
The only bios i tried that didnt work was 1.52mod and i assume that it maybe uses an earlier romsip from pre 1.36 and thats why it didnt work. The info on the beta and mod bios changes is really bad and a real shock when coming from a DFI motherboard where so many good bios files were modded and every change listed.
I dont think its possible to unlock the extra memory timing in the bios as in another thread Tictac took a look and said it was locked. Tictac knows what hes talking about so i guess its a64 tweaker for us. Or we could pressure msi to release a better bios.
let's get down to a petition for our K8N Neo2 plat !!!!!!
Hello
I have gor realy probems whits ram divider... If i set CPU 300*9 and ram 100 is fine, but If i set CPU 300*9 and ram 133 or 166 motherboard don't boot.
If i chage this settings in windows whith A64 Tweaker my system freeze and restart...
I am using ddr booster and TwinMos Speed Premium 1AA4T...
What's wrong?
I try 1.8mod, 136mod....
tnx
You most likely can't use the 133 or 166 divider due to the tighter timings they use. Which version of A64 Tweaker are you using? I'd recommend 0.31 for stability.
If you haven't already tried, boot into windows using the 100 divider in the bios, and then change the memclock to the divider you'd like, and Trc and Trfc timings to 12 and 14 respectively. Then try saving those changes and apply them every time windows starts. Make sure the basic timings are set correctly for what you want in the bios, so you don't have to change them in windows. Also, what voltage are you giving your memory?
ummmm what's a ddr booster?
There has been many posts here about the tighter timings causing the post problems with dividers on venice/san diego but it just isnt true. At least its not settings that Athlon 64 tweaker can change. I have a custom startup profile for my timings and the ram just wont work well with 166 or 183 divider but works fine in 1:1.
I think its the changes in the memory controller on the cpu that is causing this and a better bios will fix it hopefully....
well i think it is not true .. ( i meant what you had said)Quote:
Originally Posted by sideeffect
if u r one of them who can run 133 and 166 divider... run them and see what stock timing they put in A64 tweaker...
trc and trfc are at very very tight timing at 133 166 divider... just changing them will allow the most ram to run....
Yes I know they run a tighter stock timing and i changed them back and tried all other series of timings. 166 divider wont run my memory above 215 where as 1:1 goes all the way up to 265.Quote:
Originally Posted by harpyboy
do u mean that with 166 divider... no matter wat timing u change in A64.. u can't go above 215mhz ?
Hmm, whenever I use the EXACT same a64 tweaker timings for 1:1 & the 166, my ram runs EXACTLY the same.Quote:
Originally Posted by sideeffect
so how sure it is actually that there are timings which A64 tweaker can't see ?
actually im alreadi quite sure that all in A64T is all tat is there....
On a slightly different note, i've just sent off a request to MSI to add these "advanced timings" into the bios, so they can be adjusted in the bios directly rather than from windows using A64 Tweaker. Since these timings are adjustable in windows, it must be possible to adjust them from the bios!
Of course, i don't expect anything to be done about it from my single request. But what if enough people were to put there names forward for such a request? Would that be a worthwhile effort or a waste of time? To my mind, it's the advanced timings available in the DFI nforce3/4 boards that set them apart from other similar boards. If the Neo2 were to have these options available also, it might be just as OCable as the DFI itself! *Wishful thinking may be, but you know what i'm getting at...* ;)
Agreed
i doubt MSI will do anything a customer requests
i contacted them about this high-pitched noise this mobo makes (which i discovered thanks to these forums is caused by unpainted coils behind the network and usb ports) and they said, "your PSU and USB dongle are experiencing EM interference, get a new PSU and call us in the morning"
so anyway enuff ranting
i don't know squat about memory timings, could someone educate me?
what's tight timings and what's relaxed timings? i run my ram at 166 while i oc my cpu cos my ram won't oc at all so i can't run it at 200, maybe if i knew how to relax the timings i could get it to oc, also, when i set my ram to 166 i can still change the timings in my bios v1.8 (not that i know what to change them too)
help!
Ok, basically the bigger the numbers, the more relaxed the timing, the slower the performance of the memory. This means that if you set the basic memory timings in the bios to 2.0-2-2-5 (tight timings) your memory will perform faster than say at 2.5-3-3-7 (looser timings) when at the same clockspeed. These basic timings are the ones that can be changed from within the Neo2 bios now.
However, the tighter the timings used, the less room there is to increase the speed of the memory, so it's about getting the best compromise between high raw speed (in mhz) and timings that are not so loose that you will lose any performance gained by increasing the raw speed.
Below is a screenshot from the windows utility "A64 Tweaker" which enables you to change other memory timings which aren't shown in the bios. Having access to this timings can help to improve your memory's stability when overclocking. The problem is that since on this MSI board you cannot change these timings until you enter windows, you might not be able to get the stability that you otherwise could if these timings could be set directly from the bios. That is what I, and many others, would like to see implemented into a future Neo2 bios...getting it implemented on the other hand, is an entirely different matter! ;)
On the pic below, the numbers / timings i've (tried) to circle in red are those which are given in the bios as the moment, whereas the rest aren't. Those are the timings it would be useful to change within the bios. :)