I have no idea either......LOL. I get them, I post them .... :)
I have no idea either......LOL. I get them, I post them .... :)
Thanks....:up:
Maybe one day they can get this crap fixed!:rofl: :shrug:
http://i76.photobucket.com/albums/j7...VRAIDSucks.jpg
Well one thing that I see new is the "C1E bios support", which has something to do with dynamic voltage. One other thing is that no matter what I do, I can't seem to go beyond 400fsb. On the older bios, even if it won't boot to windows all the way, I still can set 400+. Oh well...Quote:
Originally Posted by Heidfirst
raid is messed up in this bios big time. as soon as i enable it all my HDD's disappear
1332~1333 FSB max overclock. Anything higher and uGuru reverts to spd.
uGuru in XP shows 0 for all temps and displays warning. I disabled it.:up: :rofl:
Enable NVraid and only my array shows up in the raid bios. My sata data drive is no where to be seen in the bios, but it's shown in XP. No prob with IDE drives.
Occasional delay in detecting the array. I know from experience I have to Ctrl+Alt+Delete or else it will come up as array failed. When it reboots most of the time it will be ok.:shakes:
Good news???: This is the 1st time I've verified EIST and C1E work on this board.:clap:
I don't know about my raid issues in XP yet. I've checked my drives and cables many times and if the errors continue I guess I'll dump the raid!:devil:
lol i dumped raid long ago, way to buggy, they need lessons off intel about how to setup and apply raids, every intel raid i have set up lasts never get any isues, nv raid on this board is a no go not worht the hassle of currupt disks, and fialed raid, wich is a shame as i have got a nice pair of 150gb raptors to put in this machine, for which i aint going to unless they finaly fix the raid problems, although nvidia did a bios update that fixed these very isuses, conserning raid, why hasnt abit also done this ?Quote:
Originally Posted by maxwedge
Ermm what RAID problems? I have been using 2x WD Raptors in RAID since this mobo's release even with BIOS v1.0 and it is still running 100% trouble free.Quote:
Originally Posted by DataVampire
It seems that the RAID/HD issues are mostly random and you were unlucky.
erm well documented ones, thats in a lot of forums, and i got rid of mine by uninstalling the damned nv raid program, not the driver, the program that ataches to the controle program, and it also happens to be the same problem that effected evga bpards to for which nvidia released a bios update for.Quote:
Originally Posted by JargonGR
EDIT:MediaShield is what it is called
Quote:
Originally Posted by aehmkei
With 12B06 my sata disks worked in pio mode. :ROTF:
And MY WINDOWS VISTA 64 is remained in PIO MODE
also when I have replaced the 12B03. :shocked:
My ViISTA 64 is DIED. :rofl:
I believe that 90% of the raid errors I was getting (see posted image above) were caused by 13 b01. I had random errors before but nothing like this before. I've flashed back to 12 b03 but before I did that I imaged back to a single sata drive and still had disk errors in event viewer, even with no overclock.:confused::down:
Edit: Actually my screen shot 8 posts up is with bios 12.b03, so I had some existing problem that I've been unable to figure out.:( :brick:
It can be that you have the low voltages in the plug of hds.Quote:
Originally Posted by maxwedge
I have had your same problems.:shakes:
I have uncovered that I had
in the plug of the hds 11 volt instead of 12 and 4 instead of 5. :eek:
One psu' cable for 2 hds to the maximum.:up:
Excuse my english ! :rolleyes: :confused: :clap: :D :ROTF: :rofl:
I've been running a dual raid0 array on the Nvidia controllers since the first day I've owned this board, never any issues at all.....Hmmm
Not with PC Power & Cooling but I guess I could check, but I doubt thats the cause. I have no problems now.Quote:
Originally Posted by silmetal
Lucky you.Quote:
Originally Posted by Lvcoyote
Then lucky me, too. I have 3 150gig Raptors in raid 0 and have been running the newest 1.3 beta without issue. For that matter, I ran all of the other beta's as well without a single hickup.Quote:
Originally Posted by maxwedge
Quote:
Originally Posted by shawn1998
Unrelated to the RAID question, but are you overclocking? I had very strange results with the last two beta bios releases. I'm wondering if I was doing something wrong or what.
Thanks,
Slammin
Others are too, I think these last couple Beta's were just for a particular issue or for a particular person.
Well like has been said you are very lucky, the raid problems currupt hds are not a hit or miss proplem, a lot of abit users are having the same isuses, it is clearly a nvivida problem, anyhow, im curious did you install/run the media shield ?? this i beleive cuases a lot of problems, when i had it installed i got a load of bsods, randam restarts, curupt hds, cuasing it to loose files, of the boot drive, ie ntdlr, bal hbalh, as soon as i stopped using media shield it went back to normal., and please remember this problem has been anounched by nvidia themselves, so it must be a combination of facters, ie hd make moddke ect and the install of the nvidia sata management software, i think its calle dmedia shield. have you checked the properties to see if there are errors there, are you using microsoft drivers or the proper nvidia drivers .Quote:
Originally Posted by Lvcoyote
hope this helps
:S 482fsb use 12B03 (1.35vnb)
http://www.pctuner.info/up/results/_...128_32m482.JPG
This announcement you speak of from nVidia is only refering to reference motherboards, ie XFX, EVGA, BFG and ECS. The Abit, MSI and Asus were not included in that announcement, as they are not the base reference boards made by Foxconn for nVidia. Also, I am not aware of all of "alot" of Abit users all having raid problems. I'd say it's more like "a few". I am on the Abit forums daily and do not see a whole lot of threads dedicated to raid and sata issues like I did over at the EVGA forums.Quote:
Originally Posted by DataVampire
Edit - Here is the link to the "announcment" from nVidia that you referenced. Note what it actually says.
http://www.nvidia.com/object/680i_hotfix.html
http://nvidia.custhelp.com/cgi-bin/n...i=&p_topview=1
wem correct me if im wrong here, ref board or not, they still all contain the same raid chipset ie nvidia chipset, so woudl produce the same erros and problems reguardless of being a ref board or notQuote:
Originally Posted by shawn1998
OK, I'll correct you as you are wrong. Please, just follow the link and read the actual statement made by nVidia, the one you referenced in error. NVidia never says that there are sata problems with any nVidia-based boards other than the reference boards. You are attempting to prove an issue by disseminating misinformation. You wrongly referenced their statement.
Funny that it must just be coincidence. for i for one have been expericancing the very problems described by nvidia themselves, wait a min, they al use the same chipsets, surley not..........
Details:
This update is related to SATA disk drives and system instability. System instability is observed in the following ways (not a complete list):
Random application shutdown
Corrupted boot drive
"Blue screen of death"
Corrupt data
This update will improve system stability and prevent future stability issues related to SATA disk drives on those systems requiring this hotfix.
strange that realy.....
hang on a min
http://www.nvidia.com/page/nforce_600i_tech_specs.html
doesnt the evga ect uuse the same specifications, surely not lol
but al jokes aside i do know what you are saying, but honestly they do share exactly the same chipsets ect, and they do have or rather did have until nvidia released a bios update for some boards, that are ref boards, ther same basic shipset is the same, thus stil have the same sata probs.
When I initially set my system up all I did was use the floppy disk to load the raid drivers and the mass storage drivers, thats all I loaded until Windows was installed. Then when I loaded the chipset drivers all I loaded was the chipset & LAN drivers, nothing else. No media shield, no Nvidia Networking stuff..... just drivers.
Quote:
Originally Posted by DataVampire
If you are going to quote the page to prove your point, then quote the entire thing. You strangely left out these specific paragraphs...
Quote:
Motherboards affected:
EVGA nForce 680i SLI motherboard
BFG nForce 680i SLI motherboard
Biostar TF680i SLI Deluxe
ECS PN2-SLI2+
Also, where are all of the rest of the multitude of Abit users with these sata issues? I am truly sorry if you are experiencing issues with sata and raid on your particular motherboard, but that doesn't mean that ALL users with that board have issues. Also, just because EVGA had/has issues, once again, does not prove that Abit has the same issues. You sure like to generalize, jump to conclusions and spread mis-info and provide proof that a different motherboard maker had issues, which somehow proves your (invalid) point.Quote:
Description:
Some NVIDIA nForce 680i SLI "Designed by NVIDIA" motherboard customers have reported experiencing disconnect or write error issues with SATA disk drives. To address this, NVIDIA has released a BIOS update for the NVIDIA nForce 680i SLI "Designed by NVIDIA" motherboards that eliminates this bug.
Now, if you have finished reading the entire statement released by nVidia, you will now hopefully do a little more research into your issue and, again, hopefully provide some different type of "proof" of the alledged sata issues that are afflicting "alot" of Abit users, as you claim.
The only sata issue I have ever had with this board was during one attempt at finding max OC when I forst got it. I attribited that to linkboost, though I have not been able to duplicate it.
Really, this is the first enthusiast mobo I've owned where I didn't corrupt a drive so bad that an OS reinstall was required. Of course now that I say that, I probably just jinxed myself.
I am still a little leary of linkboost though because it will automatically OC your PCI bus if you let it, though I have been using it for the past several week with no ill effects other than making my vid cards run a little warmer.
for god sake your missing the entire point here, they all contain the smae sodding chipset reguardless who actualy made themQuote:
Originally Posted by shawn1998
prove me wrong on that. thats why i poste dlink to nvidia site because funny enough it links of the abit uk site to that page, and for that i mean the part about the chipset
I agree as i previously stated, thats what i found to be wrong, and cuasing me probs, nvidia media shiled, if i dont install that, im fine as soon as i install media shiled, currupt disks, restarts bsods.Quote:
Originally Posted by Lvcoyote
and what has cropped out of all the main manufactures of the 680i boards, is a rumour that linkboost is cuasing instability probs, and that it is to be removed, of this i do not know or care, i do not use it. as long as i sorted out my probs, ie the bsod every 20 mins i eneded up having
NVidia has never, ever, not once, stated that there is an issue with the "sodding" chipset, but with some of the boards that the "sodding" chipset is on. RIF (reading is fundamental). It's the implementation of the chipset on their reference boards that is/was the problem, hence an updated BIOS was released to correct it. Do you think a bios update could fix a hardware issue within a chipset? No, it couldn't.Quote:
Originally Posted by DataVampire
I'll ask one more time, where are all of these Abit users with sata/raid issues?
been gone for a while as far as nVidia have been concernedQuote:
Originally Posted by DataVampire
**Note: NVIDIA LinkBoost™ technology has been removed as a feature from NVIDIA nForce® 680i SLI
http://www.nvidia.com/page/nforce_600i_tech_specs.html
Well I had this MoBO for a couple months with no major problems but suddenly it will not see my two SATA II drives (one 400Gb and one 500Gb in IDE mode not RAID). I have a pair of SATA DVD burners that show up no problem.
I have not played with a newer version of bios. So the board has whatever it came with(I am guessing bios v1.0).
By the way I am not overclocking right now. I played with the system at around 3 GHz with no real issues. But I reset the CMOS to stock.
I run Vista 32 bit and Vista 64bit dual boot.
Do you guys think I need to go to one of the beta versions maybe v1.2 beta 6?(seems to be popular). Any other suggestions or input?
Here is my specs:
Abit IN9 32X-MAX wifi
E6600 Retail Core Duo processor
2Gb of Corsair Twin2x2048-8500C5D (Dominator XMS2)
Antec HE550 power supply
2 SATA II HD (400Gb and 500Gb)
2 SATA Samsung DVD burners
Radeon X1900 GT video card
Cheers
Nick
Never had a problem here, just not sure about any actual speed increases.Quote:
Originally Posted by shawn1998
BIOS v1.1
I'm kind of sad that Linkboost is on the way out. I pulled my hair out for weeks with this board trying to get stable with either 2 or 4 gigs with even a mild overclock with the 12b03. I had disabled Linkboost and locked down the frequencies at 100,100,100,200 like everyone recommended. Stability was random and all over the map. The minute I enabled Linkboost everything straightened out and once I replaced the rubber under the heatpipe with Ceramique it was golden. I'm no overclocking genius by any stretch, but I do have some previous experience, and enabling Linkboost fixed my stability problems.
i broke a pin on my socket
any idea if i can get this rma'd
Abit will charge you $25 for physical damage and give you a refurbished board. I think you need to call their RMA department. Should have the number on their website.Quote:
Originally Posted by billdavis
-Collin-
ok I flashed bios 1.1 no problems during the flash. Still no SATA drives. Now I get a cmos checksum error 7F
I am reading the manual:
" Switch back to text mode if full screen logo is supported
-if error occur, report errors and wait for keys
-if no errors occur or F1 key is pressed to continue clear EPA or customization logo.
What does that mean?
Any input?
Thanks guys.
Nick
Quote:
Originally Posted by titsataki
@titsataki I had the very same problem, your going to have to flash the bios again with a different one. I recommend 1.2 B03. Thats the one i'm using and it completely stopped that error message. I've also found this BIOS to be the most stable for me even though it Beta!!
There's a new official bios 1.2:
ftp://ftp.abit.com.tw/pub/download/b...2x/m622a12.zip
ftp://ftp.abit.com.tw/pub/download/bios/in932x/
Quote:
BIOS release V12 for IN9 32X MAX V1.0, V1.1
Release information:
[ENGLISH]
1. Update NVMM to V4.71.20
2. Fixed an issue where the system sometimes hangs when enable the Keyboard emulation.
3. Enhanced compatibility with certain HDDs under RAID5.
4. Support 1333 CPUs.
5. Enhanced overclocking ability for quad core processors.
6. Fixed a performance issue when Pentium an Extreme Edition installed.
7. BIOS compiled date: 05/08/2007
Quote:
Originally Posted by Chopst1x
Ok I will flash again. I may try the official 1.2 version and then possibly 1.2 b03 if need be.
regards
Nick
Official v12 seems ok here. EIST and C1E work and I'm not getting any sata issues, yet.:up:
Flashed to BIOS 1.2.
Still same Checksum error. Still does not recognize any SATA device. No HD Drive no CD ROM.
What can I do next.
Any input would be appreciated.
Nick
Get a new board and upgrade the BIOS to v1.2 before you do anything else.
Quote:
Originally Posted by Undesirable
Well I have filed an eRMA with ABit but it is just sitting there. Am I supposed to ship the MB back first and then they ship another one? How does it work out?
Cheers
Nick
Their trying to fix their website because as you can tell it's down.
Are you in the USA? If so try calling 510-623-0911 or 510-492-0882. I think the 2nd # is the rma dept.
Don't send anything in unless you've gotten an e-mail with a valid rma #.:caution:
With all the problems the web site is having..... once its back up check the status again. If you dont see anything then re-submit it. You "SHOULD" get an e-mail with the RMA number and detailed instructions on how to send the board back.
yes I was able to access their eRMA site a couple days ago and my RMA was listed as accepted but I never received an email. Now I cannot even access the eRMA site.
This is a pain. The MB worked fine for like 2 months and all of the sudden took a nose dive.
Thanks
Nick
The exact same thing happened to mine - worked fine for a couple of months, then suddenly started getting instability probs until one day i went to turn it on... nothing... dead as a dodo. Luckily the e-tailer I bought it from took it back and agreed to a replacement.Quote:
Originally Posted by titsataki
Today I installed another 2GB od RAM so now there are 4 Dimms of 1GB each. And huess what... It is working flawlessly overclocked.
The memories are both OCZ but one pair is the Titanium Alpha and the other pair is the newer Reaper series PC6400.
The are both working @1039mhz (sthing lile that) 5-6-6-15.
I also resoleved an issue with the restarts and power ups. The motherboard power socket (24pin) must be problematic in my board and this was giving me lots of problems and the dreadful A0 message. I just pulled it up a bit and now all restarts and power ups are perfect.
Hi!!
I`m new member of this forum. i read most of the message of this 3d and i need help to oc my cpu..
Old system specs
E6600 / P5N32-E SLI / 2x1g ocz pc6400 + 2x1g cellshock pc6400 micron d9 / 8800GTX
With this configuration i was able to use it @ 3200mhz 8x400
New system specs
E6600 / Abit IN9 32X max / 2x1g cellshock pc6400 micron d9 + 2x 1g gskill pc6400 hz micron d9 / 8800GTX
I tried with both ram kit, 2 stick at time and all stick. With the same cpu as the old config i can`t reach 390mhz x 7 sometime i have black screen and sometimes it freeze at boot. With 333mhz of bus 1333mhz in can run it @ 3ghz without any problem. But i want ti break 400mhz fsb. I`m using bios 1.2 beta 3 and ram @ 4-4-4-12-2T.
Any idea?
Tnx
Vampire2k5
p.s. sorry for my english.. i`m studing :P
Damn you Nvidia! What the hell is this now. I just updated to the lates bios and although everything works fine and all start up issues are gone I have got the sound Crackling bug when SLI is enabled.
GRRRRRRRRRRRRRRRRRRRRRRRR. Anyone knows what i need to do? I posted the issue in the General H/W section too.
I tried reinstalling all drivers, clear cmos, lates dx9 but nothing. The same happens with both my Audigy 2ZS Platinum and the onboard sound. If I disable SLI the problem is gone.
Just go into Device mangler and disable, then re-enable your sound. Works for me. Try with and without reboot. One or the other should work.
If that fails to solve it, uninstall the nVidia ethernet driver and just us the MS default one. Some have had this work.
By the way, even after you do get rid of that startup static, it could come back. Just repeat the above steps if it does.
Quote:
Originally Posted by Slammin
Thanks for the advice I tried it and it did not work. It was a much deeper issue as it seems and I solved it by reverting to the old bios. Everything works fine so far as it was working before.
Maybe V12 official release is not for me.
Well,
Add another one to having RAID issues. I am also getting event errors! This will be my last Abit board.
I must be one lucky bastage..... I've been running a DUAL raid0 array, large overclock, SLI, and the whole shabang on this board....... Never even a hint of Raid problems......
My motherboard is on it way back from rma due to the raid issues, windows got corrupt and I could not reinstall XP because my had drives would not show up in raid, they only showed up when I used them as single drives.Quote:
Originally Posted by brdavis
Same here and my sound issue is solved. It is rock stable @ 450FSB , 3.6GHZ E6600, SLI 8800GTX 665/1536/1029 and RAID0 - never had an issue.Quote:
Originally Posted by Lvcoyote
I think I'm finally gonna give up on this board. It's been pretty stable since 1.2B1 bios, but the FSB holes & massive vdroop have always irritated me. I tried a Q6600 in it last night and 400FSB was not possible. Nor was 378. I got 367 to boot but it was not stable. I tested the chip on the DFI P965-S first, and it ran all those FSB's fine. 367FSB was 12 hours prime stable. I need sli & quad core and this board doesn't seem right for it. I did try the latest offical bios which made the system unstable and would restart properly even @ stock.
Your situation is exactly why I didn't get a Q6600 instead. I was afraid, not knowing much about what mobos did best with QUAD at the time, and not wanting to wound up with a 3.6 capable CPU that was limited by the mobo.
As it turns out, my chip will do 3.6 fine, but my PWM's hit shutdown temp! Obviously, I could just add water, but I'm not really hurting over it since I usually do run 3.6 with EIST enabled. Have not had any PWM related shutdowns running everyday stuff, and it's only when I do 4 instances of P95 w/small FFT's does the PWM immediately shoot up to 120+c and the machine goes dead.
As far as I can tell, the higher I can get FSB, the higher my ram bandwidth goes for any given timing. Not sure what the real-world affect of not being able to get a high fsb OC is with these quads, but I've read that quads do benefit from high ram bandwidth. I'm sure there is a point where more memory bandwidth does not really add performance for the CPU, but I'd sure like to know for sure where that point is.
What kind of burst speeds are you guys getting on RAID? Best I have got is 128.6 MB/s
My motherboard is back with a different problem : mad: for the last seven hours i been trying and get the mobo to save the settings to the bios with no luck. Here we go
1 Received my new mobo today from scan.co.uk after RMA because of my raid issues on my old board.
2. booted the motherboard got cmos checksum error and cmos battery error override enabled-defaults loaded Warning! cpu has been change to enter boot menu F1 to continue, del to enter setup. So i update the bios to the latest bios from the abit site, using the floppy and dos mode
4. Update went ok
3. restarted the pc and i got the same error again (cmos checksum error bla bla bla
4. Went into the bios set everything up to run stock F10 saved
5. On restarting i got the same error cmos checksum error and cmos battery error override enabled-defaults loaded Warning! cpu has been change to enter boot menu F1 to contiune, del to enter setup :mad:
6. Time for a new battery and yes after restarting yes i got the same error
7. Cleared the bios for 1 hour still the same error
8. More investigating then I noticed that the codes on the motherboard were not moving they just stay on 00 and CC, I looked in the manual and I can not find the codes :mad:
9. Pressing F1 and trying to boot to CDROM did not work (should have known that by now that nothing gets saved to the bios) :mad:
10. luckily the cdrom was the 3rd device in the boot order so I continued to set up windows with no problems oh just when windows restarted same error so I pressed F1 to continue windows loaded I installed all the drivers restarted same error, but now it loads into windows,
11. All my hardware works fine PSU.Memory,CPU
Any suggestions or should I just walk away from this motherboard.
Thanks for listening :)
Sorry for any spelling mistakes been along day and its 1:30am Nite all
If you are getting a CC code your CCMOS jumper is set wrong. Move the jumer on the motherboard.
Thanks i realized that soon as i posted but even with jumpers in he right place i get the CC error then staright to 00 error and the codes do not move even when i power on or restart, i manage to save some settings to the cmos but they show up wrong in windows, and when i restart the pc it does nothing just a black screen and after i restart my pc my settings get reset :(Quote:
Originally Posted by brdavis
any other ideas thanks
wrong speeds in windows pic here
Hate to ask simple questions....
You did check and make sure the switch (CCMOS) in the back is set correctly? Also, If you are talking speed as in the CPU it looks about right.
To all that have posted here with Raid errors. Searching the net tells me there is a pattern here with the 680 chipset...
The story continues...
Yes all the cmos switches are correct and the cpu is showing the wrong speeds in cpu-z and in windows, I set the fsb 400x9= 3.6Ghz and the memory on 1000Mhz in the bios
In the bios it shows the correct speeds but windows and cpu-z say different and my settings get reset every time I restart and I’m still getting error codes (error code CC then 00) but it still boots into windows with default settings.
Might be a long nite :(
Thanks brdavis
Yes i turned EIST Function and c1e to disable in the bios.
@day187
Your motherboard apparently has the official 1.2 bios. When I flashed to that bios this weekend, my E6600 & Q6600 did the exact same thing. No matter what I tried, the pc wouldn't restart, I had to turn it off, and when it rebooted, 350 FSB X whatever multiplier. It all cleared up after I flashed back to 1.2B1 or 1.2B3. I'm staying with 1.2B1, its been the most stable for me. Uguru still doesn't work for me but my system is rock solid @3.7GHZ. Hopefully a bios will come out soon that will remove my FSB holes & allow me to overclock my Quad. Anyway flash your bios to something else & that problem will go away.
Yep, but it's not just raid but an issue of disk errors with memory set not much more over 800 mhz. I got errors raid or not but they stopped when I slackened the memory down to 800 mhz or so. I just tighten up the timings a little to make some performance up.Quote:
Originally Posted by brdavis
Well now the motherboard will not recognize my A drive, I used Flashmenu to flash back to 1.2B3,
1. Codes on the motherboard change during boot up but time I get to windows logo with the scroll bar the code is back CC followed by 00 then into windows.
2. I still get the cmos error 9/10 :mad:
3. Nothing will get save to bios and when it does after a restart it just resets its self back to default, date, time every settings
thanks all
1.2B3 didn't work for me as I mentioned before. Please try the 1.2B1 and see if you have any better luck. Power off & clear cmos after flash.
ok cheers
still no luck but i'm not getting the cmos errors no more, just the error codes CC and then 00 and nothing will save to the bios :(Quote:
Originally Posted by The Nemesis
Thanks The Nemesis
:-)
Day187, did you replace the battery? I see you said something about it but did you do it?
Yes I replaced the battery with 2 brand new batteries, bottom line is that the motherboard is F**KED and it has gone back to scan on a second RMA 3rd time lucky. "Scan said they are going to get one of their super engineers on it like they did last time" :ROTF: :rofl:Quote:
Originally Posted by maxwedge
Thanks all for your input Keep it XS :D
So about my language don’t like swear but this as took the PI** sending a motherboard that’s worst than the one I just RMA ed thanks scan
Gone pub British style "hello Stella :toast2:"
FYI
Found that disabling command queuing in the RAID properties cleared up my RAID errors!!!
Day187,
found something today. I replaced my CPU fan which required pulling the motherboard. After reinstalling everything I was getting some of the same problems you described with CC on the CMOS code. PC would boot and would allow me to go into the bios but would not save the changes. Then several attempts would not boot at all. I discovered that the CMOS switch in the back of the motherboard was in the correct position but you could just touch it and you would get the CC code. It was like a short. I was able to get the switch to set correctly but I had to do it while the power was on and watch the code. After that I had no problems.
Quote:
Originally Posted by brdavis
That’s interesting, did you get the 00 code as well as mine went from CC to 00 then into windows with default settings even though I change them in the bios.
Should have my new replacement by weekend let’s hope this one is better.
Thanks brdavis
Yes.
The codes would go back and forth between 00 and CC. When I saw that I remembered your comments. My computer had been working fine (except for raid) until I had removed the board. The switch seemed to be very sensitive. Even though I had in the correct position I could just touch it and the motherboard would go into a spin. I moved the switch back and forth until it stopped giving me the CC code. Again, I did this while watching the code screen and power on and after that my system seems stable.
My raid problems seem to have stopped after removing some of the cpu settings in the bios and removing command queuing in system properties.
One more thing.
What I noticed also was that I was able to boot (at times) into windows and the computer would reboot and if I tried to make any bios changes it would not save. That sounded like the CCMOS switch was tripping and causing the bios to clear each time. I would guess you were having the same problem. When you get the new board watch the switch!!!
Well, my third board is more than likely about to head back to Abit. This board has never been completely right the way my first board was. From day 1, it had times when it wouldn't boot, even from a cleared cmos, and never has had the ability to overclock. I have tried every bios released, and some just won't boot into windows with anything but failsafe defaults, while others will boot in, but have none of my bios setting saved. Each bios flash has been accompanied with the same "CMOS checksum error" that others are getting (all flashes done with floppies in dos followed by thorough cmos clearing with all power removed). The computer runs great with stock settings, but it makes me a little more than angry that I can't change anything(not even voltages at stock speeds) in the bios without having it fail loading windows. So, I will be looking at other boards when upgrading next time. Hopefully Abit can make this right because so far my experience has been lackluster to say the least, mostly because of the lack of reliable support for the product. I wish everyone else the best of luck and I will update if they decide to make up for this.
I've invested in a quad core which idles @ 50'C+ @ stock, & near 70'C @ 3.2Ghz. Anything over 356FSB will not boot. PWM's are too hot to touch with quad core installed. Cool with 6600 or 6400 installed. I'm dumping this board. Its suppose to be my best gaming, 3Dmark, benching system. Pretty useless for me If I can't clock a quad core. I'll get handed my hat in any competiton without quad core clocking. Guess I'll pick up and Evga A1.
These boards have a mind of their own, then die, My other Abit Fatal1ty F-I90HD board is rock but this Abit 680i does suck.
I'm Waiting for my new RMA Motherboard back from scan they sent it to the wrong address (dont you just love scan), Will update when i get it back any year soon.
Goodluck to Abit 680i Users
Mine is already at the house, waiting for the quad price drop and I will be right where you are.Quote:
Originally Posted by The Nemesis
Something I found out after playing around with this board. All of my start up problems were solved and during the last month I have not a single issue with this board Running 450FSB (8x4500 E6600). What was causing many issues was the 24Pin ATX plug making bad contact with the motherboard connector. IT IS NOT the fault of the PSU the M/B connector seems to be not that good so what I did was to pull it about 2-3mm higher and it makes much better contact. So try it and see how it works for you.
hi first post and everything
got this board with an e6750 cpu and crucial ballistic 5300 ram (667)
what i need to know is the following
ive put the latest bios on and im having problems with the bios saving settings after i go back into windows it saves them saying upgrade success on bios boot up b4 windows kicks in,when i get into windows itself the settings are either back at stock or set at 2800 for some reason.
uguru wont work at all all it says is overclocking failed on anything and everything i try to do init.i have deleted it and put it back on numerous times same thing is happening.
ive basically read this thred all the way through tried more or less everything still the same no different.
what do i need to disable in bios to stop this going back to default all the time ?
how do i get this uguru working ?
any hep would be most appreciated as this board is seriously damging my health :)
or a lump hammer will damge it one way or another
thanks in advance
lee:up:
set up is this:
2 x 1 gig sticks crucial ballistic
e6750 cpu
motherboard u know
bios latest
cooler:scythe ninja plus
any help much appreciated
@psylee
Do you have uGuru front panel? It did the same to me until I removed it.
front panel ?
i downloaded the newest version from abit site 1.4 i think it is
no i dont have front panel sorry just realised what you meant
no i have the normal one in windows which i downloaded from abit themselves after trying to use the one from disk which did the same aswell
i can live without uguru if i can get my bios to keep the settings i put in.
it just wont save any settings i put in it
Dear all!!!
in the abit forum i found a new 1.3 beta 2 bios.. does no one try it?
Vamp
Psy did you set bios settings in the Bios itself or via Uguru software ? plz do so straight into bios...
Kisses and huggs Jr :up:
hi jr
i do save in bios m8 as uguru wont work for me
all it says all the time is overclock failed no matter what i do so i give up with that.
sometimes it changes in bios and stays what i put into it.
other times it then changes it and sets it at 2.8 for some reason.
ive never known a board so like a women in my life than this :rofl:
ive got it stable @3.6 but i know this will go further just cant get it to do it:shrug:
Maybe a new bios will solve that, anyother member having these issues with a 1333FSB CPU ? do you still have your old 6400 ?
Syptom: similar to what day187 was experiencing. Last night I walked by the machine about 15 minutes after I had turned it on and left the room. I noticed the fans were spooled up and running at max RPM. Sounded like a plane flying through the room. I did some digging: uGuru will NOT run anymore. It is completely dead. Likewise, all bios changes would not save. I checked the CMOS jumper and the EZ switch in the back panel, and both are in the correct spots.Quote:
Originally Posted by day187
The machine will boot normally, I just cannot change any of my settings. The power off code prompt is reading "CC", showing a jumper error. As soon as I boot, it goes through its normal boot process showing all the normal boot codes. As soon as windows starts up it swaps between "00" and "CC" and then settles on "CC" once the machine is completely on and windows is running.
I am still trying to puzzle this out, I will keep you guys informed.
OK, I got the damn system to boot normally.
Solution: I just jiggled the damn EZ switch on the back several times, then booted. No change. Powered the system down again and tried one more time. This time the machine turned itself on when I reset the EZ switch, and came up normally with no error codes, and now it does save my settings changes in the bios.
Problem solved?
Next problem: I am quite an idiot when it comes to clocking anything, as I have not really done a whole lot of OCing in my day. However, I KNOW my ram (see my sig) will handle 4-4-4-12 2T timings, but whenever I set it in the bios the machine just hangs up on a black screen when it gets to the point when windows begins to load. Any help on the settings would be great, thanks!
Hi SkripsQuote:
Originally Posted by Skrips
I never got my motherboard sorted i RMA it back to scan and sold it when i got it back due to it been my third motherboard and then raid issues started.
Today i've just brought an Asus blitz formula SE which i'm going to set up tomorrow, which i hope to have better luck with.
Glad you got it sorted. Skrips
Quote:
Originally Posted by day187
Thanks, I am going to need it. Then again, I knew this was going to be a bear of a task. Its a glitchy platform, I am running vista, 64 bit no less, and it was bound to have issues.
Oh, and as an FYI, I got the ram working. 4-4-4-12 2t @2.1v. I had forgotten to up the ram voltage when I changed the timings :D
On a side note, whic program does everyone use to torture test their ram for stability? I forgot the name and where to get it...
Super PI! That is what it was called. What about that?Quote:
Originally Posted by day187
"MemTest is a RAM reliability tester that runs under Windows. It evaluates the ability of your computer's memory to store and retrieve data accurately. A correctly functioning computer should be able to do both these tasks with 100% accuracy day in and day out. A computer that fails these tests, perhaps because of old hardware, damaged hardware, or poorly configured hardware, will be less stable and crash more often. Even worse, it will become even less stable over time as corrupted data is written to your hard disk"
Superpi can be downloaded here
thought the memtest we all prefer was always under dos not under winblows, correct me if I'm wrong here...is the windows memtest the same as our famous one ?
Even though on some settings I can run eg Orthos/superpi for hours, though Quake4 crashed within minutes, ... best stability benchmark is a mix of all and surely just testing in day to day use...