Mystery crash I can't solve after a week on my own

[JFTA01]

The crash

So as the title suggests, I've got a mystery that I'm hoping you guys can help me solve. My game crashes on kills but only when it's the player doing the damage/ killing on NPCs and creatures but not specific creatures. It happens with energy weapons, big&small guns and melee weapons. can use vanilla, DLC and mod added big&small guns, energy weapons and melee weapons on objects, scenery and dead actors with no problems so it may be something to do with them actually dying. AI and companions fighting do not cause a crash. The crash is not present in vanilla and doesn't seem to be caused when console killing things.

 

 

Specs

• Desktop computer
• AMD Athlon II X2 240, dual core, 2.8Ghz
• 6gigs system RAM
• HDD 315 gigs free
• Nvivda GTX 970 (The fallout 4 Graphics card)
• 4 gigs video ram
• monitor is native 1280x1024

Info

• Game is located in the default Steam install directory
• I have the latest version of the game
• All DLC's installed
• Currently using mod organizer 1.3.11
• FOSE 1.2 beta 2
• large address aware enabled
• using onetweak
• Exception code: 0xc0000005
  Fault offset: 0x001878f8
  Faulting process id: 0xf84

 

File order pastebin link

http://pastebin.com/p4nNmUkU (mod organizer decided to output this upside down)

 

Load order pastebin link

http://pastebin.com/2j98YZWN

 

.ini pastebin link

http://pastebin.com/HxQQRZKX

 

fallourtprefs.ini pastebin link

http://pastebin.com/sdt73f1J

 

Already tried

• Klite codec
• multicore ini tweaks
• multithread ini changes
• adding d3d9.dll
• XP & vista compatibility mode, running as administrator on fallout, falloutlauncher and FOSE
• Disabled visual themes, Desktop composition and display scaling on those as well
• LOOT broke everything (mainly FWE) so load order was done manually
• Cycled through ingame options, turned whole chunks of mods off and on to try and isolate the problem

 

I'm honestly out of ideas here so I'm hoping somebody here has some insight. Other than this single issue the game is remarkably stable, no stutters, random crashes, messed up textures or audio problems. I can fun for 6+ hours solid just exploring as long as I don't kill anything.

 

TLDR: nxs pls halp

Edited November 16, 2015 by JFTA01

[Purr4me]

disable all 20th plugins and move out of the games data directory It's bsa archive load the game and test save.

 

The bsa contains another esm file that;s also loading...bad archive.

 

make sure that bsa is not in the game flow.

[Purr4me]

you can unpack the bsa and remove the offending code and use Fomms package manager to repack it, no compression.

[JFTA01]

Alright, I'll give that a shot. Thank you.

[Purr4me]

I am currently retrieving My home copy of that mod cuz a lot of mods, weapon mods confuse me, not sure if Classic pack was it or that 20th one was it, all I know is 2 years ago, I repackaged my copy directly from the web site here due to the bsa containing another copy of the master file,,,,I remember this it because Mo said it was loading even while the mod was deactivated, that master file still was there in the load order on the right pane.

 

I read it's bsa contents and discovered it...shortly there after the mod was removed for some reason...same a AA arns...some such name.

 

possibly borrowed assets or something else, too many mods have come and gone, I just know there is a weapon kit type mod that has a bsa loaded..really loaded LOL.

 

This may solve your issue, it may not, only you can tell me that.

[JFTA01]

Couldn't find any bsa in the 20th century main file or any of the -alive- files. the bug is still present in a new save made after removing all 20th century components from the file order.

Edited November 16, 2015 by JFTA01

[Purr4me]

Couldn't find any bsa in the 20th century main file or any of the -alive- files. the bug is still present in a new save made after removing all 20th century components from the file order.

yeah I also see that, one of them had that issue, I just got my other copy's off of file planet, same there.

ok load the old save file with the bug when you started this quest, disable all of the mods except DLC's and load, see what takes place.

 

All I can do is download the mods I see listed in your post and load them up....I will need your effected bad save file to test the bug live.

 

then again? !! it could be just that xlive causing the bug. donno, I can try and see.

[JFTA01]

You did make me think though, I hadn't even thought to check. in total there were 3 files all enabling calibr.esm but the bug still persisted even after rectifying that.

[JFTA01]

Immediate CTD once all mods were removed. I deleted the UIO menu files before starting and reverted the darnified ini font changes. I'm still getting some form of menu crash though.

Edited November 16, 2015 by JFTA01

[Purr4me]

If we were on steam, I could watch you in real time and see what's going on....nothing beats an eye ball.

 

as far as all the UI stuff goes, if any files dealing with UI are out of place, wrong code or anything, your gonna have crash's.

 

But WMK has only two scripts calling for Fose all the time..so IF wmk is disabled and you run the game raw "No Fose" and no ui mods, it should load. OR send me your saved game file, I'll load it up here and attempt to remove the bad code stuck in it.