Hello, and welcome.
You may already know this, but if you disable a mod, even to test, you really should be starting a new playthrough or at least going back to a save before the mod was ever added (several technical reasons here, mostly that Fallout doesn't support removing mods mid-playthrough, and you may have already baked the issues into your save). If you are trying to test mods, the best recommendation seems to be to start an unmodded playthrough and play until you exit Vault 111, make a hard save, and then add your mods (when you load up the game with mods, you'll want to give the game 20 minutes or so for all of the startup scripts from all of the mods to run, maybe longer if you are starting a mod-heavy run). That hard save is one you can always go back to if you notice an issue, since you can remove any mods that are concerning you and start back up again from there.
As Cessori mentioned, the Crash Log Scanner will help you better identify what the crash logs are telling you. They aren't perfect, but they can definitely help. Also, as Cessori hinted, you should review the
Installation page of the wiki if you have not already (I also strongly recommend the
Known Issues page), and you might try posting your loadorder.txt and plugins.txt (typically found at something like C:\Users\"your name"\AppData\Local\Fallout4, please post them as attachments or under the spoiler tag), and the community can look and see if any issues stand out.
