timi Posted January 11, 2008 Share Posted January 11, 2008 Hi there, I recently built a new shuttle pc using the SN68PTG5 and need some help setting my memory. I got Corsair 2GB DDR2 XMS2-6400C5 TwinX thats meant to be set at 5-5-5-12-T1 at 1.9v. However it didnt default to this when i built the computer so i need to know what options to set. This is what it looks in the bios. Timing Mode Ø The Choice: Auto or MaxMemClk. Memory Clock value or Limi Setting platform Memclock. DDR800 DDRII Timing Item Enabled TwTr Command Delay Ø The Choice: 1~3 bus clocks. Set at 3 Trfc0 for DIMM0 Ø The Choice: 75ns, 105ns, 127.5ns, 195ns, or 327.5ns. Set at 75 Trfc1 for DIMM1 Ø The Choice: 75ns, 105ns, 127.5ns, 195ns, or 327.5ns. Set at 75 (Twr) Write Recovery Time Ø The Choice: 3~6 bus clocks. Set at 6 (Trtp) Precharge Time Ø The Choice: 2~3 clocks. Set at 3 (Trc) Row Cycle Time Ø The Choice: 11~26 bus clocks. Set at 26 (Trcd)RAS to CAS R/W Delay Ø The Choice: 3~6 clocks. Set at 6 (Trrd)RAS to RAS Delay Ø The Choice: 2~5 clocks. Set at 5 (Trp)Row Precharge Time Ø The Choice: 3~6 clocks. Set at 6 (Tras)Minimum RAS Active Time Ø The Choice: 5~18 bus clocks. Set at 18 I have no idea what to change to make it run faster they are what it is currently set at and the options. also the voltage is at default which is lower than 1.9. Please help me with what to change. Thanks Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted January 11, 2008 Corsair Employee Share Posted January 11, 2008 The tested settings are all that should be manually set any setting not listed should be left or set to BIOS default or Auto! Link to comment Share on other sites More sharing options...
timi Posted January 12, 2008 Author Share Posted January 12, 2008 thanks. it looks like shuttle has left off the setting to change ur CAS latency lol so looks like i have to wait for a bios update till i can run my memory how i want :( i wont be damaging it running at different speeds? i've checked on some program nd it seems to say the CAS is at 3 3.5 but i dont think this ram could go that low. So the CAS is really low and the other settings are really high. Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted January 14, 2008 Corsair Employee Share Posted January 14, 2008 These are all you should have to set, leave all other at default. Memory Voltage: 2.0 Volts Memory Clock Limit Platform Memclock; DDR800 DDRII Timing Item Enabled (Trc) Row Cycle Time: :24 (Trcd)RAS to CAS R/W Delay: 5 (Trp)Row Precharge Time; 5 (Tras)Minimum RAS Active Time: 15 Link to comment Share on other sites More sharing options...
timi Posted January 16, 2008 Author Share Posted January 16, 2008 I have tryed and it won't post. It's fine setting it to 2.0v and i can set it to 800 but if i change anything in the other DDR2 Timing item settings even by 1 digit it wont post. Any ideas? Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted January 16, 2008 Corsair Employee Share Posted January 16, 2008 Test the modules one at a time and see if its just one module causing the problem. Link to comment Share on other sites More sharing options...
timi Posted January 16, 2008 Author Share Posted January 16, 2008 do u not think it could be because the bios/motherboard is forcing the cas latency to be a to low setting? (they missed the setting off in the bios options) it is a known problem with these shuttles and they are slowly releasing new bios's for the ones that need it but mine hasnt been released yet. Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted January 16, 2008 Corsair Employee Share Posted January 16, 2008 Yes it could be and Shuttle has been notorious for that. Link to comment Share on other sites More sharing options...
gnuisnotunix Posted March 15, 2008 Share Posted March 15, 2008 Timi, did you try with the new BIOS? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.