DjinnKiller Posted June 12 Share Posted June 12 (edited) Not only did I stay far away from next-gen, have been and will be staying on 163 for the eternity, and my load order has been rock solid for a very, very long time. For the first time in almost 2 700 hours in Fallout 4, I get the fcuking "Pure Virtual Function Call" error after the recent Win11 update. Next-gen from Bethesda (owned by Micrsoft), recent Windows 11 update from.....Microsoft (duh). You can't fcuking win.... Edited June 12 by DjinnKiller Link to comment Share on other sites More sharing options...
worm82075 Posted June 14 Share Posted June 14 If you are talking about when exiting the game, it can be safely ignored. Just say ok and don't give it another thought. Link to comment Share on other sites More sharing options...
DjinnKiller Posted June 19 Author Share Posted June 19 (edited) Sorry for the late reply.....life and stuff caught up to me. No, this was not exiting, this was mid-/ingame. I'm used to playing or horsing around in FO4 for hours, never crash, nothing. Then suddenly I got that f#¤€% error after an hour or two after a .NET and some other, non-specified updates from MS. But at least for now, it is gone again. Color me confused. I have a pretty strict regime regarding updates, both OS and applications, I do updates, often, but controlled. This threw me, maybe some assembly cache or stuff that needed to rebuild? (I have zero knowledge about .NET) Edited June 19 by DjinnKiller Link to comment Share on other sites More sharing options...
Recommended Posts