Thanks I went ahead and downloaded that 0901 bios and winflash it successfully. Great improvement over stock 0812 when overclocking at least on my computer.
dja2k
Thanks I went ahead and downloaded that 0901 bios and winflash it successfully. Great improvement over stock 0812 when overclocking at least on my computer.
dja2k
Well ok, so it's not a rule but often plus has A3 and I haven't heard about non-plus with it.Quote:
Originally Posted by dz`
btw. what max FSB can you set (not necessary stable) and with what V on NB?. I can't even get to bios post above FSB 410 :down:
Subscribed & read front 2 back.
Just couldn't wait for the UT P45 any longer so I'll just have to buy it too if/when it shows up.
I got the non plus version with an A2 chipset which came with 0613 BIOS so she's an old stock one but after only a couple of hours she's prime stable @ 533 x 7.5 4.0GHz with my E8500 & OCZ PC2-8500 SLI's on the stock box cooler.
CN :)
Gratz!Quote:
Originally Posted by C-N
Could you please post your bios settings or ABS profile?
How did you do that? Have you updated bios?
I still can't even post-bios at anything above FSB 410 :shrug:
I updated the BIOS to 0812Quote:
Originally Posted by tamashumi
Every rig is different but here are my slightly sloppy setting, remember I only got this board yesterday & some of the voltages are a touch higher than they need to be.
P.S Anyone that wants it is welcome to use this BIOS template.
DFI LANPARTY DK P45-T2RS (BIOS 0812)
INTEL CORE 2 DUO E8500 WOLFDALE 3.16GHZ 6M L2 CACHE (Q807A273 / C0)
OCZ PC2-8500 SLI 2 x 1GB PN:OCZN1066SR2GK
XFX 6600GT 128MB (178.13 DRIVERS)
1 X HITACHI DJ 80GB HD'S
SONY DUAL LAYER DVD RW (DRU-820A)
OCZ GAMEXTREAM 700W PSU
WINDOWS XP PRO SP2
CPU COOLING: AIR / STOCK Q6600 BOX COOLER
Code:>CPU Feature:
Thermal Management Control.......... - Enabled
PPM(EIST) Mode...................... - Disabled
Limit CPUID MaxVal.................. - Disabled
CIE Function........................ - Disabled
Execute Disable Bit................. - Enabled
Virtualization Technology........... - Enabled
Core Multi-Processing............... - Enabled
>DRAM Timing:
Enhance Data transmitting........... - Fast
Enhance Addressing.................. - Fast
T2 Dispatch......................... - Auto
>Clock Setting Fine Delay Press Enter:
DLL And RCOMP Settings............. - Auto
Ch1 Dram Defaul Skew............... - Model 3
Ch2 Dram Defaul Skew............... - Model 3
RCOMP Settings..................... - Model 1
Fine Delay Step Degree............. - 70ps
Ch1 Clock Crossing Setting......... - More Aggressive
DIMM1 Clock Fine Delay............. - Current[2396ps]
DIMM2 Clock Fine Delay............. - Current[2396ps]
Ch1 Control0 Fine Delay............ - Current[268ps]
Ch1 Control1 Fine Delay............ - Current[268ps]
Ch1 Control2 Fine Delay............ - Current[268ps]
Ch1 Control3 Fine Delay............ - Current[268ps]
Ch1 Command Fine Delay............. - Current[394ps]
Ch2 Clock Crossing Setting......... - More Aggressive
DIMM3 Clock Fine Delay............. - Current[2066ps]
DIMM4 Clock Fine Delay............. - Current[2066ps]
Ch2 Control0 Fine Delay............ - Current[48ps]
Ch2 Control1 Fine Delay............ - Current[48ps]
Ch2 Control2 Fine Delay............ - Current[48ps]
Ch2 Control3 Fine Delay............ - Current[48ps]
Ch2 Command Fine Delay............. - Current[394ps]
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
Flex Memory Mode.................... - Auto
CAS Latency Time (tCL).............. - 5
RAS# to CAS# Delay (tRCD)........... - 5
RAS# Precharge (tRP)................ - 5
Precharge Delay (tRAS).............. - 10
All Precharge to Act................ - 5
REF to ACT Delay (tRFC)............. - 28
Performance Level................... - Auto
>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
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
ALL PRE to Refresh.................. - 4
>Voltage Settings:
CPU VID Special Add................. - + 237.5mV
DRAM Voltage Control................ - 2.29v
SB Core/CPU PLL Voltage............. - 1.55v
NB Core Voltage..................... - 1.5575v
CPU VTT Voltage..................... - 1.31v
Clockgen Voltage Control............ - 3.60v
CPU GTL0/2 REF Volt................. - 0.63x
CPU GTL 1/3 REF Volt................ - 0.63x
North Bridge GTL REF Volt........... - 0.58x
FSB Vref............................ - Auto
Genie BIOS Settings:
Exist Setup Shutdown................ - Mode 2
Exist Shutdown After AC loss........ - Enabled
O.C Clock Fail Retry Counter........ - 0
O.C Clock Fail CMOS Reloaded........ - Disabled
CPU Clock Ratio..................... - 7..5
Target CPU Clock.................... - 3997MHz
CPU Clock........................... - 533
Boot Up Clock....................... - Auto
CPU Clock Amplitude................. - 800mV
CPU Clock0 Skew..................... - 0ps
CPU Clock1 Skew..................... - 0ps
DRAM Speed.......................... - 333/667
Target DRAM Speed................... - 1067MHz
PCIE Clock.......................... - 100mhz
CPU Spread Spectrum................. - Disabled
PCIE Spread Spectrum................ - Disabled
I never got pass with 1.40 NB core (actually just more than 1.35), It's freeze at the windows loading, any advice ?
Try changing NB GTL if you change vNB.
But also take in mind that NB GTL is derived from vTT, just like CPU GTL is.Quote:
Originally Posted by Blackoberst
It's best to not set vNB and vCPU PLL the same voltage. There needs to be a gap between these two, or they'll interfere witch each other causing instability for the North Bridge.Quote:
Originally Posted by C-N
So up your SB Core/CPU PLL Voltage or lower NB Core Voltage. I would prefer the latter. Take in account that - idealy - CPU PLL voltage is set 0.3v to 0.4v above vCC (=vcore)
Thanks,Quote:
Originally Posted by C-N
I've tried your settings also tried pdf from DFI engineer linked before. Tried both bioses 0812 and 1003. Pity but no success. On anything above FSB 410MHz not even bios post. Well when I was trying 533 FSB with single RAM stick it posted once for like 20 tries.
I know you have non-plus board like me but I'm going to replace my board today for plus version.If that won't help I try with different PSU (my old one) then different RAM, then different mobo manufacturer (Asus/Gigabyte), etc... ;) However I would like avoid so much trying :rolleyes:
Speaking about RAM. Could it halt my FSB OC even if it's resulting dram speed is about 800-1000MHz?
I mean using DRAM:FSB divider 400/800 after rising FSB to 400~500. I tested ram only (without rising FSB) and it's stable on 1000 and 1100MHz (but it needs a bit more voltage then manufacurer specifies).
I guess because u use that DRAM:FSB ratio u can't pass over 410 fsb. For 1:1 raport u better use 333/667, u'll get the same thing and u will pass that 410+ fsb. Just use this setting
DRAM Speed.......................... - 333/667
SEPTH I never got pass with 1.40 NB core (actually just more than 1.35), It's freeze at the windows loading, any advice ?
It's because you have NB overheating, maybe, with high NB voltage. I removed stock NB cooling for change original thermointerface, but find the small gap between heatsink and NB core. It sitting on washers for defend the core, but washers not gave for heatsink to have good contact with core. BTW, the cooling solution on the board not so strong and need to be aircooled for OC, i think.
I think I tried couple different DRAM:FSB ratios, but I try today 333:667 to be sure. I forgot to take the board from home for replace anyway :PQuote:
Originally Posted by puiu
Thanks for the tip :)
You are probably right but I've never found an instability problem with any of my DFI boards right back to the ICFX 3200 which was one of the first boards with GTL, VTT & PLL features.Quote:
Originally Posted by DemonEyez
My P35 has run for nearly a year with 1.55v pll & 1.57vnb.
I wouldn't recommend upping the PLL either for 24/7 use, I've hurt plenty CPU's max fsb using high PLL voltage.
My board/chip is running prime stable at 533fsb with 1.55 vpll & 1.25 CPU vcore. The same chip has run for a couple of months @ 475 x 9.5 1.55vpll @ 1.4vcore.
Ideally Intel don't want there 45nm's going past 1.25v but I guess when you overclock best intentions & ideals go out the window.
CN :)
Have you tried 1:1 & slackening your RAM timings off to take 2x2GB sticks into account?Quote:
Originally Posted by tamashumi
Try
333/667
Flex Memory Mode.................... - Auto
CAS Latency Time (tCL).............. - 5
RAS# to CAS# Delay (tRCD)........... - 5
RAS# Precharge (tRP)................ - 5
Precharge Delay (tRAS).............. - 18
All Precharge to Act................ - 5
REF to ACT Delay (tRFC)............. - 52
Performance Level................... - Auto
Need Help guys...
I got the DFI DK P45 T2RS PLUS along an E8600, 2 x 1GB Team Xtreem PC2 9600 (1200MHz) and a Palit 512MB HD4870 Sonic Dual Edition (the 1 with 2 fans). When I connect my 4870, I get 1 long beep...at times a few small beeps and the Diagnostic LED goes as it normally does but I get no display :@
I tried with 2 different PSUs (tagan 800W & Corsair 450W)...it worked with my nvidia 7150 but get no display with the 4870.
The 4870 worked fine on my other PC but it refuses to dispay on the DFI DK P45 PLUS...on both the PCIx slot.
I even updated to the latest (non-beta) BIOS on the DFI website through the other GPU but it still doesn't work.
Is there a compatibility issue ??? or do I need to do some jumper setting ???
PLS help me out guys...this is my 1st DFI and my cuz got it 4m Canada as there's no DFI in INDIA.
yeah I also read that high vPLL could damage the chip. It would be nice to see DFI change the big steps in the bios for this voltage. Asus for example let's you control it with much smaller steps.Quote:
Originally Posted by C-N
Still I find vNB a bit high. The P35 is 90nm so 1.55v isn't that high, but P45 is 65nm and needs less voltage. So when you take that in account, 1.55v seems rather high. I wonder if longterm high voltage has severe effects on this chipset or not.
That would be nice, put my name on the petition :DQuote:
Originally Posted by DemonEyez
Yes you are right it is rather high however if you want to run fast & more aggressive then its needed for stability (at least with my board it is)Quote:
Still I find vNB a bit high. The P35 is 90nm so 1.55v isn't that high, but P45 is 65nm and needs less voltage. So when you take that in account, 1.55v seems rather high. I wonder if longterm high voltage has severe effects on this chipset or not.
>DRAM Timing:
Enhance Data transmitting........... - Fast
Enhance Addressing.................. - Fast
T2 Dispatch......................... - Auto
>Clock Setting Fine Delay Press Enter:
Ch1 Clock Crossing Setting......... - More Aggressive
Surely I'll try 333/667 as I'm not sure have I before.Quote:
Originally Posted by C-N
Btw. What's the difference between 400/800 and 333/667? Aren't they both 1:1 ?
My ram should do 533 on 1:1 without timings slackening. It's DDR2-1100MHz cl5-5-5-15 by default. Moreover I've tested 1000MHz and 1100MHz without rising FSB (on other DRAM:FSB dividers) and it fact RAM is stable not to mention about problems with bios-post (C1 on post-led).
I have 4870 also but Diamond manufactured. I have no problems at all so I doubt it helps. But maybe try to update graphic card bios... No jumpers settings (I know) will help here. Try also to set in bios PCIx for "init display first".Quote:
Originally Posted by has33
The difference is the strap, 400/800 should allow you to oc a little further with a small hit in performance.
You are quite correct 400/800 & 333/667 are both 1:1 but they use different straps. The 400 strap should be easier to run than the 333 strap but I haven't actually tested it on this board. It wont cost you anything but time to play/try the 333 strap so IMO its worth a go.Quote:
Originally Posted by tamashumi
I was referring to slackening the timings off from my 2gb setting if you were trying my exact timings as posted. My 4GB kits would not even run tRFC at 28~30 they need to be 46 + to get any joy out of them.Quote:
My ram should do 533 on 1:1 without timings slackening. It's DDR2-1100MHz cl5-5-5-15 by default. Moreover I've tested 1000MHz and 1100MHz without rising FSB (on other DRAM:FSB dividers) and it fact RAM is stable not to mention about problems with bios-post (C1 on post-led).
No one here did not mention anything about the amount of memory shown in Windows XP 32bit (maybe I just read too fast and slappy). Because on my Plus, with 2x2GB Xtreem Dark kit, system only recognize 2GB of memory. And also task manager reports 2 gigs of memery (in KB of course). Neither PAE switch doesn't help. So, this is the actual amount that OS can use, right? Or it is just shown false? BIOS version is A3. Before that, it was 0910 and XP showed 2.75GB.
Tnx!
Yea right,in theory but in practice i am able to hit 650 fsb benchable on air,and in 400/800 i cannot post at all :confused:Quote:
Originally Posted by Eldonko
these days strap has only minor changes on board since the big one that was traditionally rolled in used to be tRD. Now that it's pulled out, the chipset strap is mostly just for setting memory dividers. I believe it also affects the phase offset applied for clock splitting on the MCH. I think instabilities that come out from these phase offsets are what causes FSB "holes" the majority of the time. Playing with GTL adjustments and timing offsets can sometimes bring you back into a stable regime but this still ends up being wandering in the dark unless you have a good oscilloscope handy.Quote:
Originally Posted by Alex-Ro
That's funny, my board is useless with 333/666 and slightly less useless with 400/800. Yay for consistency!
Quote:
Originally Posted by Alex-Ro
gone through the whole thread and no quad result here:shrug:
So i share mine ;) cheers:toast: