Printable View
Quote:
Originally Posted by Jupiler
yeah i gues those dancing bannas are going to offend someone.
@grave digger
dude its not that i dont belive you man but you suport your theory with nothing and you act like im some idoit. when i can set the voltages to 1.55v and raise and lower the vid and watch the voltage go up and down in both the bios and cpu-z i tend to believe its working. no need to roll you eyes and act like im stupid cause all im going by is what i see....
peace perc,
m8, plz understand that i'm not an perfect english speaker, and maybe my
words look like "i called u an noob". I'm sorry! But if u forget CoreCenter
or all other Win.-Tools, 1,475V ist the highest option u have in Bios, if u
use the x% , too! Thats all i want to say m8! :)
ok well sorry for over reacting man. im just frustrated with this mb atm and like i siad to me it looked like it was working maybe im wrong wouldnt be the first time. ill try what you said and see if it helps...
thx perc,
If so vid over 1.45 = 1.4, 1.4 = 1.36 and so forth.
After 1.45 need %vid to up vcore, winnie screwiness - think this is sorta mentioned up front on the thread now? (Winnie self-defense mechanism?)
1.36b = 136Mod ?Quote:
Originally Posted by muzz
let me see if I understand...if you set vcore to 1.5, 1.525 or 1.55v it really is just setting it to 1.475vcore...only way t oreally increase vcore is with the vcore over vid..ie 3.3%, 5% etc
I am using 1.36b
well that explains why 1.475vcore and 8.3% over vid gave same numbers as 1.5v with 8.3% and 1.525v with 8.3%
so is there a disadvantage to setting 1.5v w/8.3% over vid..which is what I have ..should I go back in the bios and set it to 1.475vcore w/8.3%
also do you need to set agp to 67 to lock with the 1.36b, 1.37b, 1.41b....or can you leave it at 66???
nope, just get 1.36, 1.36 mod is not the same. you want 1.36, here is a direct link: http://www.lejabeach.com/MSIK8N/7025v136.zipQuote:
Originally Posted by Jeager
oh really? I think a lot of ppl thought what he thought (including me :D) and got the 1.36mod. maybe there should be a link to the 1.36b bios on the first page.Quote:
Originally Posted by DevilsRejection
FlyingHamster I love your sig pic....Hmmm
Also I set AGP to 67 on general principle :D
hehe thnx nealh ;)
perhaps u guys could help me out too. my k8n neo came in, and on the NB it says 0440A2 Taiwan. do u think this should be a pretty good performer?
That have nothing to say. Try it! :)Quote:
Originally Posted by FlyingHamster
lol I will once my 3500+ comes in. :D
I also got the Zalman CNPS7000B-AlCu, and was wondering if I have to take off anything on my k8n neo2 before installing it. anyone know?
which Ram is the best for a non-modded neo2?
TCCD RAM is. Specifically, the G.Skill LE does wonders. That, or the Patriot /w XBL. Each uses the Samsung TCCD chips with brainpower PCB's.
Also, that new OCZ VX, in combination with Boosters are amazing together, so I hear. I've never tried them myself.
What memory dividers the msi k8n neo2 have?
thx
If I remeber correct you can chose 100/133/166/200 and 200 is 1:1
where can i find modded variants bios????
Which bios works with bh5/6?/////
dude just read the first post of this topic!Quote:
Originally Posted by apostglen46
and:Quote:
TIP: bios 1.36b and 1.37 and modded variants seem to work best for bh5/bh6
:stick:
The 1.36b seems to be the most popular ones, followed by the 1.37b, and finally the 1.41.
Yeah loose the top & bottom (bottom extrusions through the holes muck everything up :mad: (much easier to bottom remove b4 you use it, use hair drier on bottom if needed), then replace bottom plate w/ the zalman and screw in the brass standoffs. Assuming you haven't removed the heatspreader on chip should be good to go. While your at it, redo the paste on the NB and maybe lap it? b4 putting it all in the case.Quote:
Originally Posted by FlyingHamster
We await results! :D
Anyone know why developers have not added in original Bios support of the function of ventilator management on NB ?
maybe it has some enorous bug or something?Quote:
Originally Posted by nafigator
im sorry i dont completely understand what your saying. so I need to take off the msi backplate with a blowdryer, then use the backplate from the zalman?Quote:
Originally Posted by mad mikee
Anyone have noticed the problems? I no :D Apropos after installing bios 1.51mod beside me temperature on 10 gr. fell. You else want to change fan? :bounces:
Xiode..that sig pic is great..LMAO
Thanks. :D
Anyway, I'm thinking of RMAing this board. I'm going to wait until I get my RMAed 3500+ Winnie back, along with some new G.Skill LE which should be here tomorrow. I can't wait! :p
mine refuses to go over 220fsb dc...... on singel i can hit 280 but dc i cant even hit 220......
Very bad Northbridge! Try to RMA it or sell it on ebay. ;)
why?Quote:
Originally Posted by GravediggA
dont think its the nb because with dividers i can hit 410fsb
Mine too... that was with BH-5 @ 3.3vQuote:
Originally Posted by Snowman89
Pumping 3.6v through it makes it absolutely stable @ 260!
Yay, I got my new G.Skill LE from NewEgg today. :D Only problem is, my RMAed 3500+ Winnie won't be here until next week. :(
aww man what a shame
where did u get it from? and why did u RMA it?
hey guys!
ive been learking in this forum for a while and i finnally signed up! im not really new to ocing or anything but i think i may like this forum better then alot of the others out there...
anyway i got this board w/ a 3000+ winnie week 42, just got my gig of gskill le (yay!) today so i can finally run 1:1. right now im running at 9x260 1:1 2340mhz. but i cant get past 260 stable, i dono if its the NB or the mem controller on the winnie. ive tried mutliple bioses, all the hidden options set right, ldt @ 3x blah blah blah. someone said putting new HS compound on the NB might help which i plan on doing. he also said "lap the NB" whats that mean? ive been considering getting a 3200 n trying that but if its the NB then im not gonna get anywhere. oh n i seem to get mem errors at anything over 260 even with mem at or below rated timings so does that point to NB or chip?
thanx all great thread lots of info that already helped me out! :toast:
And friend of me had an Gigabyte nforce3 and can't past 220 with Dualchannel,Quote:
Originally Posted by Snowman89
with one Stick he can run 285 without any problems. Now he changed to an
MSI and can run max. 303 2.5-4-4-7 1T Dualchannel! There are other Gigabytes
out there who can run the same, but thats the reason why i'm sure, that it is
the northbridge! :)
My Gigabyte nForce 3 don´t works over 230 with 1T. I selected 2T and than the gigabyte runs with 275 fsb. Its a crazy board, the msi is not better. It works wonderful with 250fsb and with 300fsb, but with 251 to 299 it runs totally instable. After 2 or 3 seconds in superpi I became the error message :( supid mb
Assuming you have done everything you can possibly do, then your bottleneck could be your cooling or the processor itself......looks like week 44-47 is getting best results.Quote:
i got this board w/ a 3000+ winnie week 42,
I just got mine, 3200, from ZZF yesterday, its a 447 SPAW, I hope to fly high...wish me luck... :)
i made some progress! thanks to u guys of course. anyway this got me thinkin.
i remembered seeing this somewhere and i thought i tried 300 before w/ no post. so i said what the hell set the htt to 301 drop the mult to 7 used the 166 mem divider and what do u know. boots into windows! then runs benchmarks!! superpi, S&M 1.3 fpu test for 20min no probs. sandra cpu and mem. halfway through 3dmark 03 had a restart. bumped the mem voltage from 2.7 to 2.8 makes it through 3dmark 03!!! so i started playing a game for further test but alas after about 10mins restart with a bsod flash (i had this before with mem problems) even tho the mem is running below rated speeds w/ the divider i decided to try setting the command rate to 2t and its priming large FFT's as i type (on the 3rd test) this is amazing! weird board eh i couldnt even get to the windows loading screen at 270 thanks a million guys i would have never thought of this! :toast: :banana:Quote:
My Gigabyte nForce 3 don´t works over 230 with 1T. I selected 2T and than the gigabyte runs with 275 fsb. Its a crazy board, the msi is not better. It works wonderful with 250fsb and with 300fsb, but with 251 to 299 it runs totally instable. After 2 or 3 seconds in superpi I became the error message supid mb
At the Moment I´m use 307FSB 1:1 3-4-4-8 1T. When my system runs with 275 2.5 3-3-7 2T I lose too much performance. 1T with 275FSB would be wonderful. The multi on 9 and 275fsb is running stable but when i use 10 or 9.5 with 250 - 279 than I becom the "not exakt in round" error message after 1 or 2 seconds by superpi.Quote:
Originally Posted by chipmonk010
Is the MemoryController or the Mainboard or my Ram the Problem? I don´t konw :(
Whats up with boot menu on this mobo, stays forever loading up, stuck at the memory prompt and Norton Ghost cant see my raid setup.
perc listen to gravedigga ... he is right..Quote:
Originally Posted by Perc
try this!
If you have a multimeter connect the negative probe (black) to a molex black wire , and place the possitive probe in the missing capacitor in the left side of the CPU socket
Set the Multimeter to the 2V setting and then try several bios Vcore settings to see what is the real Vcore .
My experience says that you should consider 0.05V more than CPUz reports
:toast:
Just cheked what esdee said above, i'm getting 1.78idle & 1.79/80 at full load, bios 1.3b6 no mods, just vcore set to 18.3%.
Damn the officiel 1.4bios suck. I can only have 1.55+10% (1.64 max in the bios/windows) :(
:banana: Hey You guys all around here - wanna thank You all for You help -
without reading all this stuff here I wouldn't be able to do this:
:D LOOK !!! :D
:toast:
Again with my settings questions:
Advanced CMOS Features:
System BIOS Cacheable - Off/On?
I put on off (default BIOS 1.36B) but I don't know what it do... I was told it can help stuttering on some games!
AGP Aparture size:
Should I put it on 256M or 512M? My 6800GT has 256MB Vram ofcourse...
Thanks !!! :banana:
I think 256mg is best...but I can not recall the reason
Thanks man.
What about the "BIOS Cacheable"? Do you have a clue?
Thanks in advance :D
Hi all...long time reader, first time poster...
How accurate do you guys believe Memtest86 or Memtest86+ to be when testing RAM with the Neo2 and other Socket 939 boards?
With the configuration in my sig, I can post at 250FSB, but not boot all the way into Windows (running at 1T-2.5-3-3-8 or 1T 2.5-3-3-10, 4x HTT, and 1.5-1.55v on the CPU, 2.7v on the RAM). At 240FSB, I can boot and run, but shutting down takes forever compared to stock speed, so I don't trust it completely. At 225FSB, things seem to work pretty well. However, at both 240 and 225, Memtest86+ 1.40 gives me a fair amount of RAM errors. I've tested both 240 and 225 with Folding@Home and it has run for hours without failing.
I don't know what chips are on my RAM, just that it's a dual-channel kit of Kingston HyperX PC3200, part number KHX3200AK2/1GR (I've heard rumors that it's Winbond CH5, but it's not proven, specs are at http://www.valueram.com/datasheets/KHX3200AK2_1G.pdf ). At stock speeds, it runs fine at 1T-2-3-3-8 (I believe it's spec-ed to run 2-3-3-6, but haven't tried it). Should I try upping the VDIMM? Or is it possible that Memtest86 doesn't truly recognize the way the Athlon 64's onboard memory controller works?
I always run with BIOS cacheable. I don't know if it increases performance as much as it used to in the 386/486 days, but it always added a little more zip.Quote:
Originally Posted by Swing
Plus, you can't do an emergency BIOS hot-swap without it (and yes, I have done this). ;)
Your ram most likely cannot handle those high FSB @1T, if it has TCCD chips I would say it could, but seeing that your SPD is loose even at stock I think you are stuck at those speeds. Loosing the timings and running a divider might help, but if you want >250FSB you have to look elsewhere.
well, I'm now running at 200MHz 1T 2-3-3-6, 5x HTT, no problems, and testing has proven it to be stable. Specs are supposedly 2-3-2-6-1 now that I've read the .PDF, though I don't think that'll change things that much. It seems the auto-timings of the Neo2 were really lax, or the SPD on the RAM is set lax by Kingston, or the board isn't reading the SPD right. I'd think there's got to be a way to go up stably, if my machine booted and ran okay under stress at 225. However, I'm wondering what the tradeoffs are, that is, if what I lose in setting the RAM and HTT speeds is worth gaining the higher processor speeds.
:D Yep - got the same with the A-DATA DDR-600:
SPD 3-5-5-10 at 303 (?) MHZ - BIOS auto detect 3-3-3-6 at ALL speed and running 3-4-4-8 at 300 MHZ.........crazy stuff !!!
:toast:
Im doing the same thing Charlie. Im using a 3500+ to hold me over till the FX-57.
Quote:
Originally Posted by Judaeus Apella
:slobber: :slobber: :slobber: :slobber: :slobber:
Uh.. forget that last roadmap...... it might be faulse...... oops. Sorry Hampster! I was the only one I could find......
Update: Up to 225MHz FSB at 1T, 2.5-4-4-8, now fully stable under Memtest86+ at 2.7v on the memory. There's probably more room left, but I'll run it this way for a little bit then try upping it again.
As for cores, I'd also be interested in Venice. The enhanced memory controller and SSE3 support may up the video encoding performance somewhat.
Hello new to these boards but have been a member of Futuremark`s MB for 4 yrs anyway here is my system:
Msi neo2 1.51x bios
Winnie 3200 watercooled TBX block week 0444
BFG 6800 GT OC 256mb
Corsair xmspc3200xlpt 2x512
Audigy2 zs in slot 3
Maxtor 80 gig ide 1
WD SE 80 gig ide 1
Lite-on dvd rom ide 2
Lite-on burner ide 2
pump relay switch
Enermax temp reader and fan controller
4-80 mm fans
2-120 mm fans (radiator cooling)
Truepower 550
ok this is what i have gotten so far : by spd my ram is rated for 2-2-2-5 which i ran stock 200x10 1.4 vcore,2.7 vdimm and ran memtest for 11 hrs and no issues what so ever,i read that this ram will only do 2-2-2-5 to 214 fsb 1:1 well i laxxed the timings a bit and ran 2-5-3-3-7 1T 225 fsb and got 9 memtest errors in 2 hrs
ok now ive gotten these settings stable: 255x10 1.51 vcore, temp at idle 38c load is 49c, timings of 2.5-3-3-7 1T vdimm 2.8,AGP 67 3xHTT and ram is running at 212fsb
ive smacked 2.75mhz 275x10 1.55x10.0% with the 133 divider but temps hit 55c underload
i cant do 225,235,240,245,250 fsb 1:1 without getting errors with timings of 2.5-3-3-7 1T 2.85 vdimm
i have seen on a few sites that my memory might be TCCD but im not sure without pulling my heatsinks off
sticks are in 1+2 and i get the same errors with 3+4 slots at above fsb
should i try laxxing the timings even more or drop my multi to 8 and go up from there this board has got me baffled,not new to o/clocking but this thing is making me pull my hair out, I want higher 1:1 action lol any ideas would be greatly appreciated
the 1.51x bios the best to run on these boards ?
oh and i dont have a fan plugged into the cpu fan header could that be problem ? i dont have boot issue...well i did but its was a bad power cord but thats solved
http://www.xtremesystems.org/forums/...ad.php?t=50367
anybody experienced the same problem?
thx
TCCD is known to go all the way up to 300HTT with loose timings, the fact that yours craps out might suggest its not. Removing the HS is not all that problematic...
my friend's 3200+ can not do anthing over 225+ htt or above either i think its the problem with the winnie as i know some people with the same problem.
if you use only one stick of ram my m8 can do 293HTT 1:1 stable but fails prime and superpi with 2 sticks at around 225htt or above.
btw he's using the OCZ Rev 2 TCCD ram.
Hi all,
How on this board do you flash a beta bios from windows. I have a Vapochill I need to update the bios to work with the winchester chip. Is their a utility for this?
Thanks
Yes you can safely flash in Windows using Winflash, thats what I use
Is this the same Winflash I got on my DFI UT3 drivers Disk? Or do I have to download a different version of Win Flash for the MSI board?
The MSI boards all come with their own WinFlash if I'm not mistaken. If you install MSI Live Update on the driver CD included with the mobo, then it's included. Kind of hidden, but included.Quote:
Originally Posted by pazza316
C:\ > Program Files > MSI > MSI LiveUpdate > Award > WinFlash
It's something like that. I'm just reciting it from memory. It's been a good month since I've used it.
Any special bios for tccd that gives the +18% vcore option too?...
Need to freeze my fx55, finally got a cpu kit :)
Tccd testing, brainpower pcb with 2,7v...
http://img34.exs.cx/img34/7066/semttulo5lj.jpg
Anyone with a neo2 that when choosing 2,85v in bios get only 2,7v real in mem's ? (read with a multimeter)
Weird :banana::banana::banana::banana: :confused:
Have anyone solved the problem with sub-zero temps on winchester+msi? I read a lot about it but i still don't know if this is a cpu or mobo issue?
I'm quite scared of getting winchester/mobo which won't run with my phase change...
This new BIOS is suppose to fix the problem.Quote:
Originally Posted by Adasi
I picked up a Newcastle 3500+ last week so that I can run my prommie...still have not read or heard any concrete fixes for the sub-zero problems with the winchesters.
Wingz, are they suggesting that its a motherboard problem rather than a CPU problem?
I've got a 0441 3200+ Winnie here that does not like the cold...
I've tried it in 4 different K8N Neo2's to no avail... 2 x 0419 & 2 x 0437 date codes...
Tried it with every bios there is for the K8N Neo2 but no go...
So imo, it's a hit & miss affair with these Winnies & sub-zero temps... Some like it hot & some like it cold...
Currently using a 3500+ NC because of this problem... At least it bloody runs...
Was trying to see if I could get my 3200+ past 250HTT... If it could boot that is... It booted but looks up as soon as it hits Windows... That's about the time it takes for my Vapo PE to hit sub-zero temps...
At least with my 3500+NC, I'm able to run 11 x 250 HTT for a cool 2.75GHz...
Now trying to get rid of one of my Neo2's to wait for the DFI NF4...
Cheers,
Minnyboy
Why don't you try epox on nf3?Quote:
Originally Posted by Minnyboy
It looks like i can't buy Neo2 because of the temp issue :( :stick:
Would buying the 3200+ winchester instead of the 3000+ winchester make any difference ?
Thought both overclock the same ?
The 3200+ has a higher multiplier which might help with overall overclock.
I have heard some bad reviews (especially from members here) about the NF3 Epox board...Quote:
Originally Posted by Adasi
I still have another 2 Neo2's here to play with... Well, one is in RMA & the other one has 2 smd resistors knocked off when removing my Hyper6... I touched tha resistors & they actually fell off...
It's getting fixed this weekend so hopefully it'll work well with my Vapo & 3200+ Winnie...
If not, then I'll just stick to aircooling & 3200+ Winnie while I wait for funds for the DFI/FX57/X850XT PE PCI-E... Not bad when I can get the PowerColor X850XT PE for US$611 (AUS$812)... Add some VX for US$282 (AUD$375)..
Ahh, the perks of being a reseller here in OZ :D:D:banana:...
Cheers,
Minnyboy
Minnyboy...what resistors fell off the mobo???
If you look to the right hsf retention, you'll notice a bunch of resistors there.Quote:
Originally Posted by nealh
Well, the 2 by themselves are missing.
I have a knack for knocking resistors off... Did it to my 9800XT a while ago... While prying the stock Intel HSF off....
The Neo2 still boots up & all but I don't wanna damage it any more than I have already... I have heaps of those SMD resistors spare... Around 40 of them... Just waiting for my mate to come over & solder them for me...
I can solder a bit but them resistors are darn small...
I might take a pic of the area where the missing resistors are attach them...
Cheers,
Minnyboy
Does any of the BIOSes work right with LDT/"HT Frequency" below 3x?
Seem this board doesnt like my BH-5. I cant overclock it at 1:1 divider at all.
Got my board fixed yesterday...
I hope they use 10nf smd resistors on their boards... Certainly looks the same...
C66 & C65 were the ones missing/knocked off... Boots up fine. Just getting to the part where I rebuild my rig again...
Dammit!!! Can't seem to break the 30k barrier in 01... 29,880 is the best I can do... Haven't turned the volts up yet...
neokenzo,
Mosy Neo2's don't OC well with BH5 @ 1:1 without more than 3v... You should know that...
The best I can do with no OCZ Booster & BH5 is only 217MHz (XMS3500) @ 2-3-3-7.. Using 2-2-2-5 @ 2.85v, I can only do 210MHz...MemTest stable...
Cheers,
Minnyboy
Was wondering what timings you guys using OCZ 3200 EL Rev 2 were using with the Neo2??? Would you mind posting your results and vdimm? Thanks
i'm currently running my Neo2 with my OCZ Plat R2 at these settings:
Speed: 275
Timings: 2.5-3-3-7 1T
Voltage: 2.85v
It's good for 277HTT with those settings, memtest stable :)
---dens
newb question: why do ppl say xxxHTT? is it not the same thing as xxxFSB? just another way of wording it? would appreciate it if somoene could help explain this for meh :p:Quote:
Originally Posted by DeNs
Could you please check if neo2 can handle such configuration:
winchester 8x300
memory 2,5-3-3-8(X) 1T changed with A64Tweaker to 183 mem divider ( it should be around 275 2,5-3-3-8(x) 1T
and to prove it run spi 16mb
TIA
yeah seems reasonable,Quote:
Originally Posted by wampir
very possible :)
dont have them tho'
so i cant test it for ya
Works fine. All in A64 tweaker work fine with my Neo2 when you have booted with higher divider; for example 166->183 does not work but 200->183 works just fine.Quote:
Originally Posted by wampir
i have a problem with my neo 2:
The mainboard dont recognize my Soundblaster audigy 2 zs.I' tried every pci slot with bios 1.3, 1.36 bitpower and 1.4, but nothing.
Some one can help me?
Hey all,
I recently tried assembling these and ran into the dreaded cold-temp glitch.
For me the temperature would always read 40C, WinXP would load and freeze or reboot.
I could boot into the bios or run Memtest86 without issue.
I went back on air-cooling and all is fine (2.6ghz, 10.0x260 at 1.55v Vcore).
This was with the 1.41B modified bios (http://www.lejabeach.com/MSIK8N/k8nneo2.html).
I have been contemplating pulling the CPU and RMA'ing it, verses trying the 1.5X bios.
Anyone actually have any luck with this other bios?
What I mean to ask is: Has anyone having this type of problem, updated to this bios and have the problem go away?
Karl
pci/agp are clocked i presume?Quote:
Originally Posted by daryl
i havent seen this problem before so
i cant help you out here, sorry
its a cpu related problemQuote:
Originally Posted by Karl Norris
some winnies like cold others dont
Hi you Nerds out there, whats your opinion to the following OC run..:
Sorry for long post..
assuming there is a rig consisting the following:
Neo2 Platinum Korea CS Bios 136 Mod...
Winchester 3000+ 0440 SPAW
2 X TakeMS 512 MB DDR400 3200 2.5,3,3,8 1T
6600GT , Chieftec 360W PSU with 12V/17A / combined 340W..
along all tests the Coretemp stayed below 55° at load..
HTT @220, Ram 1:1 /220Mhz HT 3x,,2,5.3.3.8 ,,1T,FFoff, agressive etc, all disabled. AGP @67, SpreadSpect. off --> stable..
Same but @230 Mhz , Ram 1:1 --> crash at boot --> ok think Ram is at its end (TakeMs are nown that they usually give up @225 Mhz).
So: Ram Divider to 166:
HTT @ 270 Mhz, RamDiv.166 = 220Mhz, 1,45 V Vcore , other settings as above --> everything fine stresstest etc.., looks stable.
HTT@ 280Mhz other set. as above --> crash, Ram is holding back again..
HTT@280Mhz, Ram133 = 180 Mhz, other settings as above --> stable.. remember still running @Vcore 1,45 Volts
HTT@285Mhz, Ram133, other settings see above --> BSOD: irq notl essor equal uhmm well. maybe the voltage?
Same as above but with 1.6V VCore: --> crash@boot
:confused: voltage seems to make no difference..
What is holding back now? The Rams are @ 186 Mhz or something, so they are underclocked (should work at least @200 Mhz).
Next test:
HTT@285 , Ram Divider 100, 150 Mhz :brick: Vcore back to 1,5 V,
--> stable.. but the Memoryclock.. :eek:
HTT@290, RAM still @150Mhz --> stable
HTT@300, RAM l around 160Mhz --> stable
Htt@310 " " " ,Vcore 1,65V, Vdimm2,85 Voltage doesnt matter --> BSOD
I would highly appreciate listen to your thoughts:
What do you think, is the MCU of the A64 at the end? Or is it the cheap Ram which drops.
If the memclock is around or below ramspecs, is there something which nevertheless loads the memory and can cause failure at high Htts?
The ram works fine @220Mhz but only at low httclocks, the higher the htt the lower the Ramclock must be (far below the specs)..
why?
Next question in mind: i read all the posts of these
:slobber: godmode rigs with high Vcores and that most of them achive better results if they feed more voltage, i personally found that voltage (other than size) does not matter. I reach best result with near stockvoltage, rising the Vcore makes no difference. Why that? Am i missing something?
great forum ..
thx
Hey Jack,
Thanks. I've come to believe this too from reading through piles of threads :D.
I'm going to RMA the cpu and try again. If it's still intolerant, I'll run it on air-cooled for the short term.
Karl
wow my neo2 died.. has anyone else had problems like this before with their board? :(
http://www.xtremesystems.org/forums/...ad.php?t=51411
Did you change the original chipset cooling ??? It's very noisy :mad: 5000rpm . Can change it for self made heatsink ( cut heatsink from celeron 466) is there a problem to run with it and overclock ??
The Swiftech NB Cooler is VERY nice and fits great... may interfere with large GPU, though....
Ive purchased the neo2 after reading this thread :)
I've hadnt had the chance to overclock because want to have updated all the drivers etc...
But when i connect my new floppy drive ... nothing happends.
I can see the floppy drive in "my computer" but when I dubble click it , it tells me to put a medium or something else in the drive ?
But there is already a floppy in the drive ?
Do i need to install some drivers or etc ...
Anyone had this prob before ?
stupid question, but...
I can't find my actual pci/agp bus speed anywhere. Even sisoft sandra, which on my other computers reports "agp 4x (4X66 MHZ)", reports only "8x". Is there any other utility that will show pci/agp bus speed? cpuz doesn't, corecell doesn't, speedfan doesn't, everest doesn't. I'd just like to prove that I'm not accidentally upping the speed of the pci bus.
A64 3000+ winchester at 2300mhz, voltage at "auto"
230 FSB
x4 htt mult
2x512 crucial ballistix pc3200 at 230mhz, 2.5 3 3 8, voltage at "auto"
thermalright xp30 with 90mm fan running approx 3100rpm
I still haven't hit the "wall" on OC (corecell rebooted at around 260mhz with those mem timings and air cooling) but even at 230 mhz prime95 reports an error after about 6 hours so I've left it at 230 for now.
Another weird thing - When I manually set a cpu core voltage in the bios, the corecell vcore adjustment works in REVERSE! I damn near fried my cpu. It was manually set to 1.55 in bios, and when I opened corecell it showed 18% over. I dropped it to 0% over in corecell and the voltage jumped to over 2v and reported cpu temps went from 125F to over 160F almost immediately. Almost crapped myself before putting the overvolt setting back to 18% which dropped temps back to normal. It does this in both shipping version and latest version of corecell (1.6.9 and 1.7.something). I'm using 1.4 bios which came installed.
Anyhow, I really need a pointer to a utility that will report pci bus speed. Thanks in advance.
flenser
Yeah, get and install ClockGen from cpuid.com. Make sure you get the one for NF3 boards. You don't have to use it to OC, or anything, if you don't want to, but it will show you you're AGP/PCI speeds.
Also, it is my understanding that you should in NO WAY use CoreCell to overclock. Just use it for informational purposes and, even that, with a grain of salt.
Thanks. At 230 fsb I'm getting a bluescreen reboot with the pci less than equal to error. Dropping to 220 fsb cures that. I'm not sure if it's cpu or memory that is causing it. I have no irq conflicts and the only card installed is an audigy2.
Hi flenser,Quote:
Originally Posted by flenser
IRQ not less or equal it showed i think. Not PCI...
This BSOD often means a problem with memory / adressing, i don´t think its your pci Bus clock which causes the problem. Have a look at ram.
Next: i had also this wierd voltage readings, mine showed sometimes 3,2 Volts Vcore.. in corecell.. this went away with "update" to 1.36mod bios. I dont think that these Voltage readings are for real, its just a fault in measure / reading..also the temperatre readings were way to high..
But the subzero boot problem is resolved? I haven't understand it yet ...... :confused:
I think right now it is a hit or miss with the sub-zero temp problem. As for me, I am taking a gamble and just ordered a retail 3500+ winnie, in hopes for a new stepping so that I can try with my Mach I. I will definately post, when I get everything set up and tested.Quote:
Originally Posted by vkbms
Right, it was IRQ not PCI, my mistake typing faster than I was thinking.
Memory checks good 8 hours in memtest86 so I'm not sure. The computer only BSODs like that when running this one game... Unfortunately it's the only game I ever play so I'm hosed I think. I thought if memtest was good then it wasn't the memory that was the problem, but I guess not. I've tried running the mem voltage up and down but that doesn't seem to do anything. Maybe I should up the memory timings...
For what it's worth, my AGP/PCI speed is 67/33.5, right where I set it so that's probably not the problem. I thought it might be the vid card but I ran rithdrbl for a few hours and that didn't crash it, ran both rithdrbl and prime95 for a while, and that didn't crash it. It's just that one game that dies at 230 fsb.
I'll probably drop it to 220, open a cream soda, and try to be happy with a crummy 10% OC. I don't use corecell for anything but an occasional test, but since the auto detect bit took it up past 250 fsb before it rebooted, I really thought I'd get more than 220 FSB out of it. The crappy thing is that I really won't be able to tell if it's the memory or the cpu without doing several more days of testing, and even then if it's like now, where everything tests great except for that one game, I'm not sure I'll ever determine what the problem is.