4/22/2023 0 Comments Procmon64At this point I had a long day and just went with it, launching procmon when the game starts and shutting it down once the first cutscene ends so it's logs don't eat up my RAM. I fire procmon back up, and the game works. There is no error message in Windows event viewer, no werfault.exe to report it, it's like the entire system treats the crash as a normal process close operation. I shut down procmon and then the game, thinking maybe I just fluked something, but try after try without procmon, the game would just get the black loading screen and do the fastest CTD ever, the little loading icon in the bottom right does not show up. curious as to what was causing the issue, I fired up Procmon64 to see at what point the game just dies. A week ago, I totally understood having a CTD by just clicking the play button, so eventually I update all the mods and F4SE, but no dice. Title says it all, but there is of course the story to go with it.īeen a while since I played my modded Fallout 4, so I decided I'll get back into it as a pastime when college work isn't a priority. I give massive praise to the F4SE team for pointing me in the right direction! This can be solved by quitting PH2 before launching, then once at the menu screen, it can be opened again. At some point since I played back in 2019, Bethesda’s Fallout4 and/or F4SE updated in a way which makes the combination of PH2 and KPH3 (the kernel driver) fail when running at the same time before FO4 launches past the intro BIK. UPDATE: Process Hacker 2 and it’s Kernel driver was causing it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |