my understanding crossfire is not part of this chipset specs...you should be able to do SLI.
Printable View
my understanding crossfire is not part of this chipset specs...you should be able to do SLI.
I am always learning something from this thread. I thought only nVidia chipsets could do SLI. Do you mean I now have to start saving for another GTS? :yepp:Quote:
Originally Posted by Ace-a-Rue
Whats u talking about? Intel mobos can do only CrossFire!
The Admin at Rebels Haven just posted this about the Mod BIOS:
Quote:
All 3 Mod BIOS have been updated. A bug that caused Performance Level CH(0) to not be set as per the BIOS, was fixed.
Please re-download the Mod BIOS if you downloaded it before the date and time of this post. Thanks!
http://www.anandtech.com/showdoc.aspx?i=2990&p=3
Seems to be less than 10% performance reduction compared to a pure 16 or 8 dual lane config. Athough some times its the same as a proper Cross fire X. You end up with some games not liking it at all.Quote:
Originally Posted by Anandtech
Looks like single card for me. 4870 or GTX280. More likely the 4870 1GB when it lands.
Did anyone get perforamnce boost after changing Performans level? Where?
OH MAN!...i had it backwards...thanks for the correction...obviously you can tell i do not do any of that stuff;)Quote:
Originally Posted by Darth Vader
found this quote at "The Inquirer"
http://www.theinquirer.net/en/inquir...ce-from-nvidiaQuote:
AND THE BIGGEST story of the show so far is: Intel has landed an SLI licence for desktop, not just mobile.
is my mobo dying?
- Everything was working fine until I installed a used QX9650 this afternoon
- As soon as windows opened I got an error "windows media player network sharing service stopped working and was closed". can't play any audio/video using MS software (ie media player)
- Then my system froze while browsing files in explorer (had to power off)
- My temps are nuts too... 46 42 23 31 per Real temp, 10C higher in Coretemp (at stock clocks & volts!) They were 33 33 29 29 with an idle Q6600 @ 3.6GHz! :(
- Just flashed to BIOS 17
- Now my CPU Fan isn't spinning (I'm actually using it for an 80mm fan on my PWM - bolt modded)
Could installing a new CPU bork everything this bad... maybe corrupt my OS? this install is very new and patched up. I literally just installed 10 days ago.
RMA the mobo?
a 9650 is way different than a E8400, even a Q6600 in respect to vcore and some of the supporting voltages.
the temps have been an ongoing problem for 9650's...i had one that was locked at 54C at default speed and in idle conditions...it would finally go above 54 once i started overclocking and loading the cores...you can't do anything about it since Intel does not warranty those temp sensors since they say they are needed only for core throttling or shutting down the cpu if it goes over the max rated temp....they care less about what you see in a normal operating environment.
clear cmos with the batt out for about 5-10 minutes and then try it...it might make the OS operate better...show us your voltages that you are using.
edit - ok, now cpu-z is showing my vcore +.2v idle - correction, cpu-z is showing my vcore at 1.640 no matter what i set in the BIOS?? and uguru shows everything as disabled (no readings). this is making no sense to me
thanks ace.
but what all those other new issues? why did my cpu fan stop? and the OS stability? do I need a bigger PSU?
here's my next course of action. is this logical?
- pop the Q6600 back in first. if everything goes back to normal, i'll say the qx9650 is the problem
- if there are still issues with the Q6600, i'll reinstall the QX9650 and OS. if that fixes it, then it was a botched OS
- but if there are STILL problems, I'll RMA the mobo
sorry, this is big screenie. BIOS vcore = 1.35v hwmonitor is showing my cpu core under "abit uguru 2005" alternating between 1.84 and 1.34 every 5 seconds or so. and what the **** is "winbod w83627DHG"?? it matches the LPCIO of cpu-z that seems to be the vcore that cpu-z is using. :bang head
http://farm4.static.flickr.com/3190/...02e534ba_o.jpg
edit again-
just lost another fan "aux4" this time
http://farm4.static.flickr.com/3041/...0e37d8ec_o.jpg
clear cmos and then go into the bios a load optimized default settings start from there.
1.64 is way to high for a 9650...you need to stay below 1.45v
EDIT:...i would flash to 16.b10 beta bios...it works well with my 9650...the only limitation, you can not raise the multi above 9X...but you can lower it...otherwise, works GREAT!
that's what i don't get... i don't know where the 1.64 is coming from. it's pegged there whether my BIOS is 1.25 - 1.45 (currently set at 1.35) :shrug: :confused:Quote:
Originally Posted by Ace-a-Rue
going to clear cmos as suggested
thanks
Surprised at the thread views this thing is climbing up to.
Both of my IP35 Pro boards are doing great, one never gets rebooted and has the same QX6850 I dropped in way back when the board was released.
My other one sits with a QX6700 as my main machine at work hosting stuff at the offices, this one was the one we used for LN2 overclock the week of Computex.
I have not tested with 45nm but the life expectancy is pretty good even for abused boards. If oyu changed your chip it might be the bios needs update.
well, i'm going to pop the q6600 back in and see what happens. i've tried bios 16 and 17, and after the clearing the cmos you can see my issue remains... didn't change a thing in bios (you can see i left speedstep too). my machine froze while i was posting this.. had to switch computers to post LOL
oh well, i've got two others mobos coming my way. i'll sort this chip out later
http://farm4.static.flickr.com/3037/...5bfc94da_o.jpg
q6600 is back in and that error msg went away
temps look right
volts look right
fans are back
i guess i got a bad chip. i'm contacting the seller tomorrow.. this is lame
EDIT: scratch that - just froze again. this time while looking at uguru settings. looks like i need to test a new mobo or reinstall
EDIT2: tested on an Asus P5E VM HDMI and got the same windows error msg on first boot. Reinstalled OS and seems to be working so far, still need to patch it up and check the cpu-z/real temp stuff... tomorrow
Several forums have picked back up on the board as ABIT released a Official 17 BIOS and then FELIX asked the Admin at Rebels Haven to create this mod of the 17 with the top 4 new Items:Quote:
Originally Posted by FUGGER
http://www.lejabeach.com/ABIT/IP35Pr...5probios-5.jpg
Yup. same here ... I havent posted since page 131-133. I'm using an old timer 6300@ 500X7 with all 4 slots filled with Ballistix Ram (4X1gb) at 500fsb 5-5-5-12 at 2.075 with no issues at allQuote:
Originally Posted by FUGGER
Once ACE helped me find those stable settings this mobo is quiet and stable as f@ck!
BTW, I'm still on Bios 11 ... is there any reason to upgrade since I am not changing my setup?
it's known that having both uGuru & later versions (iirc 1.41 >) of CPU-Z open at the same time causes freezes/crashes -they seem to fight over the same resources.Quote:
Originally Posted by lefy
The 1.64V that CPU-Z showed with your QX was probably a CPU-Z error as well.
Hi to all.
I have this motherboard, and I need to know if I can make an SLI of two Geforce 8800GT boards.
I know that on intelīs chipsets that feature is not supported, but maybe with a new BIOS o thru SOFTware it may be possible.
I ask because I read that even crossfire is not possible in this mother, and before I sell my 8800gt, I want to know if I can survive a little bit longer.
Thanks and sorry about my english, Iīm from Argentina and I understand and read much better than how I write.:shrug:
Crossfire is possible but the board does not have 2 16X slots (the second is 4x).
SLI is not possible.
Thanks for the answer.
I know the second PCIe is 4x, but I don´t think that it could slow the performance on a SLI or Crossfire mode.
I saw a forum where a guy wrote that he make SLI work on a Crossfire motherboard on software mode or something. That´s why I ask.
Do anyone knows if this board is compatible with this memory (CORSAIR DOMINATOR with DHX Technology TWIN2X4096-8500C5DF 4GB PC2-8500 (DDR2-1066) DDR2 Memory).
http://www.corsair.com/_datasheets/T...6-8500C5DF.pdf
with nVidia 6 & 7 series gfx cards there are some hacked drivers that will allow for SLI on non-nVidia chipsets.Quote:
Originally Posted by interpol.nyc
however, after that nVidia started encrypting that part of the driver to prevent hacks & I've never seen a publically available driver for 8 & 9 series cards that allow SLI on non-nVidia chipsets.
They should operate just fine. The 2x1G set works well according to Nelly's excellent list (thanks for keeping that up btw). As long as you set the manufacturer's recommended Vdimm (2.1v), it should run great.Quote:
Originally Posted by rubenmer5
Quote:
Originally Posted by lefy
you can't have cpuZ and Uguru opened at the same time...there is a conflict!
forget the official bioses...try beta 16.B10...don't forget to follow my flashing guide and then go into the bios and load optimized bios settings...save...now re-enter and adjust as you see fit.
lefy...what OS are you using with the 9650?
Booted Dominator 6400 C3DF with no problems...ran for a month til the RAM died:mad:Quote:
Originally Posted by rubenmer5
No mobo issues with the RAM.
You do know that new Dominator 8500s don't use Micron chips.....
ah yes, i had forgot about that. that explains the lockupsQuote:
Originally Posted by Ace-a-Rue
problem is i want the unlocked multi :( fwiw i did try 16b10 and had the same results.Quote:
Originally Posted by Ace-a-Rue
vista x64. and i took the 9650 and put in another build that was on an asus board with vista x32. the same fricken windows error messages started popping up! i have no idea why, but it seems switching cpu's (q6600 to qx9650 in both cases) didn't make either one of my builds happy. is there something wrong with my qx9650?Quote:
Originally Posted by Ace-a-Rue
i've flashed back to bios 17 final, reinstalled vista x64, and the errors are gone. the only issues now are my wacky temps, and that cpu-z still reports my vcore as 1.64 regardless of actual BIOS settings.
i just borrowed a multimeter, but i've never used one. how can i probe my mobo to find the "true" vcore? where's the ground? and where's the point to probe for vcore?
Here is my stable overclock with my q9450 using a Thermalright Ultra 120 Extreme.
http://img395.imageshack.us/img395/1...ableug1.th.jpg
Vcore - 1.4775v (BIOS)
vVTT - 1.30v
vMCH - 1.56v
vICH - 1.05v
vICHIO - 1.55v
GTLREF 67%
I was able to reach 3.84Ghz with 1.55v vCore and run benchmarks, but prime crashes at 2 minutes... :(
Results @ 3840
PCMark05
http://img181.imageshack.us/img181/4...3840jr2.th.jpg
SuperPi 32M
http://img181.imageshack.us/img181/6...3840pc1.th.jpg
SuperPi 1M
http://img396.imageshack.us/img396/3...3840mo6.th.jpg
3DMark06
http://img53.imageshack.us/img53/326...1900gc6.th.jpg
Hello Homeronte,Quote:
Originally Posted by Homeronte
Thanks for sharing for overclock result.
Which bios are you using with your Q9450?
BTW: nice 3DMark06 result
in that moment i was using 17b04 bios but flashed to official 17 bios and worked well too.Quote:
Originally Posted by Powerfull
BTW my 3dmark06 result is with my 9800GX2 i update my signature now :p:
EDIT: The only bad thing i found on this bios (beta 04 and official) is that using RAID you cannot enter to bios with an usb keyboard... it's a shame that Abit didn't fix that.
Quote:
Originally Posted by lefy
what does Uguru ver 3.107 read out for your vcore?...that is going to be within 0.01v of actual.
i have a picture of the read point but i will need to search for it...but...first, i need to do some cleanup chores before i can look for that picture...maybe someone else can show you during the mean time...i won't be able to get to it for another 4-5 hours from now.
here it is...see the green arrow pointing at the resistor with a whote box around it....that end of the resistor you should put your positive probe on...you can clip the negative onto the spring tension of the PS2 port or to one of your heatpipes on your cpu heatsink.
EDIT:...be careful with the probe as to not touch anything else (electrical parts) while measuring...i recommend that you tape your probe with electrical tape leaving only a 1/8 to 1/4 inch of the probe tip exposed so to avoid shorting the resistor out...this will keep the accidental killing the board to just about zero.
I'd like to say something. I freeze at random as well, but this seems to be because of the 9800gx2. If I take it out and run just my 8400gs I have no freezes. Can't wait for the gtx280.Quote:
Originally Posted by lefy
has anyone tried the MIPS mosfet cooler on their IP35-PRO? any thoughts?
Has anyone else ran their systems with just the Vista VGA driver for any length of time? I installed 2 WD6400AAKS in Matrix Raid with a fresh install of Vista. I have updated all the drivers EXCEPT for the Detenators for my GTS. Since I have a 4870 coming I decided to just wait on it to get here and not have any traces of nVidia drivers to deal with. Only problem is I am getting some strange momentary freezes of the mouse pointer from time to time. And I woke up to a Hardware related BSOD yesterday. It all ran fine after a reboot with not as many mouse freezes after that. And also the hiccups seem to happen more when in Windows Explorerer when I access the older drives in the system, but you also have the screen changing so it could still be the lack of a video driver. OR, could it be Vista just trying to Index the drives?
you can turn drive index off to see if that helps.
i have used the video driver from vista but i can not remember if i had any weird movement of the mouse...now...a freeze of the mouse would indicate to me that you have a resource conflict...are you using an advanced mouse driver for your mouse features?
Quote:
Originally Posted by FELIX
Quote:
Originally Posted by FELIX
i installed the 17.b04.zzz modded bios...so far your 3.5 beta Memset will not work at all on vista64 SP1...it opens but i cannot uncheck "auto" and i cannot expand the page to show both channels "A" and "B".
in the bios i have PL level 8 set but it shows PL level 7.
i tried your 3.4 version of Memset and it open and allows me to uncheck "Auto" and expand the page to see both "A" & "B" channels.
i tried to make changes to PL (it says the change was made) but there is no difference when i run Everest memory bench.
EDIT:...ok, figured it out finally after reading up so more...i had to have the "Network" chipsets enabled along with "Invoke agents" also enabled...i can now adjust my PL in the bios and windows and Memset 3.5 works perfectly
does anyone use the dominator fan with this board? does it conflict at all with the GPU?
The side of my dominator fan comes to about 1cm away from my 8800GT card! I always worry that it could fall onto the vid card and short something out. But I checked with my meter, and the side of the fan mount doesn't conduct, I guess because of the paint. It still freaks me out a little. The truth is, the dominator fan never seems to budge once I get the case back together.Quote:
Originally Posted by silverphoenix
i will try turning off Indexing. I am using just the Vista mouse driver, nothingfrom Logitec. I did run across something about AVGfree 8.0 causing this in Vista. They have it isolated and will fix in SP1. That just might be the problem.Quote:
Originally Posted by Ace-a-Rue
SP1 is out for vista 32 & 64.
VISTA 64 here: http://www.microsoft.com/downloads/d...DisplayLang=en
Thanks for the link, Ace. But I meant SP1 for AVGfree 8.0 from Grisoft.Quote:
Originally Posted by Ace-a-Rue
[edit]
I do believe that Indexing is what is causing it. I turned it off in Services and the stutter is gone it seems.
why don't you try Avast (Home-Free) from here...i am using it and i like it....give it a try...all you have to do is provide them with your name and email address where by they will send you a key good for 12 months...renewal only takes re-submitting an updated email address to get a subsequent key.
http://www.avast.com/eng/download-avast-home.html
slide down to the lower half of the page to download from their site for a faster download.
Thanks for the suggestion but I may have (really this time) found the culprit. AVGfree has an adware module in it and I also had AdAware 2008 running. I uninstalled AA and since then, not a stutter in anything. Must have been working against each other when I browsed files or ran an installer and such. I am keeping my fingers crossed. I really want to stay with Vista (this time) but it is little things like this that build up and send me scampering back to XP, which is still installed on my Raptor. But the WD's in Raid will eat the Raptor alive in performance.
[edit]
I spoke too soon. It started hanging again right after I posted. Uninstalled AVGfree and they disappeared again and things are much snappier it would seem. Off to install Avast.
i like Avast...it is a good program...works well!
And it is picking up stuff that AVGfree didn't. But the best thing is not one stutter since installing and this is while it is doing a system scan. I finally think it is gone for good. Thanks Ace.Quote:
Originally Posted by Ace-a-Rue
Boy...the vdroop on this board is KILLING my Q6700 overclock. Just reading the voltage from uGuru, the cpu voltage fluctuates from:
1.35-1.37 idle
1.32-1.34 full load
So it appears I am getting about a 0.03 volt vdroop. I know that the software voltage monitor isn't the most accurate, but hopefully it should show a somewhat decent differential vdroop reading...
So I know there has been a few mods to help vdroop. What is currently the 'best' vdroop mod...????
Also...I know other boards have options in the BIOS to eliminate vdroop. Is this board just not suited very well for quad cores??
.03v droop is quite good compared to what I get, you should be pleased. I see closer to perhaps .05-.06vQuote:
Originally Posted by bobn4burton
I have no problems with any of my quad-core cpus in the abit board, they all oc nicely. The only vdroop mod I've seen is the hard mod posted in the motherboard vmod section by Johnny Bravo. I run several boards and they all experience vdroop I simply compensate for it as needed by setting vcore accordingly in bios.
Ditto about the Vdroop comment from loonym...not bad at all...it is a VERY acceptable droop.
Hmmm...well if the vdroop I'm seeing isn't too bad...maybe my chip is just not the best.
How high is 'safe' to go on vcore for a Q6700? I think I have my q6700 at 1.385 right now and I seem to be stable at only 3.2gig :(
I was hoping to hit 3.6 gig with this chip, but maybe that won't be happening. I haven't really tweaked my settings much yet, so maybe there is some more tweaking I can do. I am also using water cooling...so my chip stays fairly cool.
Basically all I have done is to change my memory multiplier to one that keeps it running in spec and upped vcore/vdimm voltage and upped the FSB. At 3.2, I was getting prime95 errors and I've had to raise the vcore to about 1.385 to make it stable.
How much higher can I try to raise the vcore? Are there any other tweaks I should be doing to help my OC at all??
Right now I'm just trying to find the limit of my cpu, so I will try to max out my ram later...
1.385v is nothing for a Q6600, especially for one under water.
I'm currently using a q6600 in the IP35-pro. The main voltages I concern myself with to get me stable are vcore, vdimm, MCH, ICHIO, and the gtl ref settings, although I also follow the suggestion here of setting ddr2 ref to +2% since it's never hurt me :)
Keep an eye on pwm temp since that is known to get exceedingly hot without extra attention. I think it's best to try and slowly nudge some of these voltages up and try to find your own best settings although there are many examples of people's successes posted throughout this thread that you could copy as a baseline.
Good to know...Quote:
Originally Posted by Cob
So what can I go up to on water safely? 1.40, 1.45, 1.5??
Whatever keeps your load temps below 70c tbh.
Tho everybody has their own ideas on what max load temops should be.
I was woundering if any one else tried my cpu ram compinations, because I am having some trouble setting clock, according to cpuz it is always 399 even though in uguru it says 420. My system give me a speed of 3.19 so i'm assuming cpuz is correct. does anyone have any suggestion as to what could be wrong, I hope it's not ram forcing the clock. I also tried both bios 16 and 17b04 and they both have the same problem.
i would say to hold 3.6 ghz under a P95 load will require vcore under load to be around 1.42 to 1.45...that is load vcore not idle vcore.Quote:
Originally Posted by bobn4burton
to support that P95 at 3.6 Ghz, pay attention to your FSB, MCH, ICHIO 1.5 and Vdimm.
i would try about 1.25 FSB; 1.48 or 1.5x MCH; 1.60 or 1.65 ICHIO and 2.0 to 2.1 Vdimm.
good luck!:)
Quote:
Originally Posted by spunlex
first of all, what bios are you using and what version of Uguru?
http://www.rebelshavenforum.com/sis-...;f=37;t=000124
a new addition to the ip35 bios!! from polygon @ rebelshaven
+1 for Avast. I've used it for several years and it usually catches everything. The one time it didn't was recently a virus came through a Steam server twice (once on DOD: Source then on TF2). Didn't activate until I started my browser - then BAM!Quote:
Originally Posted by Ace-a-Rue
Effed things up pretty bad the 1st time, had to do a complete wipe/reinstall. The 2nd time Avast caught it tho'.
Avast also uses much less in the background than AVG, but most of the unneeded AVG stuff can be turned off.
hmmmm...interesting stuff...i'll get around eventually to trying it..hehehe
sounds like the 2nd time the code for the virus pattern was written to catch it coming via that port...sounds like you have another dimension in accessing the net.Quote:
Originally Posted by aztec
Or just bad luck.Quote:
Originally Posted by Ace-a-Rue
Thing is, I though Avast would have caught the 1st one since I force update it at least daily, not counting whatever auto-updates it does. Also I didn't have it set to boot-time scan but I do now.
Quote:
Originally Posted by aztec
you know that you can set the updates to every 30 minutes by going into "Program settings" (right click on the "A" blue icon).
also, there is "On-Access Protection Control" that allows you to increase "Resident Protection" from "Normal" (default) to "High"
Of course I've been through the settings, Ace. :) All were at "High". But I don't want it updating that often. I do it manually and it does auto as soon as any update is ready anyway. Most likely Avast didn't have a fix for that particular virus yet.
I don't like a boot-time scan on every reboot, but the short wait might be better than a virus not getting picked up in time.
I am currently susing a beta bios 17.b04, but I had the same problem with bios 16. I am using the bios to atempt to oc, but I am using uguru version 3.1.0.3.Quote:
Originally Posted by Ace-a-Rue
that uguru version is the wrong version to use...i am using 3.107 and i found that to be the best and most accurate.
that should be a good bios...i am using it but it is the modded version, which is fine but about the same as 16.B10 which i was using for an extended time.
Quote:
Originally Posted by aztec
don't take it personally!;)...just making sure you were aware.
I just updated my uguru, but I am still getting the same problem. Which ap can I trust more, cpuz or uguru?Quote:
Originally Posted by Ace-a-Rue
Quote:
Originally Posted by lefy
i have the same problem with cpuz showing 1.64 volts. it happened ever since i updated to bios 17. i have every thing as auto in bios except the vcore i set to 1.225. uguru and everest show the correct voltage that i have in bios. idk whats up with the cpuz reading either. :confused:
Uguru is the one to believe...the Vcore will be within 0.01v...on my board, it was more like 0.005v within actual as i measured it with a DMM.Quote:
Originally Posted by spunlex
CPUz is a very good program but take it with a grain of salt when it reports the vcore.
ok thanks, which one for bus speed?Quote:
Originally Posted by Ace-a-Rue
No offense taken. I just let you know that I had been through the settings.Quote:
Originally Posted by Ace-a-Rue
REALTEK High Definition Audio - version 1.97
http://www.station-drivers.com/page/realtek.htm
Entering the version 17 (Final) bios still works (somewhat) when in Intel Raid mode + USB keyboard, but is still very "touchy" on the exact moment during boot-up that the "Del" key is pressed, for the bios screen to appear. I also agree that Abit needs to provide a fix.Quote:
Originally Posted by Homeronte
Quote:
Originally Posted by spunlex
Uguru should be accurate since it has a chipset on your board communicating with the bios...if you think it is giving you errors, i would clear the bios with the battery out for about five minutes...after doing that, go into the bios and load optimized bios settings...save!...now, re-enter and make your changes....i would also go into the Bios Uguru section to make sure you have all the voltages, temps and fans checked mark for sensing...if you don't, uguru in windows desktop won't display that information.
sometimes, you also have to set "default" values in windows Uguru to get the red highlights to disappear.
the only thing that might be off is the core temp...that is subject to interpetation and abit's formula might be in question.
So how long does it take to flash the bios lol, cuz I just used the runme in DOS, and it has been flashing "Please Wait" for a good 5-7minutes.
I need to upgrade from 16 to 17 as I'm giving the board to my brother and he is using a wolfdale.
-edit btw the bios is 16 BO4
-edit lol figured it out I was running beta 16 bios so I flashed to official release 16 then to 17
how do these boards handle e8500s?
I just put my brothers E7200 which is I believe the same as the E8400 with half the cache and VT disabled, Installing windows now so I'll post up some results.
Can I flash from bios 14 directly to 17 or first to 16 and then 17?
You can go direct to 17.
i used the under the windawz appz from abit and it was fast check it out
well...that should not have made any difference what bios is installed when flashing to another version bios....something went wrong with that flash....just make sure you are not overclocking...if you haven't up to now, read my flashing guided (link in signature).Quote:
Originally Posted by silverphoenix
if you are doing a floppy flash, it shouldn't take more than 2-3 minutes to complete the flash...if you are doing it by USB flash drive, it should be over in less than 60 seconds.
Just wanna report I tested bios 17 but went back to good ol' 14. For me seems like anything newer than 14 I only get worse results as far as overclocking and mem performance goes. Oh and I grabbed the modded 17 bios for performance level setting and memset support but seems despite tweaking timings with memset etc. I still get better performance with bios 14 (~9950 MB/s read, ~10570 MB/s write, 49 ns latency in Everest with config in my sig so I'm not complaining, with 17 the closest I got was around 100MB/s lower read and write and 51~52 ns latency)
I have been using Bios 16 final with all 45nm builds so far, works a treat. Beware of 14 though, isn't stable when OCing 45nm CPUs.
I can't detect any flaw in bios 16 though, which is impressive considering I've built around 30 rigs with an IP35 pro + 45nm CPU so far :)
Only thing maybe is changing FSB/mem divider and timings at the same time (after updating bios), it tends to hang sometimes and you need to re-set the FSB.
^ What you mean bios 14 isn't stable when OCing 45nm CPUs? I've had better results with it than 16 and 17 with my Wolfie E8400...
The only prob is the vcore showed in bios isn't correct so it'll be a higher value than it really is which is perhaps why you find 16 and 17 better to OC with as with 16+ the bios / windows vdroop (idle) is for me 0.05 only while with 14 it's a lot more but then again it's only not showing correct value.
Where is a good place to compare Everest scores?
I have no idea if mine are good, bad, or average....
Nevermind.
Im currently using bios 16 with my e8400. Currently I need at least 1.29v (set in bios) to get 3.6 and about 1.44v to get 4ghz stable. Would I see any difference if I were to change to bios 17? My gut feel says that I'm just very unlucky to have a chip that needs so much juice to run 4ghz. :( Wonder if this new release will magically make my chip require less vcore. If there's no diffence, i prefer not to update (updating this bios is not good for my heart, waiting anxiously for it to complete)
I was using this board with Ubuntu releases, always overclocked to 500X7 using an C2D6300 and it was dead stable
Now after installing a Raptor 150 X for a Windows partition it seems to lose the hard disk during the install. I loaded BIOS defaults and it all went well. However I would very much like to return to my stable 500X7 overclock. I am running 4X1gb Crucial Ballistix sticks with active cooling which do not seem to be the problem as the pass memtest for 2 days in a row at 500 fsb at 5-5-5-12 and 2t
I am using Bios 11 which came with the board. Do you reccomend using at least bios 14? I really dont care about wolfdale support as I'm using a 6300
Thanks for any answers
absolutely upgrade to 14 as a minimum.:up:
is 1.44v actual vcore in windows or set Vcore in the bios?Quote:
Originally Posted by vassalle
Is there any point to updating the bios if your system is running stable? I'm still on bios 10 that came with the system. Also from what I hear having raid and a usb keyboard with the latest bios doesn't let you enter it due to some conflict.
if it ain't broke ...
i have raid/usb keyboard/lastest bios i have zero problems :)Quote:
Originally Posted by nsegative
Quote:
Originally Posted by Ace-a-Rue
Is updating through windows (non overclocked) safe? I just hate to deal with floppy discs!
IMHO it's like playing Russian roulette with your BIOS chip. If you prefer not to use a floppy, you can always create a bootable USB flash drive.Quote:
Originally Posted by Daytime Dreamer
Chuck, I have 2x1GB sticks of the Ballistix double sided 16 chip I'll sell. These are the good ones, with the BL12864AA1065.16FD3 model number and wrap around heat spreaders, not the newer BL12864AA1065.8FE5. They've run great for the past year in my IP35 Pro. Selling b/c I couldn't find another pair so I already bought the G.Skill.Quote:
Originally Posted by ChuckM
PM me. :)
Update
I flashed to Bios Version 14, following Ace-A-Rue's rules with the USB flash method ... all went well
Now ... here are my 24/7 settings which were stable on my UBUNTU 8.04 setup but not during the installation of Windows (I have noticed that stable overclocks often fail Windows setups, anyway). The thing is that when I formatted the hard disk and the Windows installation started copying files, it froze at various stages (69%, 85%) and said it could not read from the DVD ... when I pushed the reset button the hard drive could not be detected anymore during post. The only fix was to run the pc off and back on again
This were my BIOS settings for 500X7=3500mhz on a c2d6300 with 4X1gb Crucial Ballistix D9GMH, actively cooled by an OCZ cooler
CPU Core Voltage = 1.4850
DDR2 Voltage = 2.100V
CPU VTT 1.2V Voltage = 1.31
MCH 1.25V Voltage = 1.48V
ICH 1.05V Voltage = 1.09V
ICHIO 1.5V Voltage = 1.65
DDR2 Reference Voltage = 0%
CPU GTLREF 0&2 = 67%
CPU GTLREF 1&3 = 67%
Memory was set at 5-5-5-15 with all other settings at auto & 2T
Please suggest any tweaks/changes to the above settings. Just a note : I could pass memtest all day with the above settings and Ubuntu ran like a dream (video encoding, mp3's, movies) BUT keep in mind the UBUNTU setup was on a SCSI controller, the SATA ports of the IP35-Pro were never used (DVD ran of the IDE controller)