They work great for me. I havent had a bit of problem with them.Quote:
Originally Posted by supa-fly
They work great for me. I havent had a bit of problem with them.Quote:
Originally Posted by supa-fly
975XBX2 revision 504 and 505... any differences?
I checked Intel's page for errata specification updates, but it only lists changes up to 503. I have a 505 on hand that I can easily swap with my 504 (one is going to a friend) and I'm wondering if it's worth swapping out the boards.
difference is shipping biosQuote:
Originally Posted by urbanriot
If you're talking about the Corsair XMS2 2x1Gb DDR800 modules, I have them as well. I'm actually running 4 of them but can't seem to get them to pass memtest86+. Ran fine with 2 after upping the vMCH to 1.65 @ stock volts. Now I'm running 4 I've upped the memory volts to 2.20 and still not stable. =/Quote:
Originally Posted by supa-fly
What timming you guys running with these, Im using the TWIN2X2048-5400C4Quote:
Originally Posted by Eluzion
DDR 667 modules at (read my sig), just fine. I was really keen on the 6400C4's
so I could OC a bit higher try get it to 4GHz, now Im having serious doubts.
With 2 sticks, I was running 4-4-4-12 @ 1.91v (stock) without any issues. That seems to be what most people get out of these at stock volts.
Now with 4, I'm running 4-4-4-14 @ 2.2v and it won't pass memtest86+
Thanks for the quick response!Quote:
Originally Posted by Supertim0r
So physically, there's zero difference between revision 504 and 505? Where would you find this information?
Do you think you got a bad batch maybe. I think i must really consider
the Dominators instead. Anyone here have some OC'ed Dominators.
Whats your experience?
C1E lowers the v-core when the cpu is idle. It's a good thing long term but can make your life miserable while you're tuning. Disable it for now, then when you get your rig stable at your desired performance level, turn it back on again.Quote:
Originally Posted by supa-fly
Can't help you with the ATI, sorry.
Check the memory calculator in my sig. Setting the 333 reference frequency sets the 1333 strap but don't go there unless you need to.
Thanks a mil dude, that calculator is a rally cool tool.
OK now set that calcalutor to FSB 378 and check out lines 2 and lines 7.
What would you think the diffensce between those 2 in performance would be?
Kinda. Out of the package they generate 3-4 memtest errors per hour at one specific address. Max freq is something like 435 MHz before they fall apart. I should have just returned them once I got them but I was a meathead and hung on to them and did the rebate which killed any chance of ridding myself of them. I guess luckily the bad address is somewhere that wont crash the computer (yet), but still, not too good to keep around I think. I'm finally getting a cross-ship RMA on them from Corsair, and that is becoming quite the trainwreck also due to UPS shipping issues and Corsair's computer breaking a week or two ago. Maybe this week I'll swap them, maybe next week? LOL. I just hope that the replacement ones work. I'm fairly certain they were part of a rumored batch of XMS C4 that Newegg shipped the whole lot back to Corsair due to excessive returns as defective. Promos chips pushed to their limits to be sold as DDR2-800, and the guy in the testing department must have been on break when they fell off the assembly line I think.Quote:
Originally Posted by supa-fly
Just make sure the Dominators you get arent Promos based, then you will have the same thing on a different PCB and a heatsink. If I have to move to better memory I like the Ballistix, nice D-9 chips that are known to be useful when added bandwidth is desired.
I dont want to fiddle right now to test this out, but do you think it will bomb out your system if you are running higher voltage to get a higher freq? Is it quick enough to actually work as advertised?Quote:
Originally Posted by gtj
A few of us have done the tests at 1:1. The results are always the same. All other things being equal, the higher the strap the worse the performance. Basically you're forcing the NB to use looser timings when it doesn't need to. How noticable it is in real life I'm not sure but you can definitely see the difference if you run Sandra, Everest or other memory throughput tests.Quote:
Originally Posted by supa-fly
Bottom line: stay with the lowest strap that gives you a stable result.
Yes I see so, just rebooted and changed the ref from 266 to 333.
Shut down restarted bios still said 1066 system bus speed. But
CPU-Z says FSB 377.8 and mem 472.3 which is 4:5 ration. Looks
like the strapp hasnt changed. But all my benchies are the same
as when I had ref at 266, FSB at 377.8 and mem at 377.8 1:1.
Or am I missing something. I can post pics if it helps.
Here is what I accomplished so far:
I set the:
Reference Frequency to 266
Memory Frequency 533
I left the memory voltage at default, which was 1.84V
CPU:
Enhanced Powerslope enabled
CPU voltage override 1.375V
Host Clock Freq: 377
also disabled watchdog, C1E, VT, XD, EIST
so far I'm stable at 3.40GHZ with 52C temp. Orthos ran stable for more than 10hrs.
but now, when I try to get to 3.6, the system crashes.
And here is another dilemma I have : my memory is rated at 4-4-3-5 with voltage 2.0-2.1, but in the CPUz it shows 5-5-5-15. Is that normal? I still can't figure out why it changes by itself, and still don't know if 4-4-3-5 is better.
thank you guys
Look on the memory tab, not the SPD tab. The memory tab shows the actual values. You can manually configure the timings to 4-4-3-5. Those settings aren't stored in the SPD.
yup, that's where I looked, so that was my question: since they're rated to 4-4-3-5 and now they're running at 5-5-5-15, should I change those values in bios?Quote:
Originally Posted by Comp-Freak
New 2618 bios just released. Cannot download the release notes though. Anyone has this prob?
Yup, get the 404 error. It claims it was posted on the 12th. Thats 3 days to have a bogus link. Doesn't say much for Intel (or lack of) :D
Can't DL the BIOS either. 2618 BIOS Linky
Edit: Just sent their web bastard a message. Hopefully they will get on it asap.
Dude I cant download anything, none of the bios's and not the pdf either.
Did you manage to get anything at all?
Yup emailed them too. Hope they hurry!
Starting to like this board now. I hope the next bios is gold as I'm still on 2333 that really likes this E6600 (couldn' afford to keep the quad) and I'd like to get that hdd light to go away but the 2507 doesn't seem good enough to bother flashing. I'm gonna see if i aslo can get it to work with CrystalCpu later on but for now I have all i need.
Same hereQuote:
Originally Posted by supa-fly
Emailed them about the broken links.
I think they may have a problem with this bios. Looks like they were about to release it on the web and may have found a last minute problem and pulled it from public release.
Either that or the web fairys that update links at Intel have gone to sleep:eek:
maybe the guy is still in Valentine mood and forgot to do up the link
hi guys, i have a problem.
i've D975xbx2 mobo, xeon 3050 and TT Big Typhon.
yesterday i tried to get 450 fbs, and my system won't boot more.
here is the short story
first i've get the 440 FSB and boot ok.
voltages was
CPU: <1.475V>
Front side Bus Voltage Override: <1.375V>
MCH / ICH Voltage Overrride <1.675V>
after i tried to get 443 fbs and also boot ok
after i set up the 450 fsb and freezes at POST test with EB error code
i tried to setup a little more volatges
CPU: <1.5V>
Front side Bus Voltage Override: <1.4V>
MCH / ICH Voltage Overrride <1.7V>
(extreme a little, yeah?? for air cooled)
after that system also freezes at boot at the same EB code (Calling Video BIOS )
here is codes
http://support.intel.com/support/mot...434.htm#errors
after i've go down with all settings, and can't boot anymore with any configurations.
also i've reset bios settings by booting with jumper recovery position.
and can't boot this stock settings too.
but now freezes at 94 post test code (Clearing keyboard input buffer).
any ideas ??
i stilll can go to bios and do everything there, but can't pass this codes EB or 94 and system won't boot.
Links working now...
New Fixes/Features:
Updated Microsoft Vista* support for STAC9227 and STAC9274D Audio
Codecs.
Fixed boot order for SCSI HDD with certain SCSI controllers.
Adding Serial Port enable/disable setup question in Standard BIOS.
Added programming of PCI Subsystem Vendor ID and Subsystem ID for
the PCIe Graphics bridge.
Fixed issue where system would not boot after installing a Vista*
OEM Activation string.
Fixed issue where certain host bus adapter card was not
functional.
Added code to program the OEM SVID and SSID for onboard Marvell*
controller.
Reduced S3 resume time related to processor detection.
Fixed issue where 64-bit operating system installs would blue
screen with certain processors.
I have C1E and EIST turned on on 2 of my systems now and it's not giving me any problems.Quote:
Originally Posted by AndyM
I think you're going to have to up your cpu voltage. Go right to 1.5 and see if it's stable, then back it down if you can.Quote:
Originally Posted by horatiub
Memory manufacturers program the SPD very conservatively so the sticks will boot ofter install. 5-5-5-15 is typical for PC6400 memory. You'll have to change it in the BIOS to get better timings. If you go to a 400 FSB you'll be running the memory at it's rated speed but lowering the timings will probably require you to raise the voltage. If it's rated at 2.0 - 2.1, try 2.08 to start.
I just installed the newest bios and for some reason my e6600 is running at 1.6 instead of 2.4. I loaded up the default bios before I updated them and it set it successfully back to 2.4. After the update its now running at 1.6. Very strange...
gtj, yeah, my goal will be to run stable at 3.6 so if I can go to 400FSB would be nice. So, basically, you're telling me to go into the bios and change the memory timings to the original ones, 4-4-4-3, up the voltage a little and run tests.Quote:
Originally Posted by gtj
Also, isn't it 1.5v a little high for the CPU?
Quote:
Originally Posted by chaotic646
EDIT: Okay my Bios is still showing 2.4 but cpu-z is showing 1.6 with a multiplier of 6 and when I go to contol panel\system it shows 1.6.
Are both EIST and C1E disabled?
No, but C1E is for voltage not cpu speed. Everything is default so an e6600 should by default run at 2.4. I think its a problem with the new bios but cant confirm just yet.Quote:
Originally Posted by theonlybabyface
I know but my cpu speed would drop as well unless I had both disabled. It was really weird...Quote:
Originally Posted by chaotic646
Ok guys, all links to Intel new bios files working.
Go go go...
That's definitely EIST. Even when disabled, Everest will tell me it's running at x6 then it'll jump to x9 when I put it under load.Quote:
Originally Posted by chaotic646
I think it's a BIOS bug.
You shouldn't have any problem being stable at 400fsb. Start by leaving the memory alone at 5-5-5-15 1:1 266/533 then when you get a stable 400fsb lower the timings. 1.5v is just a starting point. The point is to get a stable 400fsb before monkeying around with other stuff. So get stable, then start changing things one at a time keeping good records of what you've tried.Quote:
Originally Posted by horatiub
gtj, thank you.Quote:
Originally Posted by gtj
so now a million dollar question: am I going to kill my CPU if I let it overclocked for years? It might sound stupid, but I always thought about it :)
also, as far as I know, when I run 1:1 266/533, I'm on the 1066 bootstrap, so I'm assuming that I won't lose any performance
Doesn't sound stupid at all. The short answer is "yes". Running the CPU with a higher voltage and the corresponding higher temperatures will shorten the life of the CPU. Whether there's any emperical evidence to say exactly how much, I'm not sure. I haven't seen any but I haven't looked all that hard either. Maybe it's 8 years instead of 10, I don't know. Anyway, an E6600 at 3.6g/400fsb, shouldn't have it's life materially shortened as long as you use the lowest stable voltage and keep the temperatures within reason. If you're going to be running the CPU flat out 24x7, something better than air cooling may be required.Quote:
Originally Posted by horatiub
266/533 is the 1066 strap so you're good there.
anyone here knows any xeon processor that can be used with this xbx2 ? thx
Quote:
Originally Posted by gtj
gtj - I just got around to trying this but it doesnt seem to work. I set the Intel controller to RAID, I hit ctrl-i and created my array, I booted to Windows from the marvell array, but I cant load the intel matrix drivers from the floppy. The readme.txt says you have to load them by hitting F6 during the OS install, which I knew but I dont want to install my OS on my new Intel array. Is there any way I can install the drivers from windows on my marvell array or am I going to have to install windows on my new array too just to load the drivers?
EDIT: Nevermind, I feel dumb. I just realized I could load them off of the Intel Express Driver CD. Its working fine now.
OK Here's the deal.
I was running all A OK on bios 2333 with Vista 64 bit with Crossfire enabled on the latest 7.1 Catalyst driver.
I then upgraded the bios to Intels latest 2618 and boom. The bios stops the cards from running in Crossfire mode.
The Catalyst Control Centre kept hanging, and putting errors in the Applications event log of windows.
I attempted 4 uninstall's and reinstalls of the catalyst drivers with no luck, same errors.
Logged a call with ATI and they are stumped.
I then thought mmm rollback the bios, surely not, it couldnt be the bios. OH YEAH it was.:mad:
Rolled back to 2333, uninstalled the Radeon Catalyst drivers, rebooted and reinstalled. Rebooted and all is back in good working order. Drivers all OK and Crossfire is working.:toast:
This is on a brand new install of Vista on freshly formatted drives today so i know its most definatly a problem with this latest 2618 bios from Intel.:slapass:
This is also with default values in the bios, NO Overclock.
Just thought i would share this all with you
Topboy
Yup...any 775 will work. Mine works great!!!Quote:
Originally Posted by irenic
Quote:
Originally Posted by topboy
Thanks. That's a reason for me to stay away. Any others experience the same issue???
Can someone who lives in the USA or Canada call Intel on 916-377-7000 and report this problem please as they will only talk to US or Canadian Residents and the UK office is now closed.
I think this is a pretty serious problem with this latest bios and they should know about it.
Cheers
Topboy
I had an issue with my nvidia cards as well although it resolved itself. Basically Vista redetected both the video card and the marvell raid controller and reinstalled the drivers for them. Had me scared for a bit but after another reboot, everything came back.Quote:
Originally Posted by topboy
Yeah i think from the readme of the bios they have re-written the PCI stuff and have broken it at the same time.
Quote from the readme "Added programming of PCI Subsystem Vendor ID and Subsystem ID for the PCIe Graphics bridge."
This would explain why your video cards and the raid controller got redetected in Vista.
Looks like Intel messed up with this latest bios in certain situations, i.e. crossfire.
I can't step out this meeting (boring as it is) to make a call but I just submitted a support request.Quote:
Originally Posted by topboy
http://supportmail.intel.com/scripts...d=36,2386,2578
You should do the same thing at least to get some activity going.
Done thanks for the link.Quote:
Originally Posted by gtj
Is anyone else able to verify this problem. If someone else has ATI and Crossfire can you upgrade your bios to 2618 and try reinstalling the 7.1 catalyst drivers. You can then rollback to another bios after.
Quote:
Originally Posted by topboy
I'll try it when i get home from work, i'm runnin XP-64, so will that matter???
No probs here, thought I wish it had sorted out my ATI issue.Quote:
Originally Posted by chaotic646
I dont think it matters if your on XP64 OR Vista64. I think this is an issue with the bios and ATI cards in crossfire mode however we shall see.Quote:
Originally Posted by screwtech02
Thanks for the test
Topboy
so I guess I need to start turning off my computer when I don't use it :)Quote:
Originally Posted by gtj
My last AMD based CPU, ran 24/7 for 4 yrs.
Really strange thing hey. Seems like the Bad-Axe II hat some issues with ATI.Quote:
Originally Posted by topboy
I have an ATI X1800XTX 512meg (Crossfire Compatible) If I just use that ATI
in the primary PCI-E slot, I get a no boot, if I slap in any PCI-E VGA card in
the second slot, then wham ATI works, also If I put the ATI in the second
slot it works. Wierd.
Guys,
I am going to start my new build tonight and was wondering if there is a step-by-step FAQ or anything of that nature that consolidates a lot of the great information in these posts? I don't want to miss anything and have issues. A short list of things to do when setting up my build (and subsequent overclock) would be extremely useful (as opposed to having to reset the jumper, and all of that).
e6600
Bad Axe 2
2x 1G OCZ DDR2-800 Plat R2
4 Seagate 320GB SATA-2 HDDs on Intel RAID controller (RAID 5)
eVGA 8800GTX (non-SLI)
Zalman 9700
OCZ 700w GameXstream PS
SoundBlaster X-Fi Fatal1ty Extreme Gamer
Would like to dual boot WinXP and Vista Ultimate, but will likely work with WinXP first to make sure everything works.
Thanks,
-scaryogre
Just updated to the latest BIOS. No issues here but I'm not running ATI. ;)
After flashing and loading my custom defaults, the computer wouldn't boot at first. I just shut it off, switched the PSU power off, and turned it back on and all seems well now.
I had to reinstall my video drivers. Other then that, it seems good so far.
can download already
If I'm still out of work next week, maybe I'll put a FAQ together. :)Quote:
Originally Posted by scaryogre
Put the jumper in maintenance mode and on the Maintenance page, set C1E and Watchdog disabled. On the Security page, set VT Technology disabled. On the Power page, set EIST disabled. On the Exit page, do a "Save Custom Defaults". Doing this gives you a baseline.
Reset the jumper and go back into the BIOS. On the Performance/Memory page, set Reference Freq to 266 and Memory Freq to 533. This will give you a 1:1 ratio at the 1066 strap. With those sticks, leave the timings at 5-5-5-15 for now but you can bring up the memory voltage to 2.08. Of course with the FSB still set at 266, you'll be severely underclocking the memory but you wont be there for long.
Make sure you're stable here although performance will suck.
If you're stable, you should be able to go back to the BIOS Performance/Processor page and move the Host Clock Frequency (FSB) up to 320+ without changing any other settings on that page. Do it in steps of 10 or 15 making sure you're stable at each. Don't stop at 320 if it's stable, just keep going until it's not.
After that, you'll have to decide what your goals are. Raw performance, low heat/noise, etc.
Oh yeah, keep good records.
Nah. Mine are on 24/7 and 1 is loaded 100% 24/7. Not expecting any trouble.Quote:
Originally Posted by horatiub
Thanks gtj! This is exactly what I was looking for! :toast:Quote:
Originally Posted by gtj
Also, my best wishes that you find work soon! :)
-scaryogre
ok, so I tried the 400FSB and 1.5V but I get the BOD screen. So, it doesn't boot, I get passed the windows logo and that's it.Quote:
Originally Posted by gtj
Also, I went back to 377FSB and now I notice my temp at idle at around 50, yesteryda it was somewhere around 40, so at least 10 more. If I run Orthos at 3.4GHZ, the temp stays around 60.
so, I'm not sure what to do next
Flashed 2618 BIOS worked great except I forgot to set my overclock back to default.
The flash set the RAM back to auto and I got the dreaded "3 Beeps from Hell" as my ram was seriously overclocked. Off comes the side of the case and it's hemostat vs, jumper time again :( (My GTS and cabling combined with my desk area makes the jumper tough to reach, time to steal SuperTimor's switch idea... :) )
At any rate, back in action with mild overclock (350 FSB) in place and no issues so far
Just flashed to 2618 and no problems with Crossfire:Quote:
Originally Posted by topboy
http://123pichosting.com/images/1643xfire.JPG
Did you have to reinstall the drivers?
Anyone here using a PS/2 Keyboard? I'm using a M$ natural. If I power down the system then power up, the BIOS (2507) won't detect it. But upon rebooting all is well. I have to do this every time I shut down, very annoying.
Quick question on the above: Do I want to jumper to maintenance mode right out of the gate (i.e. before first boot?). Or should I go ahead and get OS and everything installed at default BIOS settings first and then re-jumper and try to OC? I'm assuming the latter based on my prior experience (even though it has been 4-5 years since I last built a system.Quote:
Originally Posted by gtj
Thanks,
-scary
Nope, did not need to touch the driver at all.Quote:
Originally Posted by theonlybabyface
Just make sure you boot into the Maintenance Menu after flashing and disable Failsafe Watchdog (also disable C1E and EIST if you're so inclined) - this is especially important if you're updating from BIOS 2333 or older. While you're there check your mem settings as well. This should minimize any problems you may have after the update.
hey guys, i need advise.Quote:
Originally Posted by boo50
can anyone help me ??
also - how can i update bios if i can't boot from CD ??
boot process freezes earlier than boot from CD must start.
also i tried to burn BX2333P.BIO file (from 2333 bios update) to CD and power on my computer without bios jumper to recover bios, but it's just rebooted always every 2-3 sec(i suppose - i just hear what CD starting every 2-3 sec)
What is your OS. It looks like XP but which version 32 OR 64 Bit.Quote:
Originally Posted by syl
Thanks for the information
Topboy
Try: turn off the computer, unplug PSU, set jumper to recover, pull battery, go have a coffee. Then reinstall battery, plug PSU back in, power up and see what happens?Quote:
Originally Posted by boo50
Alright, an update.
Thanks to everyone's help, I have my chip running 2.8GHz (400x7) 24x7 with a 44C idle and 70C extreme load (dual Orthos or TAT - never really goes above 60C during heavy gaming).
My problem is that I can't get it to go past that. I've tried many different combinations for RAM and everything else using the calculator and the system just won't POST on anything higher than 2.9GHz.
The only thing I can think of is that VT is holding it back... but I actually USE the VT tech... does it really make that big of a difference?
I've got the chip running 1.325 volts right now and I'm running Orthos while I'm typing this (damn this chip is insane to be able to run other apps even when its at 100% utilization!) without any issues. My AS5 is still in the burn-in period though, it seems, because every day, I see another 1 degree drop in load temp. Its now at 67C according to Core Temp. Alternates between 67 and 66. MUCH better than the 70C I was getting under load with the chip at 2.6!
Anyway, any ideas how I can get a higher overclock out of this chip? I really don't necessarily need it... but I'm craving more speed. :P
try this:Quote:
Originally Posted by EtherealRemnant
watchdog OFF
C1E OFF
reference frequency 266MHz
mem speed 566MHz (1:1)
MCH voltage 1,6V
SB voltage 1,3V
vcore voltage 1,4V
power slope ON
Using XP32. Maybe the problem you're seeing is a 64-bit driver glitch?Quote:
Originally Posted by topboy
Still didn't work.Quote:
Originally Posted by heikis
I think I'm going to go back to the 2333 BIOS. People seem to have better luck with that than 2507.
Curiously enough though, I have completely disabled Watchdog (I even just verified this) but when I tried to overclock the system to 3.0GHz, it brought up a screen saying that it detected that an error has occured due to my recent changes in my performance options or hardware. Seems like watchdog to me.
I'll try 2333 tomorrow and see where I can get with it. I never really got any overclocking done on 2333 because I didn't know the key to overclocking so all of it has been done on 2507. I just like how I have the Marvell controller disabled and my HDD light still works.
If you're just burning the .BIO file as a file on the CD, that's your problem right there.Quote:
Originally Posted by boo50
You need to burn an ISO to CD, not the BIO file.
http://downloadfinder.intel.com/scri...Name=&lang=eng
You need to burn that with a burning program not as a file but as an image (like Nero or Roxio will have an option for "Burn Image to Disc" - use that).
thnx, i'll try, when i'll get home.Quote:
Originally Posted by IRQ Conflict
also - did i make a bios recovery CD correctly??
i'm just simply burn the *bio file to CD, as i read in instruction.
anyone tried this method ??
@EtherealRemnant
you told about an ISO Image BIOS Update [BX2618P.ISO]
but i'm talking about Recovery BIOS Update [BX2618P.BIO], because i can't boot from CD, i need complete bios recovery.
update: I'm still at 377FSB or 3.4GHZ, vcore 1.450, I ran Orthos but it gave me an error after 4hrs, so I'm assuming it's not stable. Weird that I can't even get stable at 3.4, I have no hope for 3.6. I'm wondering if the way I put the AS5 on the CPU has something to do with this( I applied a thin layer over the whole CPU surface, I saw that some people only put like a rice size on it in the middle of the CPU)Quote:
Originally Posted by horatiub
Quote:
Originally Posted by boo50
I haven't had the displeasure of running into your predicament, but it seems to be ok, I don't know how you would get the BIOS to access the file unless in recovery mode it must do it all by itself....I hope :(Quote:
Originally Posted by Intel
If you have a floppy drive installed and the CD doesn't work try the floppy?
Nevermind. I am being dumb. Its 6:30AM here so shoot me lol.Quote:
Originally Posted by boo50
Oh and an update on my overclock situation.
heikis, your tips worked with 2333 but my memory meant that I had to run it 333/533 instead of 266/533. Stupid OCZ Platinum Rev 2...
Anyway, I got it up to 3.1GHz so as I suspected, the chip can handle it just fine.
The problem is that dropping down to 2333 put my temps WAY up. They're up 6C from 2507 on the exact same BIOS settings... :(
So I've had it with Asus their evil little P5W DH. I'll probably pick up the Intel board shortly (based on many hours of forum/review reading), but first I have a troubling concern:
Can I move my RAID-0 (OS: Vista Ultimate) that runs on the ICH7R on the Asus to the BX2's ICH7R without any issue?
Secondly, if anyone is familiar with the Asus EZ-Backup RAID, I am using a RAID-1 (mirror) for my data (obviously what I care most about). Will it be possible to read either of my mirror drives using the BX2 board?
The Asus board is not posting, so I have no way of backing up the drives w/ that MB. Sadly this is my development PC too, so I'm kind of in a jam.
Regards,
Sker
i'm hope too.... . . .
will test later and sure post here.... .
hope i'll solve my problem.......... and this is not a hardware problem...
this board isn't cheap for easy replacement with new one... =(
huH? whats wrong with the OCZ?Quote:
Originally Posted by EtherealRemnant
I can't get the OCZ to pass memtest above 830, even if I set 6-5-5-15 for my timings at 2.1V...
I've read of others getting this stuff to 950 or so at 5-5-5-15...
Thought I'd chime in on this and let all you fellas know what I'm using and timings and such:Quote:
Originally Posted by EtherealRemnant
E6300@ 2.8Ghz Stock Voltage 35-40c Idle all the way up to 70+ with TAT:explode2:
OCZ Gold 1GB PC-6400 @400DDR SPD=5-5-5-15 @ 5-5-5-12 2.0v
MCH@ 400Mhz Stock Voltage 1066strap 1600Mhz quad pumped thingy
on air with a scythe ninja rev B.
EIST on, C1E on, Watchdog off, VT and XD both on.
Not A Single Issue so far :fact: :woot:
I think that covers it. I don't think OCZ's ram is bad, my sticks do waaayyy more than I expected them to.
Oh, trying to OC the ram, does ok 1:1? :stick:Quote:
Originally Posted by EtherealRemnant
Yeah it does fine 1:1 but won't overclock at all.
But it pisses me off that I got this RAM on the recommendations I've gotten from people saying that it overclocks great. I could have gotten the G.Skill HZ for 29 dollars more >_<
I wish I could help but I'm rather new to this OC'ing thing myself. All I know is my system is faster than one on a stock E6700 and I'm lovin it! :)
Edit: According to Everest's Benchmark.
Meh, I'm just going to express order the HZ on Newegg and then take the OCZ back to Micro Center and if they ask me anything, I'll just tell them it keeps causing BSODs. *shrugs* I only just got it on the 5th so I have plenty of time before the 30 day return window is gone.
Kewl, hope all goes well for ya!
hmm. isnt that a c4 ram? whats it like if you are just running it at 800?Quote:
Originally Posted by EtherealRemnant
Anyone know if this board likes G.Skill F2-8000PHU2-2GBHZ DDR2-1000 modules?
The 4-4-4-5 @ 1000 is tempting...
Yeah, its 4-4-4-15. Works great at 800 but its severely limiting my overclocking ability since I can't get it to run much under 800... :/Quote:
Originally Posted by argylesocks
Some interesting findings with the new bios. After flashing, you'll need to go back into maintenance mode and disable Watchdog and C1E. I also had to uninstall/reinstall my ATI drivers as well. Running Vista 32-bit btw. :)
Hey Sker,Quote:
Originally Posted by Skerlnik
Sorry, I can't answer your RAID-0/ICH7R question, but...
I switched from the P5W DH to the BX2, mainly because of disk, disk controller or RAID problems. I also had an EZ-Backup mirror, although mine had the OS as well as data. After a few weeks each time, the P5W DH refused to start the Windows installation - and this whole scenario happened more than once. I've lost count of the number of times I had to reinstall Windows. I simply could not get the ICH7R RAID working at all on that board (hence the EZ-Backup mirror).
I kept both of the mirrored drives that the P5W DH refused to boot from, and installed Windows on new drives in the BX2 (RAID 1 again). The BX2 could 'read' the P5W DH RAID drives fine, installed as normal SATA drives. The data is all transferred and the old drives have now been reformatted and give me lots of disk space :-)
If your experience is anything like mine, you won't regret the move.
Hope this helps.
Quote:
Originally Posted by theonlybabyface
OK im going to re-flash the bios upto the latest and install 32bit vista instead of 64bit and see how that goes
Topboy
Yes you can. Just you have to go through the activation process again, and then do the driver thing...Drivers hereQuote:
Originally Posted by Skerlnik
Touchstone, Reinvented... you guys are awesome! :woot:
I'm going to attempt to just plug my drives into the new (and hopefully amazing) BX2. I won't even need to re-activate Vista since it's an MSDN version (if it works at all) :) I suppose I'll need to back up one of my RAID-1 drives and then create a RAID-1 array on the ICH7R with those two drives and copy my crap back to it. Or... do you think I can create a RAID-1 on the fly with data already on the drives? Never tried that.
About the drivers on Intel's site... where is the Vista ICH7R raid driver? Don't I need an "F6" driver during the OS install (if my RAID-0 transfer doesn't work)? Does Vista already have drivers for this chipset *crossing fingers* ?
Regardless, I have ordered the BX2, and am counting the hours until I have a working PC again!
- Sker
The Intel Matrix Storage Console can morph the RAID 1 array to 0, or whatever your choice is, from Windows. However, you cannot create one on the fly, as it needs to be synchronous data on the drives for either of the RAID 0 or 1, and this can be created from POST, Bios, etc.Quote:
Originally Posted by Skerlnik
AFAIK, there is no need for RAID drivers for Vista. It'll automatically load or something like that. You can try using the Floppy that comes with the board, and seeing if it'll load. If not, no big deal.
Vista has all drivers for the BX2 except the Marvell RAID so no problem with the Intel. My advice would be to set the controller to RAID mode in BIOS but don't connect your RAID array drives. Just connect the install drive and install Vista. Then when it's stable, just hook up the drives that were already in the array.Quote:
Originally Posted by Reinvented
On the fly defintiely does NOT work so don't try it.
OH, The Intel Matrix Storage Console does NOT run on Vista. Vista's driver is newer than the console so it complains.