http://home.no/trac3r/dfi_lanparty_n...ultra_bios.htm made this today might be to help for someone.
Printable View
http://home.no/trac3r/dfi_lanparty_n...ultra_bios.htm made this today might be to help for someone.
i will update cdrom image tonight with 441's and the older 2 misc bioses which are missing from it.
Which is better, the 325 or 331-3 for bh-5? Anyone have any results. I got the 331-3 working great but in that list 325 says optimised for bh-5.Quote:
Originally Posted by NiCKE^
I don't know Smokin_Joe because my Winchester have been dead for about a month now :(
why is this thread not sticky? :confused:
I Agree!!!!!!!!!!Quote:
Originally Posted by Onepagebook
Should be sticky and why isn't OPB on his chat clients so I can ask him some questions ;)
I'll sticky this thread in the Best of AMD section tonight. I'd like for a few more people to see my post so that they'll know where to look for it.
Quote:
Originally Posted by conrad.maranan
Thank you buddy :toast:
Today i went to shop where i boguht my DFI SLi-DR for getting an replacement, but he wanted to test it, he also used an pair of OCZ VX PC3200 and it worked fine with Dual Channel, he did an bios update with some kind of BIOS, DRAM setting etc etc
I went home plugged it in to my system, but my own OCZ VX PC3200 kit cant run Dual Channel, i believe that my VX memory is an very early kit
The VX memory works just fine with Dual Channel in an MSI K8N Neo2
I think this this could be an BUG with all the "BUGGED" DFI S939 Boards, or not ??
3/4 of the posts on here were just about becoming sticky, too bad we cant go back and delete all of those =P
The link to the 331-3 bios seems to be broken. Can someone email me the file? Plz PM
Try here.:D Rebels Haven BIOS PageQuote:
Originally Posted by Quanticles
u da man =)
I aim to please. :D
refreshed cdrom image with 119, 316, 441-1 to 3.
Thnxs for the sticky...
Dragon
anyone experienced the 4.14 and newer versions? and any improvements on 3.31-3 esp. from vlad who aims to please :)?
Nope. Sorry but right now Im down I flashed from 3.13-3 to 4.14-1 & somethingQuote:
Originally Posted by rocka
went wrong :shrug: Luckly I had two spair chip's so Ill be up in a day or two. ;)
hey you guys like the idea of these added to the cdrom image:
NTFS support
a possible mini linux running prime95
network support (tcp/ip & SMB)
ramdrive/workarea support
cdrom support
??
i need to clean up the batch and reword the instructions also...
Guys,
I see many BIOS'es for TCCD, what do you recommend for my 512 x 2 PDP XBLK ?
I can't even hit 275 Mhz with the 3-25 BIOS. Can you guys please recommend something else?
Hi, I've got a problem, not sure if it's specific to the bootable BIOS cd rom, but i tried using it to flash my BIOS (since I could not get the Diamond Flash Image floppy to work, tried 3 different floppy disks that all read/wrote fine on another computer). I chose "load optimized defaults" and selected boot from cd rom in the BIOS prior to booting from the bootable cd rom. I saved and restarted the system, got into the flash menu and went for "flash 310" to flash to the 310 BIOS. It started writing the new BIOS, and got about 1/5 of the way, but suddenly there was an error message saying "your BIOS ROM is write protected" and the flashing process stopped. :mad:
I had no way of exiting the flash- program other than doing a reset, and now this message appears every time i try to start the computer:
"BIOS ROM checksum error
Detecting floppy drive A media.
INSERT SYSTEM DISK AND PRESS ENTER"
So I guess the BIOS ROM is screwed. I tried resetting the CMOS, but it didn't make any difference. I followed the flash procedures to the point (loading optimized defaults, selecting boot from cd rom, saving and restarting) as per this link on DFI-street and the first post in this thread. I hope any of you got a clever idea as to what went wrong with my flash. I will make a similar thread on the DFI-street forum.
Sincerely, Frodin
Tried to follow my AWDFLASH guide?
very wierd. thats a first. u can rescue with a floppy. make a bootable dos floppy and place awdflash.exe and bios file on there. then create an autoexec.bat file and in there put:Quote:
Originally Posted by Frodin
@echo off
awdflash.exe BIOSFILE.BIN /py /sn
replace BIOSFILE.BIN with filename
when it finishes clear cmos for a good amount of time.
Quote:
Originally Posted by pershoot
Thanks for the quick reply!
How do i create an autoexec.bat file? In the DOS- prompt when I boot from the floppy? (presuming it actually works... I remember fooling around in the autoexec.bat file in the win95 days, but never created one. )
I will be flashing the 310 BIOS, so I guess it will go like this:
@echo off
awdflash.EXE NF4LD310.BIN /py /sn
And then I put the autoexec.bat on the floppy with awdflash.exe and the NF4LD310.BIN file, and it will "autorun"? Sorry for the noob questions, I was hoping the bootable BIOS cd rom was actually going to spare me these dos command prompt parameters/ switches/ whatever they're called...
:D
And there's no "BIOS write- protect" jumper on the board is there? Never heard of it before, and it's not listed in the manual (yes, I've checked the *.pdf from the DFI website too)
the bios cdrom normally would save you from all this. however, in your case, it did not work.
create it in notepad and when u save it, toggle all files, and put a .bat in front of filename.
Ok, now I've created an "autoexec.bat" containing
@echo off
awdflash.EXE NF4LD310.BIN /py /sn
and saved it to a bootable dos floppy together with awdflash.EXE and NF4LD310.BIN. Will try it soon. Thanks again for walking me through the paramedics!
So what bios are you guys running with what ram or have tried and how have they worked if i get enough info i will add what i get to the first post.
Dragon
:mad: As some of You know some time ago this happened to me:
http://www.xtremesystems.org/forums/...ht=killed+BIOS
It was with the 331-1 and thanks God I had a second BIOS chip. That one was flashed with the 218 BIOS and when I threw it in all was workin' fine again. Bought a (new) second BIOS chip with 331-1 flashed unused so far.
Then flashed back the working one with the 218 to the 331-1 and still all was fine.
So yesterday I got my new ATI X850XT - shut down the rig, unplugged all and built in the new vid card. Fired up the system, board was starting, all diodes were O.K. and fans were spinning but no vid signal to the screen.
Hm - I thought maybe BIOS is not detecting the ATI card because my previous was a Nvidia 6600GT. Decided to clear CMOS and removed the battery.
Fired up the rig again, and....... long beeps, 3 red lite onboard diodes and a blinking power lite on the front panel. :eek:
Hm.., thought it was maybe caused by the new vid card - so I replaced it again with the 6600GT.
Same issue, no access to BIOS. Now I felt really pissed because the same thing happened to me twice.
Decided to throw in my brand new second BIOS chip with also the 331-1 on it, but no go !!! :stick:
So there is only one conclusion: Using the 218 helped me out before but two BIOS chips with the 331-1 on it refused to work.
Seems to me like the 331-1 can be flashed when rig is running, but after changing some hardware and/or after clearing the CMOS the 331-1 is not able to boot, maybe it has something to do with the BIOS boot sector.
Today I ordered two more BIOS chips ( :( ) with the last offical BIOS (310).
Should arrive on Wednesday - if they help me out like the 218 did first time there is definately something wrong with the 331-1.
Never cleared CMOS with 331-2 or 331-3 so I can't tell You if the problem will appear there also.
But be carefull guys - best is when using 331 and want to change some hardware to flash back to regular BIOS before.
Will keep You updated and cross Your fingers for me.......
Long offline periods - can only use the office machine yet...... :mad:
:toast:
Mine is slightly different. I flashed the bios from 310 to 310p. Immediately Windows had problems booting. Only way to boot is using Windows CD. So I decided to fix the problem using Windows Recover. Only to find out it not only it wont boot, but it had problems detecting my SATA's on RAID. Thought it was a faulty board.
Got another board from my mate who was running bios 310. I decided to flashed it again with 310p and the same symtoms appeared. So flashed it back to 310 and everything is working fine again.
BTW, where did you get the bios chips HCC?
My opinion of DFI boards has totally changed these past few weeks, with no posts ive got from 2 BIOS's.
It seems to happen a lot on both the NF3 and NF4.
I'm telling you guys, nothing is better than bios 2-17 yet :) Anyway, for the guy that asked for specs:
athlon 64 939 3000 0449 ccbhd at (9x275) 1.4 volts in bios
dfi ultra-d
g skill tccd 4400 LE 2x512
pcp&c 510 deluxe
And of course, I'm using bios 2-17.
Quote:
Originally Posted by HARDCORECLOCKER
Isnt 3 lights and long beeps a memory problem? Your bios and graphics card are problably fine, but you might have the memory in the wrong slots. Make sure to put your memory in the *orange* slots. If you have only one stick of memory, i think you need to put it in slot two. Try moving them around to find out.
Quote:
Originally Posted by neokenzo
You can order them online.
Just take the model number off the top of the chip and search for it online. If you cant find it then you can try http://www.digikey.com/
:confused: Didn't touch the mem at all - both sticks in the orange slots. But maybe You are right it has somethin' to do with it, yesterday I tried to boot 4 times - each time with a single stick in a different slot.Quote:
Originally Posted by Quanticles
With RAM in slot 3 or 4 the issue happened as before and the fan of my X850XT was running full speed (as in 3D mode).
With RAM in slot 1 or 2 it was different - only one red lite onboard diode and not long but short beeps.
No blinking power LED on front panel and reset was working but also no access to BIOS. The GPU fan speeded down to normal turns.
I also tried the Vdimm jumper on both rails - no go.
What I don't understand is I didn't even touched the jumper or the RAM before - only cleared CMOS and 331-1 is working no more.
I still wonder if it is caused by the Vdimm setting in BIOS - I left it always at 3,72. Maybe it should be set back to a normal normal voltage like 2,8 or somthing before clearing the CMOS.
Yet i happened after CMOS clear because I wanted to replace the vid card and some time ago it also happened after a CMOS clear when I swiched the Vdimm jumper and replaced RAM.
Tomorrow I'll get 2 new BIOS chips with the offical 310 - I really hope this will help me out.
As I said before - I also tried a brand new never used BIOS chip with 331-1 BIOS (I have a reseller of BIOS chips who flashes the needed version in stock)
and this chip doesn't work also.
The RAM is BH-5 and ran on my previous board at 3,9 Vdimm and now 24/7 at 3,72 - so I don't think it is damaged. It can even bare 4,1 Vdimm......
So I have no idea whats going on here, only thing I can say is that 331-1 was running perfectly with the BH-5 but it refuses to work after clearing the CMOS.
Any suggestions here? :confused:
:toast:
HARDCORECLOCKER, I have a similar problem. I'm spanish so I will explain as I can :s
In some cases my DFI does not boot (3 led on) When ithappens, it becomes nearly impossible to boot it clearing CMOS or trying with differente hardware configs (with one excepcion I will write later on this post)
My RAM is OVZ VX. I have tried with several combinations of hardware. My conclusion is that it has something with the board.
I've tried with different bios, 2 CPU, 2 VGA, different RAM and this is what happens to me:
- When I try any combination with a single stick or both sticks (orange slots), if the system boots, it works fine for 24/7 and it reboots normaly.
- When I shut down, when I try to start again, sometimes, it refuses to boot anymore. No matter if I clear CMOS, change sticks,... it doesn't boot. However, if I keep it off until next day, sometimes it gets fixed even if I don't change anything.
- This only happens to me with these modules. Like BH5, these sticks need high voltages and I use to run them at 3.5V, 3.6V. Anyways, I have problems even when I run them at stock speed/voltage. Currently, I have proved that when I can't boot the DFI with my sticks, it does well if I change them with a single no-branded DDR400 stick.
- I thought that it could be a memory problem algough they ran well on other mobos (different brand and chipset) I sent them to be tested at the shop where I bought them. They tested them on another DFI Ultra-D for some days, booting with different hardware and bios setups with no problem.
I think that MY DFI has something with these modules. It is not something that happened to me from the first day. It came later. I am completely desesperated.
Currently my system is running and I try to avoid shutting it down. :stick:
Nforce4 Ultra-D DFI
W3000+
2x512 OVZ VX 3200
Radeon X800XL
OCZ PowerStream 520W (The same as Hardcoreclocker)
...
For the guy that asked LOL I made the thread I am trying to collect info about the bios...and how well they are dooing...but i agree the 2.17's are to me the best bios...Quote:
Originally Posted by fareastgq
Hardcoreclocker...I havn't heard of this problem before...I will put a warrning next to that bios and possibly the 310p...I have theory about why these to are making problems I will look more into it though...and if I am right then there may be more then just those 2 bios may cause trouble...idk I will look into it if I find nothing then I just wont post it...
Dragon
I heard the 3.16 bios should be the best one but that just what I heard.
:D Mate - I appreciate that. Believe me, it happened to me two times and I did nothing but a CMOS clear after changing some hardware.Quote:
Originally Posted by FireDragon
And now we also know that the issue is gone after flashing the same BIOS again........ :stick:
So I really got the feeling that clearing the CMOS destroys something in the BIOS - maybe in the boot sector.
And......., the 218 worked for me the first time, the 331-1 did not, even my second BIOS chip with 331-1 refused to work.
So keep us updated what You'll find out - there must be somthing..... :slapass:
:toast:
:toast:Quote:
Originally Posted by Onepagebook
http://www.vozforums.com/attachment....chmentid=17498
HCC, how are you flashing the bios? are you remembering to clear ALL when flashing? i have never encountered this issue, and have cleared cmos while over 3.2, while swapping jumper, swapping ram, cross flashing up/down, etc., etc.
use these flash strings when flashing:
awdflash BIOSFILE.BIN /py /sn /cd /cp /cc /LD /R /f
replace BIOSFILE.BIN w./ bios filename. remember that will reset the machine on its own after done (load optimised once your back in, and always load optimised b4 flashing). if you don't wanna mess with typing, just dload the bootable cdrom and at the prompt type a keyword from 'legend' to flash the bios you would like.
Well.. one light means the CPU, RAM, and VGA have all been detected. I'm not sure if bios starts running before or after all of that stuff, but i'd imagine before... =/
You could go to dfi-street and put a post on their forum. If they cant figure it out they'll have an engineer contact you.
This might be a dumb question, but did you put the BIOS chip in the right way?
i always use winflash :>
I don't have a floppy drive and I was wondering how do I use winflash to flash the BIOS of my DFI Lanparty Ultra-D? Thanks!
P.S: Is the 3.10P bios still the best to use with my Patriot PC3200 Ram? It's TCCD based.
you can use my bootable cdrom for flashing. u can find a link to this in the first post.
Quote:
Originally Posted by Sgt_Strider
Just download the program and try to use it. It's xtremely straight foward. =)
Have 3-10 Bios boots up fine but get BSOD. Should I try Oscar Wu 4-14 3 Bios has anyone else had this problem?
ADA3800DAA4BP
CBBLE 0507 DPAW
3.10 has been fine for me. :shrug:
Just got my Venice 3000+ but for some reason overclocking isn't working, it might be a bios thing since I'm still using stock bios. Anyways, is 4.14-3 still being hosted? I can't get it to dl. Can I get it anywhere else?
Thanks a lot!
Thanks for the link!
i changed the driver on the bootable cdrom due to the previous driver that was being used not working on the small population of user's cdroms.
fiedragon you have a typo next to bootable cdrom on your post. it should be 4/14 not 4/1. lettin you know.
also, the floppy link would be: Bootable Floppy
you have a shortened link there which doesnt work.
i downloaded the cdrom iso but it doesn't work
At the boot, it enters correctly in the menu, i see all the versions of BIOSES, i type the one I want to flash and it enters the awdflash screen and seraches the file in z: :eek:
but it reports a no disk error and cannot flash anything
what's wrong?
the driver doesnt detect your rom. i recently changed the driver for another one, to try and attenuate for all the roms out there, but i guess that was futile, hehe.
please reply back with your brand cdrom and model #. if i cant find a driver which works for everyone 100%, i will put together a mini ISO for the small population of users that have the issue, which would contain 2 or 3 of the latest bios files.
i have
- DVD-ROM Toshiba SD-M1712 firmware 1004 on the first IDE channel as MASTER
- DVD-RW Teac DV-W50D firmware 1.07 on the second IDE channel as MASTER
do you think i'll have more luck if I upgrade the firmware of the Teac to that of Pioneer 106 (the are the same model)
thanks for the help
:)
The CD also doesn't work with my drives, with the same problem (Z: drive non-existant). They are, as listed in device manager:
_NEC DVD_RW ND-3500AG
TOSHIBA DVD-ROM SD-M1302
Updated my website with the DFI bios's so they are there now.
New 5/09 and 5/10 betas out:
http://www.techpowerup.com/articles/other/114
so which of new 5XX is good for TCCD and in orange slots ?
i refreshed cdrom image with 510-1 to 3.
i refreshed cdrom image with 509-1 to 3.
Thanks for adding the new BIOS files to the ISO pershoot :)
510-1 is a bit more agressive and 510-3 for some quick default settings and a bit easier to tweak.Quote:
Originally Posted by TEDY
changed driver back to initial one used. it was better and had better compatiblity.
Where can I download this cdrom image... is it the one in the first post? (Just wondering because it doesn't say 510-X anywhere. :) )Quote:
Originally Posted by pershoot
in the 1st post or, http://www.dfi-street.com/forum/show...45&postcount=3
Thanks! :toast:Quote:
Originally Posted by pershoot
Just made a few updates put in the new 5.09, 5.10 bios that both add X2 support with the 5.10 it adds a new future for value ram that adds it.
Dragon
Can someone help me out and what bios they recommend for the following setup:
3000+ venice
dfi ultra d mobo
ocz vx gold 3200 512x2mb
OCZ 520w powerstream
ATI X800xl pci-e
Thanks Im clueless on this..
I was getting errors in Memtest at a measly 215HTT 1:1 with my set of PC3200 GOLD fresh from the RMA truck with the 331-2 bios...
Flashed to the 510-3 bios & it changed one of the settings in the bios (TRTW was changed from 2 to 3) & now I get higher bandwidth as well as being able to run Memtest with Bank Interleave set to "enabled"...
Still early days yet cos I've had major problems with BSOD's & random reboots before... Just found out that it was either the latest nVidia chipset drivers or SP2 that was giving me hell...
I just finished reformatting my RAID-0 & re-loaded XP with just SP1 & the older 6.39 drivers...
Just been through an 18+ hour session of Prime95 at 217HTT... Gotta up the volts & OC now that I got XP to play nice...
Here's a pic of AMD64 Tweaker settings that I'm using... No Windows tweaks, just through the bios atm... I have yet to shove more than 3.2v into my RAM...
Had this DFI for over 1 month now but have always had problems with either the reboots/BSOD's or flaky RAM... Now that I have some half decent RAM & no more crashes, I can see what all this fuss with the DFI/Winbond RAM is all about & I'm liking it...
I have good luck with the 2.17 unless you are running Venice/SD or X2 then I would give those a try they are my favorite bios...But if you are havving good luck with thos then hey why not!!
Dragon
I use WinFlah to flash bios and I usually flash boot block a main block but I skip DMI block ... Is it right?
Is it dangerous WinFlash? I find it very pratical...
well guys, I just got done 3dmarking 510-2 bios, now I'm set at 9x285, using the same settings as the 2-17, except tref is now 3072 instead of 40**somthing. main timings are still 2.5 3 3 6. Not bad, about 10 more mhz on 1.45 volts for 3dmark2001 stable. Also, winflash is a very good prog to use, just don't do it unless you are running stock settings, DO NOT do it while your settings are oc'd :) 3dmark score with a vanilla 6600 gigabyte was about 19,500ish, don't remmeber exact score.
whats reguarded as the most stable / compatible bios?... im not OC atm... all stock.. thnx :confused:
Hey the link to the 510-1 bios is really 3 and vise vera if you want to correct that?
Bourch and Hardcoreclocker: I have same situation here as you two.
Nghhh...I posted my problems at different thread. Hopefully, members over there won't angry. So now, I am clear that is my Bios that caused problems.
Both of you has get rid of the problmes? Pls guide me in my problems. . I am using Bios 310 (official) and problems occured so I flashed it to Bios 331-1 (oscar wu), but same problmes, too. Too bad if my Bios ROM is faulty. I don't know can I RMA the mobo becuase of the BIOS ROM's faulty. Really appreciate your help and I need your help desperately. Thank you in advance.
OK, thnxs for that i just fixed the links
Dragon
Please amend this line:
"Bootable CDROM (ISO) DOS Image w./ All Bios Revisions to Date (5/10/05)"
The best bios for the sli-dr and VX PC-4000? Stick with 310 or is a 510 better? Which one?
which one ois better then. The 510. Should I try the 510-3, 510-2??
The 510-2 would probably be better, the 510-3 is considered a "general" bios, but seems to treat TCCD alot better than it does UTT
Quote:
Originally Posted by pershoot
Do you want me to change it? To?
Dragon
If you want you can just PM
Thank for the so cool thread. Can we flash the BIOS using the WinFlash utility? I think it faster and simpler than using the floppy which has an unstable quality.
You guyz may download the WinFlash here.
BTW, I wanna ask is there any version of BIOS which implemented the MemTest86 into it?
bootable cd not workin for ya?Quote:
Originally Posted by Publ!k En3my
Quote:
Originally Posted by pershoot
I dont have a burner to burn the boot image to CD :((. So I choose WinFlash :d
Winflash is fine that is what i always use to do my flashing with...
dragon
i flash off hdd now via awdflash method. i cant boot off cdrom on the 510's, due to it it not 'properly' detecting my cdrom for booting purposes.
cdrom image has been updated with hellfire's (dfi-street) 510-2.
whats this new 510-2?
i have the first 510-2 that came out, whats new with this 'hellfire' one?
common bug, its voltage related. i hear oscar has bigger issues so wont be fixing it for a few weeks at least.
trick is to hit ins (the zero on the numpad) and hold it just after powering system, PC loads at stock settings without saving them....
get into BIOS, lower your multi 2-3 notches. (so its roughly stock Mhz) reboot, and raise it back and it should be fine from then on.
its just a cold boot bug where the startup voltage doesnt set right, i beleive.
Can someone answer, has anyone gotten better results by going back from 5/10 2 bios to the 3 bios?? I cannot get my 3000+ venice over 2300mhz stable with this 5/10 2bios..
try running it at 2T
Basically, word is that most beta bioses for venices dont like running 1T overclocked yet.... will be worked out in final versions. so try 310, 316, or set it to 2T
The cold boot issue is something they know about, know the cause of, but don't have the TIME to fix it?Quote:
Originally Posted by Mussels
Am I reading this right?
something like that, yes. its a beta bios not a final. 310 (final) seems to work without this, i assume it would be fixed in the next BIOS or two. (as very few people seem affected anyway)
2t im not familir with this??Quote:
Originally Posted by Mussels
Very few people are affected by the cold boot/ 3 led syndrome?Quote:
Originally Posted by Mussels
You must be kidding me......
There are a BOATLOAD of folks having boot issues with this board.
It should have been fixed already.
There is a thread here, that is NOT even about the boot problems ( AN8 thread I think), where at least 3 folks complained about it in there, there are threads here, amdmb, OC,dfi etc... discussing this problem.
This problem is bigger than they think, and they know about it ( although they can't reproduce it :rolleyes: ), yet it's not important enough to support folks that already spent money on this buggy board?
What good is a board that ya have to fight with everyday when starting it up?
I never saw any print in the manual stating ya had to leave it on 24/7 to keep it running.
Anyone else see that in the manual?
Didn't think so.
Don't mean to sound off on you, but if what you are saying is true, then thats just plain BS.
Either that or we are talking about something completely different.
Good Day
m
its a memory timing. also known as CPC. 1T is CPC on (enabled) 2T is CPC off (disabled)