BLinitializedlibrary Failed 0xc00000bb Error In Windows 10
Some users encountered the BlInitializeLibrary failed 0xc00000bb error when they were trying to boot their Windows 10. If you are one of them, you are at the right place. This article developed by MiniTool Partition Wizard puts together some possible solutions to the issue, and you can try them one by one until you fix it.
BLinitializedlibrary failed 0xc00000bb error in Windows 10
A number of users have reported that they see the error message BlInitializeLibrary failed 0xc00000bb when they are trying to boot their devices, especially Surface and Windows laptops. This error prevents users from booting up the computer normally, and the device may still get stuck on the initial screen with the error code even after a restart.
The unexpected BlInitializeLibrary failed 0xc00000bb issue is not specific to a certain Windows version, and it may happen to Windows 7/8.1/10 with different PC configurations. There are also multiple factors that might be responsible for this problem, and some of them are listed below:
After learning about the BlInitializeLibrary failed 0xc00000bb error, you might be eager to resolve the problem as soon as possible. But you are strongly recommended to recover your data first. As the error code 0xc00000bb prevents your computer from booting up, you are unable to access your saved data, and you might experience data loss due to this issue.
If you are using 2 or more powerful GPUs on your computer, you are likely to encounter the BlInitializeLibrary Failed 0xc00000bb error when the 4G Decoding (or Above 4G Decoding) is disabled in BIOS or UEFI. On EVGA motherboards, this feature is called EVGA Support instead of 4G Decoding.
It has been proven that the BlInitializeLibrary Failed 0xc00000bb error could come up if the BIOS forgets which SSD/HDD is the primary bootable drive. This is because the computer will clear the Page File that may contain the current boot sequence information at every shutdown.
After refreshing your Windows components by a repair install, you should be able to boot up your computer properly. If the BlInitializeLibrary Failed 0xc00000bb error appears again, it indicates that this problem has nothing to do with Windows installation, and you might need to focus on your HDD or SSD drive.
If all the above methods fail to fix the BlInitializeLibrary Failed 0xc00000bb error for you, and your computer keeps stuck on the initial screen with the error even if you are using a new hard drive, you should contact the manufacturer of your computer for further assistance. This is always a good solution whenever you come across tricky problems with your device.
Some replies on the Microsoft forums (e.g., -us/windows/forum/windows_10-performance/bi-initializelibrary-failed...) provide solutions via the _Startup Repair_ screen, but I do not have that option as my machine boots directly to a black screen with the error code.
At the pre-boot stage, Windows Boot Manager sets the maximum number of global memory descriptor for a 64-bit UEFI system at 512. If the boot firmware creates a large amount of memory fragmentation, the memory descriptor count may exceed the set limit. This causes the "BlInitializeLibrary failed XXX" error.
I am trying to reinstall Windows 10 on a GPT partition SSD from a GPT partition FAT32 USB stick. When I'm trying to boot from the stick I get blinitializelibrary failed 0xc00000bb. What I found on google didn't help. This happened to me before about 2 years ago and I have managed to fix the problem, but I completely forgot how I did it.
I have a MacBook 2015 running macOS High Sierra 10.13.4,I installed Windows 10 using Boot Camp. After that I created two partitions swap,root to do installed Linux Mint. Finally I installed rEFInd to manage the three OS's, but where reboot I can't access Windows. It's show message error "rEFInd - Booting OS Starting bootmgfw.efi Using load option '' BlInitializeLibrary failed 0xc00000bb ", How to fix it?
The steps below will make the error 0xc00000bb effectively disappear and, for @luctp, seemed to be enough to fix the triple boot. However, in my case, more work had to be done as I explain at the end of the answer.