Lets clarify sig_patches problems:
- If your game doesn't launch, could be a sig_patches problem or a firmware problem or a bad source of the content (corrupted for example) or you may have installed only an update of the game without the base.
- If your game ask a data verification, could be a sig_patches problem. If you have done the verification but it ended with an error you'll need to reinstall the content after having installed the good sig_patches.
- If your game launch but make an error just after (usualy 1 seconde after screen go dark) this could be a sig_patches problem (loader patches), this error should append on every game if incorect loader patches.
- If you've error after all taht it's not a sig_patches problem, could be a problem with a module or a patch or a mod of the game (a problem with "atmosphere/contents" directory), a file corruption in the SD (if you have an SD formated in EXFAT corrupted datas is a problem very very much present than wijth FAT32), you may have problem with the archive bit so fix it in Hekate or your source is corrupted.
- And now don't use sig_patches and Sys-patch together, use only Sys-patch cause with firmware 19.0.0+ it seems to work better than classics sig_patches. So delete "atmosphere/kip_patches", "atmosphere/exefs_patches/es_patches" and "atmosphere/exefs_patches/nfim_ctest" directories, remove "bootloader/patches.ini" file and in "bootloader/hekate_ipl.ini" file and in any .ini files in "bootloader/ini" directory remove the line "kip1patch=nosigchk" or if you're "kip1patch" line contain more patches in one line (for example "kip1patch=nosigchk,nocmac") remove the "nosigchk" reference and the "," if this is not the last patches reference of the list.
This error list is probably not exaustive but it's the usuals errors. And if you've problem first delete the "config/sys-patch/log.ini" file then reboot the CFW then include the "config/sys-patch/log.ini" file content in your message, it will realy help to identify if the problem comes from patches or not.