Guest Posted February 16, 2019 Posted February 16, 2019 Hello all, Today I come here out of complete and total desperation based on this topic: https://www.loverslab.com/topic/46913-how-to-debug-ctd/ I am running the Lexy LotD SE guide and am getting a persistent crash that occurs on save attempts. The crashes came out of the blue and began occurring only on save attempts outdoors and in cities. It later began occurring in indoor areas/dungeons. I had updated the guide when they released different changelogs mid-playthrough, so my issue was chocked up to a corrupted save. With that in mind, I created a separate MO2 install by copy+pasting my original directory, and further updated mods accordingly with the new changelogs. Fallrim resaver did not work. One would think that a separate MO2 install along with a new game would fix the problem-- wrong. Upon clicking the 'create' button to create my new character I experience the same crash. This is presumably because the game seems to attempt to autosave upon character creation, despite having my inis (in my MO2 profile) configured to disable all types of autosaves. Nonetheless, when I look over my .Net Script Framework/SKSE Minidump crash logs, the character creation (autosave?) attempt CTD has the same output as the crash logs I had during my 200 hour playthrough with the previous iteration of the guide. The strange thing is that the crash seems to be inconsistent (more-so with new games) in the aspect that it seems to be somewhat time dependent. For example, when I load my 200 hour playthrough (loads into interior) and quickly attempt to create a save, I am far less likely to experience a ctd on the save attempt compared to attempting the save after five minutes or so (although I will crash on outdoor save attempts no matter what). The same holds true with the character creation autosave crash (using alternate start). When I quickly create a character I do not crash on the initial autosave, but if I spend 10 minutes or so creating a character, I will crash. This puts me at an impasse because I cannot confidently begin a new playthrough, and I also cannot continue my 200 hour playthrough. I've been trying to fix this issue for a week, presenting my case to the Lexy LotD Discord and reddit to no avail. I have no idea what would have changed to abruptly cause these issues, and it does not seem like updating the guide mid-playthrough is the culprit due to the fact that a new playthrough with a separate MO2 install has identical ctd logs. It's always the same SkyrimSE.exe + 136ab51. Net Script Framework crash log: https://pastebin.com/kqY1fuFt SKSE Minidump crash log: https://pastebin.com/VSEqgNUZ
sohanev Posted February 16, 2019 Posted February 16, 2019 EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 00007ff6e808ab51 (SkyrimSE+0x000000000136ab51) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000000 Attempt to write to address 0000000000000000 PROCESS_NAME: SkyrimSE.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000000 WRITE_ADDRESS: 0000000000000000 similar problem
Recommended Posts
Archived
This topic is now archived and is closed to further replies.