I have the same problem and it's driving me in-f***ing-sane because of its sporadic/random nature. My original testing sessions - Launching through MO2 with nothing but the cleaned ESMs and skse scripts. - Upon main menu loading done / console 'coc riverwood' / move around / scroll to 3rd person / move around while moving the mouse / console 'qqq' (exquisitely satisfying in these troubleshooting times) - Repeat 3 times without changing anything --- I have tried A LOT of A/B testing scenarios like all the other poor souls in this thread. I will elaborate on them here in this very reply eventually. One thing is for sure, shaders are, so far, not the issue. Or if it is, it is combined to some other behaviour. This is also why I'm writing this post without elaborating on my previous attempts, as I think I found yet another clue which was not thoroughly explored in previous replies. *Tests will be inserted here later.* --- Test #428372 - From system file read access issues to faulty INIs Context: Since my MO2 mod folder is entirely backed up in MS OneDrive. The last reply by @Glanzer made it clear that my problem was related to this. Or so I thought, unfortunately I was able to replicate the problem with OneDrive sync paused and my antivirus turned off. I flipped a table or two then closed MO2. I copied the skse scripts manually in my install folder located in another drive (away from OneDrive) and launched my game from the skse loader directly. After 3 numerous attempt, it, f***ing, worked. I was not ready to declare it a win. Obviously I will have to use MO2 in the end. This is when I remembered that I use profile-specific saves and INI settings. Since MO2 was out of the equation, it led me back to my INIs. I backed up my old, forgotten but working ~/Documents/*.ini and replaced them with my INI from MO2. AUTOMATICALLY I was able to replicate the issue. 3 times with profile INIs, the bug was there. I restored my old INIs and it was working without an issue again. Ladies & gentlemen, an age-old, issue-inducing modding plague causing these kind of issues? While proudly using BethINI?! And that no bulls*** guides will see its "fixes" appear in my files unless I know the author is well-known and/or knowledgeable on the subject. I would not have been surprised of this situation if the ProfileRedirector mod was on due to the fact that it caches INIs and might break stuff, but since it wasn't, the testing is aiming in that direction, INI issues. Even though I'm not 100% sure yet, more like 90% sure. I will be reviewing each lines of my defective "oh-so-perfect-BethINI-generated-INIs" against my old, trash but working ones. Like I said, I will keep you all informed here. Never give up. Update: - I backed up both my working and not working INIs. - I recreated my with BethINI from scratch. Using these settings. Every changed setting I would save INIs and run Skyrim to test. - Tested out those fresh INIs both outside and inside MO2. (profiles vs documents) Everything worked. - Tested loading the game with read-only INIs, nothing triggered. - Reviewed every line to see any changes between the newly crafted and the broken ones. - Copying the lines from the broken INIs that were not in the new ones did nothing to break the game. It's just working. And I'm kind of pissed that I cannot replicate the issue, because I still haven't found what is causing it! I have but speculations to make after all this. Need further testing. Here is what changed from last time: - I did not generate nor use a SkyrimCustom.ini anymore. - My files are not read-only, even though I tested those and it made no change. I will edit this again if something come up. If someone wants to take the torch from here, please do so!