7531Leonidas Posted February 6 Share Posted February 6 Take a look at a portion of my display: If I were looking for one(s) that were not working properly, then I would start with the one highlighted, since it didn't get modified when the others above it did at game launch, when listed in descending 'Date Modified' order. In my case, I know that that one, and the others below it, had no changes in settings that would cause them to be modified, or they had been disabled. No real skill needed, just look at the times. Link to comment Share on other sites More sharing options...
JanuarySnow Posted February 6 Author Share Posted February 6 I think I'm understanding. I just tried to launch Skyrim and it crashed but I had my folder open and saw what you mean. The time changed and I'm assuming they will change if i try it again tomorrow. So what I'm understanding from your list and mine is that anything that didn't just get altered as the game was launching is more or less the reason for the crash since they weren't updated as far as the individual mods go, and any text document that had a time change as the game launched, is up-to-date and is more likely NOT the reason for the CTD? Link to comment Share on other sites More sharing options...
7531Leonidas Posted February 7 Share Posted February 7 That is the assumption, yes. The last one to be updated may also have something to the effect that it didn't load, so look at that log first, I think. You can then go to the skse64.log, and read down its list of .dll starts, to confirm what did not load properly. At least you will have some idea of where to look, now. Link to comment Share on other sites More sharing options...
JanuarySnow Posted February 7 Author Share Posted February 7 I will give that a try and see what pops up Link to comment Share on other sites More sharing options...
JanuarySnow Posted February 7 Author Share Posted February 7 the last one to be updated is hdtSMP64.log0 everything below that didn't change timestamps at all. Link to comment Share on other sites More sharing options...
7531Leonidas Posted February 7 Share Posted February 7 (edited) Did you look at that log to see what it says about starting? I believe a .log0 is a backup log that holds the previous log. As such, also take a look at the hdtSMP64.log and see what it says. Mine has a string of 'trampoline alloc xxxxxxxxxx failed' notices (about 20) - I don't know if it is important, an internet search doesn't help me, since my Faster HDT crashes from time to time. Prob need a really technically involved person to explain this one. With all of that said, now take a look at the skse64.log and compare the .dll files listed in the startup to the .dll list in that folder where the logs are. You might find which one(s) didn't start properly (note that the plugins attempt to start in alphabetical order). Alternately, you could use Notepad to search the skse64.log for ' correctly ' (spaces included), and proceed down the list, to look for adjacent ones that show an error message (it seems I have 85 SKSE mods starting, anything to speed the search might help) - I don't know what an error message would look like, you might want to go to ( https://skse.silverlock.org/ ) and ask, then you could search for the error listing itself. Edited February 7 by 7531Leonidas add link to SKSE homepage Link to comment Share on other sites More sharing options...
Recommended Posts