unlocked downward mults!?! probably not but i can always hope. :)
unlocked downward mults!?! probably not but i can always hope. :)
ROFL.... Now THAT is funny......:rofl:Quote:
Originally Posted by shimmishim
Works great on mine.Quote:
Originally Posted by hotchoc
Hey guys..
The board overvolt vdimm?
what are the safe MCH/Vfsb on the board
I am starting to overclock and get vfsb to 1.3v and MCH at 1.575..with fsb speed of 390
On my RD600 max cpu speed at 1.51875v(max I would give for everyday use) was 390 x 9=3500
I am running my 10th anniv at 487 5-5-5-18 at 2.16v ..testing memtest 86+ 1.70..trying for 50 passes on test 5
couple of interesting things at least so far with Memtest on Badaxe2 vs RD600
RD600(set ram separate to cpu)
500mhz ram 5-6-5-5-18-24-42-2t gave 3100MB/sec bandwidth per Memtest
Badaxe2( 266/667- 4/5 divider)
487mhz ram 5-5-5-18 gives 4900MB/sec bandwidth
Can this be correct that 975x chipset is providing 55-60% more bandwidth or does memtest 86 maybe just not report values correctly on the RD600
I'll hunt something up tomorrow and see if I get same errors. Maybe it's a Vista thing.Quote:
Originally Posted by GamingDaemon
But now it's :banana::banana::banana::banana:tail hour :toast: :toast2:
I'm suffering from serious playback problems while using Overlay Mixer with my 8800GTS. Because of this, I once more want to make _really_ sure:
Am I supposed to insert power onto the Molex-connector on the motherboard?
Motherboard is supplied with 8pin power connection directly, no 4x8 adapter.
Same with gfx, pci-e connector coming directly from the psu.
Last person replied that I was supposed to use the molex connectior if my gfx used more than 75W... but when I read it says it's a complement if you use less power somewhere else... the molex GIVES power after all. i connected a fan to test :)
someone who's better than me at english please read the manual for me and confirm. I might have to rma the gfx otherwise.
The 4pin Molex connector on the motherboard is optional for graphics cards without onboard power connectors so that the system can provide enough extra power for them. I run a 7950X2 which has the 6pin connector coming from the psu.Quote:
Originally Posted by KMEI
Hmmm
I need some info if possible
Rick fx reported if you set 1.55v in bios ..he was get 1.49v idle/1.48 load..was this by DMM
I have a storm rev2 but can not easily(or IMHO safely) get the DMM tips where I want to read idle/load vcore
Has anyone measured on DMM??
same here likewhoa, but would it damage the motherboard to try using both?
i have a storm 2 mounted. i've measured the DMM before. you can use any of the coils around the socket to measure the voltage.Quote:
Originally Posted by nealh
I've measured quite a few times....Quote:
Originally Posted by nealh
1.5000v set in bios
idle: 1.4840v measured via DMM, 1.48v reported by Everest
load: 1.4810v measured via DMM, 1.48v reported by Everest
The sensor chip on these boards is unusually accurate, at least on my boards.
same as you GTJ, sensor is almost right on
Can't understand why they don't let you downclock the multy when everyone else out there allows it on their boards.
Well I finally got around to overclocking my system today. My Tuniq had one thumbscrew break and I didn't get around to buying another screw until this weekend. Installed it and everything seems fine so far.
Just started about an hour ago and the results so far:
With absolutely no voltage changes I can get to 3.42GHz just by raising the FSB. At 3.6GHz I can get into Windows but Orthos stops or reboots my system after a few seconds. I'm not sure why CPU-Z reads my voltage as 1.213 and Core Temp says 1.3250v. In BIOS I have it at "Default" and the reading says 1.3250v, so I guess Core Temp is correct.
I'm just testing now by booting into Windows and running Orthos at priority 9 for a few min to see if it crashes or not. I'll test for stability overnight tonight.
Thought I would post in here while I run Orthos as there is nothing else to do :) Those people that say F stepping chips suck please speak up now :slapass:
Also, anyone know which temp reading is more accurate? Should I follow the temps from Core Temp or TAT?
3.42GHz @ Idle
http://img453.imageshack.us/img453/2...ghzidleoz6.jpg
3.42GHz @ Load
http://img455.imageshack.us/img455/3...ghzloadad5.jpg
nope. i plug a molex there for daily use and everything runs perfectly well.Quote:
Originally Posted by KMEI
Does that mean you're using the following:Quote:
Originally Posted by irenic
1x24pin
1x8pin
2x6pin (gfx)
+ the molex?
please confirm i don't want to break anything
I d/led Everest but do not see where it reports current vcoreQuote:
Originally Posted by gtj
well damn it....this really sucks
3500 on my RD600 I would set 1.51875 bios(SG reported 1.52v idle, load was 1.48v)
3500 on Badaxe2 1.525v...bios reports 1.53v(IDU reports 1.55v idle/1.54v load) and my system crashes 3Dmark05....
interesting thing is 1.5375v in bios(IDU reports 1.55v) will boot and run orthos for 10min when i stopped at 3600...I could never get this to run at all, but 3Dmark05 cpu test 1 fails reboots immediately
are you grounding to a place where a mobo screw can be placed(I used this spot for DFI sli-dr..with no screw in place)
That's what I use with no problems. Can't hurt to hook up the extra molex, if the board doesn't need the power it just won't use it.Quote:
Originally Posted by KMEI
Guys, i was wondering if the upcoming E6850 would run on this board by default. Since its got the FSB 1333-Strap it SHOULD be able to run them, hm.
Has anyone ever tried to run an ES on the XBX2?
i think you're absolutely right. the 6X50 should work on the BX2.Quote:
Originally Posted by cryptocat
i'm not sure if there has been a bios update that has allowed for this to happen. if not, i'm sure they'll release one to support 1333 fsb processors.
Ok..I played with memory settings and I found on BIOS2333
I can change to 333 ref. freq. but when i reboot and enter the bios it still reports strap at 1066!
I got out my DMM but I am not measuring the vcore at the right point
Vcore is set 1.525, bios reports 1.53v...DMM reports idle voltage of 1.20-1.28v..quick load show 1.20v
I am measuring by small squares near the solid caps above the socket and below the small blue HS..I ground to a the metal ring where a mobo screws in...and I measure by touching the small "wire" coming off the small squares(if this makes any sense)
instead of using a metal ring as your ground, use your molex connector from your psu as your ground. stick the black probe into one of the middle 2 plugs/ports/sockets (it should have a black wire connecting to it) of the molex connector.Quote:
Originally Posted by nealh
sometimes when you use an improper ground, it'll throw off your readings.
Thanks gave this a try..the Corsair HX620..has cables are black..so I found a molex that was unused from a fan in my caseQuote:
Originally Posted by shimmishim
BIOS setting 1.525v bios reads 1.535...DMM check 3 of the squares..1.39-1.42v!!!..still not sure if this correct(in winxp at idle...not I have RMclock with C1e disabled and disabled in bios C1E and EIST..using bios 2333
Blah...I reset bios to optimal defaults and turned off C1E/EIST...stock idle vcore is 1.16v....load was the same
I checked my DMM on some batteries..AAA 1.5v..reads them fine
other than 2333 bios what would you guys recommend ..2507?
Quote:
Originally Posted by shimmishim
I hope that.
But you never know with Intel, they release new Chipsets for almost every new Processor that they release :U
Anybody tried using Nvidia ntune to tweak the vcores inside XP ?
http://www.nvidia.com/object/sysutility.html
yo ucant' use nTunes with an intel board.
ntune is for nvidia boards.
Found out that my cpu is kinda vcore hungry. This is my current settings (stable in OCCT, Orthos, SuperPi, XP):
Vcore =1.4125
Vfsb = 1.350
Vmch/ich =1.600
FSB = 355 X 9 @3195
Temps = 42C idle/58C load
Ram = 5-5-5-15 (1:1) 2.2vdimm
Am starting to have doubts as to achieving 3.6Ghz under 1.5 vcore
Will increasing the vmch and vfsb affect the ocing in my case?
Make sure that you're measuring on the CPU side of the blue or black power chokes. Measuring on the side closest to the blue heatsinks will give you inconsistent results because you're measuring before the filter. The 1 in the upper left corner is the only one that's safe to use because the rest all have caps right next to the outputs. Check the voltage section of the guide for pics.Quote:
Originally Posted by nealh
In Everest the core voltage is clearly marked CPU Core on the Computer/Sensor page not to mention the OSD. If you don't see voltages or fans then you're using an older version.
Thanks as always..I was check the one closest to HS, not closet to cpuQuote:
Originally Posted by gtj
the one in the pic is blocked by my storm and I can get to it...I will try again
the odd thing is everyone is reporting 1.5v..reads 1.48v....in my case it seems the vcore bios setting is lower than what bios reads(ie 1.525v=1.535v bios reading..so it seems my board is potentially overvolting)
Most have reported in the thread..better clocks at lower vcore on their cpu vs other boards...not for me..looks like badaxe2 need more vcore for same speeds
Gtj...if you set 333 ref freq..do you see 1333 strap in bios...if I do this I still see 1066 strap
Do you perhaps have Enhanced Powerslope on? Because that might overvolt it.
The "System Bus Speed" never changes from 1066 if that's what you're looking at.Quote:
Originally Posted by nealh
That's possible. It's also possible you need to recalibrate your DMM. :)Quote:
Originally Posted by Reinvented
Ok..then that is normal to 1066 strapQuote:
Originally Posted by gtj
I doubled checked my DMM on batteries so it is fine....reads there voltage perfectly
Reinvented: I do have power slope enabled..I thought everyone did when overclocking?
The Badaxe2 seems to need more vcore than my RD600 for same speed..although it will actually run 3600 but I cant get 3mark05 cpu tests to run..these tend to be a good quick sense to whether I am going to be stable(although I got 3mark05 to run and P95 crashed ..first time i had that happen..usually if 3dmark05 runs P95 usually is ok...usually the both fail equally)
EDIT:..thanks GTJ...by using the upper left power choke and measuring on the cpu side..I could more appropriate results:toast:
I tested with power slope off....wanted to see what this was doing
Power slope on:
1.525v bios setting=1.535v bios reading
Power slope off
1.525v bios setting=1.511-1.523v bios reading
DMM..power slope off
1.525v bios setting= speedfan reports 1.52v idle= DMM reads 1.47v
speedfan reports 1.51v load=DMM reads 1.46v
so on my board looks like bios idle vcore is 0.0525v lower and load is 0.0625v lower than what is bios setting and windows reports .04-.05 off
It appears that the winxp programs (speedfan and everest) are matching what the bios is reading)
I feel much better that my vcore is really not 1.53v as measured by my DMM
BTW are others finding Power slope to be a big help with overclocking....from what I could see by my load vcore DMM reading the vdroop is excellent...and powerslope is giving a bit more juice for a given vcore setting
Well, after getting the new (replacement) board and overclocking it for the last few weeks, ended up with the following:
QX6700 @ 3.3 GHz, 330 (x10) FSB with 1.3625 vCore set in BIOS on air cooling.
FSB voltage is lowest possible setting in BIOS (1.2v I think).
MCH voltage is lowest possible setting in BIOS (1.5v I think).
Prime95 with all four cores running small fft gets to about 70C after 24 hours of stressing it in typical indoor temps. So far have stressed it for 24 hours of small fft and 24 hours of blend with no errors.
Memory is 4 gig Mushkin 8500.
running 4:5, 825 with timings 4/4/4/12 and vDIMM of 2v.
I suspect I can get more out of the memory if I want to push it but I don't see much need atm.
Not bad for a 24/7 air set-up.
Can't get it to high FSB and stable no matter what I do. Interestingly I booted into 401 FSB on my P5WDG2 WS Pro by mistake with the QX6700 and it posted no problem, though I am sure Windows would have been impossible.
Well I guess my overclock wasn't stable as Orthos stopped after 2 hours running overnight. I'll try upping the vcore and see if I can get it to do better.
I just upped my vCore to 1.4000 and the readings in CPU-Z and Core Temp didn't change. That's odd, could be a bug.
Anyways I was curious, what are the temperatures supposed to be like with a setup like mine at 3.42GHz? I'm running Orthos right now and with 1.4000 vCore it's about 36/39 idle in Core Temp/TAT. Under load it's about 61/62. That seems kinda high to me with a Tuniq cooling it?
I'm running it at room temp with no air con on just to be safe.
Hmm, guess I got a little over-excited in my first post :P
I can't seem to get Orthos to run for more than 20 min on anything over 3.4GHz. I can get into Windows fine and play games and everything all the way up to 3.60GHz, but not Orthos stable. I think I will just run on Priority 1 instead of Priority 9 to test for now.
At 3.42GHz with 1.4500 vCore I actually saw my temps touch 70 degrees. The Tuniq could be seated improperly, but I'm too lazy to take everything apart again and check, haha.
At stock speeds though with the Tuniq and Intel HSF I saw a difference of about 9-10 degrees idle and 15-16 degrees load, so that has me thinking my Tuniq is working fine.
Right now I'm just doing 3.24GHz (360 FSB) at 1.350 vCore and everything else stock. The memory I have at 4-4-4-10 at 2.04 vDimm and on Orthos I'm at 2 hours. Will let it keep running overnight and see if it's stable. The temperatures are under 40 idle and under 60 load and I'm perfectly happy running at this speed.
Maybe when the TR Ultra 120 comes out I'll try it and see if I can get better temps :)
Just a quick followup
Power slope adds a small bump in vcore at a given bios setting..sort a in between value...does nothing for vdroop
Values tested with DMM
No power slope
Bios setting.....Bios reading......winxp idle/load........DMM idle/load
1.525v ........1.511-1.523.....1.51-1.52v/1.51......1.47/1.46
Power slope on
Bios Setting......Bios reading......winxp idle/load.......DMM idle/load
1.5375 ............1.54v ...........1.55-1.54..........1.49v
1.5625 ............1.57v ...........1.57v/1.56v.......1.52v/1.51v
I used Speedfan to report idle/load winxp pro values(everest is the same)
@1.5375 P95 blend failed immed and I could not get a load temp..I was using blend....
@1.5625 P95 blend generally gave a load 1.52 with a few at 1.51v..small fft gave 1.56v
So Powerslope seems to give a bit more juice and vdroop ON MY board with bios 2333 is excellent at .01(better than Intel specs? of 0.02-0.05)
But my bios reports vcore much higher than actually..typically .05v close to what Rick fx saw way back in the thread
Also the software programs seem to pull data very accurately from the bios ..they read the same
So if you have a DMM measure the vcore if you can...others have reported only .01-.02 difference between bios and actually values
this is my c1e fix :stick:
based on info I found here http://www.xtremesystems.org/forums/showthread.php?t=104811
its just a driver (very small) that sets the propper msr to disable c1e (end then exits)
only tested on my 6600 and vista but i dont see why it wouldnt work with anything else (core2/x32 WINNTOS/other boards besides xbx2)
got sick of waiting for intel to fix it
I included source so you can check it out and whatnot
at your own risk blah blah
warning: noC1E + x64 os = BSOD.
Your DMM reading are unusual. Try measuring your +5v and +12v with your DMM then compare it to what the BIOS or other programs read.Quote:
Originally Posted by nealh
Cool. Thanks.Quote:
Originally Posted by Lome
Thanks. Works like a charm. :)Quote:
Originally Posted by Lome
Oddly, my BIOS says my CPU temp is 0C. And I'm not on phase. ;)
why would you say that...Quote:
Originally Posted by gtj
Rickfx got very similar result
my board is revision 505....
PSU= Corsair HX620W..brand new for this build
EDIT:
Lome...thank you works like a charm:toast:
Gtj
Well I tested everything with my DMM
BIOS Readings
12v= 12.375
5v= 5.058
3.3v= 3.353
1.5v= 1.607
Vcore= 1.535
DMM Reading
12v= 12.10v
5v= 5.00v
vcore= 1.49v
Great Stuff, worked for me:toast:Quote:
Originally Posted by Lome
Same situation here. Very weird behaviour by this board. I was running 389x9 for like a week, no problems whatsoever. Then I couldn't cold-boot it at all.Quote:
Originally Posted by Speederlander
Also, there seems to be a hole between 333-350 for me. 333x10 is my everyday setting. I completed all 3d benches and whatnot at 375x10 and some lighter benchmarks at 385x10. However, 334x10 -> no POST.
Not sure what is causing it, I am suspecting my Gskills, so I ordered some OCZ Platinum Rev2 to see if there are any differences.
:(
Bingo. Your DMM reads low or your sensor chip reads high. I'm betting it's the DMM.Quote:
Originally Posted by nealh
why would you say the DMM is wrong..I tested numerous batteries and they all read correct voltages not lowQuote:
Originally Posted by gtj
Hmm..this is not good if your correct
if my DMM is wrong and the bios is correct..then the BAdaxe2 needs alot more vcore vs the RD600
ok..I guess I will go buy another DMM and see waht happens
If my vcore really is idling at 1.53/1.54v and loads at 1.52v...then an idle temp of 40/42C with ambient of 24.5C is amazing on e6600
how do u use it ?Quote:
Originally Posted by Lome
read noC1E.txt file (right click on noC1E.inf and select install; reboot your computer)Quote:
Originally Posted by hotchoc
Thanks Lome it works great
Quote:
Originally Posted by Lome
One of those little things that make your day. Many thanks, mate, for providing something that a company the size of Intel thought was unimportant to fix. :)
Let's say a new bios is released and you need to update it, do you need to remove this noC1e inf file?
just delete the noC1E.sys from your system32\drivers folderQuote:
Originally Posted by hotchoc
if your realy anal you can also delete
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\noc1e"
edit: heh i just woke up and misread your post
the anwser is: only if you want to turn c1e back on
Ok..I have not gone back to the BIOS readingsQuote:
Originally Posted by gtj
I bought a second DMM(sears has a nice one for $12)
http://www.sears.com/sr/javasr/produ...TOOL&ihtoken=1
I tested both DMM on batteries(gave exact same readings on AAA/AA?C batteries) and my system
From post #3338..I cant recall but I may have used a molex that was fan only as a ground and with both DMM this gave a reading of 1.46/1.47v underload
From my previous post:
BIOS Readings(vcore set as 1.525v with powerslope enabled)
12v= 12.375
5v= 5.058
3.3v= 3.353
1.5v= 1.607
Vcore= 1.535
DMM #1 Reading (hmm now that I think about it, I was using a molex adapter from attached to the 4 pin that went into GPU molex on the mobo)
12v= 12.10v
vcore= 1.49v
I have a 4pin molex cable with 2 plug one into the gpu molex on the mobo...I had previously used the free one with a molex adapter so I could see color of the wires..the cable on the HX620w are all black
so this time no adapter just used the 4pin molex and I used one of the inner plugs as ground...tested 12v line DMM #1 ..12.10/12.09v...new DMM 12.13v
OK so grounded and test at the same power choke..upper left one in pic from Gtj link
Bios 2333
Powerslope enabled
vcore 1.525v as bios setting
load is P95 v251 blend
speedfan 4.32 .... reads idle of 1.54v/load 1.53v
DMM #1
1.50v idle/1.50v load
New DMM
1.50v idle/1.50v load
so the difference vs speedfan is .03/.04 this time
so unless both DMM are bad...I am pretty happy my DMM readings are accurate
Quote:
Originally Posted by nealh
It isnt out of the realm of possibility that the sensor chip isn't calibrated correctly. and as long as you're happy, that's all that counts. :)Quote:
Originally Posted by nealh
Hey for $12(reg price is $25), if my first DMM was bad...I needed a new one anywayQuote:
Originally Posted by gtj
I am only happy that my DMM readings are pretty accurate(or I have terrible luck and both are bad) and it appears the mobo sensor is off, I am not happy about this if it is true..but what can I do to fix that... RMA the board:slapass: ...no thanks..that's way too much of a pain in the A$$ since I was using this as a replacement board, already for a crappy RD600
Well most of my problems with this board have been fixed. I can now OC much further with less VCORE. Before I struggled to get anything over 3GHz but now I'm on 3.2GHz on stock VCORE. I have also managed to disable C1E. I am very happy again. How did I do it you ask? I bought an Asus P5W64-WS Pro!
The Axe2 has potential to be a killer board but Intel refuse to make a decent OC BIOS for this board. I should have never strayed from Asus, but I have learn my lesson. So... The Axe2 will be retired to my server to do what it does best, run at stock speeds!
A little of subject but it could be good for the guide. I have built 4 computers using identical parts using the BadAxe2 with Raid 1 on the Intel SATA controller and I have some interesting results.
First is an incompatibility with Intel's Raid 1 and Vista ( I didn't try XP). When the computer is shut down improperly (reset button, power outage, etc) the computer will not reboot 99% of the time. It will just hang on the vista scroll bar for a long time then you might get a black screen with a mouse arrow. I called Intel about this and they said that it is normal behavior for Raid and that it will boot but could take up to 36 hours.....real good solution. I then asked if it would work on the Marvell side, they said it would do the same thing. I obviously didn't believe them. What happens is the Matrix Storage Manager detects a dirty shutdown and goes into verify mode but it doesn't work properly. The only work around I found to get your computer working that day...is to shut it off, unplug a drive, boot it up, it then starts right up. After its up and running I attach the unhooked hard drive and it goes into rebuild mode. It works fine in rebuild mode.
I have now switched 3 out of the 4 computers to the Marvell controller and it works ALMOST perfectly. the only problem is sometimes on reboot it gives me an Apache error which you have to cancel out of 2 times then everything is fine (I prefer to keep the Apache monitor running to check on things).
Intel has leaked out there new Matrix Storage Manager #7 on the web. I installed this on 2 of the computers and the bug still exists...it also exists on a customers Dell. Interestingly enough, with #7 on the BadAxe and last months Bios update, it seems to be fixed, but only with the latest Bios. It will boot up slow but still will boot in about 5 minutes after a dirty shutdown which is much more acceptable then 36 hours. It will then verify for hours and be back up to speed (but still very usable in verify mode, just not quite as fast).
I cannot tell a real difference in real world speed tests with regular programs but one computer running 2x 320gig raid 1 Seagate drives on the Intel side gives me a burst speed of up to 210. The Marvell Burst on the other computer is 155. Average speed is within 1 number of each other on both controllers with a reading of 67-68. Random access is 11 on Intel and 13 on Marvell.
I decided to test 2 brand new drives (they are a little slower then the 320 gig drives but are SATA 2) I keep in stock on the same board but different controllers. This is in Raid 1 setup. I used 2 unformatted 160gig Seagate SATA Drives for the test. First one with the faster burst speed in the Intel controller. Second one is the Marvell.
Hey gtj, need your expertise please :)
I've got my E6600 overclocked at 3.24GHz (360 FSB @ 1.350v). I plugged this into your strap calculator and on the 1066 strap for a 1:1 ratio I should run 266 ref freq 533 mem freq, which is what I have it set to now.
Now my question is, how low should I go on the timings? I have it at 4-3-3-6 @ 2.12v and it passed memtest+ 5 times. Should I try to go lower? Is there one number that affects performance more than others?
I look in CPU-Z and my mem freq is 1:1 at 360.x. But in some OC threads I see people running all the way up to high 600s or even into the 700s. Is a 1:1 on the 1066 strap better than these high memory frequencies?
Thanks :)
the only way to tell is to test for yourself.
in the 360 range, 4:5 (266/667) will be the max ratio you should be able to use so test it out.
at 360, you should be able to do 3-3-3-8 with less than 2.2-ish voltage as well. see if this gives you a gain as well.
I tried 3 for Tcl from 2.04 to 2.20v and it won't work. I'll give 266/667 a try. How do I tell if one setting is faster than the other? By running 32M SuperPi and comparing the times?Quote:
Originally Posted by shimmishim
Yes, that works or seeing what the latency is by using everest. lower latency = better.Quote:
Originally Posted by MuttonFlanks
and that's strange that it won't work 3-3-3-8 from 2.04 to 2.2 hmm...
have you tried 2.25? that might work.
I would becareful on the vdimm..it seems as you increase over 2.2v...many are reporting D9 chips can die...it seems on the badaxe2 it is the stick in slot 3 or 4...so I am not sure if this becasue different slots can more vdimm
Interestingly...if I recall correctly at 1:1 my latency is better than at 4:5 and I see almost no difference in performance running 3500 with ram at DDR780 4-4-4-12 vs 3500 and ram DDR 975 5-5-5-18
test and see what feels better
Good info, thanks. I'm going to test this out as well.Quote:
Originally Posted by jschoef1
Quote:
Originally Posted by MuttonFlanks
Quote:
Originally Posted by shimmishim
What they said. :)Quote:
Originally Posted by nealh
why is it that no C2D mobo has a good secondary sata controller?
RD600 sucked as well
does using the marvell controller affect OCing abilities
It's better than the early 680i boards where the PRIMARY sucked. :)Quote:
Originally Posted by nealh
I've had absolutely no problems with the Marvell. "Ernie" has 4xWD2500KS drives in a RAID 10 using the Marvell RAID under Vista. "Elmo" has 4xWD2500KS drives in a RAID 10 connected to the Marvell but using Linux's mdraid.
Not a single problem with either since I've had the boards and no effect on overclocking.
I am going to try it out...does it only support RAID...Quote:
Originally Posted by gtj
I would think you could hook up a sata drive since it has the eSATA port ..which what I want it for
Not really suprising I suppose. The P5W64 and P5WDG2 WS Pro both overvolt the Vcore so I guess you would be more stable at a lower BIOS voltage.Quote:
Originally Posted by J@mmer
"To each thier own" I guess. I'm not in love with this board, but it overclocks just fine, and is a solid product.
Have you tried a file copy with the external SATA? It seems like all you need is a file over 100MB, at least on my ThermalTake Max4 external SATA enclosure. Not sure if it is the enclosure, the cables, or the BadAxe2 that is causing the problem. I keep having to use the USB interface to move large fiels around.Quote:
Originally Posted by mezcal
When you ghost a vista partition from one raid controller to another (assuming you know how to), make sure the ghost worked properly by doing a check disk and make sure you don't get the error saying it cant write to the secondary ntfs volume...or something like that. It wont effect the test and it will boot if you get that error, but for a permanent install, that error will lead to troubles in the future (like the backup feature in vista will fail everytime). I found ghosting a Vista install gives me that error about 25% of the time and I just redo it and all is good.Quote:
Originally Posted by gtj
You also have to do a repair to the newly ghosted hd with the vista disk, only takes a min...this is 100% of the time.
Plain disks are just fine and eSATA works fine for me.Quote:
Originally Posted by nealh
thank you very much as usuallyQuote:
Originally Posted by gtj
Yes I am well aware of this and hence why I set the VCORE lower than stock to compensate. I did have a P5WDG2-WS pro previously so I was aware of this OV problem. And when u factor in the Asus Vdroop, the OV is pretty much cancelled out.Quote:
Originally Posted by aicjofs
Also the Asus watchdog feature works a treat. Intel could also learn a thing or two from this.
I never said the Axe2 was not a solid board. It's a great board but when it comes to overclocking, it has NOTHING on the P5W64-WS Pro.
I tried to find drivers for the Marvell controller and at Badaxe2 website..I saw no drivers except for RAID use, I thought you needed drivers to install the Marvell controllerQuote:
Originally Posted by gtj
HMM..did I need to install the RAID drivers to use the MArvell for nonRAID use..ie, eSATA or just single HDD..when installing the OS
Badaxe2 and Penryn support:
Source: http://www.anandtech.com/cpuchipsets...spx?i=2968&p=2Quote:
Finally, with regards to motherboard support, Intel isn’t making any guarantees about Penryn’s backwards compatibility. While Penryn will still use the LGA-775 socket that Prescott and Conroe have used, motherboard support will require more than just the presence of the socket. If the appropriate VRM spec is implemented, then Penryn will work on your LGA-775 motherboard, the problem is that motherboard manufacturers haven’t yet released information on which of their boards will support the Penryn VRM changes. If history repeats itself, you can expect very limited official support for Penryn in currently shipping motherboards and guaranteed support with boards based on Intel’s new 3 series chipsets (e.g. P35). We did see Penryn up and running on an Intel BadAxe2 board, but it had a hardware VRM modification done to it in order to properly support Penryn. Penryn may also be able to work on boards without a VRM mod, however at increased (potentially out-of-spec) voltage settings.
I want to try bios 2333 as some have said that it's better in terms of Oc. Currently have the latest bios. How do i reflash it back? Do i need to revert everything to stock speed again? Am running on RAID 1 btw
Btw, i just disable the C1E thingy via installing the inf file in the previous thread (pg. 135). Should i worry about it when i reflash my existing bios of 2674 to bios 2333?
What are the cons of bios 2333?
Thks
Quote:
Originally Posted by J@mmer
You managed to disable C1E in the BIOS? How?
Quote:
Originally Posted by cryptocat
:D that's one solution. hahaha.Quote:
I have also managed to disable C1E. I am very happy again. How did I do it you ask? I bought an Asus P5W64-WS Pro!
it does not care what bios you have it would disable c1e on any cpu that has c1e on any mobo with any bios versionQuote:
Originally Posted by hotchoc
I'll wait for a couple of more replies to find the best way to flash it without compromising the current settings and my raid
many thks lome :) i'll take the C1e advise into mind
p.s. Heard bout the hdd led with the bios 2333. Am using an Antec p180 with the bx2 and i don't recall inserting the led pins into the board. How will it affect the rig?
Sorry, I forgot ya-:banana::banana::banana::banana:tails can do that to a guy!Quote:
Originally Posted by GamingDaemon
Just copied a .nrg of 2003 Server over from terastation to play with.
XP reports it as 542 MB.
From tera to esata box on bx2 over wireless G-about 7 minutes (samba 2 + wireless = sloooow)
From esata box to single drive on ich7r-about 10 seconds.
From single drive on ich7r to different partition on esata box-same.
From different partition on esata box to raid 1 partition on ich7r-same.
From...well, you get the picture. Works fine for me.
BX2 has xp pro sp2. Updated and clean-haven't loaded anything but testing apps on it yet.
The esata box in my sig is on the red port of the marvell.
There are no other drives connected to the marvell.
I loaded the marvell drivers via floppy when I installed the os.
I have not loaded the marvell control panel (apache thing) in windows.
Anything else you want me to try?
Maybe someone else who has vista can try it to see if it's OS specific.
Yea, I have read many posts about that which is why I don't want to go over 2.20. I'll try 2.20 if it will allow me a good OC, but I don't want to go over. Right now I'm limiting myself to 2.16 just to be safe.Quote:
Originally Posted by nealh
recomend you measure the volts with dmm cause nothing in the bios comes very close to whats realy going on the board atleast on mine
what revision is your board..mine is board is 505..loaded with bios 2333Quote:
Originally Posted by Lome
look back on my early posts on this issue, the sensor on my board is way off too.....Gtj boards have better sensors than mine
My bios reports an idle vcore of 1.535v when set to 1.525v with powerslope on....2 separate DMMs read 1.50 idle and load 1.50v(after 24hrs of P95)
my vdmm measured at 2.01v(I can recall no if this was idle or load voltage) for 2.0v setting in bios(the bios doesnt report this value at least not where i have seen...so this was odd that it delivers the voltage I set when vcore did not)
BTW I have installed the OS, if I install the marvel drivers now will I be able to use eSATA???
Hmm, anyone with Revision 505 have their vDIMM set at 2.20 or higher on this board? Someone with Ballistix DDR2-800 would be even better :)
I just tried to boot at 233 reference frequency and 667 memory frequency, but nothing worked. I tried 5-5-5-15 from 2.16 up to 2.24 volts. I don't want to go over 2.24 just to be safe for now. None of them booted.
Also tried 3-4-4-12 on 233/533 frequency from 2.16 to 2.24 volts. None of them work as well.
I'm running at 4-3-3-4 on 233/533 frequency for now at 2.16 volts. I can't decide between the current setting or 4-3-3-5. I keep refreshing in Everest and the 4-3-3-4 scores seem all over the place while the 4-3-3-5 scores seem more constant and often times higher. Guess I will have to run a few SuperPi tests to see.
Quote:
Originally Posted by MuttonFlanks
I own Crucial 10th anniv ans was able to set my ram to 266/667 for 487mhz at 5-5-5-18 with 2.16v with fsb of 390..run 50 passes of test 5 on memtest 86+ 1.70
I can run prime95 but I need more vcore than I want to give my cpu and I found no speed improvement over 390fsb w/266/533...4-4-4-12 at 2.0v
Quote:
Originally Posted by mezcal
Hmmm, well, gtj gave me some things to try in this thread (http://xtremesystems.org/forums/show...=1#post2135173). One of the things is to try to use the red port. When I installed Vista, I used the Intel RAID drivers to get AHCI with the black ports, but I never installed the Marvell RAID drivers. But on the other hand, gtj has no trouble using eSATA on the black ports. :confused:
what fsb are you trying to run?Quote:
Originally Posted by MuttonFlanks
i managed 370 4:5 4-4-4-10 463 with vfsb 1.3 vmch 1.6 vdimm 2.24
i've measured the vdimm and it overvolts by about 0.03-0.04 so be aware of that.
when i got my e6600 which is capable of 3600 @ 9x400, i tried to stabilize 400 4:5 4-4-4 and 5-5-5 500FSB with vfsb up to 1.45, vmch up to 1.75, vdimm up to 2.3 but could not get it stabilized.
this is why i'm asking what fsb you're running at.
It says "raid" but they're generic drivers for both raid non-raid. Grab the download that has the name STOR_ALLOS_1.2.0.24_PV_F6FLPY_MARVELL.EXE. When you run it it just extracts the drivers to a directory then you go to device manager and update the drivers.Quote:
Originally Posted by nealh
Yep, lome's c1e driver works just fine without regard to bios or motherboard. You should be able to go back to 2333 using the windows BIOS installer. When it's done, you'll get the 3 beeps when it tries to reboot so just completely power off and power on again. Windows is then going to reinstall a driver or 2 and require a restart. Should be fine after that.Quote:
Originally Posted by hotchoc
The HDD led isn't a big deal. If you didn't connect it then you won't notice the problem. :)
I just picked up a BX2, haven't unboxed it yet.
As for this inability to turn off C1E, should this be considered a possible "deal killer" as far as BX2 use is concerned?
Yes, I do understand that there is software that turn it off after Windows boots.
Just wondering.
Is it expected that Intel will resolve this?
Also, as for Intel leaving the HDD light on, would you not think that they would acknowledge this, and simply fix this a day or so after releasing this version?
What is your general opinion of Intel's BIOS team vs. ASUS for example. Less or more responsive?
Andrew
C1E can be turned off with the patch that was uploaded a page or two ago. The HDD light on issue has been fixed for several BIOS versions now. ASUS support is possibly some of the worst ever.Quote:
Originally Posted by aamsel
Why not just read this thread to find your answers anyways? Seems a tad lazy if you ask me...:rolleyes:
+1 There is a TON of info in this thread. Much of it is repeated 50 times as newcomers are not using the neat search feature prior to posting.Quote:
Originally Posted by theonlybabyface
That said, it is kind of overwhelming to try to read the whole thing at one sitting :D
SupertimOr should change the thread name. It surely has nothing to do with the P5B at this point!! :toast:
I HAVE BEEN reading threads about this (and every other) board, and I am far from lazy, thank you very much. There are thousands of posts about this board.
Was just asking a couple questions, sorry if they seemed ignorant to you.
I am an informed PC user, but a BX2 noob.
You see....
The polite thing is either answering or ignoring a post.
Andrew
Quote:
Originally Posted by theonlybabyface
Sorry Andrew. Didn't want to seem rude or anything but these particular questions get asked ALOT and the answers are throughout the thread. I can't ignore, I want to help as so many others have done for me. Again, my apologies. :)Quote:
Originally Posted by aamsel
Why the beep? I didn't know flashing into 2333 requires a reinstallation of drivers by Windows. What drivers are they anyway ?Quote:
Originally Posted by gtj
i read all 120 of tem in 2 days. My head of spinnign after that. LOLZQuote:
Originally Posted by theonlybabyface
Whoa, at the IDF they announced a new BIOS-Update thats gonna bring us "Auto-Overclocking", making the BIOS capable of finding out the max stable OC.
Does anyone have another source for that? I found it on a german site, but id like to see some other sources.
http://www.computerbase.de/news/hard...-overclocking/
"Intel will be within two weeks by an BIOS update „bath Axe 2 “- Main board (D975XBX2) with i975X-Chipsatz by a feature to extend that the Overclocking process automated and independently determines the maximally possible attitudes.Quote:
Originally Posted by cryptocat
The user can specify thereby in three stages the aggressiveness, with which operating voltages for processor, chip set and memory are to be raised. Subsequently, the Main board will try automatically with the help of the new BIOS to take the respective maximum out of the system."
Bad translation but it sounds good to me...if it works. :D
Thats what it says, kind of, lol. (I'm glad i dont need google to translate English into German xD)
Really looking forward to it, if it works right we wouldnt have to crash Windows anymore because of unstable OC :)
That's cool, no worries.
Andrew
Quote:
Originally Posted by theonlybabyface