A specific mod will almost never be the direct cause of a CTD. In most cases, it's an installation mistake or corrupt save.
Corrupt Save: You can rule this out if CTD is before loading a save or a new game. Ensure you don't have a corrupt save. It's simple to test... just, as a test, start a new game. If no CTD with a new game, you have proven it's a corrupt save.
See Golden Rule. If using LE see... Crash on loading a save, no crash starting a new game
Installation Mistake: Check that you've installed all requirements, including the requirements of required mods. Some cases of CTD come from the requirements of your body mod (see Building toys in Bodyslide).
Make sure you are NOT using a non-standard skeleton. Must be XP32 Maximum Skeleton Extended. Non-standard skeletons will crash with certain animations
If using Vortex... first try a purge then redeploy. This forces Vortex to re-do. Its recommended to purge each time you make changes (Vortex sometimes gets things wrong if you don't)
Check this... SE versus AE Version Trap
Sometimes your mod manager is not aware of changes made externally... a mess gets left behind, and this needs to be manually cleared out, or you need to nuke (not just reinstall stuff... clear it all out, folders and all). This has been common lately with AE upgrading/downgrading or issues with Wabbajack/Collections.
For more help, get and share your crash log
Unless you know how to read the log, you would post it in a relevant support forum to get help. If you DO try reading the log, note that mods listed can be "victims" and not the cause. You need to trace using that info back to the root cause.
For AE use - Crash Logger - Use instructions on that page
Fos SE use - .Net script framework. Here are the steps for .Net script framework...
Install the prerequisite: DLL Plugin Loader. Make sure you read the installation instructions for the DLL loader - it's not difficult but it does require following the steps
Install .Net script framework. Use your mod manager
Run your game to the point of making it crash
Open the folder within Data, here... /Data/NetScriptFramework/Crash/ (if you are using MO2, look in your override area) and you will find a time-stamped text file. That's your crash log
Attach your log if you are posting for help
When you share the crash log in the Support Forum, please provide it as an attached file, or use Pastebin and link your Pastebin. (for Nexus you will need Pastebin)
If using Pastebin, no need to signup... just open your log-in notepad... copy... paste into Pastebin... click create new paste button... share the URL it's created up top