Apoqsi Posted August 21, 2016 Author Share Posted August 21, 2016 what corrupted the drivers?I honestly don't know. It could have been a bad install of the latest drivers or just the overuse of Express Installation with NVIDIA that caused an issue. Other than that, I'm completely oblivious. I would have figured corrupted drivers earlier if every or at least a few other game had issues as well... But it was only FO3 & NV having the crashing issues. Link to comment Share on other sites More sharing options...
dubiousintent Posted August 21, 2016 Share Posted August 21, 2016 Later video drivers often drop support (generally meaning they are not tested against) older games. It's best to not automatically update video drivers unless you have reason to believe it will fix a particular issue. It's also worthwhile to keep a copy of the previous version around for a while after you do. Good to hear you figured it out. -Dubious- Link to comment Share on other sites More sharing options...
allusers Posted November 17, 2016 Share Posted November 17, 2016 Hey Guys,I just want to quickly reply here in case the suggested Solution isn't working for someone. I had working and heavyly modded Fallout Games for Years now and even upgrading to Windows 10 never caused any problems until someday loading any savegame or starting a new game in New Vegas or Fallout 3 resulted in a crash even in the vanilla versions. It gave me quite and headache and i was'nt able to fix it until today. The posted file from the eventviewer indicates that there is something wrong in the "skype.exe" application. So i closed Skype. And yes, now everything is working properly. I don't now why Skype would interfer with the Fallout Games, but if you are looking for a very quick and easy way to fix this issue, ditching skype might just do the trick. Link to comment Share on other sites More sharing options...
dubiousintent Posted November 17, 2016 Share Posted November 17, 2016 Most programs are written as if they are the only one running on the hardware. They tend to not "share" resources. Background programs are the exception, but they need to be able to signal to the OS when they need resources. Communications apps have a high priority, because of response requirements. Which means they can grab things (like sound cards) and not let go until they are done, potentially causing other programs to have to wait on them. Games also have a high priority (because: interactive), but they don't expect to "wait" on hardware resources. So you get CTDs. The take-away lesson is: minimize the number of background programs you have running when playing games. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts