DarmanSejuk Posted April 16, 2024 Posted April 16, 2024 Hi I'm having this issue when trying to play Skyrim AE. I have tested out the vanilla version and a few other mods without this issue. before the latest skyrim update(thanks bathesda...) everything was working perfectly. If anyone could look at the crashlog and make sense of what is causing the CDT when loading a game or starting a new game that would be great. Including my LOOT load order. 2024-04-16-00-45-34.log skee64.log SLR LOOT.txt
traison Posted April 16, 2024 Posted April 16, 2024 Your crash was indirectly caused by ConsoleUtilSSE.dll. A mod tried to run "setfog 0 0" using it. Plenty of threads about this issue on LL, here's one. 1
DarmanSejuk Posted April 16, 2024 Author Posted April 16, 2024 5 hours ago, traison said: Your crash was indirectly caused by ConsoleUtilSSE.dll. A mod tried to run "setfog 0 0" using it. Plenty of threads about this issue on LL, here's one. I have disabled that mod and the same issue occurs. I'll disable again and repost the crash log.
DarmanSejuk Posted April 16, 2024 Author Posted April 16, 2024 (edited) Ok... well updating the console utility seems to have worked. I thought I have that up to date. Thanks your pointing me in the right direction. Kindof annoying that every search for that error was pointing to an animation issue. Edited April 16, 2024 by DarmanSejuk
traison Posted April 16, 2024 Posted April 16, 2024 (edited) 51 minutes ago, DarmanSejuk said: Kindof annoying that every search for that error was pointing to an animation issue. If you searched for EXCEPTION_ACCESS_VIOLATION (ERROR_ACCESS_DENIED) then yes you'd probably get any random crash log from any random application. It does not mean you need to run something with elevated privileges. Practically every crash in Skyrim is going to result in that specific error code (0x5 or 0xc0000005). You need to see that error from the point of view of the CPU. All it means is that the CPU was instructed to intereact with memory it wasn't allowed to interact with. If you really want to Google these crash logs based on some unique identifier then: Search for "SkyrimSE.exe+0CE9843" - This is where the exception occured. Make sure the game versions match - Offsets move around every time the exe is compiled. From the top down, check how many callstack entries match - The more the better. Edited April 16, 2024 by traison
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now