I am having the same issue as OP.
When I cold boot or restart, I get stuck on loading Windows with the Q-Code of B1 for anywhere between 2-4 minutes before reaching my desktop. Once Windows has loaded, my PC works perfectly fine/normal.
My system is a few years old with the same CPU & RAM since day 1 and the GPU was upgraded over a year ago. I did recently install an SSD into a PCI-E slot to use as a boot drive (Win10) and it was working fine for about a month (there is no validity to xoutostrela's answer since I have more than 50% free space on it). Then I added a second monitor and this is when the slow boot started. This is the part that has stumped me since adding a second monitor should not cause this and it doesn't go away when I remove the second monitor from the mix.
There is not much information online about the B1 Q-Code but what I was able to find states that it is related to RAM or the memory controller. So I tried removing all RAM sticks and testing one by one in each slot but I still get the same behavior. It would be nice if a solution can be found for this issue.
CPU - i7 4790k @ 4.4GHz & 1.21v
MB - Asus Maximus VII Hero
RAM - 4x 4GB G-Skill Trident 2400MHz (set of 4 in a single package)
GPU - MSI RX480 8GB @ stock
PSU - Corsair AX860i
SSD1 - Samsung 120GB PCI-Ex4 NVME installed in an adapter in the last GPU slot (x4) (OS install with some apps)
SSD2 - Intel 500GB (games and other apps installed)
HDD1 - WD Black 500GB (used for linking Downloads, Documents, Pictures, Videos, Desktop, TEMP and other cache folders off of the OS drive to save space and writes)
HDD2-5 - Additional storage and redundancy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Well, I just did the platform update for Windows 10 (from 1709 to 1803) and the issue seems to have disappeared now...
Strange that something that seems like a hardware issue would be caused by Microsoft software... or is it?!?!?!
dun-dun-duhhhhhhhhhhhhhhhhhhhhhh!
So OP, try updating your Windows 10 to the new platform update and see if your issue disappears. It would be nice to confirm if this is indeed a Windows 10 issue and not hardware from more than one user.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Just posting an update: my hardware has not changed since the last post but the issue comes and goes randomly with Windows updates, further enforcing this as an issue with Microsoft Windows software (at least in my case).