While I agree with @Twistys comment below this answer, to definitely first try "to use the advanced startup option Last Known Good Configuration", I still think the gold standard is to ensure you have an Image Backup, in case that fails. In the past I've seen the "last known" somehow get lost and not work on occasion. I think the reason it fails at times, is that it depends on resetting what changed. Obviously, it only resets a small subset of your system, and if Windows can "put back the broken piece", it works. Malware is just one classic exception.
While you are doing your experiments, I'd make sure you could get back to where you started, with an IMAGE BACKUP as well. It's pretty easy to brick your system if you remove the wrong driver.
Fixable? Yes, but you'll waste a lot of time trying to fix an unbootable system for no good reason. I'd strongly recommend an Image Backup, and NOT any of the other "recovery or Windows reset utilities". If you use the Windows Image backup feature that comes with Windows 10, it is relatively fast, somewhat foolproof, free, "industry Standard", with lots of other tools and companies that can work with these Images. Since this Image format is also used to mount Windows virtual volumes, you can also mount that Drive Image and access it as another hard drive volume. (Careful though, research this, since mounting an image as a virtual drive in the same system as your drive C: would confuse Windows, and so Windows will change the volume ID before it mounts it.)
To use Windows Image Backup, you can simply search for "Image Backup". There are a few problems with the implementation that comes with Windows, however. First, unless you are going to do the research, there are many options available using the commandline version of Windows Image Backup, unavailable in the simple "no-option" UI. For instance, if you use the standard Windows UI, it will do ONE backup, and then you will overwrite that one copy, the next time you do a backup. The commandline allows you to back up the factory partition, for instance, (with difficulty), perform a bootable image backup or not, exclude or exclude certain files and folders. (For instance, Windows EXCLUDES your DRM folder!)
Although you can overcome the "only one backup allowed" problem, if you start messing around with the ACLs in any folders or files inside the WindowsImageBackup folder, you can easily render some, or all of your Image backups inaccessible to restore that image. (Windows Recovery Console from where you restore your image is running as SYSTEM, and not as a user). Don't forget to build some media to boot from, such as a USB, DVD, etc., so you can get to Windows Recovery Console!
Overall, we like standardized formats, since there is a lot of expertise to fix something if the Image breaks. There are other companies also using the Windows Image Backup format for a variety of uses and implementations, as well as my company. As a result of the need to overcome these Windows implementation issues, we built automation around Windows Image Backup, to fix, workaround, and make sure that you have multiple and regular past and recent Image Backup copies available when you need them. (For instance, we remind you when to plug in your external drive on a daily or weekly basis.) Check out our Protect My PC since it is free and also because it does nothing "strange" or proprietary--it IS a standard Windows Image Backup.
No matter what though, DO an image backup with SOMEONE'S product so you can do a bare metal recovery. (I'm also the CEO of the publisher, CDP.com, so as you see features you'd like, let me know.) In today's PCs, most image backups using a USB-3 external drives can be backed up in less than 30 minutes and could contain 10-30 Image Backups from different times, and still leave room for anything else you'd like to keep there, (such as Windows File History). If you do this manually, set up some type or reminder system to do the backup. If not, I can assure you that most of us, or someone else you support, will seldom if ever plug that external drive in, let alone take the time to do that backup.