fatal1ty fp-in9 sli

[s_noopy]

ok. feeling little noobish - what is:
- NVMM?
- PECI function?

[miesso]

i've just downloaded these new bioses and the instructions to upgrade are these:

a. Create a MS-DOS startup disk.
b. Extract all files in the operation system.
c. Copy the files to startup disk.
d. Boot into MS-DOS.
e. Run "runme.bat"

does it mean that using awdflash to upgrade is not possible?

[IkariGend]

i've just downloaded these new bioses and the instructions to upgrade are these:

a. Create a MS-DOS startup disk.
b. Extract all files in the operation system.
c. Copy the files to startup disk.
d. Boot into MS-DOS.
e. Run "runme.bat"

does it mean that using awdflash to upgrade is not possible?

No, you can use awdflash. The thing is, if u use runme.bat this batchfile starts an other batchfile und gives that the name of the bios file, and then the second batchfile guides you through the awdflash-process by just typing the lengendary "any-key"

[miesso]

well...i've just flashed using "flashmenu"....

it's strange but i can't even get my machine to boot when my fsb is @400....and @425 it does boot, but there's a huuuge vdrop (according to cpuz)

i'm using 1.525 in bios (to 8x425mhz) and cpuz shows me the vcore floating from 1.36v to 1.46... very weird.... lower vcores have no such drop...1.425v has dropped to 1.38 during orthos (cpu@3.00ghz)
and i've also realized that i need to increase my cpu vtt an my nb voltages to 1.43 so i can boot...

when running @ 8x425 (vcore-1.525v in bios, nb and vtt - 1.43, and memory @ auto) i'm getting errors in super pi 1m, in the third loop ("NOT EXACT IN ROUND) what could be doing that? my memory is 667 and in this config it's running @661mhz...

[BUFF]

it's strange but i can't even get my machine to boot when my fsb is @400....and @425 it does boot, but there's a huuuge vdrop (according to cpuz)

strap change

[BUFF]

BIOS release V14 for FP-IN9 SLI

Release information:

[ENGLISH]

1. Correct the PECI function.
2. Fixed the issue where the system may not boot when P4 EE installed.
3. The FanEQ function now works as intended.
4. Update NVMM to V4.072.28.
5. BIOS compiled date: 06/07/2007.

ftp://ftp.abit.com.tw/pub/download/b...li/m624b14.zip

[ollie27]

Hey, I have flashed to bios 14 could no longer boot at my old speed of 2.4GHZ same settings as i used with beta 13 but wouldn't boot even with more voltage increase. Set voltages back to how i had them running beta 13 and clocked up to 3Ghz and guess what it boots up and is stable STRANGE. Another problem i have found is that now my motherboard reports my cpu temps to be 10c higher than before even at stock volts/clocks? Is it possible that it is giving me the wrong readings? Using Abit EQ and everest to monitor temps and both report 10c+ increase. Anybody else notice this using the 14 bios. Thanks guys

[CptGrey]

I've been using Beta 1.4 since it came out. I assembled and installed my system under 1.3, but only started to OC under 1.4. Everest UE has been reporting my CPU maxing at 55-56C during stability testing, so that seems right. I've got a great HSF but I don't think I it was keeping my temps that low with room temps of 24-27C.

Since I've only been able to hit 356 FSB and stay stable, should I go back to 1.3?

I'd really like to push it to 400-425...

[SM0k3]

has anyone been able to hit 3.4ghz or 3.6ghz on the e6600 with this board?

I have mine O/C'd to 3ghz but anything higher and its only stable for a short time before I get random restarts and crap.

[ZuluZ0mbie]

I've got a E6700 currently stress testing at 3.5...

I find I've got to really up the NB voltage else I get screen freezes and random restarts.

Bios voltages are:

CPU 1.375v
DDR2 2.2v
CPU VTT 1.35v
NB 1.43v

Temps underload are:

CPU 46C
AUX 48C
Cores 42C

[ollie27]

Pci slots work fine for me - E4300 overclocked to 3ghz cold boot issue gone with bios 14.

geil ultra cas 4 pc2 6400 at 2.1v ram works fine i am using it now at 900Mhz 4-4-4-12

Chipset drivers for vista will have to get from nvidia site - but beware am having allsorts of problems with the sata drivers. Nvstor32.sys BSOD constantly.

Hope this helps

[Azurael]

V14 is awful on my board. Something is seriously screwy with it; It won't even finish booting Windows at my 100% 24x7 stable Orthos-tested overclock... Back to v13, at least I don't have the 'For evaluation only' message with the release version.

Incidentally, nVidia's Vista x64 drivers are completely broken. The SATA driver is unstable as hell and believes the drives are running in PIO mode (although this is obviously not the case), luckily the Microsoft-supplied original version seems to be OK. The Ethernet driver initiates a connection at 1Gbps but the pegs the throughput at 100Mbps, and this is the case with the version supplied with Vista too

[ZuluZ0mbie]

Hi Azurael

Is the bios 13 you are using not a beta?

I've just looked on Abit's website and 12 is the newest version listed

Thanks

[ABIT Sean]

The new bios files are listed on the ftp site.

ftp://ftp.abit.com.tw

[ZuluZ0mbie]

Should I try bios v14?

ollie27 said that the cold boot issue is resolved with this bios, but most people seem to think that v13 is the better one for o/c'ing.

Also any view on ollie27 +10C rise in temps and SATA driver issues (Ollie27 I take it the SATA issues have only appeared with the v14bios?)

Cheers

[Azurael]

No, SATA issues are down to nVIDIA's crappy Vista drivers and nothing to do with the BIOS.