late breaking news, ignore all my past posts about 2395 having tighter timings. LOL, i was way off. Whatever they did with the move to 2395 they lost performance on the board. Posting table soon :D
edit:
wait, maybe it's just mem bandwidth and latency. still testing
ok, 2333 is better, at the very least it is more stable and a tiny better performance.Quote:
Originally Posted by Blauhung
blue is 2333 in the picture
oh and the last row of benches is 3dmark cpu test
and final edit, ignore my voltages i will still have to lower them a bit.
and also got some stuff of the 800 strap vs the 1066 one. Basically it looks like there may not be much difference at all. I was trying to hold as much constant as i could. the only real nod I would have to give the 800 is that it looks like it is faster on 3dmark06's cpu test then the 1066 strap
the real interplay that is going on here is the fight between memory bandwidth and latency. bumping up the FSB has a HUGE impact on how much bandwidth you get. It looks like that bump is fighting against the higher latency on the 1066 strap and is very close to winning especially with pi times. i will be doing more. The hardest part is trying to find settings to compare CPU speed at different FSB and still get the same memory clocks.
Nice one Blauhung! Those are really helpfull.
Ill stick with 2333 and 1066 strap.
Nice work, Blauhung :toast: That'll come in handy.
yep, awesome work :toast:
the 2333 need more vfsb ?
I would say nice work but I have no damn clue what it all means.
as i said, ignore my voltages, a few of them are higher then they need to be. I just was sitting at something i knew worked, I had to head to the girlfriends house so i didn't want to waste time messing with optimizing voltages.Quote:
Originally Posted by Supertim0r
Heh, you were gonna optimize something else. ;)Quote:
Originally Posted by Blauhung
I HATE this board :mad:
WHY do I need to switch that :banana::banana::banana::banana:ing jumper when an OC attempt is screwed. And that's not the only thing, you have to switch it back, and last but not least: It is so hard to reach there by my VGA card and some caps. I wonder how long it will stay working :confused:
Isn't there an option to "reset" the settings by holding a key or something? By my old MSI K8N Neo I could hold Insert and then power up, but it doesn't work on my badaxe 2.
IT DRIVES ME MAD :slapass: ALREADY beaten the front of my DVD player :D :D Throwed my PC on the side so what's next :cool:
Will this board run 400fsb on the 1066 strap? or does it go to the god forsaken 1333
I don't know why you guys are having these problems with reset, switching jumper, etc. :confused:Quote:
Originally Posted by NoepZor
I had never have to use that mobo switch. After each failed OC attempt when board does not post, all I have to do is to turn off PSU switch and wait less then a minute! Turn PSU on and board is alive again and I can get into BIOS. Sometimes reset button (case reset button) helps during the boot when there is no POST.
on 2333 bios you will get close if not over 400 FSB, depends on luck atmQuote:
Originally Posted by ChaosMinionX
make a switch like a few of us have. i actually really like the config switch. It gives you a stable center for setting up the boot options.Quote:
Originally Posted by NoepZor
take smaller steps in overclocking. 5 mhz at a time on the fsb. Shouldn't be a problem.Quote:
Originally Posted by NoepZor
Do you guys ever experienced hangs or freezes in the bios?
That (recommended method) didn't work for me. I had a bad flash yesterday and tried that method for over two hours; system tries to access floppy but then nothing happens for more than ten minutes.Quote:
Originally Posted by lad
This is what finally did it. I went from jumperless and switched to configuration mode (that is pins 2-3) and it worked. I think what happens is that the system tries to boot finds the bios corrupted and switches 'internally' to recovery mode. I did this twice and it worked flawlessly both times. It takes about 1-2 minutes to kick in so some patience is needed.
yup, seems to be if I wander around in there for any extended period of time It will freeze up on me eventually. I'm trying to get an answer from tech support, but so far they just tell me to try pulling the battery and letting the CMOS clear.Quote:
Originally Posted by tjelaw
here was the other suggestion
as if i wouldn't notice the board grounding out to the case while running windows :rolleyes:Quote:
Please, place the board over a non-conducting surface. Just plug in the power supply, the video card, minimum amount of memory, and the processor, and try to boot up. In some cases a metal piece coming from the chassis could cause grounding to the board and would not power up.
Quote:
Originally Posted by Blauhung
If i didnt know better i'd swear that was tech support from ASUS...:D
That is of course if you ever talked to a LIVE person.....:rolleyes:
yeah, made jumping over to the EVGA 680i kinda tempting considering they have someone who will talk to you 24/7. I think this board is much better though.
I do quite frequently. Its very annoying. Sometimes I have to reset 3-4 times just to get a few settings changed that I want. It seems like it does it more if I try to change multiple settings at once. If Im only changing one or two things its usually ok. Im sure this will be fixed in a futre Bios update.Quote:
Originally Posted by tjelaw
and hopefully you don't have to compromise between that and the stability and performance that 2333 gives.
That doesn't seem to work for me. :rolleyes:Quote:
Originally Posted by mnemonik23
After I got a stable OC set up, I then tried using IDCC to make tweaks. When it fails, I turn PSU off for a bit. Turn back on and still no POST. Have to go for the jumper. :( Am I doing something wrong?
Atleast I'm running at 3.6ghz on air though. :woot:
Temp is lil higher than I like so that means I won't try to go higher, which is slightly disappointing. Damn the B chips.
Also, is there any way to control fan speed in the bios? I'm using a 3 pin fan and I just want it to go full blast (or even up it's voltage, since it's silent :P). I tried turning off auto fan management in bios but that didn't work. I finally found the setting in IDCC to max it so I guess it's okay.
The other question is I've read some people are having success with Memset and recommend lowering tRFC from 42 to 28 or even lower. When I tried that my system "zaps" and then it wont post. I tried a few times with setting as high as 28 with no success. Do I just have crappy-ish ram? I have the OCZ OCZ2P800R22GK platinum rev2.
Thanks for any help in advance. Lots of good info in this thread!
The only way Ive found to control fan speed is with IDCC.Quote:
Originally Posted by Rysing_Phoenix
From what I read on other forums, the freezes happen when using a USB kb or mouse. From experience, mine has never frozen and I am using PS/2 kb and mouse.Quote:
Originally Posted by chaotic646
-sfxs