No probs here, thought I wish it had sorted out my ATI issue.Quote:
Originally Posted by chaotic646
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).