I just tested it and you're correct. It's not fixed yet.Quote:
Originally Posted by cryptocat
I just tested it and you're correct. It's not fixed yet.Quote:
Originally Posted by cryptocat
I haven't played around with overclocking on the board for a while just playing games and dinking around with building a carpc, but i do have a nagging issue with whenever I put my computer in standby all the fans stay on. I have suspend mode set to S3 in BIOS. I can't for the life of me figgure out how to make it go into an actual S3 standby mode.
Is the board hot enough that the sensor chip is keeping the fans on until it cools down enough?Quote:
Originally Posted by Blauhung
Here is the response from OCZ:
How do i clear the cmos?Quote:
Originally Posted by ocz
hmm, i don't know if i have sat with it long enough to know, but from what i remember, my normal temps are all mostly in the low 40's.Quote:
Originally Posted by gtj
Go into the BIOS and Load Optimal Defaults.Quote:
Originally Posted by argylesocks
Completely power off.
Remove the battery for ten minutes.
Put the battery back in.
Go into the BIOS and load the 4-4-4-15 2.0v settings.
Boot to memtest
Hello all,
when running 4GB on Bad Axe 2 i would be interested
in your overclocking experience.
see: Overclocking 4GB with Bad Axe 2
Thank you very much,
Aljechin.
Bios 2663 released. Release date 03/05/2007. No downward multi, C1E bug is still present; absolutely crap! I'm really getting frustrated with the tardiness of Intel's bios engineers. Bios works fine, no noticeable performance again.
Bios Version 2663.
New Fixes/Features:
Updated processor support.
Fixed a problem where Setup F9 key caused unexpected page movement
at submenu option.
Fixed a missing highlight cursor problem in Setup after pressing
F10 and no response.
Fixed Setup cosmetic issue where garbage characters are printed
outside of string input box.
Fixed F10 boot menu showing two lines of duplicated title.
Added AMT1.0 support for certain SKUs.
Fix POST hang when SATA Controller is set to disable and IDE/ATA
Mode is set to legacy mode.
Fixed issue where certain host adapter cards not functional.
Added support for loading the Microsoft Windows Vista* native TPM
1.2 driver.
Fixed yellow bang in Windows XP* Device Manager for the TPM 1.2
device.
Drivers for onboard sound doesnt work on Vista :mad:
Anyone have it installed correctly?
Worked fine for me. Did you upgrade over XP and did you remove the audio drivers before upgrading?Quote:
Originally Posted by JZX100
I've got a fresh install of Vista 64 and the Sigmatel Audio drivers only partially work ... windows sounds, media player and itunes all function fine, with front panel support.
However, certain games don't work at all, the biggest culprit for me being Supreme Commander. Pretty sure that's more a problem with the game developers, as otherwise the drivers are ok.
update:
first off, thanks for all the help.
i cleared my cmos per gtj's instructions.
set my memory to 4,4,4,20 @2.0 and MEM:800
tested each module indivually with memtest86+
each one passed fine :) yay.
reflashed to bios 2634
booted to windows and did a 20minute orthos with no problem :)
im running at 9x266. now im a little scared to bring it back to 3.0+
for some reason, "steam" would no longer run. meaning i lost all my Half-Life2 game. :( i uninstalled & will try to reinstall it in a bit.
when looking at my cpu-z memory timings table it tells me:
333MHz should be 4,5,5,13 should i be using that when i go back to 333, or can i stick with the 4,4,4,15 ???
thanks again.
I just got my BadAxe2 along with a e6600 (SL9S8 Malay L628F028) yesterday and will do my upgrade this weekend. Is the 2333 bios still the preferred version?
Also could someone tell me if this chip is a good production and what week is this?
Thanks...
Who has been running this board on 24/7 phase and have you had any issues getting a good condensation proof seal front and back?
Glad you're (mostly) back.Quote:
Originally Posted by argylesocks
The SPD timings table is keyed by memory frequency not FSB so the 333 timings are only valid if you're running your FSB at 333 AND you have a memory divider of 1:1. At that setting however, you'll be underclocking the memory a good amount.
Did u get s-ata driver to work with 64bit Vista?Quote:
Originally Posted by slappynutz
I just recived my BX2. Installed Vista Business 64. So far I have probelems with the message; s-ata driver did not instal... I also have the issue with mobo cant locate my other 4 harddrives.
My last probelm is, I can`t update Bios, using the .exe file. And I have no floppy:(
So I've got a major problem and need some help.
I have this board with some G.Skill HZ and an E6600 and RAID-0. Bios is latest 2663. I've got a Tuniq 120 and the idle temps are extremely low at stock (<30C). I've read about the first 20 pages of this thread (it's exhausting). I've disabled C1E, EIST, AST and Fan Control (using manual controls to keep them maxed for now.) Watchdog is enabled. The memory is rated at 5-5-5-4 DDR1066 and I've started the timings at 5-5-5-12 to loosen.
One at a time, I upped the RAM voltage to 2.36, then the ICH to 1.65, the FSB to 1.35, and the CPU to 1.50. This is all still using stock/automatic clock settings. I ran orthos for a while to ensure this was stable before upping clocks. After all this, and the system being in use for a while, my idle temps are now 37C.
The RAM defaults to 667 (I don't know what the "Default" ref freq is). Then I set the RAM to ref=266, clock=400. I tried FSB 300 via the BIOS and it would do the Failed to Post message. So I went back to FSB=266 and booted into Windows and used IDCC to gradually up the FSB clocks.
I set it to 275 and it was fine. I set 280 and clicked Apply, and it froze instantly. The disk stopped responding. I rebooted and my #3 raid disk indicates an error. I recovered from this (amazingly without starting all over.)
I'm confused as to why I can't get the FSB clocks to anywhere near what others seem to have easily gotten, and annoyed that it ate my RAID in the process.
It's possible that it froze since I ran orthos after setting 275 but I don't think so. But IDCC is really temperamental about any other program running that touches the sensors (I don't think orthos does though). Freezing at 280 would be consistent with failing to post at 300, and the disk crash is (I suppose) a reasonable side effect of such a crash.
What did I do wrong? Maybe C1E should be on and the overly-senstive Watchdog disabled?
Update: Booted a CD with PQMagic and checked the disk, it said it was improperly dismounted. Heard it could be fixed with a chkdsk so I booted into Safe Mode Command Prompt and ran it, found no problems. Booted into normal mode and the RAID driver warned me that a data request failed and advised me to do backups (meh). Disk 3 of 4 had a red icon, I right clicked and said "Mark as Normal" - hilarious! "Oh there's no problem here, pretend it never happened" I guess. Anyway not really wanting to reinstall I marked as normal and rebooted. The RAID error on post went away and all seems fine. Amazing. I'm doing a full surface scan right now just to be sure.
Update: This is nuts. I just went to bios 2333 with ref 333 (1333 strap) and memfreq 667 and tried fsb=300 in IDCC and it freezes the system. What's going on? fsb=275 is the only one that works.
Update: I just tried 200 ref and 400 memfreq and it still locks up at 280. It hits 279 fine but always freezes at 280, I can't figure it out. Help!
minsc_tdp
the watchdog is waaaayyyyyy overly sensitive and to do any kind of OC you HAVE to disable it..... C1E definitely doesn't actually turn off, EIST is debateable... so in my experience you can leave em both on... IDCC has been unstable for me so I do the old fashioned BIOS method.
I've got the same ram/cpu/board/bios and similar cooling so if I were you, I'd load setup defaults, set watchdog off, and start again like so:
1- install OS (unless you've already got a working install)
2- enable enhanced power slope
3- decide what the max vcore is you are willing to run and set it (I decided 1.45)
4- set fsb override to 360 or so (you should be able to get at least there with stock voltages + 1.45 vcore), then step up 10 at a time until you run out of room
5- everytime AFTER you set fsb, go to the ram and set 533-5-5-5-15 v2.12 as it can get a little squirrely and decide to default your ram (tune the ram last)
6- after you get a max clock at stock voltages + 1.45 vcore (or whatever you are thinking) then you have the option of raising vMCH and maybe vFSB to get some more clocks
7- last- tune the ram up from the 533-5's.... remember that at 400fsb the 667 divider = 1000 and the 800 divider = 1200
with just 1.45vcore, watchdog off, enhanced power slope on, and simply changing fsb you should be able to get up into the 375+fsb range (worst case).. adding more vmch and maybe some vfsb should get you up to 400+ depending on your particular CPU
so, if i set my MEM ratio at 533 (1:1), and i have a FSB of 333, why cant i run at tighter timings (4,4,4,15)?? not sure why its telling me to run with some looser timings, if im underclocking my ram.Quote:
Originally Posted by gtj
i noticed that you have yours at 4, and you are running at 1:1 with higher FSB than what im trying for...
New install.Quote:
Originally Posted by gtj
My WinXP is in portuguese, so upgrade is not possible. My Vista is in english and the message error displays in japanese :eek:
http://img250.imageshack.us/img250/8601/untitledaq8.jpg
buy a $5 drive from newegg & hang it off the side of your case when you need it.... works for me :)Quote:
Originally Posted by Nightprowler_77
You can also just burn the ISO and boot from CD.Quote:
Originally Posted by argylesocks
Ah, if that's what you want to do, then you're OK. The SPDs are always programmed with conservative timings to give the board a better chance of booting under different circumstances.Quote:
Originally Posted by argylesocks
Wow, is it possible you accidentally selected the wrong locale when installing Vista?Quote:
Originally Posted by JZX100
The default Vista drivers do work fine if you don't need the front panel audio. Have you tried the audio without installing the separate package?
I've already rolled back to bios 2333 which doesn't have WatchDog.Quote:
Originally Posted by stmckin
So basically I've done all this, vcore is 1.5 and stable at default clocks, but when I hit your step 4, I tried to start small by raising FSB to 275. 279 is OK, 280 isn't. Maybe it's because I'm using IDCC to do this? Maybe I should just make a larger jump straight to 375 and see what happens?Quote:
I've got the same ram/cpu/board/bios and similar cooling so if I were you, I'd load setup defaults, set watchdog off, and start again like so:
1- install OS (unless you've already got a working install)
2- enable enhanced power slope
3- decide what the max vcore is you are willing to run and set it (I decided 1.45)
4- set fsb override to 360 or so (you should be able to get at least there with stock voltages + 1.45 vcore), then step up 10 at a time until you run out of room
Well I haven't seen it do this yet after many attempts. It sticks where I set it. And I'm doing the FSB adjustments from IDCC in realtime so I'm pretty sure this is OK. But should I be doing this from the BIOS?Quote:
5- everytime AFTER you set fsb, go to the ram and set 533-5-5-5-15 v2.12 as it can get a little squirrely and decide to default your ram (tune the ram last)
So my max FSB at 1.5 is 280 MHz. vMCH and vFSB are raised already also to 1.65/1.35.Quote:
6- after you get a max clock at stock voltages + 1.45 vcore (or whatever you are thinking) then you have the option of raising vMCH and maybe vFSB to get some more clocks
7- last- tune the ram up from the 533-5's.... remember that at 400fsb the 667 divider = 1000 and the 800 divider = 1200
Yeah that's what I thought too. Just ain't workin. 280 is not a number it likes. I actually managed to hit 281 one time, and when I tried to immediately go back to 279 it crashed.Quote:
with just 1.45vcore, watchdog off, enhanced power slope on, and simply changing fsb you should be able to get up into the 375+fsb range (worst case).. adding more vmch and maybe some vfsb should get you up to 400+ depending on your particular CPU
It seems like the memory settings aren't right for certain FSB clocks, maybe I should just go higher.