dufriphepr Posted April 25, 2016 Posted April 25, 2016 After a CTD, I often get some weird glitches (GetDistance returning way too large values, effect scripts suddenly stopping, etc.) that persist after reloading the game, and the only reliable way to get rid of them is to reboot the PC. It's like there's some data kept in memory that's retained across process instances. Has anyone encountered the same problem and has a solution that does not require rebooting?
echotest123 Posted April 25, 2016 Posted April 25, 2016 Haven't encountered that problem myself, yet I'd recommend you try checking your taskmanager if Skyrim REALLY shut down or if the process failed to terminate entirely. You might want to run a memroy check, too. Worst case I can think of your RAM is faulty, that happened to me before and was rather unpleasant, I experienced similar problems back then, but I also got bluescreens, so that's that. Uhm... do you have SKSE and an SKSE.ini set for debugging help? If not, install it and google for the SKSE.ini, there a great guide for starters on the steamforums (skse-memory patch + .inis).
myuhinny Posted April 25, 2016 Posted April 25, 2016 One thing you could try is to kill your steam.exe that is running in the task bar then click start menu and restart it and see if that might fix it not sure though just throwing ideas some which I have used before. Mostly when steam was being whiny and popping up errors when trying to start the game and the only way to fix it was to kill the steam.exe and reload it (restarting would of probably of worked but why waste more time then is needed). Not sure if it'll work or not but it's worth a try you never know till you test it.
Guest Posted April 25, 2016 Posted April 25, 2016 After a CTD, I often get some weird glitches (GetDistance returning way too large values, effect scripts suddenly stopping, etc.) that persist after reloading the game, and the only reliable way to get rid of them is to reboot the PC. It's like there's some data kept in memory that's retained across process instances. Has anyone encountered the same problem and has a solution that does not require rebooting? It is a feeling that both TommInfinite and me had, with NV, but never had a way to really test it. I can't tell you specific cases like the GetDistance you mention, but more in general a script that is behaving in a strange way and I can't see any mistakes on it. When it happens, the first thing I do is shutting down GECK before testing in game. The second thing is rebooting. True? False? Mystic? Placebo? I don't mind, what counts is that after a while it solves
dufriphepr Posted April 26, 2016 Author Posted April 26, 2016 I can't tell you specific cases like the GetDistance you mention, but more in general a script that is behaving in a strange way and I can't see any mistakes on it. Yep, that sounds exactly like the problem I have. I always close GECK before running FNV so that's not what causing it. Killing processes manually does not make any difference and according to resmon.exe the RAM is properly cleared, although of course some data is kept in standby. Literally the only reliable solution I have found is to reboot, but at least this works 100% of the time. I really don't want to reboot once every 30 minutes though.
Guest Posted April 26, 2016 Posted April 26, 2016 Well no I have not these issues so much regularly, it could happen once every many days/weeks. Actually I can't even remember last time that I had something like that, even if I script for hours
Recommended Posts
Archived
This topic is now archived and is closed to further replies.