Windows 10: Secure boot, PIN only, driver verifier

I encrypted my drive with BITLOCKER PIN while not saving the recovery key and had secure boot enabled, then I restarted and enabled driver verifier with all options on all drivers. I cannot get into my computer anymore. : Help.

:)

 

BSOD hidclass.syss with verifier enabled

Hi DocSams,

Could you upload the memory dump, C:\Windows\MEMORY.dmp, to onedrive and post a share link. The minidumps provided severely lack in data.

If you haven't yet, please disable driver verifier.
Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. On 3 boot failures, you'll boot automatically to the recovery options,
   • click Troubleshoot
   • go to the advanced options
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code:

 

Windows 8 Secure Boot Feature: Not So Secure?

So Linux is switching to secure boot also? Or they have to because of UEFI?

 

Windows 8 Secure Boot Feature: Not So Secure?

• Linux
• Linux
• Linux
• Linux
• Oh and OSX

Here is a statement from a Kernal Developer at Red Hat:

I'm not sure this exploits the legacy BIOS but rather it exploits the legacy boot method on MBR drives, injecting a signed key before the OS boots, which you are correct in that it has nothing to do with Windows 8. And the simplest fix would just be to require boot drives use GPT when Secure Boot is enabled in UEFI.