Antiforma1 Posted September 10, 2024 Posted September 10, 2024 im having a ctd before the logo appears can´t even reach main menu.log says apparently that the issue is my pc fault but how? crash-2024-09-10-03-43-55.log
traison Posted September 10, 2024 Posted September 10, 2024 2 hours ago, Antiforma1 said: log says apparently that the issue is my pc fault Hehe, how did you determine that? Anyhow, you crashed because of one of these: Missing master plugin. Missing BEES. Incompatible mod with a dll. 1
Antiforma1 Posted September 10, 2024 Author Posted September 10, 2024 9 hours ago, traison said: Hehe, how did you determine that? Anyhow, you crashed because of one of these: Missing master plugin. Missing BEES. Incompatible mod with a dll. forgot to download/install bees it seems works fine now thanks.
monty359 Posted September 12, 2024 Posted September 12, 2024 On 9/10/2024 at 6:08 PM, Antiforma1 said: forgot to download/install bees it seems works fine now thanks. On 9/10/2024 at 6:28 PM, traison said: Can you elaborate, what BEES is? Looking at Nexus, BEES comes up as NPC replacer. I have a problem since a couple of days, that my MO2 does not start skyrim. Before the loading screen event appears, MO2 crashes/stops loading. There is no error in the log, that indicate, what is wrong. Thanks
traison Posted September 12, 2024 Posted September 12, 2024 4 minutes ago, monty359 said: Can you elaborate, what BEES is? https://www.nexusmods.com/skyrimspecialedition/mods/106441 5 minutes ago, monty359 said: Before the loading screen event appears, MO2 crashes/stops loading. There is no error in the log, that indicate, what is wrong. Check skse64.log. You probably have a dll that's incompatible with the game, crashing it before the crash logger is loaded. If you're lucky, the last log entry will point straight at it. 1
monty359 Posted September 12, 2024 Posted September 12, 2024 6 hours ago, traison said: https://www.nexusmods.com/skyrimspecialedition/mods/106441 Check skse64.log. You probably have a dll that's incompatible with the game, crashing it before the crash logger is loaded. If you're lucky, the last log entry will point straight at it. Did some testing: 1. there is no SKSE64.log file, it appears, that the crash happens before the dlls are loaded. 2. There is a SKSE64 Loader.log with this contents: Spoiler skse64 loader 02000130 01DB0523E95DE91A 6.2 (9200) config path = G:\Games\SteamGames\steamapps\common\Skyrim Special Edition\Data\SKSE\skse.ini procPath = G:\Games\SteamGames\steamapps\common\Skyrim Special Edition\\SkyrimSE.exe launching: SkyrimSE.exe (G:\Games\SteamGames\steamapps\common\Skyrim Special Edition\\SkyrimSE.exe) dwSignature = FEEF04BD dwStrucVersion = 00010000 dwFileVersionMS = 00010000 dwFileVersionLS = 00000000 dwProductVersionMS = 00010000 dwProductVersionLS = 00000000 dwFileFlagsMask = 00000017 dwFileFlags = 00000000 dwFileOS = 00000004 dwFileType = 00000001 dwFileSubtype = 00000000 dwFileDateMS = 00000000 dwFileDateLS = 00000000 productVersionStr = 1.5.97.0 version = 0001000500610000 product name = TESV: Skyrim steam exe dll = G:\Games\SteamGames\steamapps\common\Skyrim Special Edition\\skse64_1_5_97.dll main thread id = 17120 hookBase = 000001DE52FE0000 loadLibraryAAddr = 00007FFC55750830 hook thread complete launching WARNING: something has started the runtime outside of skse64_loader's control. SKSE64 will probably not function correctly. Try running skse64_loader as an administrator, or check for conflicts with a virus scanner. i am looking in the web for the Warning text, there are lots of hits, but as of now, no solutions worked sofar. i Have: MO2 latest version skyrim and skse64 version 1.5.97 (SE) mo2 and all .exe files in the game folder are starting as administrator (tested without, get error even before crash) any ideas? Thanks!
traison Posted September 12, 2024 Posted September 12, 2024 That happens if something resumes the SkyrimSE.exe process when skse64_loader.exe still expects its threads to be suspended. Finding the source of the issue may require a debugger.
monty359 Posted September 12, 2024 Posted September 12, 2024 25 minutes ago, traison said: That happens if something resumes the SkyrimSE.exe process when skse64_loader.exe still expects its threads to be suspended. Finding the source of the issue may require a debugger. A debugger, is it a software? Any specific one comes to mind? A google search finds quest debugger for skyrim, but i did not see anything, that can debug a launch of skyrim. Any idea, what can "resume" the Skyrim SE process? Thanks!
traison Posted September 12, 2024 Posted September 12, 2024 34 minutes ago, monty359 said: A debugger, is it a software? Not meaning to be rude, but if you don't already know what it is, you won't be able to use it. Not to mention use it to identify live tampering from a 3rd party, which may be coming from the spooky ring 0. 34 minutes ago, monty359 said: Any idea, what can "resume" the Skyrim SE process? Any other process, process module or kernel object currently running. Anything with the same or higher privileged permissions as the token you run Skyrim with. Typically that only rules out services that aren't kernel objects and are running without access to the desktop I *think*; practically everything else either has access to your things, were started by you or has higher privileges than you. If I had to pick out some "most likely" candidate here I think I'd inspect anti-virus solutions first.
monty359 Posted September 12, 2024 Posted September 12, 2024 1 hour ago, traison said: Not meaning to be rude, but if you don't already know what it is, you won't be able to use it. Not to mention use it to identify live tampering from a 3rd party, which may be coming from the spooky ring 0. Any other process, process module or kernel object currently running. Anything with the same or higher privileged permissions as the token you run Skyrim with. Typically that only rules out services that aren't kernel objects and are running without access to the desktop I *think*; practically everything else either has access to your things, were started by you or has higher privileges than you. If I had to pick out some "most likely" candidate here I think I'd inspect anti-virus solutions first. Antivirus has rules to ignore the folders of skyrim, MO2 and the mods folder of MO2. Knowing what it is, has to begin somewhere. Give me a hint to be able to narrow the search.
traison Posted September 12, 2024 Posted September 12, 2024 (edited) 39 minutes ago, monty359 said: Give me a hint to be able to narrow the search. I like where your head's at. Debugger: https://x64dbg.com/ Since you're on MO2 you will have to start by attaching it to MO2 and tapping into the CreateProcess(W/A) call so that you can then attach it to skse_launcher.exe. Repeat the process in the launcher and pay close attention to what happens to SkyrimSE.exe after it is created suspended from the launcher. You won't have to worry about debugger traps or DRM bypass here, as you never get to that point in this issue. Edit: Oh forgot to mention. There's a timing issue to all this process hopping. It will fail the first time you do it, but luckily x64dbg remembers breakpoints. So once you got breakpoints on the calls to CreateProcess(W/A), do it again, only faster, and it won't fail. The tricky part here is that by the time you get a debugger into SkyrimSE it will most likely already have been resumed and perhaps terminated. This is where I can't really help you. I have no answers for detecting thread resumes before they happen. I just got a feeling if anything is going to be able to do it, its going to be a debugger or ETW. If you're lucky, you can tap into a function in the kernel32 library in SkyrimSE.exe to detect it. If you're unlucky the only place to see it is in the calling app, and the message trail ends in the kernel. If that's the case then there's really no way to spot it (Edit: without knowing where its coming from, or without being inside the kernel). Since I mentioned ETW, maybe you want to look into that as well. Event Tracing for Windows. It can be used from Powershell for instance, Process Monitor from Sysinternals being another. ProcMon does not appear to be showing thread suspends/resumes (assuming these actually have events), so perhaps need a more DIY approach. ETW can also be used from C# if you're not allergic to coding. Edit again: Not seeing a resume/suspend event in ETW. Might have missed it. Edited September 12, 2024 by traison 1
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