great, someone bumped the thread, so i guess i'll have to tag along too
i've never used driver crapper or probably any io bit software
snappy driver installer (origin) downloads driverpacks, then it would install the drivers it finds. it would try to find the most optimal driver (even older versions, and should recommended be signed) and then install it. sometimes it comes across unsigned drivers, or drivers that don't work (e.g. installation of ivy bridge graphics driver doesn't work, have to manually do it from the ivy bridge guide here) probably because the driverpacks thinks something is something, idk. for modern systems running older os, it maybe incompatible (for instance, it discovers modded ryzen chipset that has directory of windows 10 on a windows 8.1 system, unsigned and it failed to install, until i found out about the modded driver on winraid for 7 & 8.1) and almost certainly the incorrect ryzen chipset driver for vista
it also installs unsigned keyboard & other hid drivers on modern os
this is at the fault of the driverpacks, or you (most certainly), not sdi(o) itself
so either create your own driverpack (pack into .7z format) or recommended you find the compatible driver first (this is prerequisite for packing) and then install it
example: https://mega.nz/folder/qtxS2KaS#Tsm4EHhoz5fhLdPMK8P87w
if there are no drivers for such hw and sdi doesn't install it correctly, then you're truly out of luck. please i'm begging you, please stop with the opinions
but everything is YOUR RESPONSIBILITY, and enough is enough. bye.