The OFFICIAL MSI K8N Neo2-939 tips and tricks guide thread

[sinister1st]

HMM anyone having a problem using 1.B official posting into bios with restart?

I just flashed to 1.B from 1.9 and i have to do a full shutdown to get to into bios. When restarting NO GO with delete key! I get a nasty little cursor! Then haveto shut down. RESTART then boom fires right up.
FLASHED IT TWICE! Still same thing, i guess im going to give one of the modded bios a shot. With 1.9 i had no errors with anything and i see some people getting errors here and there with raid and other goodies. I seen a few people on msi forums getting the same error as me, im wondering if it is my keyboard i dont know why it would be its not usb.

[Millyons]

same here, i didnt try the 1.B betas, do they do the same thing?

[sinister1st]

Sorry for the double post but i figured it out. What i did was NOT let it quickboot 1 time and then i HAVE to choose USB K\B storage support ENABLED even though IM NOT USING A USB KEYBOARD. Well i bet the next bios will kick butt but this one doesnt seem as well made as 1.9. If i cant get 270x10 im going back to 1.9. No other errors gonna test this tommorow. I better go tell some noobs at msi forums. Something so easy can be so dam annoying.

[BerT]

Just flashed from 1.5 to 1.9 but didn't find any improvements @ my overclockingresults.

3200+ Winnie
Neo2 Platinum
OCZ Gold Rev2 2*256 (tccd) or 2*256 Kingston HX (BH5)

Also my max HTT still is +-300 ...


Any comment on that ?

[sideeffect]

Just flashed from 1.5 to 1.9 but didn't find any improvements @ my overclockingresults.
3200+ Winnie
Neo2 Platinum
OCZ Gold Rev2 2*256 (tccd) or 2*256 Kingston HX (BH5)
Also my max HTT still is +-300 ...
Any comment on that ?

Well I dont think 1.5 or 1.9 are very good bios files. The best for winchesters are probably the 1.36 rev4 by NFM and the 1.8 rev 3 by NFM.

The best for x2 is probably 1.B and im using 1.B with my san diego and im happy with it.

[el rolio]

Well I dont think 1.5 or 1.9 are very good bios files. The best for winchesters are probably the 1.36 rev4 by NFM and the 1.8 rev 3 by NFM.

The best for x2 is probably 1.B and im using 1.B with my san diego and im happy with it.

heh well im goin back to the 1.8 rev 3 that i got my stability tests done on. as always SE, thanks

[Budwise]

i just flashed to Syar's modded version of 1.B Final, and it works great. No problems at all.

[sinister1st]

Well I dont think 1.5 or 1.9 are very good bios files. The best for winchesters are probably the 1.36 rev4 by NFM and the 1.8 rev 3 by NFM.

The best for x2 is probably 1.B and im using 1.B with my san diego and im happy with it.

I have a X2 4400 and it loved the 1.9 bios. Im wondering if that bios was made just for that chip. ISNT it true that the X2 3800 doesnt work proper on 1.9 ?

Im looking for some results between these to bioses 1.9 and 1.B with the X2 4400. SIDE EFFECT that TCCD version of your bios 1.B looks tempting for my gskills i think ill give it a try THANKS. How does it run at stock and are you able to change the 256 clocks?

[sideeffect]

Well my tccd bios is designed to allow more mhz on the ram speed. So if your planning to run stock i dont really see the point in it or the point in tccd tbh.

From my testing though my ballistix bios is slightly faster at the same settings than the 1.B official is and its also more stable.

256 clks should work best with tccd if thats not the case then you could try the ballistix bios which sets 64 clks.

BTW the ballistix bios should work well with almost any memory at high HTT should probably call it the high HTT bios.

[sinister1st]

Thanks SE ill see how it does, I sometimes like to run my gskill at 2-2-2-5@stock when not ocing and thats not usual. My neo 2 is a pretty good board i hope the next bios has no bugs i cant believe i have to enable usb keyboard support to go into bios 1.b. When is msi going to just enable all ram dividers, what do they think they are going to surprise us all sometime next year and make the other unavailable options open? Since im not running raid i havent had the great annoying experience of "rom invoke" or any of the other errors, i wonder why this only happens to SOME people? Maybe a differnt board type? MADE IN TAIWAN?

[sideeffect]

The rom invoke is caused by the Nvidia Lan. If you disable the onbaord Nvidia lan the message goes away.

Maybe ill have usb mouse/keyboard on by default in the next bios. I just left it at the MSI default which is disabled.

MSI just spends a lot of time testing things. Like I have enabled the 150 and 183 dividers in my bios and they work fine. MSI would know that they work but it probably hasnt been fully tested yet so they havnt enabled them fully.

They did the same thing with USB 2.0 support. The 1.B bios was the first to enable it since this new bios format turned up but the mod bios makers have been enabling it since 1.9 bios with no problems.

[Draxx]

Is it just me or has AGP performance suffered in later BIOS's? I was getting higher 3D Mark scores with BIOS 1.5 then I'm getting now with Syar's 1.A mod. To make it worse my CPU is running faster now!!

[sunn]

hello there, i know this thread is a guide for tips and tricks, but im wondering i anyone could 'guide' me on a decssion?

i currently have a Asus A8V Deluxe but recently i thinking of changing to the Neo 2, no real reasons just some annoying problems i get with it. so anyone think its a good move?

i have 3200+ winnie, 2 x 512Mb Geil Value RAM, XFX 6800GT

any pros and cons i should know about thats not on the first post?

[msimax]

anyone wana buy redline utt

[IMG][/IMG]

[IMG][/IMG]

[IMG][/IMG]

[IMG][/IMG]




i willing to let them go for $16 each

[sideeffect]

lol is the pcb included in that price?

Are they 64 mb each ?

[Lestat]

sure looks like hunks of plastic to me

what the hell are you ever gunna do with those ?

you could always solder them onto your existing sticks of ram for double layered chips...
1 gig sticks....

and those are a tad large for any ram chip that fits onto a PC... look at your finger then compare it to the chip now look at a stick of ram you have sitting around and compare the chip on it to your finger.. now look back at these pics they sure seem twice as big as the ones on your pc ram dont they ?

[msimax]

those are real utt lestat came from that stupid stick i couldnt rma

[TMM]

Is it just me or has AGP performance suffered in later BIOS's? I was getting higher 3D Mark scores with BIOS 1.5 then I'm getting now with Syar's 1.A mod. To make it worse my CPU is running faster now!!

no problems here. As good 3dmark05 scores as 1.3B6 bios (im running sideeffects 1.BB3)

[TMM]

Ah nuts. Just flashed back to 1.3B6 (1.BB3 isn't so good for my winchester), and i can't load from SATA :s. did a full flash of bootblock and everything, cmos reset with battery out for half and hour and still the same problem.
Thinking it may be a problem with how the newer bioses format the drives, since i formatted this drive when i had 1.BB3 installed... formatting again from 1.3b6 now :s wish me luck

edit: **** it didn't work ideas?

[BerT]

I think im gonna give NFM 1.36 modded bios a try.
But first I'm gonna test 1.9 bios further.
Msi must have made some improvements ?

Any other suggestions on winnie bios ?

[sideeffect]

Yes dont use 1.9

Try 1.36 or 1.8 or 1.B

[BerT]

SE and your bios ?

1.3B6 rev 4 is mostly for BH5 aint it ?

[Lestat]

those are real utt lestat came from that stupid stick i couldnt rma

i didnt really doubt it more of a joke.

but seriously look at your finger then the chips then compare with existing ram is it just me or do they look larger than chips already on a stick of ram ?

and if you unsoldered them, then you did a fancy nice job guy!

you wanna solder 2 of them onto my xbox ? lol
too bad they wouldnt fit

[TMM]

hi, i need urgent help. Im figured that its not flashing everything... since my NVRAID is 4.81... and 4.81 was not introduced until bios 1.5, and im flashing 1.3B6 (not modded)!, either that or i need a bios that flashes it back :/

i'm using the /wb switch but its still not helping. i get "error loading operating system" when trying to boot from sata and the only way i can fix it is to flash to 1.BB3 again . also tryed official 1.8 but i still can't boot from sata!. i've formatted my drive several times, and even done a FIXMBR from the windows recovery console with no luck.

please help

edit: ok to clarify i've thrown another Sata drive from my AthlonXP rig in there and its started booting windows (at which stage i just turned off the comp as i knew it would BSOD before it finished loading). So it seems the 1.BB3 bios has done something funky to my MBR, which is causing earlier bioses to not boot the drive... wtf. Going to try and format the offending drive in another rig and see what happens.... will do that in teh morning tho

[Lestat]

1)
after flashing you need to go back and turn raid ON for the appropriate hard drive ports
2)
put the boot order of the hard drives in proper order.

the different nvraid roms dont make this happen. its a setting in the bios that you have wrong. although a bad nvraid rom could do it yes,, but i dont think thats the problem.
use the 1.36r4 modded bios or the 1.8 official from msi both are good.

Also the Boot order you need to make correct and also the Hard drive boot order.

It says error loading operating system becuase 1) its looking at the wrong hard drive.
2) its looking at your raid hard drives but they are not raid so it can not load windows properly

its a simple fix.

also you need to use a large string of switches with the flash i cant remember what they are and im at work so i cant tell you what they are but search this thread ive posted them several times, also sideeffect and others know what they are so wait to se eif they reply.

the fix is simple just hang tight...


also the nvraid doesnt like being messed with you have to delete the raid and choose clear data,, then reboot, then go back and make the raid again. then load up the xp cd and load windows.

you added an edit and im not sure i understand it but i highly doubt the MBR of the disk is bad unless the rAID is still intact, you must delete the raid vbia the nvraid setup menu.