How to get rid of self-botched BIBM?

User discussion and information resource forum for BootIt Bare Metal and BootIt UEFI

How to get rid of self-botched BIBM?

Postby Ambertus » Thu Oct 10, 2019 1:34 am

For two years, I've been trying to get BIBM to work with my Windows 10 Pro 1809 and 1903 builds, but it never NEVER WORKS! It screws up everything in its path, causing things like Win 10 failing to boot because of "inaccessible boot device", "critical process crash", and a few other nasties. What's worse, restoring my WORKING, cloned backup copy of the partition now suddenly shows the same symptoms!

I've given up on BIBM. It was never properly designed for all of Windows 10's maldesigns and farcical "features". I know many others have gotten it to work, but they must not have a situation anything like mine (or something).

And now it's just plain murdalizing me! I installed v1.59, booted, and BAM: a horrific crash in the pseudo-DOS portion of the boot. So I copied back my good backup clone, but THE EXACT SAME THING IS HAPPENING!

I deleted the BIBM partition and rebooted, but THE EXACT SAME THING IS HAPPENING!

How, dear Bob, HOW do I get rid of this cursed abomination? :twisted:
Posts: 55
Joined: Wed Feb 13, 2013 11:06 pm

Re: How to get rid of self-botched BIBM?

Postby TeraByte Support » Thu Oct 10, 2019 9:25 am

It works perfectly with all Windows versions, including All Win10
versions, when using standard basic disks and BIOS/MBR/EMBR (for UEFI,
you'd use BootIt UEFI). Once you choose what to boot via BIBM, it's out
of memory completely and doesn't interfere with any OS boot process. If
your really got any of those messages, it wasn't caused by BootIt. The
only thing that could happen is you don't setup a boot item to include a
partition needed in the correct order. But actually, that was old
windows versions that used boot.ini, which hasn't been used since Vista.
Obviously if not limiting primaries you could also hide partitions
needed, but that wouldn't result in any of the messages you claim. The
Inaccessible boot device shows up after the kernel has started loading
and windows can't find itself when it goes to load the protected mode
disk drivers (missing storage driver, limited memory, bad file system
are common reason). Where we talked about it in tutorials and such,
that had to do with older XP and multiple hard drives booting from
alternate hard drives where you need to use the swap option. Also of
course, your BIOS must work properly, in the old days, you had some
limitation likes 8G and 128G.

In general, messages on the black screen come from bcd/bootmgr and the
BSOD's come when loading kernel.

If you want to uninstall it, you simply choose uninstall which is
covered in the manual as well as the kb (search uninstall). If it was
installed and you deleted the BIBM partition, you'd get a message that
the EMBRM couldn't be found, it wouldn't attempt to boot an OS unless it
wasn't active, which means it was never part of the boot anyway.

I should point out that if you're really getting those types of messages, your system
may be having hardware issues. Memory is a common cause, sometimes the CPU
caches (L2/L3) a problem, or cables/interference, etc.. I'd start with memory,
cpu, then power supply, cables and drives, then mobo.

One last thing, sometimes virus are broken when BIBM is installed and they
cause problems booting Windows. So it's also possible you have an unknown
virus. Most of the time with that, your first boot after installation is good,
then problems start.

On 10/10/2019 12:34 AM, Ambertus wrote:
> I deleted the BIBM partition and rebooted, but THE EXACT SAME THING IS HAPPENING!
> How, dear Bob, HOW do I get rid of this cursed abomination? :twisted:
TeraByte Support
Posts: 2965
Joined: Thu May 05, 2011 3:37 pm

Return to BootIt Collection