AFAIK access violation is a problem with memory. It could be one of a few things
1. It doesn't have permission
2. It cannot find the information in memory
3. RAM is broken
#3 is unusual and unlikely to ever be the problem especially in this case.
#1 Could be a problem but generally with skyrim it isn't about that
So we're left with #2. It can't find the information in memory. Why would that be?
Basically (and this is as far as I know, so take it as a grain of salt).... A mod is trying to access something in memory that isn't there. What is it trying to access? I don't know but most probably reference from a master file that isn't there or hasn't loaded yet (bad load order). BUT you should run LOOT and see if there's any missing masters. If it can't find anything and there's no errors and you successfully sorted and applied the load order and it keeps crashing then you should do the A/B testing. Narrow it down. Disable all your mods, run the game, see if it works. Good? OK. Now enable the biggest mods you have and run it again, still OK? No? Disable some of those mods and see which one is causing the issue and go from there.
Just looking at your list I see A LOT of JK patches. Isn't there a consolidated file with all of those so you don't have to run like 300 mods? You also have Bruma patches but I don't think you have Bruma? Hard to tell but Bruma is problematic with some mods from what I've been reading right now. It might be that as well. Running LOOT is likely going to help you figure this out at least.
Edited by hedgie2019, 10 May 2022 - 01:40 PM.