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
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 :)
I updated the BIOS to 0812
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.
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.
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,
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.
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.
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?
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.
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 :D
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.
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".
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.
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!
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.
gone through the whole thread and no quad result here:shrug:
So i share mine ;) cheers:toast:
Thank you guys for tips. Some good news (below)
Indeed it was worth of playing. I get bios-posted my rig @ 533MHz :D Even windows started to loading, ofc it hasn't loaded at all ;]
I used your insane voltages to get this result and most of settings but this time timings was left on auto. My 4GB kit is 1100MHz cl5-5-5-15 by default, so 1066 shouldn't cause instability I guess - am I right? Not sure about tRFC...
Speaking about voltages, what temp do you have on NB? Mine is ~60 right after turning on, checked in PC Health at bios. Isn't that to much for stable work?
Nope you didn't read to fast. There was nothing about this it the thread. Sorry I won't help - 64bit OS here. I recommend to use such xD
Similar here. I can't even post with 400/800. btw. what NB voltage do you use for such high fsb?
Well I heard "something" about this strap-crap thingy... Guess I need to get more knowledge about how it affects stability. I have access to really good oscilloscope or maybe even two :scope: But I'm not familiar with use of it. Those are my father's toys ;P Maybe I'll ask him to do some measurement for me or teach me how to do it myself. But I need to know what to measure in the 1st place xD
Now I'm bit confused. Not sure to replace for the plus version or look more stability with non-plus. For now I've tested 400FSB and it seems to be stable (it wasn't before with 400:800).
I've run for stability test: 1 core SuperPi 32M and the other core single thread of Prime95 large FFTs (max heat & power...) at the same time. If SuperPi done its calculation successful while Prime still runs without an error I'm starting to consider the setting stable :]
One more thing, my rig seems to be strongly undervolted.
Examples:
NB 1.285V @ BIOS => 1.24V @ SmartGuardian
VTT 1.26V @ BIOS => 1.23V @ SmartGuardian
CPU 1.31+V @ BIOS => 1.29V @ SmartGuardian
RAM 1.908V @ BIOS => 1.88V @ SmartGuardian
What can cause this, PSU, mobo itself or something else?
Happy days my friend thats great news :up:
On the subject of insane voltages I took a look at the P45 spec sheet & Intel reckon absolute max should be 1.21v :ROTF:
tRFC makes all the difference when you want every last mhz out of your RAM.
My NB temp is 42~43oC under load with a slow 80mm fan on it.
Stick with your non plus board & spend some time with it I'm sure it'll come good oh & my voltages appear lower in SG too but the few I have measured actually read slightly over on a DMM.
Anybody got the voltage read points for this board ?
Thanks :D
...probably something wrong with NB heatsink on my mobo as I have fan on it too. 120mm over NB, ram and partially CPU - it's just laid on them ;) but blowing fine. Probably heatsink doesn't fit well. Someone posted before about such issue with this board. Maybe smash with a hammer make it fits good xD
Hmmm...
With 10/3 BIOS task manager reports 2gb
With 12/8 BIOS task manager reports 2.75gb
I have XP SP2
WTF?
Hey GaS & cole2109,
Although I have all the bits to test I don't have the time today to put them all together to see how much memory my system sees. I do however remember XP just like Vista pre SP1 would only see 3.something gigs when there was 4 fitted. As far as I know XP cant address 4GB plus when you install like a HD3870/4870 or something big the OS takes away the video ram from the system RAM.
I guess what I am saying is you probably wont see anywhere near 4GB of RAM when you run fat graphics cards so if you can try a little graphics card & see if its just your OS allocating all its addressing space or I would say if it still just shows 2GB you must have a problem.
You could also use CPU-Z to check both 2gb sticks are being seen, also you could try moving channels to see if that helps/shows your RAM.
CN :)
There is no problem with both sticks, they are properly showed. I guess there is something with so called fat gfx, will try some old one. Anyway, this is a way too big (50%) memory consumption?!
Hey's that's the info I was looking for.:) I'm still on:
Enhance Data transmitting........... - Auto
Enhance Addressing.................. - Auto
T2 Dispatch......................... - Disabled
Ch1 Clock Crossing Setting......... - Auto
because my vNB is only 1.30v. My main focus was on getting 9x500 Prime stable with as little voltages as needed
I'll raise it to 1.40v. Let's see if it's enough for me to do your settings.
32bit system can address 4GB of memory in total. That's mean RAM, graphic card memory, other devices memory and physical addresses of devices (page file also I guess). So usually in the 32bit OS one can see only 3-3.5GB.
Your graphic card has 1GB of memory, right? So including all "other stuff" mentioned above 2.75GB seems to be correct. (and the 10.3 bios is still beta so it can have some strange behavior)
Only solution is 64bit OS.
It is BIOS for sure.. About 64bit; maybe Windows 7:)
Anyway, does anyone have GX2 on the Plus version? Because they are not compatible with each other, although the system works, the performance is pretty poor. DFI has encounter problem, so it should be fix asap. I really hope so, because I have this board for like 6 weeks..
Hmm, may have to try this new bios. The beta ones im using atm arnt as good as the previous ones:D
Let us know how you get on as it would be nice to work out whether the much coveted A3 revision of the P45 is actually a superior lower voltage chip than its A2 brother or not.
My board is currently priming 500x8.5 atm with fast/more aggressive settings & 1.54*vnb :D
Just put Flex Mode on auto,if you disable it you will have single channel only ;)
Some preliminary results on the A03 bios with a q6600 L809A957 batch with 1.325 VID: so far so good(even though the batch/VID indicates that I have a bad chip...), 470 FSB. The trick is to get the hang of the GTL, VTT, and NBv/NBGTL settings. What I find useful is to find a point where the GTL, VTT, and NBv/NBGTL settings all work for a specific fsb, and then up these settings to the "next level" so to speak. So its kind of like finding out how much more voltage your chip can take at a specific fsb. The reasoning behind this is that if you can find that next level on ur current fsb, the next step up fsb will be semi stable on these settings. Then you tweak the voltages to be stable again for the new fsb, rinse and repeat until you get your desired fsb. This logic may be incorrect but its working out for me so far, I went from a wall at 410 FSB to 450 FSB to 470 FSB, and now hoping to hit 500 FSB. Another thing is that I find when setting these "levels" my NBv and VTT on the bios sensors are the same usually for stability. Meaning I might be setting 1.425 for NBv and 1.409 for VTT, but in the bios sensors they both read 1.4v.
Also another note, the best tool to test for VTT/GTL/NBv/NBGTL stability is prime95, for me whenever a core crashed, I just had to up my NBGTL or NBv+NBGTL to get it to not crash. After prime runs for about 15 minutes I would switch over to LinX to test overall fsb stability. I find that if LinX errors then I had to raise the cpu core GTLs up to gain stability. Otherwise if LinX crashes and freezes your computer then you need the "next level" of voltages to get the FSB stable.
Hopefully this helps anyone with trouble on this board. I also want to add that this board is really amazing for what it can do on just 4 phases, with vdroop off I get rock stable vcore, with vdroop on I get rock stable vcore after it droops. Really great board with the latest a03 bios.
Update Post #1 :)
Right now I'm running Othos for 1.5 hours stable with your settings at 9x500. vNB is 1.41v right now, I have to do some further testing and see if I can lower it. :D:p:
With vNB @ 1.41v I'm running as follows:
CPU Clock Ratio........................... 9x
CPU Clock................................... 500
DRAM Speed............................... 333/800
Enhance Data transmitting............. Fast
Enhance Addressing...................... Fast
T2 Dispatch................................. Disabled
Ch1 Clock Crossing Setting............ More Aggressive
Ch2 Clock Crossing Setting............ More Aggressive
CH1CH2 CommonClock Setting........ More Aggressive
@P_1: could you post your bios settings? thanks
by the way, for the LANPARTY JR P45-T2RS... Beta Bios 2008/10/07
Major Reasons of Change:
1. Support DRAM Speed 266/1066 and 333/1066.
2. Patch for JMB368 and ICH10 SATA not in native mode hang"75".
3. Fixed Can not detect CPU name when use Q9xxx CPUs.
Is this Board (P45-T2RS Plus) recommendable for Quads (specifically: Q9950 E0)? I mean, it only has four phases...
And, are there any differences regarding OC between P45 A02 and A03?
For all you guys who want to watercool their VRM's and Southbridges:
http://www.pc-icebox.de/anfitec-pwm0...er-p-4728.html
http://img337.imageshack.us/img337/6...ehler41be8.jpg
http://img337.imageshack.us/img337/8...ehler31ve2.jpg
http://img530.imageshack.us/img530/3...ehler11zc5.jpg
http://img359.imageshack.us/img359/2...ehler51in8.jpg
http://anfi-tec.de/mainboardpwm.pdf
Only downside is that currently they're sold in Germany, don't know if they do international shipping
I replaced my board for plus verions today.
It has PCB rev A2, it's written on it (I mean revision of the board itself not the chipset).
Seller from which I have the board told me that non-plus also going to be on new PCB rev (so probably with newer chipset revision, that is A3).
Also it delivered with 09-01 bios (non-beta? o_O).
Bad news are I haven't tested anything not even checked chips with cpuz becouse my OCZ SSD core V2 drive stop working.
After whole day of tries and tests I have to confirm that drive is not compatible with DFI LN DK P45-T2RS+ (or with new PCB/chipset rev of both mobo versions).
I going share with you some detalis, maybe someone could help me, but probably tomorrow I'll have to replace again for Asus P5Q Deluxe as I'm tired and disappointed with DFI issues.
Here's the story:
After replacing board system stopped boot. I mean not even started booting. After showing devices table and standard message about cmos backup just stops and nothing happened. I've checked drive with couple tools, recreated partitions (many times: by windows install and acronis disk director suite), reinstalled vista (later many times). Only difference after installation was I got "BOOTMGR IS MISSING" instead of no communicate at all. I was trying to recreate MBR, boot sector, boot menu and all that stuff automatically and manually by commands (bcdedit, bootrec, bootsect), different sata cables and different sata slots on the board including additional sata controller (main feature of plus version) also flash 812 bios. Nothing... Moreover I connected normal 7200 drive installed system and it works. On the other hand, if SSD is connected via usb (it has such a feature) it boots o_O also I was trying via sata in my friend's PC - boots no problem WTF?!. So there isn't any bootmgr problem in fact, is it? Bootmgr is in its place and works correct but not with this board. It's so strange issue, damn... I have no idea what's going on especially previous board was (?) almost the same :shocked:
Now it's late and I'm going sleep but tomorrow morning I'll check this topic for any advice before I'll go for Asus board.
PS. this revision/version is almost 15C cooler on chipset (checked in PC Helath in BIOS). I have 35C instead of 50C
Try setting the Intel controller to RAID. Install Windows using the Raid driver and F6. The drive will install as a non-member Raid drive. I have tries an SSD on at least six different DFI models and this is the only way I could get Windows to boot. The upside is installed like this the performance is really good.
Here you go:
http://img201.imageshack.us/img201/5...mentbh0.th.jpghttp://img201.imageshack.us/images/thpix.gif
http://img201.imageshack.us/img201/6...mentgz2.th.jpghttp://img201.imageshack.us/images/thpix.gif
http://img201.imageshack.us/img201/1...mentgb2.th.jpghttp://img201.imageshack.us/images/thpix.gif
http://img201.imageshack.us/img201/5...mentwn9.th.jpghttp://img201.imageshack.us/images/thpix.gif
http://img201.imageshack.us/img201/3...mentax3.th.jpghttp://img201.imageshack.us/images/thpix.gif
Praz! I love you xD
It helped.
Small difference: I had to switch to JMicron chip and change to 'RAID+IDE'.
On Intel's chip bios-post freezes if I change to anything different than 'IDE'. I didn't have to install anything - not even a driver. Vista just booted :up:
Intel chip is unusable for this SSD drive. Well it going to handle dvd and storage drive.
I wonder if OCed NB can damage drive or corrupt files if drive is connected to it? If yes, JMicron should be safer for system drive.
btw. anyone successful with running Linux on that board? I've tried Ubuntu Hardy Hadron 8.04 x64 - Live CD hanges before there is option to install. On my mobile this OS runs fine.
I had almost the same issue as you, the solution in the end was to change to IDE and flash to new bios. Its a known issue with the stock bios, I suggest using the A03 bios on DFI's beta site.
tamashumi
Did you try Intel RAID with th JMicron enabled and disabled. Some BIOS versions won't allow the board to boot depending on the JMicron setting.
Praz
I didn't. I'm during windows installation with jmicron driver, set at BIOS to RAID+IDE. I think it going to work, do you think it would cost in performance against NB ?
I'll check with jmicron@disabled and intel@raid after the installation.
Anyway, I can use it at last :)
P_1
I tried 812 from DFI site. On this bios non-plus board worked fine with SSD drive (On A03 too). I haven't tried A03 with fresh's Plus of mine.
Will see, maybe if I would be able to run on both chips I'll benchmark them for comparision
Yep, same here. I checked 2 BIOS'es with Vista x32bit and find same strange issue with 10.03BIOS and 4x1Gb G.Skill mem. It's reported 3075Mb available memory, but after reflashing 901 BIOS, it's about 3300Mb mem. available. Approx. 300mb more! Wassup? And no matter if it's 1Gb card or 1/2 Gb video- only BIOS was changed. Same setting and configuration.Quote:
With 10/3 BIOS task manager reports 2gb With 12/8 BIOS task manager reports 2.75gb I have XP SP2
Finally I'm running SD drive on Intel chip in AHCI mode.
Flasing 10.03 bios allowed me to pass through bios drive detection. No freezes anymore so I could choose any possible option: intel @ raid/ide/ahci with jmicron @ disable/raid+ide/native ide.
I stayed with AHCI on JMicron: system on OCZ SSD + storage on Samsung F1.
DVD-RW is connected to JMicron in Native IDE.
I'm tired (yesterday tries until 5 a.m. xD) but satisfied. I stayed with rig I wanted and drive incompatibility has been eliminated. Mostly thanks to Praz and P_1 :up:
I can't do benchmark comparison because changing any sata option prevents loading system :/ Even if I just disable JMicron - in my opinion it should't affect Intel's config o_O
Also I can't run Acronis True Image bootable CD for partitions cloning. Maybe any recommendation here?
Probably installing linux would blow this thing up in the sky shattered into pieces (I'll try again).
Not to mention that I'm had to use beta bios...
This board is an experimental poligon :shakes:
DFI should care more about their product finish. Their reales seem to be not complete for the market yet.
One thing to mention, now chipset rev I got is A3 and seems to be cooler.
Probably I'll get some too when WC set starts working on my rig. Germany are close to me :)
But you posted pieces for JR board, yup? Would they fit on full-atx one?
I'm using v11 but not latest build for sure. I'll check for some update.
rev A3 P45 Intel chipe runs stable at FSB 400 @ 1.16V (1.1925 set at bios). I'm during first tests now so I try later, maybe even it gona works at default voltage :]
New mobo also keeps voltages strongly fixed and closer to what was set at the bios. I think it's advantage of newer PCB rev not plus-version itself.
But mine E8600 is more hungry for voltages, to keep it stable @4GHz +1.37mV is needed. Is it normal? It becomes quite hot during benchmarking - up to 70C. I guess I need replace stock thermal grease...
Guys, what do you think about Xeon E3110?
1003 BIOS needs more vcore to be set in BIOS to get the same CPU-Z voltage in windows for me but everything else appears the same as previous versions.
How can you tell? what are you using to compare?
VDIMM measured on the EC5 + spot between the SB & DIMM slots show me .05v more voltage than set in BIOS.
@ PRAZ I don't suppose you would have & mind sharing the volt read points for this board?
On a good note my board is flying along on the 266 strap :D
You asking how I measure voltages? Only by software (SmartGuard) and bios PC Health.
My comparision base only on that. I can see now that voltages are closer to that set in bios (only at NB is greater difference but before was at almost all key components).
More important is that before voltages wasn't fixed they waved in some range +/- 0.02V @ CPU f.e., VTT, VDIMM and NB also. Now voltages are fixed. I think its advantege of newer PCB revision. It's rather not bios domain as on non-plus with older PCB rev I tried both bioses with no difference when speaking of fixed voltages. Fixed I mean values aren't changening when I look on SmartGuardian readings for longer period of time while benchmarking.
AFAIK non-plus board going to be (probably alredy is) released on newer PCB rev. BTW. can you check what rev has yours board? It's written in corner of the board near com1.
What's EC5? Do you measure voltages with some tool?
Yes, I thought maybe you were using a DMM (Digital Multi Meter)
Mine appears good a solid.Quote:
More important is that before voltages wasn't fixed they waved in some range +/- 0.02V @ CPU f.e., VTT, VDIMM and NB also. Now voltages are fixed. I think its advantege of newer PCB revision.
REV.AQuote:
Can you check what rev has yours board? It's written in corner of the board near com1.
Look in between the southbridge heatsink & the memory slots, you will see a capacitor & beside it the pad for another cap with the letters EC5 written between them. I use a DMM to check VDIMM here (that is assuming I am in the right spot)Quote:
What's EC5? Do you measure voltages with some tool?
Not yet, maybe I will. I have one around somewhere in the house.
Good to you mate :D
At previous board mine wasn't. They were varing...
I guess, 1st one. Maybe good piece of it. Pity I haven't checked the replaced one's rev:rolleyes:
Good to know. If I have some time to play with DMM I'll check it.
NB voltage decreased to 1.185V at bios (SmartGuardian reading shows 1.15V). FSB still 400MHz. It seems to be stable after my test procedure. I try to lowering it more but not today. Newer chipset (mobo?) revision is less power hungry in fact. I hope it results with better OC potential :)
thanks for all advice, I've changed GTL REF, but still hang at windows load with 1.37 nb core, maybe I'll check my other devices like graphic cards or somethin
I noticed that at my current settings my pcie link width is being reported as 2x instead of 16x. Does anyone else have this problem? I'm thinking its the SB/PLL voltage I am using(1.75) any thoughts?
Nice! It would be interesting to see what kind of bandwidth and latency you get in Everest. Here's mine for 9x500 and the 333/800 strap:
http://www.plaatjesupload.nl/bekijk/...814524-230.jpg
CPU Clock Ratio........................... 9x
CPU Clock................................... 500
DRAM Speed............................... 333/800
Enhance Data transmitting............. Fast
Enhance Addressing...................... Fast
T2 Dispatch................................. Disabled
Right now I'm running Othos for 1.5 hours stable with your settings at 9x500. vNB is 1.41v right now, I have to do some further testing and see if I can lower it. :D:p:
With vNB @ 1.41v I'm running as follows:
CPU Clock Ratio........................... 9x
CPU Clock................................... 500
DRAM Speed............................... 333/800
Performance Level........................9
Read Delay Phase Adjust................All on Auto
Ch1 Clock Crossing Setting............ More Aggressive
Ch2 Clock Crossing Setting............ More Aggressive
CH1CH2 CommonClock Setting........ More Aggressive
[
Anybody noticed these on DFI JR P45 with the 10/07 bios?
http://i33.tinypic.com/nqyfdv.jpg
Uhm I guess I need to check pcie link width too though ;]
DemonEyez
Lowering voltage on NB is a good thought. I'm looking forward for results :)
emoners
What's that right of your screen shot - some Vista sidebar gadget? I''m looking for something like that :>
@ DemonEyez : How can u get that kind of temperatures from Chipset ( 34* ) couse i have the same board lets say and with 1.28 NB voltage i get like 50*++.
I never did get to the bottom of it, I tried to work it out nobody could help so I just accepted it & lowered the frequency. I ran 125mhz ish & dropped it down to 115 ish.
I am at work atm but off the top of my head I get 10650 across the board & 48~49ns latency. I'll post the screen up when I get home.
On the 266 strap I have to drop the cross setting back to relaxed to run Orthos stable otherwise the Bandwidth is about 10850mbs & 47ns latency again I'll post it up later.
Looks like I'll be getting a Plus then :D what have you set in BIOS to get 1.4 in SG?Quote:
Right now I'm running Orthos for 1.5 hours stable with your settings at 9x500. vNB is 1.41v right now, I have to do some further testing and see if I can lower it. :D:p:
This is what "P_1" is referring to but I don't think he has the JR.
OT
Quote:
C-N : Mine appears good and solid
:lastweek: Captain slow here just got the joke :DQuote:
tasmashumi : Good to you mate :D
Just did some tests, I loose stability when lowering vNB and keeping those timings tight. Prime/Orthos fails after 4 hours.
So it seems that 1.40v is the minimum voltage required for those tight settings with my board
I'll revert back to looser NB timings and lower NB voltage (1.31v) for 24/7 use. Running with those tight NB timings and Performance Level only differs 300MB/s in Everest Read Bandwith and 3ns in latency.
In my opinion the 0.1v increase needed for that is far too much and not worth it for daily use.
I run with a Swiftech MCW30 waterblock on it.
Those are some nice numbers for bandwith and latency. Just for the fun of it i'll try 266 strap this evening
Seems the Plus does have the better chips and does run with less voltage
The board undervolt a bit. I have to set 1.445v in Bios to get 1.40v in SG.
Same goes with vTT. 1.33v set in Bios gives 1.30 in SG.
But those voltages are rock solid, no fluctuations whatsoever :)
I wouldn't rely on SG/Software to be any where near accurate, I don't think I've had a DFI yet that displayed DMM voltages in SG/Software.
I may have to sit down & work out the read points on the weekend coz not knowing is killing me.
Here's the 266 strap screen shot with more aggressive & fast.
Haven't managed to get this properly Orthos stable yet & tbh I don't think I can do it either but I ain't finished yet ;)
I just tried to boot with the 266 strap , using the same settings as you did but my board refuses to boot. The only thing I get out of it is a nice C1 error, and a message that there's some error with the bios bootblock. :shocked:
I've never seen such a message and do not hope to see it again. So I'm not trying the 266 strap again.
Seems that although you don't have a Plus board , you got a golden one :yepp:
For Orthos or Prime to be stable you'll need more volts on the NB is my best guess, and perhaps some NB GTL tweaking?
Would be really great to see those timings stable. That are some wicked latencies :clap:
I think you could be right but I cant get any more than 1.55/57 (set in BIOS) to run, it just locks up in Orthos. NB, GTL's & vref are all tweaked out. I have only just scratched the surface with CPU skew control & done nothing with dram skew so theres hope yet.
This is weird, for ahci to work I have to enable the jmicron controller... Otherwise it just won't find any devices, even though the ahci screen shows that my hdd and dvdrw are present.
I just find out my real problem about nb core, it's because my gfx card (ASUS EN8800GT Glaciator) I cant run to my windows with 1.4 nb core after I removed nvidia card driver but after I installed nvidia card driver, it's starting hang on that even after restart
maybe I gotta find other card for this
any 8800GT user's in this forum can boot after nbcore 1.4 pls tell me, at least I must just change the manufacter of this card (to like XFX, Winfast or somethin), thanks
bios can't help, even with latest 10.03
I have XFX 8800GT which I bought on 8800GT release date. Board refuses to POST above NB Core 1.3700v in BIOS. I'm hoping that 1.37v should be enough for a modest OC of 500FSB*9 with either 1:1 or 5:6 FSB : DRAM
SEPTHI'm currently using Inno3D 8800GT(OC version) and didn't find any issue no matter what VNB i change. BTW, you not need other card, try to flash newer BIOS for 8800GT. The most of these cards has reference design and only BIOSes and memory different.Quote:
any 8800GT user's in this forum can boot after nbcore 1.4 pls tell me
using XFX 8800GT...no problems above 1.4v for NB
http://i116.photobucket.com/albums/o...IJRP45-480.png
thanks all of you, now I'm gonna try flashing bios, if it's not work, maybe I'll change to XFX or something
I'm now stable on 9x450. Nothing special but this is kinda OC and far better that I could get on non-plus board. I haven't tried higher yet. First gona tune voltages to minimum required for stable work at this frequency. I let you know :)
Ofc the answer was a water block, but you could also check how NB cooler fits and maybe change thermal compound. Do you have plus version? Mine plus is like 10-15C cooler then previous non-plus on the same voltage.
Hehe I ment exactly the same what DemonEyez said (quoted below). Maybe you should not raplace it. Are you still going to?
I see you test stability quite hardly. My tests are for now rather briefly. But when I get some WC kit and higher frequencies then I do longer test runs.
Agree that for everyday use one doesn't have to squiz out all juice in a risk of damaging its rig.
This is EXACTLY what I observed (and posted before). On non-plus voltages are varying and NB needs more V (at least set in bios).
Have I mist something, did you change your board from non-plus to plus version too?
Damn weird, as you know I had troubles with sata controllers on this board already. This is another thing I observed. Stupid design idea or a bug :/
One more thing to mention to get SSD OCZ working with this board, BIOS has to be 10.03 and SATA controller needs to be in RAID/AHCI mode (with normal 7200rpm drive or non-plus version it isn't necessary).
What are those GTLs? But please do not paste me a link with specific technical details for couple of hours reading.
I gona to find and read something like that sooner or later ;]
For now I just need to know shortly common sense of this setting and what gives its value change.
I still don't think there actually is any difference once you push the board fairly hard I think you will need all the NB voltage you can get. I have no doubt there are good & bad boards but I don't think I have a golden board I think the people that have had bad experiences probably just got unlucky or as I see quite a bit there hardware didn't play nice with the picky DFI.Quote:
Originally Posted by DemonEyez
Seems that although you don't have a Plus board , you got a golden one
I have seen a couple of people using 1.5v + on the NB with the JR, STD & Plus boards with both the A2 & A3 revision of the chipset.
I too can run high fsb on tiny NB voltage but you have to back the performance off so far my Casio calculator would win a race :D
If I find clear evidence the Plus board with the A3 chipset is better than the non plus A2 board I will order one but atm even though my P45 is running nice my P35 still keeps up with it no problem.
My did 610FSB with 1.38-1.39V on NB...
which is the best bios for t2rs (not the plus) paired with a q6600?
I call my system stable only when it has run Orthos or Prime for at least 8 hours. Normally I let it Prime all night and see the results in the morning. Finding the right settings can take up a lot of time in the beginning, but once found i don't change it anymore and use it untill I sell the board for a different better one. :D
I have the Plus version the beginning. Never had the non-plus. I was comparing my board with C-N's I can do his timings with less voltage (only not the 266 strap)
@DemonEyez
I like "rock" stable myself. OCing for just give a try single run of SuperPi or 3dMark hoping that maybe it won't crash till the end of benchmarking and later spanking a monkey over the result really sux :down:
For now I have many different settings to check, so tests have to be shorter. When I reach desired OC then I run some priming over a night (or day when I'm out of home).
Btw. you're welocme to try my test procedure for fast tests (f.e. when new board comes). SuperPi 32M up to the result while Priming with large FFTs single thread. It's heavy demanding, not much can affect stability if this one pass.
Which Prime preset do you use for testing?
Which 'performance' option do you mean? ;)
Don't know about quad cores but I recommend 08.12 bios, latest non-beta.
I had no difference between 08.12 and 10.03 (latest beta) on non-plus board. Which cannot be said about plus version (for which I would recommend 10.03).
What about max FSB at non-plus version?
I've just got one, not installed yet but looking at "her" :D