did you try a different multiplier?
if you lower vdimm, do you still get the same fsb stable or do you have to back down the fsb?
what temps do you mean? i know for example that most bartons crashed when reaching more than 40°C load temps when they were pushed to their limit. if i kept it below 40°C it was stable...
??? for what the :banana::banana::banana::banana: do you need grease for the socket?!?!?!?!Quote:
Originally Posted by saaya
MSI NEO2 "bugs": all its PCI - Slots have to share IRQ´s... I hate IRQ sharing....
to prevent condensation with sub 0 cooling
Abit AV8:
BIOS 17 adds .5 cpu multys
cant get my BH-5 to work for :banana::banana::banana::banana: in any dimm slot/any voltage (225 as high as it will go :rolleyes: )
got G-skill (TCCD) up to 285 (3,4,4,10) dual channel (primed 15 min then error :mad: )
the .5 multis dont really work and i dont think they are usefull at all so im ignoriing them so far... let me know if you think i should add infos about them!
285 in 1:1? thats very good for the via k8t800 afaik :)
did you do the chipset mods already? increased the psu rails?
ya, 1:1
chipset mods...?
no psu mods...ultra X connect. MBM reads: 12.01, 5.19, 3.42 so they are a little over "standard" :shrug:
did you increase the chipset voltage i mean. vdd vio?
Hey Guys, The F5 BIOS for the GB K8NS Ultra 939 fixes the cold boot issue and seems to have helped th board quite a bit with a Winchester. Someone linked to it in a post. Apparently GB TW sent it to him to try :). Worked great for me.
Get it here toward the bottomof the page: http://www.xtremesystems.org/forums/...ght=k8ns+ultra
Sayaa, maybe you can add this to the correct section in the first post. Thanks!
I like the way you turned a bash fest into a very informative thread. Good work.:)
oya..."maxed out" all but southbridge V (no HS on it yet...) and CPUQuote:
Originally Posted by saaya
AV8s have volt settings for:
cpu, NB, ram, SB, hypertransport (edit: ) AGP
(@ work, will edit if my memory errored)
thx a lot andy! :toast: added it to the first page :)
feel free to send all people with 939 problems to me/this thread :)
btw, will i get the cd for christmas? :D
:D glad somebody noticed it :toast:Quote:
Originally Posted by Zebo
gl joe... but sounds like the chipset is maxed out to me :/ maybe bumped rails give you a few more mhz...
Saaya , I got an question about the Epox 9nda3+
Will a vmod for the vdimm also killing the board ?
Or is it just the OCZ Booster thats blowing the mofset ?
Thx
i think its just the booster... but im not sure, check if theres a vdimm mod for the board somewhere, i dont think a vdimm mod would kill the board though... epox wouldnt be that stupid to make a vdimm mod impossible :D
they made that mistake once with the 8rda+ and it hit them bad, so i doubt they make the same mistake twice :)
Epox 9nda3+
Ive had no problems with undervolting vdimm up to 3.3vdimm(not tried higher as my EB doesnt need it)
This board DOES have problems with TCCD and Bh-5 as of release bios(havnt been overclocking ect. much so i havnt been keeping up with bios revisions)
256 meg sticks of BH-5 work flawlessly on this board but 512meg sticks it hates with a passion to where it will not run 1T at any voltage up to 3.3v at ddr400 2-2-2-5. It LOVES micron chips tho. my 3700EB 2x512 will run 272+ flawlessly with 3.28vdimm 3-2-2-8 1T.
It doesnt overclock my cpu as far as my asus did at the same voltage. the asus would send my 3500+ NC to a touch higher than 2.7ghz. unfortunatly im only able about 2.65ghz on the epox.
There's a post in the vmod section for vdimm/vcore mods but i havnt yet found the vdimm read point so im working off the sensor that i believe is accurate if not a tad low.
There's the vcore/vdimm mods anyway.
http://welloverclocked.com/Epox.jpg
http://welloverclocked.com/bh-55.jpg
There's the better of my 2 sets of bh-5(other set did 250 with the same 3.28vdimm)
here's the money shot with my EB
http://welloverclocked.com/273-32210.jpg
great :toast:
please let me know if the memory issue still exists with the latest bios :)
afaik the latest bios makes tccd running just fine and 512mb sticks work fine as well.
This is what I came across in the release notes of the latest BIOS --->
:eek: Say what!Quote:
** Support DDR400 for double banks DIMM.
Is it wrong to expect that in the release BIOS... lol
BTW vdimm will go to 2.8v with the latest BIOS, although it does jump around all over the place (poorly regulated) and under volts. For earlier BIOS', System Performance would have to be set to normal, for vdimm to be set to 2.8v...
''The newer northbridges (0410/0411) seem to need less vdimm to reach the same overclock in 1:1!''
How I see which I am I number it mine northbridge?
I caught we memos with chip Ch-5 are good?
Thnks..
Mickey Mouse :D
you have to remove the nb heatsink
i dont understand your second question :D
you have some private messages btw :D
The Epox has issues with the ras to cas delay option.Quote:
Originally Posted by Mongoose420
I tested it with mine a week ago.
The max i could run with this board was :
http://home.quicknet.nl/qn/prive/pjm..._2.5_4_3_7.JPG
If i set the ras to cas delay option lower than 4 i cant even boot above 240 :confused: :stick:
Well my guess its a bios issue and knowing epox it will be fixed shortly :D :toast:
very possably for your memory. but ive had 3 sets of memory all above 250 trcd2 1T.
I'm having a hell of a time getting anywhere clocking this 4000+. I keep getting "NTFS.SYS" BSOD errors. My bios is 1.37 and the only thing i can think of as a problem is i am leaving my AGP locked at 66, does the MSI k8n neo need the agp set to 67 to actualy lock even with the 1.37 bios? gawd i hope this is the problem cuase as soon as i go over 220FSB it bluescreens with the ntfs.sys error even though the CPU is at -56 and the evap is at -67.
Whats your HTT set at?
Looks like its to high.
I saw Gigabyte K8NXP-SLI at Gigabyte websites....so they have release it ? But i think this motherboard will expensive :( like other ***NXP model's.
http://www.gigabyte.com.tw/Motherboa...K8NXP-SLI.htm#
http://www.gigabyte.com.tw/Motherboa...xp-sli_big.jpg
Sounds like your SATA drives aren't on locked SATA ports...Quote:
Originally Posted by DGeNeRaT3