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

Printable View

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

10-14-2005, 02:01 PM
sideeffect

Quote:

Originally Posted by flick

Hi,

I haven't posted here in a while. Has anybody had a problems with AGP and bios's past 1.8, i.e. 1.9-1.c3 and X2 dual core cpu's? I have an X850XT PE and an X2 4400+ on my neo 2 platinum. I have serious problems gaming after about 3-4 hours where any game I'm playing will begin to slowly stutter to the point that it's unplayable. It does it with any game and the only way to fix it is to restart the system. Then it's good for another 3 hours or so. It seems like a memory leak of some sort. The big key here is that it only happens with bios's past 1.8. I understand that 1.9 and on are new bios's, but am wondering why it's doing this to my system. 1.8 and down I have no problems what so ever. I can game all day and not have a problem, but I don't get the dual core advantage. Also 1.9 and above everything else is great and works fine as far as dual core goes. It's just when I'm gaming. Any information would be helpful. :confused:
<p>
<p>
I also have a Prometia which the bios's still don't see right because of the negative temperature. I still can't delete into the newer bios's without a temp mod. Anyway that's a side note.

If you look about 2 posts up from your post you will see the fix for negative temps and getting in bios setup. If you cant get in bios setup then it could be many things that are causing the freezing in games like fast writes on or ATI/Nvidia speedup etc etc etc. So get a bios you can get into and try again.
10-14-2005, 02:29 PM
sideeffect

You know whats interesting. 1.45 + 10 percent doesnt = 1.63 volts. But when you set it with the motherboard thats what you get. Another interesting thing is that 1.45 + 18 percent does = 1.63 volts.

1.55 + 10 percent = 1.65 volts So I think MSI based the percentages off of 1.55 volts and when the cpus went to 1.45 volts they still get the benifit of thinking its 1.55 and so sets the percentage accordingly.

so whats going on here? Maximum voltage with the 1.36 bios was 1.75 volts. Thats 1.45 + 30 percent but that value is 18 percent ??? 1.55 + 18 percent = 1.73 so that fits in with my theory.

Well anyway im confusing myself thinking about it.
10-14-2005, 02:31 PM
msimax

Quote:

Originally Posted by FlyingHamster

someone said this in another thread:

is this true?!?! does vAGP = chipset vdd on the neo2??

my journey to 400htt seems unaffected by using vagp worst case i see is damaging ur vidcard

u can try this but i didnt try it yet
http://xtremesystems.org/forums/atta...chmentid=17105
10-14-2005, 03:30 PM
msimax

hey SE can u mod ur 1.c for no temps
10-14-2005, 03:34 PM
sideeffect

I'll mod 1.C final when its out in a few days with a no temp version.
10-15-2005, 01:57 AM
el rolio

Quote:

Originally Posted by sideeffect

You know whats interesting. 1.45 + 10 percent doesnt = 1.63 volts. But when you set it with the motherboard thats what you get. Another interesting thing is that 1.45 + 18 percent does = 1.63 volts.

1.55 + 10 percent = 1.65 volts So I think MSI based the percentages off of 1.55 volts and when the cpus went to 1.45 volts they still get the benifit of thinking its 1.55 and so sets the percentage accordingly.

so whats going on here? Maximum voltage with the 1.36 bios was 1.75 volts. Thats 1.45 + 30 percent but that value is 18 percent ??? 1.55 + 18 percent = 1.73 so that fits in with my theory.

Well anyway im confusing myself thinking about it.

yea homie, ive noticed that too. didnt FULLY think it all thru and it seems you know why... cuz it hurts... but i wanted more than +5% or +8.3% and like using 1.55 setting + supn wasnt good enough. basically up here at 2.7ghz i didnt need WAY over 1.6v, i just need enough to be at or slightly below so what i did i think was to choose something in between 1.45 and 1.55 to see which ones did different things... anyhoo it worked i think. next time i jump into bios i'll check out what it was. oh and lookin forward to that 1.c, hopefully its good and looks like it will coincide with my new proc arriving
10-15-2005, 06:12 AM
stw500

Quote:

Originally Posted by Losphoron

sorry man..I didn't saw your post.Scrolled too fast :D
Sorry to hear that..Should i go for my kingmax Super ram 512 ppc3200 ? No money for premium versions :P

Well, no problem! :)

I don't have any experiences made with the kingmax. So I won't say anything to it...

Just read that Samsung-Chips PC3200 can go much higher than made for. But I don't have a clue if they run on the Neo2...
10-15-2005, 11:23 AM
Special_K

is anybody running 2x1GB RAM on this mobo yet?

K tried it, but the system was unstable on high load (read: playing BF2) and everything pointed to a bad PSU as the 12V rail would drop badly, but now, when running 2x512MB RAM the 12V rail is solid?

any ideas/experiences from anyone?

laters

K
10-15-2005, 12:05 PM
Losphoron

theDud3 what memories you have and how much you OC your Vinnie...
10-15-2005, 12:19 PM
twohype

Quote:

Originally Posted by Special_K

is anybody running 2x1GB RAM on this mobo yet?

K tried it, but the system was unstable on high load (read: playing BF2) and everything pointed to a bad PSU as the 12V rail would drop badly, but now, when running 2x512MB RAM the 12V rail is solid?

any ideas/experiences from anyone?

laters

K

Yep, check my sign it works great. Man BF2 rocks with 2 gigs. Maybe your ram is defective or needs to be of higher quality :)
10-15-2005, 02:05 PM
Special_K

they're Ballistix Z503's =/

but why would they make the 12V rail fall so drastically?
10-15-2005, 02:35 PM
Rbreb13

Quote:

Originally Posted by Special_K

they're Ballistix Z503's =/

but why would they make the 12V rail fall so drastically?

Thats what I run with no problems. Still working on a good/stable top speed though. Some others are using them also.
10-15-2005, 05:20 PM
phobix

Quote:

Originally Posted by flick

I have serious problems gaming after about 3-4 hours where any game I'm playing will begin to slowly stutter to the point that it's unplayable. It does it with any game and the only way to fix it is to restart the system.

Got the same problem here with X2 3800+ Neo2 but after 30 minutes???? If you figure out what it is let me know and vice versa
10-16-2005, 11:04 AM
Lestat

Quote:

Originally Posted by el rolio

yea homie, ive noticed that too. didnt FULLY think it all thru and it seems you know why... cuz it hurts... but i wanted more than +5% or +8.3% and like using 1.55 setting + supn wasnt good enough. basically up here at 2.7ghz i didnt need WAY over 1.6v, i just need enough to be at or slightly below so what i did i think was to choose something in between 1.45 and 1.55 to see which ones did different things... anyhoo it worked i think. next time i jump into bios i'll check out what it was. oh and lookin forward to that 1.c, hopefully its good and looks like it will coincide with my new proc arriving

Side effect i said this a long time ago and no one seemed to care.
i pointed out that the voltages in the bios were wrong with what is really being displayed.

oh well.

like i also said a long time ago someone needs to make a bios like Murdock did where there are no % anymore its all 0.80 all the way up to 1.7
all you do is remove the percant option but make anything over 1.45 equal VID + %
1.45 + 10% = 1.595(1.6)
so instad of having to set vcore of 1.45 then set % over VID @ 10%
you have the vcore automatically set it when you choose 1.6v

he made it work somewhat. it worked only for certain voltages in other words.
but it did work.
10-16-2005, 11:11 AM
el rolio

Quote:

Originally Posted by Lestat

like i also said a long time ago someone needs to make a bios like Murdock did where there are no % anymore its all 0.80 all the way up to 1.7
all you do is remove the percant option but make anything over 1.45 equal VID + %
1.45 + 10% = 1.595(1.6)
so instad of having to set vcore of 1.45 then set % over VID @ 10%
you have the vcore automatically set it when you choose 1.6v

he made it work somewhat. it worked only for certain voltages in other words.
but it did work.

yea THAT would be nice to have. i dunno if its possible anymore?
10-16-2005, 12:31 PM
sideeffect

Quote:

Originally Posted by Lestat

Side effect i said this a long time ago and no one seemed to care.
i pointed out that the voltages in the bios were wrong with what is really being displayed.

oh well.

like i also said a long time ago someone needs to make a bios like Murdock did where there are no % anymore its all 0.80 all the way up to 1.7
all you do is remove the percant option but make anything over 1.45 equal VID + %
1.45 + 10% = 1.595(1.6)
so instad of having to set vcore of 1.45 then set % over VID @ 10%
you have the vcore automatically set it when you choose 1.6v

he made it work somewhat. it worked only for certain voltages in other words.
but it did work.

I dont think Murdok ever did that Lestat. Never saw a bios like that for neo2 from him. Yes it is possbile but its not a good way of doing it imo.

Theres 3 good reasons why it shouldnt be done only 1 good reason for it.

So yes its possbile no its not a good idea.

Only real way to do it is to force +10 percent then hide the option then rename all the values to take into account the +10 percent. Problem with that is +10 percent isnt always a good setting on peoples pcs. Its not as stable as pehaps +5 or +8.3 and if they are only using say 1.5 volts it makes no sence.

Best way to fix this problem imo is to rename the percentages their correct values like +10 should be +18 percent. Also 1.475 - 1.55 should be locked.

That would make the bios make sence fine for anyone with a winchester venice or san diego pc. People using Newcastle based cpus would lose 0.1 volts though.
10-16-2005, 12:58 PM
phobix

Running modded 1.b here with an X2 and I can't get more than 1.55 volts. This is with the startup up VID at max and the percentage at max. Any suggestions on uping the Vcore a little more... I am phase change cooled so I am not really to concerned about heat.
10-16-2005, 02:08 PM
sideeffect

Think your stuck phobix. Newer X2 cpus seem to have a max VID of 1.375 volts instead or 1.45. So thats where your losing out on the voltage.
10-16-2005, 02:28 PM
phobix

Oh well, the good news is she is priming @ 2.7ghz right now. 300x9 memory @ 500DDR (166 divider) 2.5,3,3,7 1T. Pretty decent 24/7 overclock if she proves to be 100% stable which is what I need in my system.

I am starting to see the limitations of this board once you throw a dual core CPU into the equation. It is not so much the voltage but the amount of current these CPUs draw under load.
10-16-2005, 04:31 PM
flick

Quote:

Originally Posted by phobix

Got the same problem here with X2 3800+ Neo2 but after 30 minutes???? If you figure out what it is let me know and vice versa

Hey phobix,

I used driverheaven's driver cleaner pro, cleaned off all the nforce chipset drivers and the ati drivers, reinstalled nvidia's latest nforce drivers from their website and then reinstalled the latest catalyst drivers. The result is that online gaming with bf1942 and any mod no longer studders at anytime. However, if you enter single player mode after about 30 minutes the game will lock up, but you can at least ctrl+alt+del out and end the process. It sucks if you play single player, but works great now for online bf1942. I don't understand why, but it works online without any stuttering. Good luck and if you happen to come upon something else, let me know.
10-16-2005, 05:12 PM
el rolio

Quote:

Originally Posted by phobix

Oh well, the good news is she is priming @ 2.7ghz right now. 300x9 memory @ 500DDR (166 divider) 2.5,3,3,7 1T. Pretty decent 24/7 overclock if she proves to be 100% stable which is what I need in my system.

hey i also got a question for you man. at that exact memory timings and speed and settings, what is the voltage you set in the bios? i seem to error out at any setting above 2.6v
10-16-2005, 05:12 PM
sideeffect

Quote:

Originally Posted by phobix

Oh well, the good news is she is priming @ 2.7ghz right now. 300x9 memory @ 500DDR (166 divider) 2.5,3,3,7 1T. Pretty decent 24/7 overclock if she proves to be 100% stable which is what I need in my system.

I am starting to see the limitations of this board once you throw a dual core CPU into the equation. It is not so much the voltage but the amount of current these CPUs draw under load.

Doesnt the x2 draw less power than the 0.13 nm FX53 or 55 though. Im pretty sure it does.
10-16-2005, 06:04 PM
phobix

Quote:

Originally Posted by flick

Hey phobix,

I used driverheaven's driver cleaner pro, cleaned off all the nforce chipset drivers and the ati drivers, reinstalled nvidia's latest nforce drivers from their website and then reinstalled the latest catalyst drivers. The result is that online gaming with bf1942 and any mod no longer studders at anytime. However, if you enter single player mode after about 30 minutes the game will lock up, but you can at least ctrl+alt+del out and end the process. It sucks if you play single player, but works great now for online bf1942. I don't understand why, but it works online without any stuttering. Good luck and if you happen to come upon something else, let me know.

Good tips!

I solved it by manually setting the affinity in task manager by alt+tabbing back to windows. I am sure that if I had re-installed windows it wouldn't be an issue but I have way too much time invested in my current build to re-install at this point in time.
10-16-2005, 06:06 PM
phobix

Quote:

Originally Posted by sideeffect

Doesnt the x2 draw less power than the 0.13 nm FX53 or 55 though. Im pretty sure it does.

I think TDP at stock vcore is 89watts...However there is a cut-off point (Freq/Vcore) where the TDP is no longer linear. I can tell you 100% that it draws more than my winchester did at the same clock because my evap temps under load are 8c higher.
10-16-2005, 06:09 PM
phobix

Quote:

Originally Posted by el rolio

hey i also got a question for you man. at that exact memory timings and speed and settings, what is the voltage you set in the bios? i seem to error out at any setting above 2.6v

Could be your memory controller causing you grief. I had to lower my Vdimm considerably to get stability @ 500ddr, 2.6vdimm vs 2.85vdimm on the winchester.

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