BIOS Flashing not working

Hi First post!

Anyways, I consider myself pretty good with computers overall so im not stupid or anything. I have an Albatron K8SLi motherboard, two 6800gs's in SLI an Athlon 64 3200+ @ 2.4ghz and 2gigs corsair XMS ram.

I went to my mainboards website and saw there was a bunch of bios updates that I could do. Some supporting new E6 Stepping on CPU's, some supporting Dual Core processers, some fixing the broken tempature gauge.
this page can be found here: http://www.albatron.com.tw/english [...] pro_id=190
.
I didnt have a floppy driver so I took, it out of my old computer and hooked it up, made a bootable floppy with the latest BIOS, 1.12. (i was currently at 1.01). (skip ahead) I flash the bios sucessfully and reboot. Before I flashed I also brought back down to stock speed just incase, so. It boots up, I see there are new features in place... it gets time to load windows after POST, and right as you would think the windows loading screen would show up, I blue screen of death. I tried restarting many times, none worked. So I made another bootable disk on a nother computer, with the BIOS update one BEFORE 1.12 (1.08 ) and flashed again. The flash was sucessful and when it got time to load windows it blue screened again. So I flashed back down to 1.01, and windows worked....

I tried again with a couple things, and I found that the only BIOS update that would work and let me load windows without blue screening was 1.07, everything else crashed.
Albatron support is impossible to talk to.
Does anyone know at least WHAT is going on?
and maybe if you know what is going on, how to do anything about it?
Its not TOO important because it works pretty fine now, but, in the future if I get a dual core CPU, (which I Might) I dont want to have to spend another 120$ on a new mobo, I can just flash this current one. Thanks for any responses.
-sackynut

nope, after the blue screen, I restarted (with the little reset button) and it gave me the windows did not start right error and it gave me

Start Windows normally
in safe mode
with command prompt
something about networking

so I chose safe mode, and it blue screened again before loading windows. So I dont think safe mdoe works either.

I have one hard drive, Ill check to make sure its in single drive though. im using SATA II.

disable sata device 2 and try again

I did for the most part. Let me give a quick overview. My lowest (default) ram voltage is 2.7. when i OC, i bring the ram to 166mhz, and because of the added HTT it is back at 200mhz again. according to CPUz. after the bios flash, i checked all the settings and they SEEMED to all be the same. I MAY (and this is a definite maybe) try flashing again and fiddling with the RAM timings, and making sure they are the same, but it was a pain in the ass to go through all that. If I buy a dualcore I will definitly try again, but unless I think I have found a solution I will hold off.

Clear cmos, remove the battery and set the jumper the clear for 45 sec. Reinstall battery and jumper to there original position. Now restart it should startup now.

It's a jumper block, that plug on top of pins sticking up. If you have the manual it should be right next to the battery. Should be 3 pins sticking up with the jumper bridging 2, normally black. May be labeled cmos/clear.

if that doesn't work go into bios where you enable or disable sata port highlight raid above there and hit enter see if there is an option to switch between raid and base(possibly called something different ) set to the option that isn't raid and try to reboot again

the ram could make your system unstable but i don't think it would consistantly keep you from booting especially since everything was ok before the bios upgrade

o yeah! good idea...

a noticable problem? not really.
But my tempature gauge on the mobo was broken, stuck at 66C, so they released a fix for that, along with Dual Core support and E6 stepping support. as well as many other fixes, some I wanted (because I had issues with the thing it was fixing every now and then) and some I didnt. I figured it was worth it. Also, I plan on probably going dual core (I might wait for AM2 though), and I figured, instead of buying a new mobo, I could just flash this one. good thing I learned early

well, I have the motherboard drivers that are the version before the newest ones. I have like 6.61 or 6.66 something like that, whereas the newest is like 7.77 or something. does that mean I should get th 7.77 and try flashing again? would that serisouly work?

wait
okay reply with a list of what you feel for best performance (or at least I should) update driver wise:

1.chipset/motherboard
2. video card
3. sound card
4. any others?

hate to bring this back but...
i unisntalled all drivers and tried to flash again (in hopes it would work and I could reinstall the drivers after) no work. same problem. but this time I saw the windows boot screen for about one milisecond before it BSOD. I noticed my RAM timings had changed, so I put them back to the original timings of the original BIOS, no work.
I have heard (on other forums) of people with similar problems. But I do not understand.
it goes from 1.01 to 1.07 and then 1.07a, 1.08, 1.08b, 1.09, 1.10, 1.11 etc to 1.12.
the only BIOS I can successfully flash to is 1.07. after that it BSOD's, and I notice is starts to BSOD at the BIOS for dual core support. I mainly want this because I want to go dual core and not have to get another mobo. But it doesnt want to co-op with me. I also tried disbaling RAID and all that, I disabled SATA device 2, and left one enabled. didnt work.

ALSO: within the "chipset features" section of my BIOS under the Advanced tab... there is a section for RAM timings and a little thing called "System BIOS Cacheable". System bios cahceable is currently set to [Disabled]. Should I enable this? what does it do?