**Official DFI LanParty UT P35-T2R Review/Overclock/Guide Thread**

[jimmyz]

Thanks jimmyz what if i also change the ratio to above 1:1? would it work better?

yeah, but then you got to loosen timings most likely. or up the volts, I would just tighten them up as much as possible and keep 1:1.

[kitfit1]

Guys i need some inputs here...how can i do a finer tweak with this?

You could also drop your multi to 8, and up your cpu clock to 530. Check the link in my sig.

[C-N]

vCore is already 1.6v, VTT 1.6v, NB 1.65v, GTL's 118/118/121. Any suggestions please? Thanks

edit: just noticed you are at 1x pci-e width ? maybe adjust the fsb vtt a little higher, cpu vtt is a little low in relation also, might help.

I had a similar issue with my PCI-E dropping to 1x when I used 1.65v + on the NB with my PCI-E overclocked to 110-115mhz. I found either lower the NB voltage or lower the PCI-E frequency & the link width will return to 16x

CN

[emoners]

ah ok... THANKS jimmyz, kitfit1 & C-N!

[ooeric]

got board today. dont understand... C1 error
no post. nothing.

plugged in 4 different ram
ballistix (new)
corsair xms2 (used on non OC pc)
533 1gb kingmax (spare)
533 256 corsair (used to test machines, working)

clear cmos who know how many times already.
ezclear the same

mem slots? tried all slots all arrangements..
still dont understand.. everything else works fine

[jimmyz]

got board today. dont understand... C1 error
no post. nothing.

plugged in 4 different ram
ballistix (new)
corsair xms2 (used on non OC pc)
533 1gb kingmax (spare)
533 256 corsair (used to test machines, working)

clear cmos who know how many times already.
ezclear the same

mem slots? tried all slots all arrangements..
still dont understand.. everything else works fine

533's probably will not boot, It's not supported by the board. try 1 stick of your new ballistix. turn on psu wait ten seconds, boot , if no boot try turning of psu again till the light goes out then repeat. there are several different ways people use when confronted with c-1 that method generally works for me. if you don't get a boot try different sticks one at a time.
good luck and keep us posted.


ps: when or if it does boot, get into bios and raise the v-dimm to 2.0 and the memory should be able to boot normally then.

[ooeric]

533's probably will not boot, It's not supported by the board. try 1 stick of your new ballistix. turn on psu wait ten seconds, boot , if no boot try turning of psu again till the light goes out then repeat. there are several different ways people use when confronted with c-1 that method generally works for me. if you don't get a boot try different sticks one at a time.
good luck and keep us posted.


ps: when or if it does boot, get into bios and raise the v-dimm to 2.0 and the memory should be able to boot normally then.

ill give that a whirl.
i have 4 sticks of ballistix anyways . lol




no go. tried about 30 times.

board has nothing on, no hdd no dvd no usb
only ps2 kb.

[cantankerous]

You have tried one stick at a time in each slot individually? Not a single stick in any slot will allow it to boot?

Try doing the EZ-Clear method by holding the reset and power button simultaneously for 5 slow seconds. Release them both then try and power up again.

[seamumc]

I was wondering if anyone else has experienced issues using Intel's AHCI or RAID modes with Vista?

RGone, on the DFI forums, gave me some help and I've apparently resolved my issues for the moment. I was experiencing performance issues that seemed to be disk related, there's a good description of the kind of issues I'm seeing at this site: http://forum.videohelp.com/topic339459.html

According to Intel's explanation the issue is, from their point of view, Low Power Management support in Vista. By default Vista will take advantage of LPM features, unfortunately many disk drives do not support LPM very well and the outcome for AHCI is that performance degrades. (Attempts to use RAID may fail.)

For now I have a clean install of Vista64 SP1 RC1 and I'm making a wild guess that by not installing the Intel INF drivers I'm avoiding the issue, and my performance is excellent and my event viewer is clean. My understanding is that INF files basically provide information to the OS that identifies the hardware and its capabilities to the OS. By not installing the INF drivers I'm forcing the OS to use generic, safe drivers that do not provide for the additional features available in the hardware, i.e. the LPM support. Without the INF drivers installed the only device not recognized by Vista is the SMBus.

Am I reading the situation correctly or am I just crazy? Has anyone else here had issues getting AHCI and/or RAID working on the ICH9R, or is everyone just using IDE Mode?

[seamumc]

Just flashed to new beta I just received from DFI, sorry but I dont really notice differences between bios, I just flash mostly to fix problems so cant answer if its better than previos or not....

its lpdc24 or something like that and heres the description:

1. Change ICH9R AHCI ROM

2. Pach for QX9650 radio issue

3. Adjust dram tfine item value

4. Add O.C fail item

This is the 12/24 beta bios.

I tried this BIOS in an attempt to address an issue I was having with AHCI in Vista. I could not perform a clean install of Vista with this BIOS, the install would crash, lock up, every time I attempted the installation. Went back to 11/07, glad I was able to, and installation went fine.

[ooeric]

You have tried one stick at a time in each slot individually? Not a single stick in any slot will allow it to boot?

Try doing the EZ-Clear method by holding the reset and power button simultaneously for 5 slow seconds. Release them both then try and power up again.

tried tried. . just dont understand.

[DoObs]

Looks like i will have one of these soon, selling my DFI P65-S,

Was either this one or a Blood Iron

[cantankerous]

tried tried. . just dont understand.

Very odd, usually doing the above will get the board to post at least once so that the bios can be entered and vdimm raised. Have you never been able to get it to post even a single time? the only thing left to do is try to exchange the board for another and see how you fare. Perhaps something is wrong with the board itself if you have exhausted all other options in troubleshooting it to work.

[shawn1998]

tried tried. . just dont understand.

He got this board from me over on the hard forums. I never had a single issue with this board, ever, so I am really confused as to what is going on. The only ram I ever ran in it was G-Skill DDR2-800, which was rated for 1.8 to 1.9 volts, and always ran it at it's default in the bios (1.85). I am guessing that the board is not liking the Ballistix at all, based on the 2.2vdc specs they have, but I don't understand why the Corsair aren't working. Unless, that is, they are rated at 2.1vdc like some of the XMS2 sets are.

As far as the 533 ram, that will not work at all on any P35 chipset mobo. Ooeric, you don't have any elcheapo DDR2-667/800ram you can get your hands on? I bet if you could get ahold of just one stick of it, you could get into the bios to up the voltage. Also, I have a spare bios chip for it that I got from Brother Esau (which I totally forgot about until a few minutes ago, so if somehow the bios is corrupt, I can send that out to you right away (for nothing) to help get this sorted out.

Shawn

[ooeric]

still trying .

not even 1 single boot into post.

using a cheap e6300 a got a longgg while back.

[mad_skills]

What is this 12/24 bios like? Anyone tried it?

[seamumc]

What is this 12/24 bios like? Anyone tried it?

In post 2814 I document that I could not install Vista64 with the 12/24 bios. I had random lock ups and only reached the screen for selecting the hard drive for installation once out of 5 attempts, so I couldn't even attempt to load Intel's latest AHCI/RAID drivers, which was the reason I was attempting to use the bios in the first place. I reverted back to the 11/07 bios and installation went fine.

I believe Cantankerous applied the bios to an existing setup, i.e. wasn't installing an OS from scratch, and saw no difference.

[Tancoll]

Guys i need some inputs here...how can i do a finer tweak with this?

vCore is already 1.6v, VTT 1.6v, NB 1.65v, GTL's 118/118/121. Any suggestions please? Thanks

My goal is to get 4.5 Ghz.... if that is possible on air

I need 1.7v under SS for 4.5GHz stable.

[C-N]

What is this 12/24 bios like? Anyone tried it?

I flashed my spare chip & gave 12/24 a real quick run with my e6850 @ 4GHz DDR 1200 CL5 , I didn't have any issues.

Here are the voltages/settings I used

>CPU Feature:
 
Thermal Management Control.......... - Disabled
PPM(EIST) Mode...................... - Disabled
Limit CPUID MaxVal.................. - Disabled
CIE Function........................ - Disabled
Execute Disable Bit................. - Disabled
Virtualization Technology........... - Disabled
Core Multi-Processing............... - Enabled
 
>DRAM Timing:
 
Enhance Data transmitting........... - Fast
Enhance Addressing.................. - Fast
T2 Dispatch......................... - Auto
 
>Clock Setting Fine Delay Press Enter:
 
Ch1 Clock Crossing Setting......... - More Aggressive
DIMM1 Clock Fine Delay............. - Current[?]
DIMM2 Clock Fine Delay............. - Current[?]
Ch1 ControlFine Delay.............. - Current[?]
Ch1 ControlFine Delay.............. - Current[?]
 
Ch2 Clock Crossing Setting......... - More Aggressive
DIMM3 Clock Fine Delay............. - Current[?]
DIMM4 Clock Fine Delay............. - Current[?]
Ch2 ControlFine Delay.............. - Current[?]
Ch2 ControlFine Delay.............. - Current[?]
 
Ch1 Ch2 Common Clock Setting....... - More Aggressive
 
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
 
CAS Latency Time (tCL).............. - 5
RAS# to CAS# Delay (tRCD)........... - 5
RAS# Precharge (tRP)................ - 5
Precharge Delay (tRAS).............. - 10
All Precharge to Act................ - 4
REF to ACT Delay (tRFC)............. - 26
Performance Level................... - 7
 
>Read delay phase adjust Press Enter:
 
Channel 1 Phase 0 Pull-In.......... - Auto
Channel 1 Phase 1 Pull-In.......... - Auto
Channel 1 Phase 2 Pull-In.......... - Auto
Channel 1 Phase 3 Pull-In.......... - Auto
Channel 1 Phase 4 Pull-In.......... - Auto
 
Channel 2 Phase 0 Pull-In.......... - Auto
Channel 2 Phase 1 Pull-In.......... - Auto
Channel 2 Phase 2 Pull-In.......... - Auto
Channel 2 Phase 3 Pull-In.......... - Auto
Channel 2 Phase 4 Pull-In.......... - Auto
 
MCH ODT Latency..................... - Auto
Write to PRE Delay (tWR)............ - 11
Rank Write to Read (tWTR)........... - 10
ACT to ACT Delay (tRRD)............. - 3
Read to Write Delay (tRDWR)......... - 8
Ranks Write to Write (tWRWR)........ - Auto
Ranks Read to Read (tRDRD).......... - Auto
Ranks Write to Read (tWRRD)......... - Auto
Read CAS# Precharge (tRTP).......... - 3
ALL PRE to Refresh.................. - 4
 
>Voltage Settings:
 
CPU VID Control..................... - 1.52500v
CPU VID Special Add................. - Auto
DRAM Voltage Control................ - 2.27v
SB 1.05V Voltage.................... - 1.150v
SB Core/CPU PLL Voltage............. - 1.75v
NB Core Voltage..................... - 1.45v
CPU VTT Voltage..................... - 1.35v
Vcore Droop Control................. - Disabled
Clockgen Voltage Control............ - 3.60v
GTL+ Buffers Strength............... - Strong
Host Slew Rate...................... - Weak
GTL REF Voltage Control............. - Disable
CPU GTL1/3 REF Volt................. - 93
CPU GTL 0/2 REF Volt................ - 93
North Bridge GTL REF Volt........... - 93
 
Genie BIOS Settings:
 
Exist Setup Shutdown................ - Mode 2
CLOCK VC0 divider................... - Auto
CPU Clock Ratio Unlock.............. - Enabled
CPU Clock Ratio..................... - 8
Target CPU Clock.................... - 4000MHz
CPU Clock........................... - 500
Boot Up Clock....................... - 350
DRAM Speed.......................... - 333/800
Target DRAM Speed................... - 1201MHz
PCIE Clock.......................... - 100mhz
PCIE Slot Config.................... - 1X 1X
CPU Spread Spectrum................. - Disabled
PCIE Spread Spectrum................ - Disabled
SATA Spread Spectrum................ - Disabled

I couldn't find any extra performance over my favourite BIOS (1019) so I have reverted back to it.

CN

[mad_skills]

Tnx you both, i appreciate it.

[cantankerous]

In post 2814 I document that I could not install Vista64 with the 12/24 bios. I had random lock ups and only reached the screen for selecting the hard drive for installation once out of 5 attempts, so I couldn't even attempt to load Intel's latest AHCI/RAID drivers, which was the reason I was attempting to use the bios in the first place. I reverted back to the 11/07 bios and installation went fine.

I believe Cantankerous applied the bios to an existing setup, i.e. wasn't installing an OS from scratch, and saw no difference.

That is correct. I flashed and am using on an already installed OS without a single issue. I will be formatting shortly to go back to RAID since my Raptor that died arrived from RMA last week. Just waiting on the official SP1 for Vista before I do all this. Hopefully within the next few weeks.

[emoners]

@C-N: sorry for the ignorance, but why did you set the BootUp clock to 350? & how come i can't set the Clock Crossing Setting to More Aggressive? if i do that, it would give me a 52 on the PostCode (tried using GKX & GMH - same thing happens)

[C-N]

@C-N: sorry for the ignorance, but why did you set the BootUp clock to 350? & how come i can't set the Clock Crossing Setting to More Aggressive? if i do that, it would give me a 52 on the PostCode (tried using GKX & GMH - same thing happens)

Boot up clock is @ 350 just simply because it was a round number & I like round numbers.

You could have all sorts of things preventing you from running aggressive settings but from my experience setting the clock crossing to more aggressive requires a tad more vnb & vdimm which I can understand as the bandwidth & latency's in Everest improve therefore the rig is loading up more.

(If you are on read delay 6) I find trying to hold rd6 over 500fsb with 1200mhz + needs a shed load of vnb & vdimm where as rd7 which is not far behind rd6 (2-400mbs) will run quick with nice low voltage & imo is where you should be at for 24/7 use.

I would also say some BIOS's set the "current/auto" values differently & have given me a bit of jipp in the past.

Hope this helps

CN

[emoners]

thanks C-N!

[Brother Esau]

@ DJSUB............Brotha you're Bios Chips are on the way to the Philippines and sorry about the delay in getting it out to you because of inability to access my info you sent me in PM with you're shipping info During by little forum Vacation

Sorry for the inconvenience so I have sent you "2" Bios Chips instead of 1.......... Aloha Brother