Bios 131 specifically adresses boot issue with certain type of ram, maybe give a go to 131 bios.Quote:
Originally Posted by goddh0r
Quote:
1. Fixed IR connection failure.
2. Fixed Boot failure when installing certain CL2 memory modules.
Printable View
Bios 131 specifically adresses boot issue with certain type of ram, maybe give a go to 131 bios.Quote:
Originally Posted by goddh0r
Quote:
1. Fixed IR connection failure.
2. Fixed Boot failure when installing certain CL2 memory modules.
that could fix my problem too, mushkin bh5 running well @ 250 1:1 1,5-2-2-0 but setting to 300 @ 166 divider = 245 RAM / hangs at device list boot screen. try it today eveningQuote:
Originally Posted by Blindbat
Its scary how many problems there are already, and half the world don't even have it yet. Although I must admit, people are getting better results than the Asus. Let's hope its just the first few batches that has these problems (sorry guys). Although I find it odd that the beta testers didnt seem to have these problems.
Quote:
Originally Posted by situman
Not really. No offense to anyone in specific, but there is no accounting for the experience, skill level, and supporting equipment of those trying out these boards. I always find that I, personally, have much fewer problems with new kit than those folks who report lots of trouble in the early stages.
Heck, even my Asus SLI is a better board than everyone indicated. I bought it as a "fill in" until the DFI showed up, but I've grown to appreciate it a lot. Not the best OCer HTT wise, but a good all around mobo.
Just food for thought.
Beta testers are mostlikely the ones that have identified the problems, contrary to normal procedures they have given us a glimpse off their results, but stated from the start... ~ Beta, hence the work and time invested by them, in order for stable boards to be delivered to us.Quote:
Originally Posted by situman
Hence the delay in shipping boards, and fast maturity of bioses beeing release.
A big thank you to them, and faith in DFI for doing what they do promptly and efficiently.
I am convinced they want to deliver another winner to the market place !
they might get tweak versionQuote:
Originally Posted by situman
:toast:
:confused: I wish I only could be half as optimistic as You...... :toast:Quote:
Originally Posted by Blindbat
At least DFI tries to get it right before shipping. As we all know most don't.
:D Yep - that I also see so far - it depends on the point of view.... :toast:Quote:
Originally Posted by xgman
Im still waiting patiently for these boards to come out and then patiently wait for the prices to drop, lol. Don't really plan to go Nvidia SLI, but I guess I will see what the ATI or even VIA has to offer in terms of "SLI" functionality. Just want a good step-in into the AMD64 world.
so did 131 put memtest and cpu test into the menu or is it still not there?
Still didn't see it yet :mad:Quote:
Originally Posted by P_1
finally i discovered whats going on:Quote:
Originally Posted by FallenAngel
the dfi got trouble using dividers somehow, if i go for 10x280 and mem@333 its a nogo, bluescreen PFN_LIST-CORRUPT, if i set the mem back to 400(which i didnt try before, cuz i thought well with ddr333 im on the safe side anyways), everything's fine, can boot into windows and run applications. This issue still persists with the new bios 131.
I check 1-31 bios the metest86 & CPU test is still in there... maybe oskar forgot to put it in bios menu :(
Anyway here is some voltage information for DFI nForce4 :toast:
Code:#include CPU_VID_Control.h
{
Auto
0.800V
0.825V
0.850V
0.875V
0.900V
0.925V
0.950V
0.975V
1.000V
1.025V
1.050V
1.075V
1.100V
1.125V
1.150V
1.175V
1.200V
1.225V
1.250V
1.275V
1.300V
1.325V
1.350V
1.375V
1.400V
1.425V
1.450V
1.475V
1.500V
1.525V
1.550V
}
#include CPU_VID_Special_Control.h
{
Auto
Above VID * 104%
Above VID * 110%
Above VID * 113%
Above VID * 123%
Above VID * 126%
Above VID * 133%
Above VID * 136%
}
#include LDT_Voltage_Control.h
(
1.20 V
1.30 V
1.40 V
1.50 V
}
#include DRAM_Voltage_Control.h
{
2.50 V
2.60 V
2.70 V
2.80 V
2.90 V
3.00 V
3.10 V
3.20 V
3.30 V
3.40 V
3.50 V
3.60 V
3.70 V
3.80 V
3.90 V
4.00 V
}
#include Chip_Set_Voltage_Control.h
{
1.50 V
1.60 V
1.70 V
1.80 V
}
:D For me, personally, it doesn't matter - can download it everywhere.Quote:
Originally Posted by P_1
IMHO there are a lot of more important unanswered questions, f.e. why does nobody ecxept OPP and OPB can do 300+ ???
:toast:
well ive never seen a dos based cpu tester b4. i remember some french site wanted to make something called cputest86 but it never got released?
:D Ah, SRY - now I got You - talking about DOS based....., hm, is there any advantage compared to the windows based versions?Quote:
Originally Posted by P_1
:toast:
not corrupting your hd? ;)
are there indee so many ppl havin trouble? i didnt try much more than 300, but 9x300 was working flawlessy...Quote:
Originally Posted by HARDCORECLOCKER
maybe some people got the non fixed fubarred boards? :down:Quote:
Originally Posted by goddh0r
Got a board from the latest shipment arriving today and it came with BIOS Jan 25. Revision is still A01. Unofficial word is that even the boards from the first shipment last week has been implemented whatever changes necessary. That's why there was a 2-day delay in getting those boards out last time.
Updated with BIOS 1.31 and performance is at least on par with 1.26. Managed to run FX-55 at 10x290 and 9x320 with 1.6v vCore and finished typical benchmarks - SuperPI and 3Dmarks. So far, it's running great with no instability problems at all. :)
Link: http://premium1.uploadit.org/WaterGun//9x320s.JPG
marquzz over @ techsweden.org has a beta board (i think, he atleast has a SLI-DR) and he tested 400fsb and it worked perfect, so is it the newer cards that can run high fsb or is it the review samples? :confused:Quote:
Originally Posted by HARDCORECLOCKER
Bios embebed apps are a good way to test OC if you are near the hardware limit. Running these apps without booting into windows can prevent you corrupting the OS. It also saves time as you don't need to wait until windows boots each time you get BSOD :banana:
Still waiting the reply from bytesatwork :confused: Can't wait anymore
:brick:
Coluld someone test wich mem dividers are causing problems?
Bios embebed apps are for newbs. We've been overcloking for years without it, do things the old fashion way and just overclock like your supose to. Overclocking isn't for everyone!Quote:
Originally Posted by Bourch
OPP
Nice put OPP ;) Guess have to wait untill everyones here put their cpu on this mobo..
:slobber: Anybody remember this (#70):
BETA sample MOD ???
:toast:
What your saying doesnt make sense. How does using embedded apps make one a newb? :rolleyes: With an embedded app you can test your ocs quicker with no risk of corrupting your hd. This saves the trouble of using a spare hd to test your overclock. With an embedded bios you can start testing your oc's much quicker, therefore making the overclocking proccess more efficient. It doesnt make overclocking easier at all, one still needs to know what they are doing, you cannot just say "OOOOOO I HAVE AN EMBEDDED APP IM A SUPER OVERCLOCKER NOW"... no it doesnt work that way, embedded apps are just tools for overclockers it doesnt replace experience, just makes the proccess smoother for people that know what they are doing.Quote:
Originally Posted by OPPAINTER
Yes it does replace experience.:DQuote:
Originally Posted by P_1
Overclocking takes time and patients. You need to check for both your Max CPU speed and your max mem speed and get it right, and this needs to be done in small increments.
You don't just throw a bunch of numbers in the bios and hope for the best.
OPP
Who said anything about using random numbers? And if you do use a bunch of random high numbers the board just wont boot and in the worst case(some tard that uses 4v for their ram and 2.1v for their cpu by "mistake") fry their hardware. So in the end it still doesnt replace experience. If you dont like embedded apps, OK. But several other people, including me, welcome this feature.Quote:
Originally Posted by OPPAINTER
Can your little app do this for you, I don't think so.Quote:
Originally Posted by P_1
OPP
13x267, OCX VX at 2-2-2-5
http://www.xtremesystems.org/forums/...id=23729&stc=1
LOL... I'm waiting for the day when 3d mark 2001 is built into the bios, and using advanced algorithms, will know excatly what your score will be before you even run the benchmark.Quote:
Originally Posted by OPPAINTER
I get embebbed apps like an aditional resource with helps in some situations. I will use them for quick tests in the begining, until I familiarize with new hardware limits. Once I am on the good way, back to prime stress and 3dmark loops. Anyway I don't see them as a replacement to the old fashion methods.
I wish to speak a more rich fluid English an of course with a richer vocabulary :(
:mad: O.K. - enough is enough - come down guys - this is not the place to win a boxing championship..........
:toast:
Oskar already install it in 1-31 bios... maybe some1 should ask him how to execute the program :toast:Quote:
Originally Posted by P_1
Code:CBROM V2.07 (C)Award Software 2000 All Rights Reserved.
******** nf4ld131.bin BIOS component ********
No. Item-Name Original-Size Compressed-Size Original-File-Name
================================================================================ 0. System BIOS 20000h(128.00K)12ABCh(74.68K)NF4LD131.BIN
1. XGROUP CODE 0E9A0h(58.41K)09E6Ch(39.61K)awardext.rom
2. CPU micro code 01800h(6.00K)0024Ah(0.57K)CPUCODE.BIN
3. ACPI table 05E71h(23.61K)01F7Fh(7.87K)ACPITBL.BIN
4. YGROUP ROM 0F760h(61.84K)0465Ch(17.59K)awardeyt.rom
5. GROUP ROM[ 0] 07BF0h(30.98K)032E5h(12.72K)_EN_CODE.BIN
6. Other(40B5:0000) 02140h(8.31K)00CE4h(3.22K)_ITEM.BIN
7. OEM0 CODE 021C0h(8.44K)008FCh(2.25K)BSMICODE.ROM
8. PCI driver(A) 0C000h(48.00K)064B3h(25.17K)NVRAID.ROM
9. PCI driver(B) 10000h(64.00K)07B05h(30.75K)NVPXES.NIC
10. PCI driver(C) 0F000h(60.00K)071FBh(28.50K)r5_5137.bin
11. LOGO BitMap 4B30Ch(300.76K)059D5h(22.46K)LPLOGO.BMP
12. OEM1 CODE 00090h(0.14K)000AFh(0.17K)MemSetup.rom
13. OEM2 CODE 14628h(81.54K)07F69h(31.85K)MemTest.rom
14. OEM3 CODE 14668h(81.60K)0827Fh(32.62K)CPUTEST.rom
Total compress code space = 5C000h(368.00K)
Total compressed code size = 52831h(330.05K)
Remain compress code space = 097CFh(37.95K)
** Micro Code Information **
Update ID CPUID | Update ID CPUID | Update ID CPUID | Update ID CPUID
------------------+--------------------+--------------------+-------------------00000000 00000000 0039 0048| 00000000 00000000 003A 004A
00000000 00000000 0041 0150|
:D Hey OPP - we all know and respect Ya fantastic record - but everybody had been a beginner once and nobody's perfect, do You see ?Quote:
Originally Posted by OPPAINTER
BTW - more interesting if the board You use is a stock one or a BETA sample MOD, can You clear it up ???
:toast:
Well, while I'm at it:D
This mem test thing people use, whats up with that:D
I've never used mem test in my life, never will. They should have left that app in the memory Labs. I hear people complain about not being able to pass mem-test all time.
Who cares about mem-test, I sure don't need it.
Alright, I'm done complaining about these Overclocking apps now:D
OPP
:D I agree - especially because memtest is not a real help for me - got it error free but rig didn't boot at all so something's wrong with it.Quote:
Originally Posted by OPPAINTER
Can You answer the question depending Your board?
:toast:
DFI Boot Up logo :toast:
http://www.xtremesystems.org/forums/...chmentid=23753
Well then beginers should read the "How To Overclock Guide 101" then. Like most of us did.Quote:
Originally Posted by HARDCORECLOCKER
I have no Idea about my board. I can tell you it doesn't have the final mods on it though, they are supose to send one of those to me this week.Quote:
Originally Posted by HARDCORECLOCKER
The board I have here runs great, rock solid, 4V mem works all that.
OPP
thats nice! :slobber: :toast:Quote:
Originally Posted by tictac
DFI PC Health Status :toast:
DFI Memory OptionCode:CPU Core Voltage :
LDT Bus Voltage :
ATX +3.3V Voltage :
ATX +5.0V Voltage :
ATX +12V Voltage :
Chip Set Voltage :
DRAM 2.5V Voltage :
ATX +5VSB Voltage :
Battery Voltage :
CPU CORE Temperature :
PWM AREA Temperature :
CHIP SET Temperature :
CPU FAN Fan Speed :
FAN 2 Fan Speed :
CHIP SET Fan Speed :
There are many more... too lazy to check them allCode:Command Per Clock (CPC)
Auto
Enable
Disable
CAS Latency Control (Tcl)
Auto
1.5
2.0
3.0
3.5
1.0
2.5
4.0
4.5
RAS# to CAS# delay (Trcd)
Auto
00 Bus Clock
01 Bus Clock
02 Bus Clocks
03 Bus Clocks
04 Bus Clocks
05 Bus Clocks
06 Bus Clocks
07 Bus Clocks
Min RAS# active time(Tras)
Auto
00 Bus Clock
01 Bus Clock
02 Bus Clocks
03 Bus Clocks
04 Bus Clocks
05 Bus Clocks
06 Bus Clocks
07 Bus Clocks
08 Bus Clocks
09 Bus Clocks
10 Bus Clocks
11 Bus Clocks
12 Bus Clocks
13 Bus Clocks
14 Bus Clocks
15 Bus Clocks
Row precharge time (Trp)
Auto
00 Bus Clock
01 Bus Clock
02 Bus Clocks
03 Bus Clocks
04 Bus Clocks
05 Bus Clocks
06 Bus Clocks
07 Bus Clocks
Row cycle time (Trc):
Auto
07 Bus Clocks
08 Bus Clocks
09 Bus Clocks
10 Bus Clocks
11 Bus Clocks
12 Bus Clocks
13 Bus Clocks
14 Bus Clocks
15 Bus Clocks
16 Bus Clocks
17 Bus Clocks
18 Bus Clocks
19 Bus Clocks
20 Bus Clocks
21 Bus Clocks
22 Bus Clocks
Row refresh cyc time(Trfc):
Auto
09 Bus Clocks
10 Bus Clocks
11 Bus Clocks
12 Bus Clocks
13 Bus Clocks
14 Bus Clocks
15 Bus Clocks
16 Bus Clocks
17 Bus Clocks
18 Bus Clocks
19 Bus Clocks
20 Bus Clocks
21 Bus Clocks
22 Bus Clocks
23 Bus Clocks
24 Bus Clocks
Row to Row delay (Trrd):
Auto
00 Bus Clock
01 Bus Clock
02 Bus Clocks
03 Bus Clocks
04 Bus Clocks
05 Bus Clocks
06 Bus Clocks
07 Bus Clocks
Write recovery time (Twr) :
Auto
02 Bus Clocks
03 Bus Clocks
Write to Read delay (Twtr):
Auto
01 Bus Clock
02 Bus Clocks
Read to Write delay (Trwt):
Auto
01 Bus Clock
02 Bus Clocks
03 Bus Clocks
04 Bus Clocks
05 Bus Clocks
06 Bus Clocks
07 Bus Clocks
08 Bus Clocks
Nice bios... oskar wu :toast:
:D THX OPP ;)
@TICTAC:
Why don't You ask OSCAR about the embeddet thingies.......,You're not so far away :banana:
:toast:
For me oc is just for benchmarking...simple (and no memtest, pifast etc...those are for the labs). As long as it stable and can finished benching with the highest vcore/htt/fsb and highest core/mem on vid. card then is ok. :toast:
Hexus PiFast 4.3 in dos kernel would be cool :toast:Quote:
Originally Posted by HARDCORECLOCKER
OPP, nioce put, you're quite right, except for that memtest. If you're looking for a 24/7 stable rig, you simply need it when you OC.
Gotta 24/7 rig right here at 270x10, runs flawless.Quote:
Originally Posted by Alexandrus
OPP
Hey, why you guys all want to go back in DOS?:D
Seriously I dont think we need those. The challenge is to be able to get it stable for the bench, which runs in windows. If it is stable DOS who cares?
Well said my overclocking brother :toast:Quote:
Originally Posted by skate2snow
OPP
somebody used dividers already ? i got same problem with ddr333, have to test new bios now. what type of rams do you use ?Quote:
Originally Posted by goddh0r
psycho303
All the dividers worked fine for me on my board, I tested them with VX memory.
OPP
Usa says boards arriving Tues. :)
flashed 131 now, and it WORKS ! :banana4: can run my mushkins bh5 with 333 divider now ! good work DFI !Quote:
Originally Posted by psycho303
CMOS reloaded is one of the most inovative features :toast:
hope cpu/memtest comes soon :)
im using Geil Ultra-X, and the issue is only occuring with multiplier 10, multiplier 9 is working fine with ddr333 dividerQuote:
Originally Posted by psycho303
I too don't know why everyone is so obsessed with prime and memtest.. Both take way too long, and I normally can't wait more than 5 minutes.. You can have a peace of mind much quicker by running Lobby Hi or SP 1m, then, if you really want to get fancy, you can run a 32m run..
Tictac, are BIOSes in C++? I noticed the #include parameter...
your idea of overclocking is different from mine. Mine is to get the highest clock while being stable at everything not just a bench to get the top score. I want a clock that performs under everything not just a single app. So im betting u never used prime 95 either, cpu tester would be just like prime 95 taht just doesnt load from windows.Quote:
Originally Posted by OPPAINTER
:D If You ever tried to run a 3D mark with Ya rig You wouldn't have to give such comments here - or do You think OPP's rig went through it without beeing 100 % stable ???Quote:
Originally Posted by P_1
:toast:
err i can run prime 95 while running 3dmark and 3dmark wouldnt even fail while prime does shortly after. In my experiences 3dmark stable doesnt mean your stable in every app.Quote:
Originally Posted by HARDCORECLOCKER
:D Hm - never made that experience - thought it always was a hard job to pass 3D mark without any errors........., BTW I use SuperPI to test stability,the quick 1M for a fast check of new settings and 32M in the end.Quote:
Originally Posted by P_1
:toast:
I dont understand you. OPP is one of the biggest overclocker, and you argue with him on the subject of what is overclocking / how to overclocking / which utility to use?
And from another of the biggest overclockers rig (Hipro5 sig...) : If you can read this, then you aren't "well" Overclocked yet...!!!