DFI nF4 LP 7/4 new beta BIOS

Printable View

Show 100 post(s) from this thread on one page

07-08-2005, 08:10 AM
xgman

Quote:

Originally Posted by brandinb

ok this bios rocks my gskill tccd went from 300-303ish benchable at 2.5-3-3-6 to 310 rock stable and 315 benchable!! thats right ddr630 2.5-3-3-6 @ 2.8 volts all tight timings

now the bad side is while testing this out and achieving this wicked mem clock i got blue screen?? was like wtf now one mem module is broken and will get errors at any speed any setting but the other module is perfect and will still do ddr630 2.5-3-3-6 so im not sure if it was the bios or just my mems time to die but ... its dead lol

Well that just shows you the result of pushing the limits are not always without casualty
07-08-2005, 10:53 AM
suio

704-2 Bios Flash Failed (from Merlin's 510-2Mix to Oskar's 704-2)

This is the first time my system failed on a bios flash. The flash went smoothly without any problem. After I pressed F1, it beeped with no boot. I used "insert-reset" trick and broght the system back. We have two damage reports with this bios so far (damaged CPU and memory chip).
07-08-2005, 10:59 AM
Rezag1000

clear CMOS, My system didn;t boot either until I /cc'ed
07-08-2005, 10:59 AM
LORD

Quote:

Originally Posted by eva2000

Just tried 704-3 and seems my vdimm is overvolted

bios set 2.5v = 2.63v and 2.6v = 2.72v ??

So what's wrong with that? I seee it as, EXTRA volts is a bonus, if real.... :D LOL
07-08-2005, 11:01 AM
XiN

Quote:

Originally Posted by suio

704-2 Bios Flash Failed (from Merlin's 510-2Mix to Oskar's 704-2)

This is the first time my system failed on a bios flash. The flash went smoothly without any problem. After I pressed F1, it beeped with no boot. I used "insert-reset" trick and broght the system back. We have two damage reports with this bios so far (damaged CPU and memory chip).

A friend of mine has the same problem. He has flashed from 623-3 (without error messages).

He can't boot...

What's "insert-reset" trick?
07-08-2005, 11:08 AM
suio

Quote:

Originally Posted by XiN

A friend of mine has the same problem. He has flashed from 623-3 (without error messages).

He can't boot...

What's "insert-reset" trick?

Hold the Insert Key and then hit the reset button (next to the pwer button). I didn't have to clear the CMOS and it booted right up. The system is ultra stable after the incident with 704-2 bios.
07-08-2005, 11:12 AM
XiN

Thx a lot. I'll say it to my friend ;)
07-08-2005, 12:12 PM
MUCHO

Quote:

Originally Posted by suio

Hold the Insert Key and then hit the reset button (next to the pwer button). I didn't have to clear the CMOS and it booted right up. The system is ultra stable after the incident with 704-2 bios.

Pardon my ignorance but what and where is the insert key?

Thanks!

:D:D:D
07-08-2005, 12:17 PM
Flox

Quote:

Originally Posted by MUCHO

Pardon my ignorance but what and where is the insert key?

Thanks!

:D:D:D

The key on your keyboard named "INS"? ;)

Should have read this before sending back my old Ultra-D.

Had a non-posting board after reflashing from 623-3 to 510-1 (lost my onboard sound with 623-3).

But I´ll keep that in mind for the next time... ;)

Greetz, Flox
07-08-2005, 01:16 PM
pershoot

Quote:

Originally Posted by suio

704-2 Bios Flash Failed (from Merlin's 510-2Mix to Oskar's 704-2)

This is the first time my system failed on a bios flash. The flash went smoothly without any problem. After I pressed F1, it beeped with no boot. I used "insert-reset" trick and broght the system back. We have two damage reports with this bios so far (damaged CPU and memory chip).

you didn't flash properly. i have flashed up/down 7-10 times already within the past 2wks, from 704 to 510 to higher to 702 to modded/unmodded, etc, and haven't cleared CMOS either after bios flashes (using the 3 flash routine to forego the cmos clear) and have always POSTED.

use the bootable ISO for flashing or manually: awdflash /py /sn /cd /cp /cc /LD /R /f . always load optimised b4 and after a flash.

sorry for your loss.
07-08-2005, 01:19 PM
kiwi

pershoot:
Wanted to thank you for maintaining NF4 bios CDRom. It is very useful. Good job! :toast:
07-08-2005, 01:21 PM
xgman

Before anything else, if your board won't post after a upgrade to 7xx bios, clear the cmos and then boot again. It should be ok after that. Some bios versions require that and some do not. Just try the clear cmos before asking for help.
07-08-2005, 01:23 PM
pershoot

Quote:

Originally Posted by kiwi

pershoot:
Wanted to thank you for maintaining NF4 bios CDRom. It is very useful. Good job! :toast:

im glad the iso is workin out for ya:)
07-08-2005, 01:46 PM
suio

Quote:

Originally Posted by pershoot

you didn't flash properly. i have flashed up/down 7-10 times already within the past 2wks, from 704 to 510 to higher to 702 to modded/unmodded, etc, and haven't cleared CMOS either after bios flashes (using the 3 flash routine to forego the cmos clear) and have always POSTED.

use the bootable ISO for flashing or manually: awdflash /py /sn /cd /cp /cc /LD /R /f . always load optimised b4 and after a flash.

sorry for your loss.

Pershoot,

I have flashed this baby back and forth 50 times for the past 3 weeks. I never had any problem prior to this incident. I didn't lose anything. Just a simple "insert+reset" execution. I have heard your speech before and I did exactly what you described. There is always a risk in doing this and I will get a bios savior ASAP.

Thanks
07-08-2005, 01:52 PM
cupra

the 704-1 are bad for me, i will try the 704-2 that people say its better.
07-08-2005, 02:18 PM
pershoot

Quote:

Originally Posted by suio

Pershoot,

I have flashed this baby back and forth 50 times for the past 3 weeks. I never had any problem prior to this incident. I didn't lose anything. Just a simple "insert+reset" execution. I have heard your speech before and I did exactly what you described. There is always a risk in doing this and I will get a bios savior ASAP.

Thanks

good stuff, you didnt lose any hardware.

you stated you did the 'press f1 to reboot'. i bet you did not give all the flags and just did a /f. maybe a /sn. that would not be the proper way to flash (if you did it like that) so you did not do the method i described (still speculating here). you run in to trouble not giving all the necessary flags for a full clear. not all the time, but the trouble will come eventually.

/py /sn /cd /cp /cc /LD at the very least. /f is reccomended in addition. /R is nice & convenient to do as well.

this is why i created the ISO specifically for this. to thwart off bad flashes from the community, as it was getting abundant. i dont get why more people just dont use it. i cant make it anymore simple nor safe to flash without actually flashing for someone, hehe.

and ill probly keep giving the speech, if it keeps more people from bad flashes.
07-08-2005, 03:50 PM
suio

Pershoot,

You're right. I used the same procedure but different parameters. I will use your parameters from now on. Thanks Bro.
07-08-2005, 04:20 PM
xs64

Quote:

Originally Posted by stealth17

yeh its just the crappy mem controllers and i dont think the vtt issue on the dfi nf4 is helping with consistancy either.

what i hate the most is i can goto memtest #5 and get say 11 errors, ill restart with same settings and get 24 errors. its never consistant so its hard to tell if changing a setting is helping or hurting :(

xs64, try running your bh-5 at these settings

250mhz 2-2-5-2-7-15-0-2-2-1-3120-1

you will still need the voltage but at only 250mhz you will get pretty good performance. try that and your key might be tight but a bit slower. you can also try to get cas 1.5 which at lower speeds usually help me, and try for tras 4 or 0. LMK! :toast:

oh and about the bios, 704-2 is much more smooth than 702-2! no more hangs or anything! now time to do stability testing considering this like bh-5 bank interleave on and 702 didnt :p:

EDIT: 702 messed up my cpu temp sensor too...704 fixes :banana:

Finally , i can bench my BH5 at 281 3.7v :banana: , but not stable at all
Prime seems not like my CPU , so i'm running Folding at 275x9 3.6v and it stable rock :) :woot:

so thank you about your help
07-08-2005, 05:42 PM
suio

For those who has TCCD based memory chips and uses -2 bios, what DRAM slots do you use? I use orange slots. My system can't even boot into Windows with yellow slots.
07-08-2005, 06:00 PM
stealth17

Quote:

Originally Posted by suio

For those who has TCCD based memory chips and uses -2 bios, what DRAM slots do you use? I use orange slots. My system can't even boot into Windows with yellow slots.

every system is different. please dont ask these questions. ITS WHAT WORKS FOR YOU!!
07-08-2005, 06:01 PM
stealth17

Quote:

Originally Posted by xs64

Finally , i can bench my BH5 at 281 3.7v :banana: , but not stable at all
Prime seems not like my CPU , so i'm running Folding at 275x9 3.6v and it stable rock :) :woot:

so thank you about your help

folding wount tell you if your stable.

try to pass OCCT
07-08-2005, 06:06 PM
xs64

Quote:

Originally Posted by stealth17

folding wount tell you if your stable.

try to pass OCCT

Yep . i know folding is not good as OCCT or prime , but just because my Winnie is suck and it wont stable over 2.3Ghz :mad: , i have no choice man :(

So since i buy a new CPU ( maybe X2 :D ) and i dont play games or do something stress much , i just keep folding and saving money for new chip :D

edit : at lease with only this 704-2 bios , i can bench my BH5 @ 281Mhz :hehe:
07-08-2005, 06:10 PM
flexy

why are you people folding with instable CPUs ? Are you aware that you're submitting wrong results ? Folding is a distributed computing app, right ?
Or are you just folding for testing isntability ? Then rather use OCCT.

I always wonder what results people submit folding/seti etc. when their PCs are actually not even stable....i am just waiting for them to send a mission to a star (SETI) because they think there are alien signals coming from - but in reality it was just nonsese created by some overclocker's PCs.... J/K :)
07-08-2005, 06:25 PM
xs64

Quote:

Originally Posted by flexy

why are you people folding with instable CPUs ? Are you aware that you're submitting wrong results ? Folding is a distributed computing app, right ?
Or are you just folding for testing isntability ? Then rather use OCCT.

I always wonder what results people submit folding/seti etc. when their PCs are actually not even stable....i am just waiting for them to send a mission to a star (SETI) because they think there are alien signals coming from - but in reality it was just nonsese created by some overclocker's PCs.... J/K :)

If you know a little about folding , there is some Core is call Tinker and Gromacs Core

Tinker cores are fine for my system , it strees my system not too much and i can complete a good result . But Gromacs cores are hard to fold .
Just because of that , i always fold Tinkers :D
07-08-2005, 06:54 PM
stealth17

if they are bad work units then you dont get points when you submit them...thats all

Show 100 post(s) from this thread on one page