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

Ok the bios works fine now ill add the cd1986 no temp mod bios to the ftp for anyone else who has the issue.

Just had a little mess around with it the 216 divider now works. Couldnt test the 250 as my main ram is being rma'd and im using pc2700 ram atm. The 3.5 Ht multiplier options has gone, it didnt work in the previous betas but it was there, i guess they couldnt get it working.

Nfms timings set but nfm have you tried to add the 183 divider into the bios? does it have the options in bios. Also twtr (Write to read delay time) sets to 1 with 166 divider still. Please force it to 2 in rev 2 :)

Good job with the bios though :clap:

Rev2 will be out shortly. 183 divider is there but it is not activated. It's like with extra 13%, 15%, 18.3% VID option, they are there but thre's nothing you can do about it :( . Yeah I will remove temps from BIOS so people don't be pissed if something does not work.

Ok, Rev.2 is up. Testing needed.

Quote:

---

Changelog Rev.2:

- twtr = 2 clks
- All temps hidden, to see them hold "Shift + F2, hold it still and with your
second hand press "ALT + F3"

---

Suggestion for Rev3 NFM, change what is loaded when you press "load optimal defaults" to some more OC friendly settings. I've found it a great way to save some time once you've cleared the CMOS. Some of the default settings used from the factory are no good for OCing, and we have to keep changing them everytime we reset the bios! :rolleyes:

yes good idea cd1986 im all for that. :slap:

Some ideas for defaults

Ati/nvidia speed up = disabled
boot up logo = disabled
small logo = disabled
S.M.A.R.T = Enabled

Tested the bios and it works. Flashed ok the temperatures are hidden and i cant unhide them with alt shift thing. i see the little flash u get when it supposed to show hidden options but they dont appear.

Twtr still defaults to 1 in 166 divider also. The rest of the timings set ok though

maybe you set read to write instead of write to read :slapass: :p:

; Write to read delay(dth)
twtr_data equ 0FFFFFFFEh ; Write to read delay (1bit)
twtr_1 equ 000000001h ; 1 clock
twtr_2 equ 000000002h ; 2 clock

yeah i probably messed up with that one, so many values :confused: :slapass:

Ati/nvidia speed up = disabled
boot up logo = disabled
small logo = disabled
S.M.A.R.T = Enabled

will do that

also i will do:

spread spectrum = disabled
cool n quiet = disabled
agp fast write = disabled

EDIT: Rev.3 is up

twtr still defaults to 1 in dividers. Maybe it doesnt work or maybe the code is wrong. Oh well not a big problem really.

The bios is really good the default settings work nicely and i can enter bios setup which is always a bonus :) I cant get the temperatures to show but that might be my problom alone as i have the issue.

Someone else try and unhide the temperatures.

Good work NFM going to use this bios from now on.

Well i tried 1.98 and i have to say it is still in beta phase. Don't know why did they post this bios on korean msi. I'm switching back to 1.8.

Quote:

---

Originally Posted by need.for.mhz

Well i tried 1.98 and i have to say it is still in beta phase. Don't know why did they post this bios on korean msi. I'm switching back to 1.8.

---

how bad is it ?

Quote:

---

Originally Posted by harpyboy

how bad is it ?

---

Its not bad its just not official. Somethings dont work like after more testing the 216 233 and 250 dividers dont work. The northbridge fan control isnt included. There are no .5 cpu multipliers.

The bios seems pretty much stable now though and my overclock seems ok with it as with the 1.8.

I dont think there is much point upgrading to the bios unless u have a san diego or a x2 processor.

Quote:

---

Originally Posted by sideeffect

Its not bad its just not official. Somethings dont work like after more testing the 216 233 and 250 dividers dont work. The northbridge fan control isnt included. There are no .5 cpu multipliers.

The bios seems pretty much stable now though and my overclock seems ok with it as with the 1.8.

I dont think there is much point upgrading to the bios unless u have a san diego or a x2 processor.

---

I lose my USB 2.0 capability. It only has USB 1.1???

Yes usb 2.0 support isnt added yet so not i good idea to try this bios if you need usb 2 :D

But can I get the same overclock i'm getting on 1.8mod cuz befor 2.9 wasnt stable on 1.95, I need the memory options my ram is almost stable and it would be a killer 24/7 setup, 2.9ghz with 7500+mb/s :banana: , but I need better memory options to finish it off.

Quote:

---

Originally Posted by 4rory

But can I get the same overclock i'm getting on 1.8mod cuz befor 2.9 wasnt stable on 1.95, I need the memory options my ram is almost stable and it would be a killer 24/7 setup, 2.9ghz with 7500+mb/s :banana: , but I need better memory options to finish it off.

---

What you could do is that you let A64 tweaker automatically load the timings every time windows starts...
(I do it this way, always start up with the '100' divider and let A64 tweaker do the rest)

lol that causes instand crash, I can't even change more then one setting in a64 tweaker without instant freeze.

A64 tweaker is a windows killer waiting to happen.

for you to have someone start ram at 100mhz and then A64 tweaker INSTANTLY kicks the ram in tha arse and forces it to make in instant jump up to insane overclocked speads WHILE in windows is foolish to say the least.

many people wont be able to do this as it will simply lock their system.
i dont recommend anyone try this unless they have 100% stability with their overclock via the bios and booting into windows.

you could potential damage your systemand corrupt windows beyond a point of repair if the system crashed.


I NEEEEEED someone to test something for me

1.9 bios any version most importantly the supposed actualy bios from the MSI site and also NFM's modded version.
You MUST have adjustable rails on your PSU in order to try this.

1)
adjust your 12v+ rail above 12v maybe 12.5v
2)
adjust your 3.3+v rail past 3.3v 3.4 3.5 3.6

now boot the system.
Are you having the same issue i am having ith the 1.9 bios that the system will NOT boot to any media. no matter what you do it posts fine it goes thru the NVRaid detection fine and whatever else you may have, and then it might read the floppy like its gunna start but nothing happens.
Same for a CD like the XP boot cd. it says "press any key to boot from cdrom" then either nothing happens OR it says "checking system" like the xp cd does when you boot to it but again nothing happens.
same thing with the Hard Drive.
It will flash the HD light but nothing happens.
You can press F8 and choose safe mode but nothing happens.
If you have linux it MAY boot to the linux kernel argument options screen but nothing will happen after that.

the only way to fix this is to reduce all voltages down to damn near the exact voltage they are said to be,, ie; 12v 3.3v 5v

even after doing that i am having SEVERE issue trying to boot to a floippy to reflash the bios. roughly 1 out of 20 reboots will then boot ot a floppy where i can reflash with the 1.8 bios.

Also,

can anyone else chime in on stability or other issues with the 1.9 bios. ?
and has anyone of you modding gent's even TRIED to allow the bios to go above 2.85v on the vdimm ?
the hardwarelock on these boards is what ? 3.0v if i remember correctly and frankly gents... I NEED 3.0V this OCZ EL Gold Rev2 PC4000 cant even go past 260mhz STABLE ( and i enphasise stable) without more than 2.85v
this is good ram and will reach 1:1 ratios of 290mhz if you get a good kit.
My last kit did 311mhz STABLE on a 9/10 divider but i had to have a minimum of 3.0v to do it.

also the 183mhz mem divider. we all know thats simply the 1/2 cpu multiplier setting. thats why its in a reserved state.
Simply remove all 1/2 cpu multi's and any instance or mention of it in the bios and then remove the reserved setting in the ram divider section and one would think it would allow the ram to run at the 183mhz divider
yes ? or has MSI made it more complicated than that and its more of a hardware issue than a bios issue.

http://www.swjka.com/neo2/view_thread.php?fid=3&tid=13
with this Bios, i have only 3000 MB/s Readspeed @ everest. With 1.8 Bios i have about 6000 MB/s. WTF?

hoohhhhh... tat's pretty weird... anyone has this issue ?

seems like dual channel is gone

Quote:

---

Originally Posted by jcollett69

A few thing about RAM. Most "manufacturers" do not make the chips themselves. Rather, the purchase the chips and PCB on the open market, test them to certain timings and speed, and sell them as their own. Any particular line of RAM could have different types of chips in them depending what was available on the market at the time. Sounds line you may have RAM that was produced from Winbond dies, the older set most likely being BH and the newer most likely CH. BH is well known for not booting into CAS 3 but will do 2.5 or 2.0 with proper voltage. Get that vDIMM up into the 3.2 to 3.3 range and you may find that your RAM can do 2-2-2-5 at fairly high speeds (~250MHz). I know the MSI board will not do that voltage. A vDIMM hack or OCZ DDR booster would correct that issue for you.
As far as having four double-sided DIMMs populating your motherboard's RAM slots...this will always cause your BIOS to revert to DDR333 speeds. Search these boards for much of this knowledge being repeated over and over ad nauseum. OK, I'm done here.

Hoping for that new BIOS :shrug:

---

ok first up, i have 2 double sided sticks (2x512).
second up the chips appear to be one revision different. i dont recall the first letter but the two are: xb and xc for the chips. not sure what letter replaces the "x" but the 2nd letter for one is "b" and the second letter for the other is "c".

so idk. they are def diff revisions just dont understand why 2x doublesided is dropping it to 166? esp since each individually does 200. and it seems wierd that it happens in all combinations of using the 2 sticks together.

i have set the timings manually as i mentioned in my original post. basically the ONLY problem is the 166 drop from 200. timings wise i can run the faster timings with both sticks in at the same time no prob. so yeah why is it dropping back to 166?

look at this. :O

/edit
Wahhhhhhhh, PC1600. What the F

Go into A64 Tweaker and see what Max Async Latency says. and Tref
Controller mode also. And clock frequency
128bit should be dual channel and 64bit single channel (i believe thats correct, the single channel part i mean)
The first 3 things i just mentioned if they arent set right will just absolutely kill your ram thruput.
basically if you have a screen shot of what your settings were before. go into it now and compare them to see whats going on.
also CPU-Z see if its showing the proper settings. CPU-Z will tell you if its Dual or Single channel on the Memory tab.
and yes it does sound like Dual channel is gone.
but also set the ram chips like every other mobo in the world.
Slots 0 and 2 dual channel and slots 0 and 1 and 2 and 3 are single channel.
in other words first slot and 3rd slots. just for the heck of it try it. see what happens.
again reflash the bios again with the same rom file and see what happens.
im telling you guys this 1.9 bios is FUX'd BIG TIME!!
whom ever is programming it at MSI is a bunch of blooming retards.
Also does this same thing happen with the actual 1.9 bios from the korean site ? or IS that the korean site bios ?

I think you've got your wires crossed?
1&2 or 3+4 = Dual channel.

Msi

Can someone please!!...tell me the best bios for my setup??
I have problem to run my memorys in 250fsb (2-2-2-8) 1:1.....I now they handle 258fsb (1:1) 3.3V on a DFI board!? :confused:

Now I use v1.8.

Thanks..

Quote:

---

Originally Posted by ColdCollisions

I think you've got your wires crossed?
1&2 or 3+4 = Dual channel.

Msi

---

dual channel is activ, but my RAM is adjusted as pc1600. I have switched in the Bios to Auto Mode and now I have 5600 MB/s (PC3200 speed again). :)

But Speed was better with default 1.8 Bios and same timings. :(

@mapel110 ...sorry mate I was actually talking about this post quoted below, wrongly stating which RAM Slots were Dual Channel. Highlighted in red.

Quote:

---

Originally Posted by Lestat

Go into A64 Tweaker and see what Max Async Latency says. and Tref
Controller mode also. And clock frequency
128bit should be dual channel and 64bit single channel (i believe thats correct, the single channel part i mean)
The first 3 things i just mentioned if they arent set right will just absolutely kill your ram thruput.
basically if you have a screen shot of what your settings were before. go into it now and compare them to see whats going on.
also CPU-Z see if its showing the proper settings. CPU-Z will tell you if its Dual or Single channel on the Memory tab.
and yes it does sound like Dual channel is gone.
but also set the ram chips like every other mobo in the world.
Slots 0 and 2 dual channel and slots 0 and 1 and 2 and 3 are single channel.
in other words first slot and 3rd slots. just for the heck of it try it. see what happens.
again reflash the bios again with the same rom file and see what happens.
im telling you guys this 1.9 bios is FUX'd BIG TIME!!
whom ever is programming it at MSI is a bunch of blooming retards.
Also does this same thing happen with the actual 1.9 bios from the korean site ? or IS that the korean site bios ?

---

Quote:

---

Originally Posted by Vega

Can someone please!!...tell me the best bios for my setup??
I have problem to run my memorys in 250fsb (2-2-2-8) 1:1.....I now they handle 258fsb (1:1) 3.3V on a DFI board!? :confused:

Now I use v1.8.

Thanks..

---

1.8 is probably your best bet. Try NFM's rev 3 1.8 bios. And just because one board can run memory at a speed doesnt mean much nowadays esspecially when dfi relax timings to allow for high fsb doesnt mean the memory is running faster.

If it was the 754 DFI board it was single channel also and not dual channel like the msi.

Good luck anyway getting stable but the 1.9 isnt really ready yet to be as good as the 1.8.

yup... or 1.36mod if u need the extra vcore.... but 1.8 works so damn nice for me .....

do u guys think there will be a 500:400 divider for the new BIOS for the rev.E ??



alrite guys... my SECOND RMA RAPTOR WD HDD came DOA again !!! ... well not really DOA... but right after 100% format.... dead....... i called WD complainted a hell lot and they gonna send me another by tomoro and prepaid shipping for the last hdd back..... looking at the 3 dead raptor on my desk... how sad can it goes....... :'(

Quote:

---

Originally Posted by ColdCollisions

@mapel110 ...sorry mate I was actually talking about this post quoted below, wrongly stating which RAM Slots were Dual Channel. Highlighted in red.

---

please read what i said coldcollision

i said if MSI would make their boards like everyone else in the world were slots 0/2 and 1/3 are dual channel
i did NOT say that msi boards are slots 0/2 cuz they are 0/1 for dual channel.

I did read what you said, that's why I posted?
:rolleyes: GO check it yourself:fact: . Now this is well off topic so I'm not going to post anymore.

I'm just now treading into 64 territory. Been overclocking XPs since they came out. So, I've bought a K8N neo2, Venice 3000+, and 2x512mb OCZ EL Platinum Revision 2. Im new to HTT and doing heavy overclocking on the FSB and ram.

I have read the guide Xtreme provides to overclocking. I have also done more digging on the potential of the K8N Neo2. I would like to squeeze about 2.4-2.6 ghz out of this.

Suggestions? My system should be here in a day or 2. What kind of settings should I test out. Help a amd64 o/c newb out.

Hey guys, i am new to the forum. I heard there is a cool for sale section, but you have to have 100 posts. So I am gona start here I guess.

See you in the future.

welcome tyrvidar...

anything we tell u now is pointless... u can figure everything out when u actually touch ur new rig :) ... and then u will realise there r a lot of issues..... tat is when u come here and ask again.... :D

haha I know man... Must you destroy my hopes ahhh.

Quote:

---

Originally Posted by ColdCollisions

I did read what you said, that's why I posted?
:rolleyes: GO check it yourself:fact: . Now this is well off topic so I'm not going to post anymore.

---

once again i say it with more conviction.

read what i said and know what i said. cuz you didnt read it properly. i did NOT say 0/2 were dual channel i SAID 0/2 SHOULD be dual channel like every other board in the world but MSI has to be different and make things complicated by making slots 0/1 and 2/3 dual channel.

0123 call it whatever you want slots 1 2 3 4 or a b c d cuz technically they are called slot 0 1 2 3 and have been since god knows when.


Anyways has anyone seen what i mentoined above with the voltage issues ?
and why on earth does the -12v report at only 7v ? this really needs to be addressed cuz i have a feeling this too is causing issues even though the hardware may see the true -12v if the bios is reporting only -7v then it can and will halt the system from properly functioning.

i wont use 1.9 any further that bios scares the hell out of me. it took me nearly all of one evening to get the dang thing to even boot to a floppy when i tried the modded version. i thought for sure the mobo was dead.
Im still wondering if one of the modders can chime in on whether raising the vdimm voltage is even possible or if they have even tried it.

same thing with the 183mhz ram divider.
remove all 1/2 cpu multipliers and that should enable or allow you to enable the 183mhz. or simply removing the *reserved* value from that particular hex line in the bios might do it. but i have a feeling more digging in the never ending hex values for the root of that *reserved* value is needed to fully enable the 183mhz. i mean the 1/2 cpu multi is just running 183mhz ram. but since its catagorized as a cpu option is it possible that the system pukes on certain cpu's instead of it running properly when using the actual setting under a ram setting ?
im really grasping at straws there but hey sometimes the right question drives a programmer to think and look at things differently which can result in finding new and interesting things or tricks.

Quote:

---

Originally Posted by floodo1

ok first up, i have 2 double sided sticks (2x512).
second up the chips appear to be one revision different. i dont recall the first letter but the two are: xb and xc for the chips. not sure what letter replaces the "x" but the 2nd letter for one is "b" and the second letter for the other is "c".

so idk. they are def diff revisions just dont understand why 2x doublesided is dropping it to 166? esp since each individually does 200. and it seems wierd that it happens in all combinations of using the 2 sticks together.

i have set the timings manually as i mentioned in my original post. basically the ONLY problem is the 166 drop from 200. timings wise i can run the faster timings with both sticks in at the same time no prob. so yeah why is it dropping back to 166?

---

no help? sorry for such a basic question but im just running this board basic style until xmas when i can finally afford some real ram :(

Lestat all the .5 cpu mutipliers have been removed from the 1.9 bios but the 183 divider option is still not there. It cant be modded in by NFM hes already looked at it. So until MSI decide to be nice to us and add it themselves i think were screwed.

Cant remember which bios it was but 1 of them showed me a accurate -12 volt line. Think it was 1.41 mod. All the others with the option added show the wrong value :p annoying. But the issue that really annoys me is the cpu temperature in the bios it reads 268 degrees and hardlocks the bios when i try to view it. It even stops the 1.9 bios from entering setup. Thats why it was modded by nfm and cd1986 to remove the temp readings from the bios.

Once in windows it shows the temperature with core center or speedfan/mbm without a problem.

Ive been using 1.98 beta bios since it came out without a problem. Its never crashed for me and the extra configurability is worth it for me. But i dont see much point in people who arent using san diegos or x2 cpus switching from 1.8 atm.

Quote:

---

Originally Posted by Lestat

Slots 0 and 2 dual channel and slots 0 and 1 and 2 and 3 are single channel.
in other words first slot and 3rd slots. just for the heck of it try it. see what happens.

---

actually that doesnt come out to say a whole lot.. I think you left out a sentance?

Quote:

---

Originally Posted by floodo1

ok first up, i have 2 double sided sticks (2x512).
second up the chips appear to be one revision different. i dont recall the first letter but the two are: xb and xc for the chips. not sure what letter replaces the "x" but the 2nd letter for one is "b" and the second letter for the other is "c".

so idk. they are def diff revisions just dont understand why 2x doublesided is dropping it to 166? esp since each individually does 200. and it seems wierd that it happens in all combinations of using the 2 sticks together.

i have set the timings manually as i mentioned in my original post. basically the ONLY problem is the 166 drop from 200. timings wise i can run the faster timings with both sticks in at the same time no prob. so yeah why is it dropping back to 166?

---

xb and xc? Its kind of hard to answer since we dont know the manufacturer (hyinx, samsung, winbond, etc) and you havent given us any other info off the chips to indicate model numbers or speed ratings. Do you have the ram in the two slots closest the CPU or two farthest from it (dual channel on the Neo2) or are they in 1 and 3 or 2 and 4?

guys im back in business.... hdd came back working fine ;) hohohoho

who else except sideeffect had tried the 1.98 BIOS ??


also, i manage to get hold of OCZ EL plat rev2.. the one with TCC5.. but it seems that it max out around 275Mhz 2.5-4-4-8... almost exactly the same as my Patriot XBLK TCCD.... so... does the problem lies with the Venice mem controller and the Neo2 BIOS ?? or it just coincident that both of these ram max out around there ?

i had tried the 1.98 NFM modded... very nice.... is a keeper... thx NFM again

for some reasons it allows my OCZ to clock up to 285Mhz.. alittle higher.... but still not good ennough for me...

its likely a combination of both.

I have a 0444 3000+ winchester and the max I can do is 285 2.5-4-3-x-1T or 310 2.5-4-3-x-2T with 2.8v on my 2x512 OCZ PC4800 Platinum (TCC5), but this also requires a modded bios since the original didnt hold trc and trfc constant when using dividers or at different FSB's.

Quote:

---

Originally Posted by STEvil

its likely a combination of both.

I have a 0444 3000+ winchester and the max I can do is 285 2.5-4-3-x-1T or 310 2.5-4-3-x-2T with 2.8v on my 2x512 OCZ PC4800 Platinum (TCC5), but this also requires a modded bios since the original didnt hold trc and trfc constant when using dividers or at different FSB's.

---

2T really hurts on benchmarks... but i really like to hear from you whether it does have any real life effects ... like on games and daily apps ?

im still playing around with it... hope i can get more out

I have everything hooked up ~ time to start testing, 210 so far and going up.

Edit- Blahh im such a 64 o/cing noob. Blue screens at 215.

Updated to official 1.8 bios.

Venice 3000+ OCZ plat Rev 2 3200... where do I start at haha. I turned HTT to 4x.

use htt 3x, and lossen you ram to 2.5-3-3-7, and 166 divider then push the cpu to test for max bootable speed, then test for max stable cpu speed, then report back and we will give you the next steps.

Update~ 255 and climbing. Thanks, will update in a minute will see how far this goes before I have to up the voltage on the cpu. U = roxor. I had to pop my 64 cherry eventualy this is good stuff.

Update~ maxs out at 270 what should I do from here, up the cpu voltage like any old XP O/c? I want to squeeze about 2.6 out of this puppy.

Quote:

---

Originally Posted by harpyboy

2T really hurts on benchmarks... but i really like to hear from you whether it does have any real life effects ... like on games and daily apps ?

im still playing around with it... hope i can get more out

---

There are a lot of 1T/2T 1gb/2gb threads in the memory section of the forums.

Hey guys I'm back, although I still don't have my new cpu yet since AMD is out of stock of 3700 sd's and so I have a question, they offered me a 4000 but it would be either a clawhammer or some other core and not a sd :/

so what do you guys think? maybe I should get the 4000, sell it and just buy another 3700 sd or wait till they get more sd's in stock

Quote:

---

Originally Posted by harpyboy

who else except sideeffect had tried the 1.98 BIOS ??

---

I've been running the 1.9B8 bios since it was first released. No problems at all so far. I've had a setback though....my TDX CPU block decided to puke on and drown my 9800pro on Saturday night. I've tried to get it working again, but it's fubar.....soooo, I have a new BBA x800xl in my board now. :banana: :woot: As soon as I get new gaskets for the TDX I'll resume with my OC tweaking.

Seem to be getting alot of static in my headphones from the onboard audio. I miss my soundstorm on my abit board nforce2 already.

anyone recommend the best bios for Venice's ? My 3200 arrives this afternoon so i want to flash the board and be ready for it.

any particular bios shown to perform better than others ?

i figured NFM 1.8Rev3 would be good but didnt know for sure.

ok im running 1.8rev3 and for some reason the voltages are whack.

My 3200 Venice is locked at 1.45v i've raised it to 1.5 and it doesnt go to 1.5 it is reported as 1.45 by every app i can find in windows.
even changing it with clockgen doesnt work.

anyone seen this before ? i cant tell if its a bios issue or a venice vcore lock.

LBBE 0519 APAW 3200+

the board undervolts...usually up to .1v for me, its .1 less than whatever you set, so i set 1.55+10% to get 1.62v.

Quote:

---

Originally Posted by Lestat

ok im running 1.8rev3 and for some reason the voltages are whack.

My 3200 Venice is locked at 1.45v i've raised it to 1.5 and it doesnt go to 1.5 it is reported as 1.45 by every app i can find in windows.
even changing it with clockgen doesnt work.

anyone seen this before ? i cant tell if its a bios issue or a venice vcore lock.

LBBE 0519 APAW 3200+

---

Yes thats normal 1.45 is the maximum the vid will allow for venice san diego chips. To raise the voltage anymore u use the pecentages. Maximum setting is 1.45 + 10 percent which = 1.63 volts or so.

Try 1.45 + 5 percent that makes about 1.52 volts and is a good place to overclock from on air cooling.

xb and xc? Its kind of hard to answer since we dont know the manufacturer (hyinx, samsung, winbond, etc) and you havent given us any other info off the chips to indicate model numbers or speed ratings. Do you have the ram in the two slots closest the CPU or two farthest from it (dual channel on the Neo2) or are they in 1 and 3 or 2 and 4?[/QUOTE]

ok i'll take the ram out later tonite and give you all the info i can from it.

doesnt matter if i run it in single or dual channel. atm i have it on the 2 slots closest to proc. but i can run any combination of using both sticks and it drops back to 166.

let me write everythign down and get back....thanks for the help so far :)

Ok just got done trying the 1.98 bios modded by nfm.doesnt like my mobo/cpu at all, I want to make it clear I am not bashing nfm with the following at all. currently on 1.8 rev3 by nfm, with 1t fix. 250x11 perfectly stable, ram 1:1. 275x10 with ram 1:1=no good, this was what I was trying to fix. now results with 1.98. Basically at stock(with default craptastic timings), it would post, but not load windows. Had to remove my pci ata controller card to get into windows. 250x11 = post but no boot, even without pci card. 275x10 = no post, 1.8 would get into windows, just fail superpi and prime after a while. so my experience with this bios is that its garbage, I await the final, and may even revert to 1.8 if these problems persist, I despise getting down on the floor and changing the cmos jumper.

@Tyrvidar ok so 270*9 is 2430mhz ok, so bump the vcore depending on ur cooling to about 1.55 to 1.65 for the best of air cooling xp-94s and such.

Keep your memory very low and laxed to keep it out of the question, and the htt mulit to keep it at 3.

A fast way to get the max cpu mhz i find is to set cpu to 2300 lets say and 1.65 volts prime look at heat, judge if its to much heat, anything hihger then 55c is to high, then determine ur max vcore then keep bumping up fsb with clockgen and doing superpi 1 mill till it doesnt go anyhigher then back off 10fsb and start priming. :D then once u get the max primeable, start to lower vcore and prime :D.

Did any one tried some mushkin redline 3500?
With a OCZ DDR BOOSTER?

TKS!

I appreciate your Help 4rory alot. I will hold off on testing this to the limits and in the meantime will let it burn in. Will look into one of the xp94s and such over the next month. Stock cooler can only do so much hehe.

Thanks again ;). Some noob o/cer will see this thread and use your post you helped me with.

I recently upgraded my CPU to a manchester (X2 4200+), and no BIOS I've found yet lets me boot all the way into windows with both the CPU and my SATA drives being recognized properly.

1.8 : dual CPU is not recognized

all 1.9 betas: drive on SATA port #3 works fine, but drive on port #4 shows up as "new hardware", and windows wants to install a driver for it(?!), and the partitions aren't available.

anyone else run into a similar problem ever?

Quote:

---

Originally Posted by angra

I recently upgraded my CPU to a manchester (X2 4200+), and no BIOS I've found yet lets me boot all the way into windows with both the CPU and my SATA drives being recognized properly.

1.8 : dual CPU is not recognized

all 1.9 betas: drive on SATA port #3 works fine, but drive on port #4 shows up as "new hardware", and windows wants to install a driver for it(?!), and the partitions aren't available.

anyone else run into a similar problem ever?

---

have you tried using xp?

Quote:

---

Originally Posted by sideeffect

have you tried using xp?

---

Not yet - I'd really rather not rebuild my OS right now; I have a ton of apps installed, etc., and it's only been six months or so since my last rebuild.

Both SATA ports seem to work fine under 1.8, so I strongly suspect a BIOS issue of some sort. It's just odd.

though I do recognize that XP is a lot more likely to have up to date support and attention paid to it, so maybe I will end up going that way.

fortunately, the drive in question is used only for nightly backups so I can live without it for a while at least.

next test will be to switch 3&4 and see if the problem stays with the drive or the port.

Msi has been working on the sata ports trying to sort out the locking issue so its possible that the bios has messed it up :)

From what ive read though the 1.98 beta bios locks port 1 and 2 so pehaps its worth testing it out and see if you can boot that way but probably not best to plug it in at 280 htt. :stick:

Yeah I noticed comments along those lines in this threat, I think that's worth a try, too, and I will.

Since the drive itself is purely a backup drive, I can afford to take more risks than normal in the data-corruption area.

@Tyrvidar
Glad I could help.

With the 1.36mod bios I can get volts up to +18.3% with venice my max effective vid is 1.450v correct? does this mean that if I apply +18.3% I get 1.71vcore? and then the board undervolts also? but 0.1volt right? that means max I can get is 1.61vcore this seems a bit low, I just want to know if I should try this bios and try the high volts to see my max overclock, I'm on air and am willing to apply a bit over 1.65 for a nice screeny, already got a 3131mhz on a +3200. That was with 1.8mod bios at 10% i think cpu-z reports close to 1.65 volts.

No the vcore reading is accurate. So 1.45 + 18 percent will give you about 1.7 volts. The chip doesnt undervolt it just wont accept a vid higher than 1.45. The percentages take it higher than that.

The newcastles would do 1.55 + 18 percent as their maximum because they had higher voltage defaults to begin with.

The vid is controlled by the cpu not the motherboard.

Ok so my venice with all voltage settings maxed on 1.36mod bios will give me a safeish testing vcore? 1.450+ 18.3% will be ok for venice?

Quote:

---

Originally Posted by 4rory

Ok so my venice with all voltage settings maxed on 1.36mod bios will give me a safeish testing vcore? 1.450+ 18.3% will be ok for venice?

---

jus for benching.... i wouldn't recomend running it 24/7 with it...

1.8 BIOS allows u to run 1.7v as well... using corecenter

this whole NEO2 + Venice voltage issue is a joke

MSI needs to fix this.

the voltages are off from what you have them set in the bios usuall .25v
plus most of the settings dont work
i had the bios set to 1.7v and it was only like 1.6 in windows.
or rather Core center said it was 1.7 but reported it as 1.6
totally screwed up

this needs to be addressed and quick before people start frying chips.

i can never tell what im setting the voltaged too unless i reboot and go back into pc health. and then when i get into windows sometimes its even different.
I cant even get 1.475 to 1.575v its a huge dead zone up to 1.45 its ok and from 1.6 and up its ok. thats a lovely hole in the voltage spectrum.

i am almost done with this board. i think this venice will be my last amd64 for a long time unless i win the lottery.

i do believe im gunna have to get me an Ultra-d msi just cant made this mobo with too many issues and now the venice's voltage issue;s yeah...

The only bios i have not tried is the 1.36mod becuase its too old for this venice and i dont feel it would be wise going back to such an old bios.

considering doing a droop mod to my board..

Quote:

---

Originally Posted by Lestat

I cant even get 1.475 to 1.575v its a huge dead zone up to 1.45 its ok and from 1.6 and up its ok. thats a lovely hole in the voltage spectrum.

---

I can see what you're saying about a "voltage hole," but I haven't had any issues at all yet. I know that if you set the VID to anything higher than 1.45v with a Winchester or a Venice, it will only see 1.45v. (i.e. 1.55v VID = 1.45v VID) The 1.37mod or 1.36mod bios, the one that supports 18% over-voltage will give you finer steps than any other bios, but I really don't see that much of a point unless you want over 1.6v for constant use. :shrug:

If you don't have time to calculate what each VID and %overvolt is, here's a chart for you. ;) Just find the voltage that you want to try and use the selected VID and %....

1.325v * 3.3% = 1.3687v
1.325v * 5% = 1.3912v
1.35v * 3.3% = 1.3945v

1.35v * 5% = 1.4175v
1.375v * 3.3% = 1.4203v
1.325v * 8.3% = 1.4349v
1.375v * 5% = 1.4437v

1.4v * 3.3% = 1.4462v
1.325v * 10% = 1.4575v
1.35v * 8.3% = 1.4620v

1.4v * 5% = 1.47v
1.425v * 3.3% = 1.4720v
1.35v * 10% = 1.4850v

1.425v * 5% = 1.4962v
1.45v * 3.3% = 1.4978v
1.375v * 8.3% = 1.4891v

1.375v * 10% = 1.5125v
1.4v * 8.3% = 1.5162v
1.45v * 5% = 1.5225v

1.4v * 10% = 1.54v
1.425v * 8.3% = 1.5432v
1.425v * 10% = 1.5675v

1.45v * 8.3% = 1.5703v
1.45v * 10% = 1.595v


I have it up to 18.3% on a sheet of loose-leaf, but I've spent too long typing this up as it is....:P And I know that the board won't be as precise with voltage as my calculations are...it will however give you an idea concerning which direction the voltage will want to swing. (i.e. 1.57v will want to swing up and 1.53 will want to drop a little.)

Hope this helps somewhat..... :rolleyes:

(I tried to line it up nicely, but it's getting too late to even worry....5:15am, no sleep as of yet...)

Hi guys its not msi's fault that the winchester venice and san diego cpus wont go above 1.45 vid. Any setting above 1.45 vid will be ignored by the cpu.

Its because newcastle had a stock voltage higher than the 0.9 nm cpus. Neo 2 was built before 0.9nm cpus came out and they need to leave the settings up to 1.55 for the newcastle cpus.

The vcore is about right. 0.25 difference isnt a lot if thats true all motherboards are never spot on because they use cheap sensors.

There is a thread about venice cpus and voltage and they said lots have been frying with 1.75 volts. They didnt recommend more then 1.65 for 24 / 7 usage
and even then keep the chip cool.

I only use 1.65 with my vapochill.

just bought a 6800 gt :banana: :banana: :banana: :banana: :banana:


sale on at www.overclockers.co.uk

Leadtek WinFast GeForce 6800 GT 256MB = 165 pounds inc vat

http://msi.designlab.info/thread.php?threadid=17656

Murdock has some mod's on the 1.97 and 1.98 bios. these are new. they also have a new version of AWD Flash
Murdock also says that they are a new bios layout and such. basically he says its a new code or new sequence layout of the bios.
a guy actually spoke english in there and they replied in eglish.. must be nice i have posted in english and no one replies. ggrr
his issue does not seem to be related to the bios but more so a mod he did to the temp sensor.

has anyone tried either of those 1.97 or 1.98 bios ?


Sideeffect -

i wont run mine above 1.65 i mean be realistic the default voltages are only 1.38 or 1.4 thats a HUGE voltage jump.
mine is water cooled and runs idle 28-32c(depending if im running stock volts or more) and during Prime95 45c MAX.
that is even running 1.65v

the thing is i cant get the bios to give me an accurate setting. basically i have that hole in the vdimm from 1.45 all the way thru 1.6

and .25v different i didnt mean .25 i actually meant .025 but after during more experimenting i found that th ehigher vcore you use in the bios the more the vcore is wrong in corecenter and cpu-z

basically corecenter will report 1.7v for what you have it set,. but its real reading or realtime reading says 1.6
so there is a difference of .025 all the way to .1v thats a major screw up. and its the bios that can control this even though yes many people report this issue but how mnay report this issue with the DFI boards ? or asus or gigabyte ?

And Clockgen will not set the vcore or the multiplier. its like it doesnt work with the venice or something.

Corecenter will adjust the vcore properly BUT dont tell me or anyone else to use it simply cuz thats silly the bios should be handling the voltage settings porperly.

I told people when the venice came out to go buy a NEW board . this damn NEO2 has enough issues running 2 year old cpu's let alone a brand new model.
I guess i should have followed my own advice.
damn pci-express i aint upgrading to something that doesnt give me more performance. not to mention the insane cost facotr of doing so.
but thats the only way im going to get a NEW mobo that ould support this venice properly i suppose. unless of course ALL mobo's are having these voltage issue's.

Lestat are you using the most recent version of corecenter because corecenter, speedfan, systool, mbm, cpuz and the bios all show the same vcore for me. There is a slight fluctuation to the reading but that will be the sensor.

As has been discusssed lots before the sensors on motherboards are cheap and show variations that dont exist when you use a digital multimeter.

The fix for entering bios setup was fixed by me and cd1986 before murdok also. The latest Nfm bios has the fix. Funny that he ignored my post when i first posted the issue weeks ago. :p:

I just read your pictures in msi user forum. Strange i dont get those issues at all maybe its the venice ?

Anything over 1.45 doesnt have an effect maximum setting for my san diego is 1.45 +10 percent which gives me 1.63 volts.

The setting is different in corecenter than the reading but thats because of the newcastle venice thing. Thats why newcastles can use 1.7 volts instead of 1.6 volts with the same bios.

Also maybe its the bios i havnt used murdoks version try using nfm's 1.98 mod and see if its the same.

@ Curroption lol you should of listed the voltage settings from about 1.4 to the max we don't really need to know about vid settings under 1.4vcore.

Also has anyone noticed that under load the vcore goes up? quite a bit also, clockgen says something about startup vid... and max vid... seems like under load vid jumps up another 50mvs.

Quote:

---

Originally Posted by 4rory

@ Curroption lol you should of listed the voltage settings from about 1.4 to the max we don't really need to know about vid settings under 1.4vcore.

Also has anyone noticed that under load the vcore goes up? quite a bit also, clockgen says something about startup vid... and max vid... seems like under load vid jumps up another 50mvs.

---

It was really late and I was a zombie when I listed the settings. The lower VID settings can be useful when using over 10% overvolts.

I've noticed that vcore jumps a little bit when the cpu is under load. I don't trust Core Center or any other software for reporting voltage. If you want to be sure what voltage you're putting through your core, then use a digital multimeter....that's what I do.

All the 1.9 beta and mod BIOSes seem to be giving me really bizarre temp readings. I've seen some mention here and there of this here and there, but i'm not sure if people are having these issues specifically with the 1.9+. Could be a CPU issue? Dunno, I only get it on overclocking attempts - but I haven't done a lot of non-OC attempts yet either, to isolate.

I get negative temps, and sometimes crazy high (like 115C+). water lines seem warm but not hot, and the chip runs when I get these readings. don't know what to make of this. any ideas?

here is a screen

1.9 still in bios, no other bios offically supports x2, I'm sure if your contact is fine that ur perfectly safe just a software issue,

@Corruption where do I test with dmm on the boad for vcore?

Quote:

---

Originally Posted by angra

All the 1.9 beta and mod BIOSes seem to be giving me really bizarre temp readings. I've seen some mention here and there of this here and there, but i'm not sure if people are having these issues specifically with the 1.9+. Could be a CPU issue? Dunno, I only get it on overclocking attempts - but I haven't done a lot of non-OC attempts yet either, to isolate.

I get negative temps, and sometimes crazy high (like 115C+). water lines seem warm but not hot, and the chip runs when I get these readings. don't know what to make of this. any ideas?

here is a screen

---

weird. You get these readings with other programs as well like mbm or speedfan ?

haven't tried mbm or speedfan yet. Will do so if it would be helpful for diagnostic.

everest home and corecenter report the same readings.

I am becoming tempted to try and embed a thermistor between my cpu and waterblock to see if I can tell what the actual temps are, but I am not so sure it's a good idea to try something like that - afraid uneven pressure might risk damage to CPU...

The 2 pins on the cpu that transmit core temps are on the very edge of the cpu, it's pretty easy to attach wires to them, put the wires in the socket and install cpu, but you have to use very thin wires, like the ones on thermistor, could try cutting off the sensor and using the wire. This way you get core reading, maybe it's the sensor on the core thats bad, then you could probably rma it.

But you say its only with 1.9 version bios's? 1,8 gives constant temp readings?

There is definitely some sort of issue with the sensors and the 1.9 bios as i cant get any readings in the bios at all i have to use a modded bios to remove the options from the bios or the bios setup wont even load.

All the windows based temperature monitors give me constant results though.

Wizzard has just added a neo 2 profile to systool which gives the most accurate results from the sensors try and use that see what happens. systool

here it is under 1.8.

I am not 100% positive it doesnt happen under 1.8 yet. I had a strange unstable boot when I rebooted after flashing back to 1.8. I will run @ stock speeds and 1.8 for a while to see if I get any odd behavior.

screen under 1.8

will try systools shortly.

the attachment is speedfan, running under 1.9b8 (leftover attachment from aborted post earlier)

well it did it under 1.8

I guess all signs point to bad CPU at this point, huh? I'll try swapping my venice back in to see if if that clears things up.

I can not for the life of me figure out how to get the hidden bios up. I've done the whole shift +f3, then alt +f2.

I am running 1.8 offical

Hye guys, im purching one of these in two days and a 3000+ vience. Ill report back with my problems!

- Michael.

hey guys I have a question, since I rma'd my cpu to AMD I was wondering how a 4000+ clawhammer would be (since they're out of stock of any sd's) also what about a 4000+ San Diego? I heard the lower multipliers were locked?

I'm thinking of just getting the 4000+ clawhammer and either using it for awhile or selling it and just buying another 3700SD

The lower multis arent locked on the 4000 sandy because ive seen posts with people using lower multipliers.

I wouldnt personally bother with a clawhammer because it wont clock as well unless your using a cascade or something:p

cant you get a refund and buy a 3700+ sandy else where?

AMD doesn't do refunds, also I was wondering about a 4400+ dualcore, how well have those overclocked?

what I really think I'll do is just sell the 4000+ clawhammer from AMD since it'd be new in box and just buy a 3700SD from newegg again

Quote:

---

Originally Posted by angra

well it did it under 1.8

I guess all signs point to bad CPU at this point, huh? I'll try swapping my venice back in to see if if that clears things up.

---

All your temperatures are messed up though not just the cpu. Id suspect the motherboard sensor rather than the cpu. I think it could be that the bios messes up the sensor rather than breaks it as i have had issues sometimes when i flash a bios.

To cure it i reflash using winflash clear cmos take out power lead for at least 30 seconds boot into windows and flash again if it hasnt cured it.

Quote:

---

Originally Posted by uniacid

AMD doesn't do refunds, also I was wondering about a 4400+ dualcore, how well have those overclocked?

what I really think I'll do is just sell the 4000+ clawhammer from AMD since it'd be new in box and just buy a 3700SD from newegg again

---

The dual cores seem to clock really well. Similar to the san diegos in clock rate. If you can afford it.

Ask for 2 x 3200 venice cpus find the best clocker and sell the other maybe :p:

I am astonished the you fellas are even trying an X2 or San diego with this motherboard. the new mobo's are the only ones that are gunna work.
This board is never gunna work properly with the Venice san diego or X2. no bios can fix the issues as they are hardware related not software. A bios can only mask them or work around them to a certain degree.

that being said i have a simply question.

Clockgen allows you to run the 183mhz memory which is the 9/10 divider that DFI uses.
We all know that that value in the bios is labelled as reserved. so why if clockgen allows it hasnt anyone actually enabled it via a bios mod ? I've seen the bios hex. and it says *reserved* yet the ability to make it 183 is there.
now somehting funny is that the 1.98beta mod bios(im not sure if the unmodded beta has it) actualy has 213 233 and 250 mhz in the dram freq, lol thats funny cuz its worthless. The mobo doesnt support preset ram over DDR400. yes you can raise the freq via HTT but not force the ram to run at 250mhz if its ddr500.
mine is ddr500 and i set it to 250mhz. POST says DDR500 but once you get into windows and or memtest its 100mhz. actually anything over 200 defaults the memory back to 100mhz.

I hate the way this venice is treating the voltages im setting in the bios i never know what its set to unless i set it reboot and go into PC Health and look there.

im not brave enough just yet to go attaching sensor wires onto the chip lol but does anyone have a picture of this ? id like to atleast see it.

also same for checking vcore and vdimm with a meter. im not much for using a meter as i never have had the need although i do have one. can anyone provide a link to a "how to" for doing this ?

i sure hope there is a way via a bios mod to address the venice issues i really cant afford to upgrade my mobo at this time. :\

Quote:

---

Originally Posted by Lestat

I am astonished the you fellas are even trying an X2 or San diego with this motherboard. the new mobo's are the only ones that are gunna work.

---

which board are you using/would you use with a X2, Lestat?

I don't know of too many mobo that have come out since the X2 did. I can see what you are saying, but it's not immediately obvious what mobos "should" work with x2 and which shouldn't.

my neo2 has been great with the venice.

Quote:

---

Originally Posted by Lestat

I am astonished the you fellas are even trying an X2 or San diego with this motherboard. the new mobo's are the only ones that are gunna work.
This board is never gunna work properly with the Venice san diego or X2. no bios can fix the issues as they are hardware related not software. A bios can only mask them or work around them to a certain degree.

---

I have a san diego running at 3ghz on my neo 2. Pc is prime stable pc never crashes in what way does it not work?

Lestat maybe you messed up your vcore regulators when you were pumping 12.5 volts into the 12 volt line.

http://www.swjka.com/k8nneo2bios//vcore.jpg

http://www.swjka.com/k8nneo2bios//Vddr.jpg

Just tested vcore with dmm, wow I was tense lol 1.6 set in corecenter, 1.450 +5% in bios cpu-z shows 1.524 idle to 1.544 Load dmm shows 1.560 idle. Whats safe for venice again on air 1.65? 1.75 kills?

You guys know the earliest revision bios that will run venice?

Quote:

---

Originally Posted by urbanfox74

You guys know the earliest revision bios that will run venice?

---

i had tried all the way back 1.36 it works.... any earlier i dunno