Switch[uK] Starts Clocking

[Switch[uK]]

Ok, thanks guys. Ill give it a go. Just so i know though; how would I know it was the NB? As appose to something else?

[DeImOs]

When the FSB raises the NB can "suffer" from it.. just try raising the NB or the CPU voltage..

To be sure the instability is caused by the CPU or NB set the DRAM speed to the minimun so they wont go over the rated 1600Mhz.

[Switch[uK]]

Ok so here is an updated version of my bios as it currently looks:

DFI UT X48-T3RS LanParty
CPU Feature
- Thermal Management Control: Enabled
- PPM(EIST) Mode: Enabled
- Limit CPUID MaxVal: Disabled
- CIE Function: Auto
- Execute Disable Bit: Enabled
- Virtualization Technology: Enabled
- Core Multi-Processing: Enabled

Exist Setup Shutdown: Mode 2
Shutdown after AC Loss: Disabled
O.C. Fail retry Counter: 0
CPU Clock Ratio: 9.5x
CPU N/2 ratio: Enabled
Target CPU Clock: 3163MHz
CPU Clock: 400MHz
Boot Up Clock: Auto
CPU Clock Amplitude: 800mV
CPU Clock0 Skew: 0ps
CPU Clock1 Skew: 0ps
DRAM Speed: 400/1600
Target DRAM Speed:DDR3 1600
PCIE Clock: 100mhz
PCIE Slot Config: 1X 1X

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled

Voltage Settings
CPU VID Control:  1.25000V
CPU VID Special Add Limit: Disabled
CPU VID Special Add: 102.12%
DRAM Voltage Control: 1.803V
SB Core/CPU PLL Voltage: 1.510V
NB Core Voltage: 1.304V
CPU VTT Voltage: 1.100V
Vcore Droop Control: Enabled
Clockgen Voltage Control: 3.45v
GTL+ Buffers Strength: Strong
Host Slew Rate: Weak
x MCH RON Offset Value: Could Not Find
x MCH RTT   Offset Value: Could Not Find
x MCH Slew Rate Offset Value: Could Not Find
x MCH VREF 1 Value: Could Not Find
x MCH VREF 2 Value: Could Not Find
x MCH VREF 3 Value: Could Not Find
GTL REF Voltage Control: Disable
x CPU GTL1/3 REF Volt: 110
x CPU GTL 0/2 REF Volt: 110
x North Bridge GTL REF Volt: 110

 CPU Core Voltage: 1.21V
 DRAM      Voltage: 1.80V
 NB Core   Voltage: 1.29V
 CPU VTT  Voltage: 1.12V

DRAM Timing
- Enhance Data transmitting: AUTO
- Enhance Addressing: AUTO
- T2 Dispatch: Auto

Clock Setting Fine Delay: Press Enter

CAS Latency Time (tCL): 9
RAS# to CAS# Delay (tRCD): 9
RAS# Precharge (tRP): 9
Precharge Delay (tRAS): 24
All Precharge to Act: AUTO
REF to ACT Delay (tRFC): AUTO
Performance LVL (Read Delay): AUTO
Read delay phase adjust: Press Enter
MCH ODT Latency: AUTO
Write to PRE Delay (tWR): AUTO
Rank Write to Read (tWTR): AUTO
ACT to ACT Delay (tRRD): AUTO
Read to Write Delay (tRDWR): AUTO
Ranks Write to Write (tWRWR): AUTO
Ranks Read to Read (tRDRD): AUTO
Ranks Write to Read (tWRRD): AUTO
Read CAS# Precharge (tRTP): AUTO
ALL PRE to Refresh: AUTO 

DRAM CLK Driving Strength: Could Not Find
DRAM Data Driving Strength: Could Not Find
Ch1 DLL Default Skew Model: Could Not Find
Ch2 DLL Default Skew Model: Could Not Find

Fine Delay Step Degree: Could Not Find

DLL Mode: 0

Ch1 Clock Crossing Setting: AUTO
- DIMM 1 Clock fine delay: Current 462ps
- DIMM 2 Clock fine delay: Current 462ps
- DIMM 2 Control Fine Delay: Current 385ps
- DIMM 1 Control Fine Delay: Current 385ps
- Ch 1 Command fine delay: Current 238ps

Ch2 Clock Crossing Setting: AUTO
- DIMM 3 Clock fine delay: Current 646ps
- DIMM 4 Clock fine delay: Current 21ps
- DIMM 4 Control Fine Delay: Current 490ps
- DIMM 3 Control Fine Delay: Current 490ps
- Ch 2 Command fine delay: Current 259ps

Ch1Ch2 CommonClock Setting: Auto

Ch1 RDCAS GNT-Chip Delay: Auto
Ch1 WRCAS GNT-Chip Delay: Auto
Ch1 Command to CS Delay: Auto

Ch2 RDCAS GNT-Chip Delay: Auto
Ch2 WRCAS GNT-Chip Delay: Auto
Ch2 Command to CS Delay: Auto 

Common CMD to CS Delay: Auto

While i was typing this to you last time, I locked up. As you can see Ive tried to increase the NB voltage and the CPU VID now. When I logged back in I had an error message from my system registry saying:

One of the files containing the system's registry data had to be recovered by way of Log or alternate copy. The recovary was sucessful.

Anybody got an idea why thats happening?

Gonna go burn test this now but I'm not holding high hopes...

Switch[uK]

[Switch[uK]]

400 it is!

OCCT ran for 11mins to confirm but I am stable at the above settings at 400FSB. This means my ram is running nicely at 1600mhz as always intended. Gonna try for 425 next and if that doesnt work ill go to 410 then stage up in 10's till I become unstable again.

Results from OCCT can be seen here:



Thanks for the advice guys

1 (more) question that I do have is if i keep going up on my NB voltage will i need to get some sort of NB cooler. The DFI UT X48-T3RS does have a fairly sizable looking chunk of NB cooler with a heat pipe to a vast "flamefreezer" which sticks out of the back and my rear 100mm fan pushes air right through it. Is that gonna be enough?

Switch[uK]

[DeImOs]

I dont think the NB will give you heating problems... and you can always increase a bit the case airflow to improve chipset cooling.

[Kelainefes]

You can get a HR05 IFX SLI or a Xigmatek Porter if you want to, but at 400 FSB it's not needed at all. If you are shooting for 500 it might make a difference, expecially if you have 8GB of memory.

[Switch[uK]]

I'm also having problems at the moment with corrupting registry files. In addition to the above mentioned error message on windows log in i'm getting an annoying little windows "reminder" to tell me that C:/$MFT is corrupted and to run chkdsk. I already did and the error is still there. Little help.

[Kelainefes]

You probably need to manually increase the tRFC of your memory. Use Everest or Memset to find out the current value. You also need to find out the suggested value for your sticks, but I think it will be between 70 and 80.
You may need a little bit of NB voltage but start with the tRFC.
I don't know how to solve that problem if chkdisk does not work, but the above instructions should prevent further damage.

[Switch[uK]]

Registry problem sloved. I had a virus. Plus I have avast! So the problem is seemingly over. Thats what you get for downloading mirrored content from northkorean bit torrents...

Anyhoo, back to clocking. As pointed out i need to alter my tRFC or as it is also know my REF to ACT Delay.

However, I cant seem to see anywhere on the datasheet what the recommended tRFC is for my DIMMS.

http://www.corsair.com/_datasheets/TW3X4G1600C9DHX.pdf

I know the numbers on DIMMS are something to do with latencys but which number corresponds to what I am trying to alter?

Little help (again) guys...

[Kelainefes]

Ask on the Corsair forums if you wanna have a definitive answer, but since the problem was a virus you can leave things as they are for now.
A tight tRFC is often cause of disk corruption, that's why I thought that was the issue.

If you wanna push your memories beyond the stock 1600 MHz, loosening the tRFC should help keep stability without increasing the voltage too much.