Overclock.net banner

"BLInitializeLibrary Failed" - An error message shown during POST of Maximus VIII HERO

1 reading
114K views 28 replies 16 participants last post by  peppersmagik  
#1 ·
"BLInitializeLibrary Failed 0xc000009a"

WvEpJJ5h.jpg


I really hope that you guys could help me.

I saw this error message a few days before, and it recurs today unfortunately. So far this error happened when I exit UEFI, including exit without saving or save&exit. The details of what I have done are as follows:

- updating BIOS using ASUS's USB Flashback feature
- clearing CMOS by clicking on-board red CLR_CMOS button once
- entering UEFI to secure erase my SSDs
- selecting to boot from my inserted windows installation USB under boot tab
- THE ERROR HAPPENED

It also happens another time when I intend to boot into OS. So I believe the error would not be caused by either my USB nor OS (windows 8.1 with update). But I can still boot into OS or the USB after I reset my system.

I have done some research about BLInitializeLibrary. I just learnt it initializes boot loaders so the UEFI can search for OS and boot-into it. I saw some people using motherboards from other brands have also experienced this error before. So I wonder if it is a bug of UEFI caused by unknown reasons of bootloader initialization.

I would be grateful if ASUS (maybe Raja) and you guys can give me some idea of how the error can be solved...Thanks
 
#2 ·
Quote:
Originally Posted by SilasAC View Post

"BLInitializeLibrary Failed 0xc000009a"

WvEpJJ5h.jpg


I really hope that you guys could help me.

I saw this error message a few days before, and it recurs today unfortunately. So far this error happened when I exit UEFI, including exit without saving or save&exit. The details of what I have done are as follows:

- updating BIOS using ASUS's USB Flashback feature
- clearing CMOS by clicking on-board red CLR_CMOS button once
- entering UEFI to secure erase my SSDs
- selecting to boot from my inserted windows installation USB under boot tab
- THE ERROR HAPPENED

It also happens another time when I intend to boot into OS. So I believe the error would not be caused by either my USB nor OS (windows 8.1 with update). But I can still boot into OS or the USB after I reset my system.

I have done some research about BLInitializeLibrary. I just learnt it initializes boot loaders so the UEFI can search for OS and boot-into it. I saw some people using motherboards from other brands have also experienced this error before. So I wonder if it is a bug of UEFI caused by unknown reasons of bootloader initialization.

I would be grateful if ASUS (maybe Raja) and you guys can give me some idea of how the error can be solved...Thanks
The error shows that is most probably an OS problem, not BIOS one. BIOS doesn't use any kind of librarires as far i know, and it won't show the error message in this way. Reformat your HDD and reinstall your OS and try again.
 
#3 ·
Quote:
Originally Posted by ku4eto View Post

The error shows that is most probably an OS problem, not BIOS one. BIOS doesn't use any kind of librarires as far i know, and it won't show the error message in this way. Reformat your HDD and reinstall your OS and try again.
I dont think it is the problem of OS. The error also happens when I have already secure erased all my harddrives (SSDs) then boot into Windows installation USB...
 
#5 ·
I had this issue before. I don't remember how I fixed it. I think I had disabled fast startup or set the fast startup to fast. This was on a gigabyte board, weird how the exact same error you're having I had it before. You could also try enabling CSM (Compatibility Support Module) if you haven't already and see if that helps.
 
#6 ·
Quote:
Originally Posted by benjamen50 View Post

I had this issue before. I don't remember how I fixed it. I think I had disabled fast startup or set the fast startup to fast. This was on a gigabyte board, weird how the exact same error you're having I had it before. You could also try enabling CSM (Compatibility Support Module) if you haven't already and see if that helps.
Both Fast Boot and CSM is enabled by default in ASUS ROG board
 
#7 ·
Silas,
I have the exact same problem on GA-Z97X-UD5H BK Gigabyte board. I'm fine when save and exit but exit without saving ends up at BLInitializeLibrary failed 0xc000009a. Updated, downdated, cleared, restored bios, with or without CMS, all permutations but no win.
Any comments or solutions since then?
 
#8 ·
Quote:
Originally Posted by kagan View Post

Silas,
I have the exact same problem on GA-Z97X-UD5H BK Gigabyte board. I'm fine when save and exit but exit without saving ends up at BLInitializeLibrary failed 0xc000009a. Updated, downdated, cleared, restored bios, with or without CMS, all permutations but no win.
Any comments or solutions since then?
I have the same Gigabyte motherboard and also the same error by leaving the Bios without saving.
I think its caused by the EFI Bootmanager ( inclusisive Winload.efi )
Has anyone a solution?
 
#10 ·
Quote:
Originally Posted by TheXes View Post

Have you found what the issue was with BLInitializeLibrary Failed ?
I have the same board and same issue now :S
Have this exact same issue when I exit from bios without saving changes on my motherboard too. Gigabyte GA-Z97X-UD5H-BK.
 
#12 ·
Quote:
Originally Posted by super1 View Post

I get the same error when I exit without saving
I have Z97X-UD5H (rev. 1.1) Bios F10
I don't remember if I had this error with Bios F8 or F9
For the motherboards that have this issue, there appears to be no solution as of now even with newest BIOSes currently.
 
#14 ·
Quote:
Originally Posted by super1 View Post

So you tried with Bios F11a ?
I was thinking to flash it

thanks
F8a is the latest I can get on the GIGABYTE GA-Z97X-UD5H-BK
 
#21 ·
Still happens after Z97? Oh well.. I thought they would fix an issue like this because it does get pretty annoying when I want to use UEFI and exit without saving.
 
#23 ·
Quote:
Originally Posted by Oubadah View Post

I had this on my Gigabyte z97 boards after exiting without saving. I opened a support case with Gigabyte in an attempt to report the bug. For a little while it seemed like the rep was engaged and actually treating the case as a bug report, but then they suddenly reverted to the generic "reset the BIOS" and "return it to the supplier for testing" idiot responses. At that point I realized I was wasting my time and gave up.

Band-aid solution (for Gigabyte boards at least): Always Save and Exit, even if you didn't change anything. That will avoid the error.

Gigabyte never fixed the weird system reserved memory bug either, where different amounts of memory would be reserved after BIOS resets even if the BIOS was configured 100% identically.
TY for that. Could you recommend or advise how I would go about finding a reputable MB maker who would offer better support or not make that mistake in the first place?
thumb.gif
 
#24 ·
Quote:
Originally Posted by Lestat Craven View Post

TY for that. Could you recommend or advise how I would go about finding a reputable MB maker who would offer better support or not make that mistake in the first place?
thumb.gif
ASRock replied me on the next day regarding issues with the 990FX Killer compability with ATA HDD's. Fast enough, but the english wasn't really good.