Serial ATA AHCI BIOS, Version iSrc 1.20E
Copyright (c) 2003-2008 Intel Corporation 23
** This version supports only Hard Disk and CDROM drives **
Please wait. This will take few seconds.
If your Gigabyte BIOS hangs at this message after you change to AHCI mode, then this solution worked for me
1) take a system backup (including system image) of your boot O.S. with windows backup
2) create a system repair disk (DVD) with windows backup
3) reformat (quick) then delete the partitions on your boot drive (not sure if this is necessary)
4) boot to the repair dvd, follow instructions to restore latest system image
5) reboot, change BIOS settings to AHCI, reboot and all should be just fine.
For some reason the 1.20E AHCI BIOS just does not like to go past a disk that has a win 7 x64 IDE operating system on it, and restoring the image to the same drive seems to fix the problem.
Last edited by DrPhill; 02-10-2010 at 03:28 AM.
It is likely if we knew what the AHCI BIOS was checking on the hard drive, a simple hard disk utility could fix it immediately (see bottom of post) but we don't so....BTW it will post drives and only hang when it gets to the device it has problems with.
Suggestions only here. I see you are running RAID so my solution may not really applicable if the problem is on one of the drives in the raid array and you have data you need to recover from a broken raid that won't boot RAID because of this code 23 BIOS problem.
If you are making a RAID array from scratch and get this problem I would suggest under IDE mode first (quick) formatting each drive as simple NTFS and then deleting the partition under disk manager in control panel->administrative tools->computer management. Don;t do this if you have any data on the drive(s) you want back.
If the problem drive is on a standalone drive you are booting from then my solution should work so read on:
I now use windows 7 exclusively and I ain't going back....ever, so I do not know if this works for XP/Vista.
I use the Windows 7 Backup/Restore available in the control panel and back up the system image while in IDE mode (the only one that will boot!). Don't forget to make a system repair disk from this backup utility as well since the win 7 installation disk complained to me about not wanting to restore the system backup image I made. Don't be tempted to try to move the backup image somewhere else before restoring it. It WONT work.
Of course you need a spare drive to take the image, and I would recommend keeping your IDE boot disk until you can prove the image restore works to another drive (it is amazing how many ways restore will find a reason to spit the dummy making a restore impossible in spite of having a valid backup system image). If you have data on your raid disks be careful when you restore the image as it WILL reformat all disks not containing the backup image by DEFAULT (you get an option to exclude). I would not recommend reconnecting data disks except the disk you have the backup image on until you have an image restored and booting in AHCI mode.
I suspect what is happening is that a status byte(s) on each hard drive is being checked by the AHCI BIOS is checking on POST; and if it is not happy with the status it hangs on code 23. it does not seem to matter if the drive is intended to boot from or not, but if Win 7 is initially installed in IDE mode it is definitely a recipe to hang when BIOS->AHCI. Just why the AHCI BIOS should care about the contents of the drive is beyond me as it is up to the O.S. to make sure the right drivers are present. Anyway until we know what the BIOS is checking we won't know what the EASY fix is.
Thanks again Jeltz, Well, I’m not sure if I’m following you, I’m kind new in this stuff so, I’ll try to be as more specific as I can about my problem.
1) The raid 0 (striping) was successfully assembled because I have formed one volume from two HDs and I was able to install the windows seven on it. I had one HD already and bought another one identical to do the striping. I didn’t format any of them prior RAID configuration assuming that it would be automatically done.
2) During windows seven 64bits installation I tried to load the latest driver for the ICH9R SATA RAID controller from a pen drive (since I don’t have any floppy drives) and I didn’t succeed because according to windows the driver wasn’t signed. After a few tries I manage to install the Operational system without the driver (maybe gigabyte bios or win seven already had that driver, I don’t know for sure.
3) During system startup the “Serial ATA AHCI BIOS version iSrc 1.07 08042006” screen started to be shown every time just after gigabyte award bios. After scanning the bios shows everything that is connected to the sata ports and then it says “AHCI BIOS not installed” but after that it shows in green a notification stating that the Raid 0 (stripe) state is “Normal” and shows in green the discs that are assembled on raid array (I’ve already posted a picture of this) and windows starts normally. The hang on “Serial ATA BIOS” 23 is only for a few seconds.
4) After windows 7 64 bits installation and after installing all possible actualizations and drivers including “Intel Matrix Storage Manager”, the performance of the RAID 0 disk didn’t improved as expected. the windows experience index didn’t changed at all and the benchmarks a did seems to show that the performance is not as good as it should be.
I don’t know for sure if the fact that I didn’t load the driver during windows installation, as recommended, is causing this problem and if that’s the case how can I pass through that driver loading screen using a pen drive.
I did the system image and the recovery disk, but on the native mode and not on the IDE it can cause problems on system recovery after formatting?
Anyway, I guess if I try formatting the drivers on RAID array I would be unable to load the driver again.
Last edited by DrPhill; 02-10-2010 at 06:38 PM.
I've being reading some forums and the more I read more I believe that the problem here is the hard disc itself. The painful truth is that Western Digital Caviar Green Sucks! If you want a fast HDD don’t buy this one.
I definitely don't think it is the drive Dr Phill. I have created and fixed this problem on a number of hard disks now, including Hitachi and an old Maxtor.
I am satisfied it is the BIOS hanging on the contents of the hard disk...which IMHO it should never do.
Greetings , Jeltz,
So, during the system startup, we shouldn’t be seeing the “Serial ATA AHCI BIOS” screen at all? It indicates that something is not as it should be? Because if that’s the case I’m definitely going to reformat and try again to install that driver again (don’t know how to pass that “driver not signed” part yet)
I was almost convinced that the installation was not the problem because except for the bios part (and of course the poor performance) everything was normal.
What you suggest?
A few questions about the ga-x58a-ud3r,
I'm a little unsure about how the PCIe slots work with this board. If both the new
sata3.0 6gbs and usb 3.0 are turned on, will the two x16 slots both work at the full 16 for for a two card crossfire/sli? If a three card cf/sli is used, will it be x16 x16 x8 with the new sata and usb turned on?
Also, will you be able to boot from an ssd using the sata 3.0 6gb? I heard that this does not work at present but a bios
updatemay enable this in the future? Anyone have any info on this?
Lastly, the approved memory list at Gigabyte does not list any 1600 or 1333 memory. I assume that most DDR3 1600 and 1333 will work, but I hate to buy the odd brand/model that doesn't. Can anyone confirm any specific ram that they are running successfully with this board?
Thanks. This seems like a great board but I'd like to get the above questions answered before I buy.
No, when the BIOS is set to AHCI rather than IDE mode, you should always see the SATA AHCI BIOS screen, but it should not hang while detecting devices. It should detect all the SATA devices you have plugged in, list them on screen and then continue to the boot device. This thread is about the hang in this BIOS on code 23 (23 towards upper right of screen).
If the BIOS does not hang, then if the boot device does not have an O.S it will then sit there waiting forever for an O.S. If the boot device does have an O.S., in Windows 7 at least it will boot with the correct driver (AHCI or IDE ) even if you have changed BIOS setting to/from IDE. Previous operating systems you may get the BSOD if O.S. lacks an AHCI driver. This BSOD can generally be fixed by changing a couple of O.S. registry settings in IDE mode before the boot to AHCI.
NOTE: Raid is more difficult all round. It is way too easy to destroy data trying to recreate a broken RAID unless you do EXACTLY the right thing first time. AFAIK RAID piggy backs on top of AHCI mode.
Im having serious issues with my raid-10 setup on the X58A-UD7. I have 4 velocirators in raid-10, but every time my disk 3 is giving an error, I have replaced the drive with a new one, and still the same error, is there some know problem and solution with the raid firmware? It is all attached on ports 0-3 on intel slots
There are currently 39 users browsing this thread. (0 members and 39 guests)