That's what I've been doing all this while. No phone line at home. Everything offline.



16th Sept.
Flashed to 17 last night. A little bit worried when flashing. Dare not let it run the whole night, yet. Will see if it's okay after this. Then only will start to oc. This weekend just want to pay up the 3 weeks of no games.

This post has been edited by Fries: Sep 16 2005, 12:16 PM

Abit is good bro, Me gettin AN8-Sli fatality, OC wise stable because of UGuru

Saturday, Sept 17.

It happened again!!! ARRGH!!! Ran it overnight. Then this morning played some games. Right after closing the last game, it rebooted itself. Went into BIOS, both my OTES fan settings are gone. Only AUX left. Now the only way to control the OTES fan is through ABIT OC software.

Anyone else facing this problem? Is bios 17 really stable? Because I don't have this problem while using bios 16.

Somebody HELP!!!

I had this problem no matter bios stock,15, or even 16...that is the problem i've been trying to tell ya all about....

u need to reset cmos after flash brother...
if the otes cannot be detected...
i think there might be problem with your casing and mobo...
try remove the mobo outside the casing with no harddisk , no cd-rom and other external devices....
boot and see if it is there... and plug in by one device see everything is ok...
after that... if you sit the mobo inside the casing and having problem again...
it would be the casing is bend adi....
you need to troubleshoot it....

when my OTES menu missing my board was on a box and below the box were a sound dampening piece (insuflex)...

I know you're having this problem before, but does it restart by itself? Last time, when it happened, no matter what version you flash after that, the problem won't go away. It only happen after I flashed to version 17. Afraid have to RMA again. Because last time, it restarted while flashing. And it took me 3 weeks!!

That's not the case. What do you think, if the board is inside the casing, and you can't see it, then you describe that undetected? Even if it is set up in the open space also, it still can't be detected!

yerp...restarting itself the need to press the nuke symbol to reset cmos...and sumtimes reset cmos oso doesnt help in restarting back the computer....i have to take out the battery...wait an hour or so....then only put back the battery...and wallaaa...it boots with default value....

Yup. And the problem is still there. It won't go away.

try flash back to bios 15 and reset ur bios.. itz never happend to me either An8 or An8 ultra

It happened to me and antonio_zth.

Now I'm afraid of flashing it anymore. Last time I did that, it restarted by itself during flashing. Hate to send it for RMA.

I think it should be a bug...
Please blackbox abit about it...
sure new bios can fix that problem...

Sent a report to Abit's technical support just now. Just wondering if anyone else having the same problem.

you may try at http://forum.abit-usa.com
asking any other SLI user whether this problem occur too...

is this board good & stable for amd x2 processor?

irenic i can see a lot of user use san diego with all AN8 XXX version... in the abit forum

It have no problem at all to run the X2 CPU...

This post has been edited by cyberloner: Sep 18 2005, 01:01 AM

So ou're getting the same board as mine. Though mine is not the fatal1ty, but they are almost identtical anyway

I'm using bios 17 and it is running fine. Hand when I try to OC it using software though...

Make sure you update the bios to the one that supports X2 though. If you do it after windows reinstallation, using the uGuru utility to update the bios, you'll need to reinstall windows again.

I leaned that the HARD way

This post has been edited by wild_card_my: Sep 18 2005, 08:24 AM

Lazy to find out exactly which version, but ver 17 so far has been very stable. No reboots nor shutdowns after flashing to it.

I flashed it in windows. However, I downloaded the bin file to the hard drive first and then use the utility to flash from file.

1. Immediately after flashing rebooted the system and then set the bios to default.
2. Rebooted it.
3. Go into bios again, set the ram timings and other settings correctly to reflect the overclock.
4. Then boot into windows.

Using these 4 steps, it helps eliminate the issue where you have your RAM timings wrongly. Usually, if a machine reboots by itself, that means your RAM tak tahan already.

So far, using bios 17, I've managed to have stability, have support for X2 (If you use the default Abit boot screen, it will show you the X2, FX and 64 logos) and the dreaded temperature issue is resolved.

Just my sharing to help get you guys solve this issue. BIOS 17 is great!!