CTD after video intro - fresh win 7 then 10 install

[foggyknight1]

HD problem resulted in fresh install of Win7 but FO4 didn't work any longer so went to Win10, hoping, but no joy. Running bare, official DLC's only, without the high resolution pack checked. Did a full reinstall from Steam, too, with the same result. The menu comes up and I click on the new game option, then the intro video plays for a couple of minutes, the five infantrymen walking away down the road goes white and every time then, CTD. Suggestions on how to work through this problem?

[JimmyRJump]

Never known to have needed a re-install of my OS because a game didn't run properly. I'm running FO4 on Win7 and have been doing so since FO4 was released.

 

This being said, keep in mind that, when re-installing whatever operating system, you also need to re-install the software some games need to work in a good fashion, like DirectX and .NET Framework, etc...

[foggyknight1]

To clarify, my Win7 operating system was reinstalled because it got clobbered with a failure of the C: drive. Once the drive and O/S was replaced, FO4 which existed on my SSD F: drive and had worked fine for over a year, failed to work anymore, just the CTD as described. Went to Steam and had the FO4 files checked and they came back as good, so in frustration I installed Win10, reinstalled DirectX, C++, and .NET, all of this on the new C: drive, hoping for better luck . No luck. Went back to Steam and did a total reinstall of FO4 on F: because it is no surprise that a fresh O/S might need new installations of the applications that worked on the old one. But that didn't fix it.

Something just isn't communicating but what and why not has me stumped. Is it FO4, the operating system, the computer hardware, or what? Thanks for reading this and thanks again if you have any suggestions.

[JimmyRJump]

Have a look at what the Windows Event Viewer says about the crash. It can be a point to start, although the Event Viewer often only gives an initiation of the cause of a program shutting down and not the whole line of events. Sometimes it's a domino effect with one failure leading to another and the initial failure seemingly unrelated to the game going belly-up.

 

Also check if your Anti-Virus solution doesn't interfere in whatever way. I guess not, since you're getting as far as the start of the War Never Changes movie, but one never knows.

 

And for what it's worth, what are your computer specs (CPU, RAM, GPU brand/type + V-RAM)?

[foggyknight1]

Maybe this box o bolts is overloaded and the motherboard just don't have the needed gizmos to function, but that it worked before the drive loss hints that's not the case. Anyway, it's a box I put together built around a MSI Z170A gaming MB with 16 G of ram pumped by a i7 quad core 6700K at 4 GHz. The GPU is an Nvidia 870 with 4 Gigs, I think - this Win10 POS won't let me find the device manager to check for sure. Have six hard drives in it with C; holding the operating system and my two fastest, SSD's, holding my game info. Win 10 is still trying to catch up with the updates and is having lots of trouble with that, so something appears hosed unrelated to Fallout. I'll look for the Windows event viewer and if I can find it in this mess it'll at least be a starting point - thanks for that clue. My Norton AV hasn't been a problem in the past, but I'll disable it for a test just in case anyway.

Thanks again.

[JimmyRJump]

For loading purposes you can try both ENBoost and Bilago's FO4 Configuration Tool. The former makes it possible to use system RAM as V-RAM through an .ini file, the latter is just a help for all kinds of tweaks (ini files and in-game) and for choosing which launcher to set as default (regular or the f4se)...

 

Don't let the bug reports on Bilago's tool fool you. They're mostly -if not all- the result of folk not knowing what they're talking about and/or have tweaked their game into ruin.

[foggyknight1]

Just to try to be polite and close out this thread gracefully, it appears to be a HW problem. Was watching a YT video clip this evening when the machine gave a brief error message and rebooted. Prior to that I had uninstalled FO4 and then did a reinstall of it and the problem continued only now it crashes before the brief movie at the beginning. So, it's MB and ram shopping I go. Thanks again FO fans.

[JimmyRJump]

Just to try to be polite and close out this thread gracefully, it appears to be a HW problem. Was watching a YT video clip this evening when the machine gave a brief error message and rebooted. Prior to that I had uninstalled FO4 and then did a reinstall of it and the problem continued only now it crashes before the brief movie at the beginning. So, it's MB and ram shopping I go. Thanks again FO fans.

In case of having installed the latest Sicromoft Windows patches for the Intel exploit, your troubles could be temporary. Because of some of these patches I had my motherboard acting all weird for a few days: it gave an error 62 (two-digit LED indicator on the board itself) during post and the boot sequence of Windows (7) got stuck on the black screen with the three colours appearing. Only way of booting through was press the "reset" button on the motherboard when the 62 appeared. After four days everything went back to normal for some unfathomable reason.

 

I had already slaughtered my piggy bank for an upgrade in the form of a socket 2066 motherboard, i7 extreme CPU and some DDR4 RAM. For the time being I keep an eye on things and stuffed my pig again...