Setup BitLocker, lost BIOS access

[CoolJosh3k]

So I went ahead and got bitlocker all setup on my new system, but now I cannot access my BIOS at all.

 

I’ve tried hammering my del key to death and using Windows’ feature to take me to BIOS on reboot.

 

Is this an avoid BitLocker and clear cmos situation? How do I get back into BIOS, even if it means giving Microsoft the middle-finger and going for something like VeraCrypt?

[Levent]

12 minutes ago, CoolJosh3k said:

Is this an avoid BitLocker and clear cmos situation? How do I get back into BIOS, even if it means giving Microsoft the middle-finger and going for something like VeraCrypt?

Not really no. If you clear CMOS, you wont be able to boot to Windows until you input the longass bitlocker unlock key. Is this a prebuilt HP/Dell system or something?

[CoolJosh3k]

Custom built.

 

I am assuming BitLocker screwed with my BIOS and I can clear cmos to fix BIOS, then have Bit Locker work still.

[Levent]

8 minutes ago, CoolJosh3k said:

Custom built.

 

I am assuming BitLocker screwed with my BIOS and I can clear cmos to fix BIOS, then have Bit Locker work still.

Bitlocker has no way of screwing with your BIOS. In any case, whatever you decide to do make sure you have access to your bitlocker recovery key (login to your MS account and also keep the recovery key somewhere else).

[CoolJosh3k]

I did enable resizable bar, install RGB Fusion. Pretty sure I was rebooting normally after that though?

 

I’m sure this only happened after bitlocker.

[Kilrah]

I've been using bitlocker for years and it never did anything BIOS-related.

[CoolJosh3k]

Back the next day and have cleared cmos.
 

Now I get either
* D2: PCH initialization error
* F3: Recovery firmware image is found

 

leaving it like this the PC just shuts off after a bit.

[CoolJosh3k]

Update:
 

Opened the side panel and I can see the graphics card is sagging.
However, I did manage to find that the problem seems to have been my monitor. Even though I changed nothing, apparently my monitor decided to no longer accept the signal. I touched it’s little joystick thing which brings it to life and suddenly it realises there is a signal. Set it to auto-detect, which causes the monitor to cycle through all inputs, and that seems to have done the trick.
I assume the D2 error will show again in the future though. I have one of those chunky graphics cards installed (RX 6800).

 

Thanks to those who commented to try and help.