JimboUK Posted December 4, 2017 Share Posted December 4, 2017 Can also confirm this, I'd been getting random crashes that are now gone, I'm still keeping it for the fast exit and frame limiter, VSync is no good on a 144hz display. Link to comment Share on other sites More sharing options...
dubiousintent Posted December 4, 2017 Share Posted December 4, 2017 (edited) Thanks. Taking it as a given now. Updated as 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. -Dubious- Edited December 4, 2017 by dubiousintent Link to comment Share on other sites More sharing options...
EPDGaffney Posted December 9, 2017 Share Posted December 9, 2017 Sorry, I know this is slightly old, but my game has actually been freezing, not crashing, and I want to clarify what's actually happening as I have a hunch it's a related problem given that my game runs extremely fast and smooth but will suddenly (seemingly randomly) freeze after fifteen minutes to an hour of play. It's been doing this since about that Windows 10 update, and it doesn't ever exceed 2GB of RAM usage. I'm about to test the fix but I think it could be useful to the community in general if we clarified crash vs freeze. Cheers. Link to comment Share on other sites More sharing options...
dubiousintent Posted December 9, 2017 Share Posted December 9, 2017 (edited) Technically I would call them both a "crash" (an unanticipated program error condition), but in the case of a CTD there is usually a Windows Eventlog entry because the OS caught the error condition and stopped processing the "app/game" and brought you back the the desktop under control. (You can still "do stuff" like look at the EventLog.) A "freeze" OTOH is essentially a "hang" (: "an infinite loop"): the system comes to an uncontrolled stop because it (the system and not just the program in question) can't decide what to do next or endlessly repeats the same set of instructions. You don't have control or progress, except possibly <CTRL+ALT+DEL> to get to the task manager or reboot, though that is where you can quibble whether it is a "freeze" or a "hang". These are casual terms and I'm sure there are lots of nits to pick with them between experts. A "stack overflow" is the typical diagnosed "heap size" error and can cause either condition. It just depends upon what the system was attempting to do at that moment and what the "overflow" overwrote in some other program's memory space. The Win10 FCU broke the "bHookCriticalSections" in NVSR. If you still have that enabled, then suggest you disable it per the "Troubleshooting" entry posted above and see if it helps. It's still early days on the ramifications of this FCU patch, especially for older games. Edit: to add "infinite loops". -Dubious- Edited December 9, 2017 by dubiousintent Link to comment Share on other sites More sharing options...
EPDGaffney Posted December 9, 2017 Share Posted December 9, 2017 Well, beautiful people, that was indeed the fix, far as I can tell. I'm so happy I don't know what to do. Yes, you're right about the crashes, but in order to determine that my problem and theirs are related, the exact nature of all our situations could be useful, and probably even more so for furture users. Unfortunately, disabling that setting at the very least seems to have made my game run far less smoothly, as it was shockingly smooth after my overclocking the other day, but I played for over an hour with no crashing, so I'd say it's a victory all the same. Think I'm going to overclock some more anyway and see what I get. Link to comment Share on other sites More sharing options...
EPDGaffney Posted December 10, 2017 Share Posted December 10, 2017 (edited) I'd like to update everyone and say that for me, turning off NVSR entirely was necessary. Audley suggested the same but I had already tested with it off. I played for over an hour with a large load order including Nevada Skies, graphics upgrades, and Freeside Open and no problems besides some stuttering that NVSR used to take care of. My game was fixed with just the bHookCriticalSections option off, but on restarting my PC, the problem was back. This fixed it, I think at least. Edited December 10, 2017 by EPDGaffney Link to comment Share on other sites More sharing options...
Recommended Posts