Need help with papyrus log just before ctd

[bajs11]

I got following lines just before the game crashed to the desktop:


[ (00162585)].BCF_WorkbenchScript.::remote_Actor_OnPlayerLoadGame() - "C:\Program Files (x86)\SteamLibrary\steamapps\common\Fallout 4\Data\Scripts\source\User\BCF_WorkbenchScript.psc" Line 86
[11/13/2018 - 07:58:00PM] error: Attempted to add invalid perk to the actor
stack:
[ (00000014)].Actor.AddPerk() - "" Line ?
[WI_Manager (0C022E5E)].WastelandImports:WI_PerkDispenser.PerkDispenser() - "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Scripts\Source\User\WastelandImports\WI_PerkDispenser.psc" Line 23
[WI_Manager (0C022E5E)].WastelandImports:WI_PerkDispenser.::remote_Actor_OnPlayerLoadGame() - "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Scripts\Source\User\WastelandImports\WI_PerkDispenser.psc" Line 13
[11/13/2018 - 07:59:25PM] ==========================keyCode:87 shift:False
[11/13/2018 - 07:59:26PM] ==========================keyCode:87 shift:False
[11/13/2018 - 07:59:27PM] ==========================keyCode:87 shift:False
[11/13/2018 - 08:00:22PM] ==========================keyCode:87 shift:False
[11/13/2018 - 08:00:22PM] ==========================keyCode:87 shift:False
[11/13/2018 - 08:00:39PM] ==========================keyCode:87 shift:False
[11/13/2018 - 08:00:43PM] ==========================keyCode:87 shift:False
[11/13/2018 - 08:00:43PM] ==========================keyCode:87 shift:False


Does this mean that the "WastelandImports\WI_PerkDispenser.psc" is the the cause of the ctd?
It happened at Mass Pike Interchange, my character was standing at the top of the elevated highways



EDIT:
luckily I saved right before the previous CTD and launched the game again at the exactly same spot.
As expected the game crashed again if I tried to get closer to the area where the elevated highways crossing the road below and got a new papyrus log.
It seems they both contain the same lines:


[ (FF00CA94)].ObjectReference.Enable() - "<native>" Line ?
[ (00162585)].BCF_WorkbenchScript.ResetFlicker() - "C:\Program Files (x86)\SteamLibrary\steamapps\common\Fallout 4\Data\Scripts\source\User\BCF_WorkbenchScript.psc" Line 110
[ (00162585)].BCF_WorkbenchScript.::remote_Actor_OnPlayerLoadGame() - "C:\Program Files (x86)\SteamLibrary\steamapps\common\Fallout 4\Data\Scripts\source\User\BCF_WorkbenchScript.psc" Line 86


What is strange is I don't even have the game installed on C:
Its installed on a SSD on F:

 

 

 

Edited November 13, 2018 by bajs11

[Wolfmark]

Usually you won't find the reason for crashes inside the logs created by Papyrus scripts.

The paths that appears in the log files are from the compiled script files (where the scripts were located when they were compiled by the mod author).

If you're lucky and can reproduce the crash then disable the mods one by one to find which one is triggering the bug that is causing the crash. I would start with the mods that require F4SE or include a F4SE extensions (a DLL file), because these are the ones that can crash the game easily.

Also see the game settings. For example in my setup changing fLocalMapLoadedAreaRadius_Interior and fLocalMapLoadedAreaRadius will cause CTD in some locations when opening the PipBoy (I also was lucky to reproduce the crash and only reverting these settings to default fixed the problem).

[bajs11]

Well the thing is ctd always occurs at certain specific area and Mass Pike Interchange is one of them.

The papyrus logs I have uploaded belong to the same problem that lead to ctd because I saved the game right at the edge of the zone that causes the crash.

 

I have even made a compatibility patch for every single mod using FO4Edit so there shouldn't be any conflict between the mods and yet ctd occurs whenever my character get too close to Mass Pike Interchange, Nahant/Croup manor and Jamaica Plain.

There is also the area between Red Rocket and Concorde, entering Concorde from either Red Rocket or Abernathy Farm would cause ctd but I have found this one to be caused by Beantown Interiors and hoping whenever the next update whenever it will be will fix the problem.

[RolloWolff7]

I wish there was a crash logger it is annoying not knowing what crashed the game. I got the same log and ctd after that, though video cards sometimes crash espeically the AMD wattman a lot. Though it seems like script errors can cause crashes as well, so with the logs you can see those things at least.

[G4M3W1NN3R]

I wish there was a crash logger it is annoying not knowing what crashed the game. I got the same log and ctd after that, though video cards sometimes crash espeically the AMD wattman a lot. Though it seems like script errors can cause crashes as well, so with the logs you can see those things at least.

 

you will need to open all of your mods in xEdit and check to see if their is any Red Background - Red Text on any record(s), this indicates mod conflicts, and is very likely why you are crashing.

 

papyrus logs are not crash reports, they literally tell you errors in scripts, the majority is to do with bethesda own scripts their files are very dirty, mod conflicts or crash reports will never be mentioned here. papyrus is the scripting engine, as such it can only mention scripts.

 

and alot of that infor mentioned in the papyrus logs is redundant, and enabling papyrus logging can in fact causes crashes on its own.

 

Papyrus logging is completely designed for devs to test their scripts nothing more nothing less.

 

xEdit and Debugging is used for understanding executable crashes

 

their is no easy mode. ie a log that tells you exactly why and what caused the game to crash. the closest to that is xEdit and Debugging.

 

however debugging requires the need to understand Assembly Language, Procedure Calls, Operands and Offsets.

Edited November 25, 2019 by G4M3W1NN3R

[RolloWolff7]

Well actually there was a mod I had installed and I looked at when the game crashed, and actually everytime I went near a certian corpse a crash occured. The Log did lead me to the mod not because the scripts showed the crash but that the scripts were running when it crashed so the mod was causing it. I disabled the corspe in game and no more crash, then I disabled the whole mod and the crashes ceased, it was a loot item causing the crash. So it is like doing detective work, the logs themselves never showed the crash, but it was not just the logs they were only one clue to what mod it was. Now another one is with a raider it exploded but it's body was meshed with the gore parts and that caused a crash also, because the game freezed when going near the corpse and a CTD.

Edited November 28, 2019 by RolloWolff7