umm help? CTDs right after the black and white intro.

[Rasthal]

like the title says. cant describe it any other way.

 

here is the papyrus:

Spoiler

[10/26/2018 - 12:55:48PM] Papyrus log opened (PC-64)
[10/26/2018 - 12:55:48PM] Update budget: 1.200000ms (Extra tasklet budget: 1.200000ms, Load screen budget: 500.000000ms)
[10/26/2018 - 12:55:48PM] Memory page: 128 (min) 512 (max) 153600 (max total)
[10/26/2018 - 12:55:48PM] Maximum stack depth: 100
[10/26/2018 - 12:55:48PM] This is a script log only and does not contain information on any other part of the game, including crashes.
[10/26/2018 - 12:55:49PM] Cannot open store for class "ccRZRFO4001:ccRZRFO4001_SetStageOnTriggerEnter", missing file?
[10/26/2018 - 12:55:49PM] Cannot open store for class "ccRZRFO4001:ccRZRFO4001_RadioSceneScript", missing file?
[10/26/2018 - 12:55:49PM] Cannot open store for class "CreationClub:ccAWNFO4001:LeveledListInjectorScript", missing file?
[10/26/2018 - 12:55:49PM] Cannot open store for class "DLC04:DLC04OperatorsRifleAnimationScript", missing file?
[10/26/2018 - 12:55:49PM] Cannot open store for class "ccRZRFO4001:ccRZRFO4001_RadioSceneToggleScript", missing file?
 

Edit 1: doing a validation now.

Edit 2: did not work.

Edit 3: um ok it works when i start the FO4SE with outside of the MO. but dont seem to be loading any mods

Edit 4: got it to start but now when i try to start a new game it is just a white screen.

[Guest]

I don't use MO, but like NMM, it has quirks.  I have had every sort of  ctd, blue screen, black screen with and without  sound, failure to load, etc

in every single case of mine the problem was a  missing master or requirement for a mod, and sometimes load order, and sometimes NMM just mucked up a mod.

The only other thing that I have had this happen with is after one of Steam's "UPDATES" ?

[AWP3RATOR]

Quote

[10/26/2018 - 12:55:48PM] This is a script log only and does not contain information on any other part of the game, including crashes.

The papyrus log is generally not all that helpful in tracking down CTD issues.  This could literally be any number of issues ranging from mods not made for Fallout 4 to bad installs, to a MO2 issue, to F4SE not installed correctly - could be anything.

 

In the test you performed where the game worked, but did not have mods recognized (because MO2 does this for you) - did it work at all?  Were you able to get in to the game itself?  (Edit #3 above)  If this did work, then it's generally not going to be a game issue with the core, but rather modded content.

 

In tracking this down, I would recommend starting with a fresh profile in MO2 with no mods installed and not using F4SE.  If that works, then add the F4SE launcher and verify that works.  If those both work - go back to your original profile (with the issues) and disable ALL of the mods.  Test again.  If it works, start adding them back slowly.  When it fails again, you'll at least have a place to start looking for invalid files, bad installs, mod not for the right game, etc. and so on. 

 

On a side note, I had an immediate CTD after the main menu in the past  100% everytime.  The culprit was a malformed record created during a save in FO4Edit where some of the data required by the in-game workbench system was missing and had an invalid reference.  I had another when a mesh itself had issues (bad/junk data in the mesh itself).  The game would only crash when that mesh needed to be rendered in 3d - so was more difficult to track down.