363rdChemicalCompany Posted July 12 Share Posted July 12 Odd FO4 crash problem on gaming laptop that had been unused 4 weeks. Was working fine when I put it up. Now when I try to start via any method: a)my F4SE pathed to GOG install or b)via F4SE pathed to Steam install from Vortex (different shortcut and my usual method) or c) Start from Steam launcher (do not expect this to work fine since I am on .163 game version d) even just just try to start plain GOG game Vanilla install on my HD, via GOG's launcher, game instacrashes. No launch game menu, no option to launch save games, the FO4 wont even start. Also I noticed that even if I try to start via GOG FO4 launcher or the F4SE that is pathed to GOG. it still seems to trys to launch the Steam copy of the game. Which is real odd. I even reinstalled GOG as to tends to be robuist and the problems persists even if I try to start direct from GOG game files. Same with the Steam install. I cannot of course have Steam verify my files as it will delete my HD pack from Luxor and well as try to update. PLus I have my .acf locked down to read only so Steam likely cannot verify anyway. But I verified install via GOG during my reinstall. And event he Vanilla GOG wont start up from game menu. Uninstalling and reinstalling my steam copy is not an option since its .163, but I did it with the GOG version which I have a copy on my D drive, but this did not do a thing, game still instacrashes on load attempt no matter which method ( F4SE or vanilla) is used. Did not even get to FO4 load menu crash-2024-07-12-10-31-45.log crash-2024-07-12-09-51-28.log crash-2024-07-12-11-10-45.log Link to comment Share on other sites More sharing options...
363rdChemicalCompany Posted July 13 Author Share Posted July 13 Maybe I should post this in the General Nexus help forum I am beginning t suspect this may have nothing to do with Fallout4 but a corrupted .dll file or the like.. Are there windows tools to verify your windows registry files? Link to comment Share on other sites More sharing options...
subaverage Posted July 13 Share Posted July 13 I am still on Windows 10, but I could imagine that this works in Win11, too. In case you did not already do this you can try to open the command prompt (terminal) with admin rights and run the following commands: "sfc /scannow" and after it's completed "DISM /Online /Cleanup-Image /RestoreHealth". And maybe reinstall DirectX and the latest drivers for your system. I do not recommend to use registry repair tools. 1 Link to comment Share on other sites More sharing options...
363rdChemicalCompany Posted July 13 Author Share Posted July 13 1 hour ago, subaverage said: I am still on Windows 10, but I could imagine that this works in Win11, too. In case you did not already do this you can try to open the command prompt (terminal) with admin rights and run the following commands: "sfc /scannow" and after it's completed "DISM /Online /Cleanup-Image /RestoreHealth". And maybe reinstall DirectX and the latest drivers for your system. I do not recommend to use registry repair tools. Thank you thats awesome answer! Also I was just coming here to post that the problem has magically disappeared. maybe my recent windows update fixed something..... Link to comment Share on other sites More sharing options...
Recommended Posts