Can we all remember if we have a crash log to put the crash log in spoiler tags so it makes it a lot easier to read and it doesn't clutter up the comment section.
you can do this by writing [ spoiler ] your crash log [ / spoiler ] it will make it a lot easier for everyone.
Hey Guys! Recently I started having some crashes in the game and I still haven't been able to identify the problem. Among them, when completing the mission against The Mechanist, I had two crashes in the same place. Can anyone help me with this?
I'm not 100% sure, but I think "Functional Displays" is the culprit in your case. Also from a quick look at your load order, I can already see some mods that can cause problems in the future. I hope you can solve your issues :)
I have 2 separate profiles for FO4 on Vortex. One is the Storywealth collection (and some official addons for said collection) and one is the District collection. Both CTD immediately at launch. I tried to figure it out on my own with the crashlog because it's one of those Exception Access Violations, but the Plugin section is empty, even though Vortex claims they are enabled. I have used Buffout but it doesn't seem to make anything clearer for my dumb brain. This is a CTD 4 or 5 seconds after pressing Launch in Vortex (F4SE). I do have a Nvidia card, which is why some mods pertain specifically to that. I have gone thru Wyre Bash for both profiles and made my load order good and fixed any Missing Requirements issues.
I found out about the ESL limit and I have everything set as Light that can be. I am well under the limit for the Storywealth profile, and a little under the limit for District.
I have tried to read all installation instructions extremely carefully, so I truly do apologize if this ends up being something very dumb. I have downgraded the game at the instruction of both collections.
Thank you in advance to anyone that can, or even just tries to help. I think, like many, binging the Fallout show has reawoken a deep need to play the game, but after logging thousands of hours vanilla and only QoL mods, I want it to be relatively fresh to keep me invested (that's the only reason I picked such massive collections, knowing full well I much too stupid to likely make it work on my own haha).
If my mod list is needed (I don't know if the information is in that crash log and I just don't know I am looking at), please let me know. If I do need to post them, if you have a quick way to "copy all" on vortex, I would be greatly appreciative for the information as each collection is around 700 mods. Thank you!!
Both logs have some crash info in common and it is on meshes. I would suggest that you take a look to see if you are missing a C++ runtime as MSVCR110.dll comes up in both instances and is a Visual Studio redistritubal file. It is a dependancy that is not going to be listed in your mod launcher.
I know I went ahead and did that step but if that is a potential cause, I will try again. Maybe a file got corrupted or I clicked a wrong button. Thank you! I will let everyone know if it works so any future people with the same issue might find this helpful.
EDIT Unfortunately, that did not end up being the case. Thank you, anyway!
Buffout 4 is not coded for F4SE for Next Gen update yet. It fails to register when launched and is therefore not running until the author updates it for the new .dll registers.
It looks like you are crashing due to possibly too many .ba2 files in your load. The first error I see is (BSResource::`anonymous namespace'::LooseFileAsyncStream*) which indicates too many .ba2 archives trying to load. This tool https://www.nexusmods.com/fallout4/mods/56255 can help you read log files and narrow the problem down as well as lead to fixes.
For too many .ba2 files, you either need to make sure buffout is configured to allow more then 254 non texture .ba2 files and if you are using MO2, there is a hiccup in getting this to work, remove some .ba2 files by unpacking them into their folders (something like this https://www.nexusmods.com/fallout4/mods/82082), or download non .ba2 versions of some of your mods or just remove mods you really don't need.
BA2 Limit Crash | LooseFileAsyncStream You went over your BA2 limit, which triggers after reaching a certain number of plugins that load at least one BA2 archive. This limit is dynamic and changes based on the number of installed mods. Solution: You can unpack the smallest (in terms of bytes) Main.ba2 archives from mods with Cathedral Assets Optimizer or BSA Browser until crashing stops or you get a different crash message error. Instructions on how to unpack BA2 archives with CAO available in this article! You should also only unpack Main.ba2 archives, do not unpack Textures.ba2, since unpacked texture files usually lead to a severe performance impact. And unpack BA2s less than 10-15 MB in size. You can use TreeSize Free to figure out which mods have the smallest BA2 archives. Note that as long as you are getting the BA2 Limit Crash, you still haven’t gone under your specific BA2 limit. You have to keep unpacking BA2s until you’re no longer getting this error. Note that your BA2 limit can drastically change after unpacking or uninstalling a few mods.
FOR MODDERS / DEVS : This limit might have something to do with the file handle limit, but every attempt to determine the exact cause was met with failure. Buffout4.toml allows to change the MaxStdIO value up to 2048 (anything above causes a crash with no crash log), but this does not actually bypass the BA2 limit, sadly. After further testing, here’s everything I know for sure:
> Running f4se_loader.exe through a Mod Manager is what actually causes the BA2 Limit Crash. (Placing plugins and their BA2s directly into Fallout 4 / Data folder and directly running f4se_loader bypasses the BA2 limit! Though obviously, having mods installed like this is definitely a bad idea.)
The limit actually depends on how many plugins load at least one BA2 archive. I’ve manually created 250 empty plugins (plugin1.esp to plugin250.esp) and each had one associated BA2 archive and only one (1) file was packed into each BA2. The game would consistently crash when loading exactly 244 of these plugins while using MO2 or Vortex.
The limit does not depend on the amount or size of files packed into each BA2, nor the total amount and size of these files. I packed 100 000 files into a single BA2 and was still able to load it into the game just fine with ~300 other BA2s. And as mentioned in previous example, even loading one (exact same) file in each BA2 still causes the BA2 limit crash.
Majority of players so far are hitting their BA2 limit with a different value, though it’s usually between a total of 350 to 500 BA2s loaded by the game. Even then, some players can load their 700 BA2 setup without any problems and without any BA2 limit crashes whatsoever.
You might be able to reverse engineer the call stack address(es) mentioned in the crash logs and I’ll gladly provide them if you want to take a look. You know where to find me. I’ve already asked the Buffout 4 Dev ( Ryan / Fudgyduff ) about this, but no luck. Let me know if you have any better ideas.
I posted a crash log in the past and gave up at one point but now I'm getting this kind of one constantly after I stopped playing for a while. With the only thing I'm noticing is ""meshes\Interface/Objects/LoadScreen/LoadScreenTranslucent.nif"". Which has constantly been in every crash log ever since.
The crash happens before the main menu (like my previous comment) and I tried everything. - Removing Mods that affect the loading screen. With the exception being the mod that, through configuration, I made it so that the screens freeze in place instead of showing the 3D models later. It worked beforehand so I don't see it being the problem. - Verifying the game files. And downgrading back to the update I was on, which was the one right before the Next Gen Update. - Editing F4SE plugins. Like Buffout's config file. - Removing THIS mod's files but I just get the regular CTD without Buffout's fatal error message. - Reducing my BA2 file limit and extracting the more smaller ones manually. - Cleaning my dirty plugins with xEdit. - And where I am now. Where I restarted my PC, hoping it's a over time problem with my laptop.
When I look up LoadScreenTranslucent.nif, I get nothing but people's pastebin logs and a single reddit post that had a solution but didn't work for me. What the hell is this file and why am I thinking it's the cause of my crashes?
This appears to be related to Previsibines Repair Pack (PRP). PRP itself won't cause crashes, but it often conflicts with other mods which can cause various issues. Unless you know which mod(s) might be conflicting, your best bet would be to perform a binary search. Instructions can be found on page 4 of the Buffout 4 Dictionary.
15437 comments
you can do this by writing [ spoiler ] your crash log [ / spoiler ] it will make it a lot easier for everyone.
Crash log
Tnks
Crash log 2
I'm not 100% sure, but I think "Functional Displays" is the culprit in your case. Also from a quick look at your load order, I can already see some mods that can cause problems in the future. I hope you can solve your issues :)
I found out about the ESL limit and I have everything set as Light that can be. I am well under the limit for the Storywealth profile, and a little under the limit for District.
I have tried to read all installation instructions extremely carefully, so I truly do apologize if this ends up being something very dumb.
I have downgraded the game at the instruction of both collections.
Thank you in advance to anyone that can, or even just tries to help. I think, like many, binging the Fallout show has reawoken a deep need to play the game, but after logging thousands of hours vanilla and only QoL mods, I want it to be relatively fresh to keep me invested (that's the only reason I picked such massive collections, knowing full well I much too stupid to likely make it work on my own haha).
If my mod list is needed (I don't know if the information is in that crash log and I just don't know I am looking at), please let me know. If I do need to post them, if you have a quick way to "copy all" on vortex, I would be greatly appreciative for the information as each collection is around 700 mods. Thank you!!
District Only Profile
District
Storywealth Only Profile
Storywealth
https://next.nexusmods.com/fallout4/collections/5atq9t - Step 1 of the Storywealth guide is to install the runtime.
Find the All In One here: AIO Repack for latest Microsoft Visual C++ Redistributable
I hope this helps.
EDIT Unfortunately, that did not end up being the case. Thank you, anyway!
https://pastebin.com/J7jqjPcP
It looks like you are crashing due to possibly too many .ba2 files in your load. The first error I see is (BSResource::`anonymous namespace'::LooseFileAsyncStream*) which indicates too many .ba2 archives trying to load. This tool https://www.nexusmods.com/fallout4/mods/56255 can help you read log files and narrow the problem down as well as lead to fixes.
For too many .ba2 files, you either need to make sure buffout is configured to allow more then 254 non texture .ba2 files and if you are using MO2, there is a hiccup in getting this to work, remove some .ba2 files by unpacking them into their folders (something like this https://www.nexusmods.com/fallout4/mods/82082), or download non .ba2 versions of some of your mods or just remove mods you really don't need.
This is copied directly from the Buffout 4 Dictionary.
You went over your BA2 limit, which triggers after reaching a certain number of plugins that load at least one BA2 archive. This limit is dynamic and changes based on the number of installed mods.
Solution: You can unpack the smallest (in terms of bytes) Main.ba2 archives from mods with Cathedral Assets Optimizer or BSA Browser until crashing stops or you get a different crash message error. Instructions on how to unpack BA2 archives with CAO available in this article!
You should also only unpack Main.ba2 archives, do not unpack Textures.ba2, since unpacked texture files usually lead to a severe performance impact. And unpack BA2s less than 10-15 MB in size. You can use TreeSize Free to figure out which mods have the smallest BA2 archives.
Note that as long as you are getting the BA2 Limit Crash, you still haven’t gone under your specific BA2 limit. You have to keep unpacking BA2s until you’re no longer getting this error.
Note that your BA2 limit can drastically change after unpacking or uninstalling a few mods.
FOR MODDERS / DEVS : This limit might have something to do with the file handle limit, but every attempt to determine the exact cause was met with failure. Buffout4.toml allows to change the MaxStdIO value up to 2048 (anything above causes a crash with no crash log), but this does not actually bypass the BA2 limit, sadly. After further testing, here’s everything I know for sure:
> Running f4se_loader.exe through a Mod Manager is what actually causes the BA2 Limit Crash.
(Placing plugins and their BA2s directly into Fallout 4 / Data folder and directly running f4se_loader bypasses the BA2 limit! Though obviously, having mods installed like this is definitely a bad idea.)
- The limit actually depends on how many plugins load at least one BA2 archive. I’ve manually created 250 empty plugins (plugin1.esp to plugin250.esp) and each had one associated BA2 archive and only one (1) file was packed into each BA2. The game would consistently crash when loading exactly 244 of these plugins while using MO2 or Vortex.
- The limit does not depend on the amount or size of files packed into each BA2, nor the total amount and size of these files. I packed 100 000 files into a single BA2 and was still able to load it into the game just fine with ~300 other BA2s. And as mentioned in previous example, even loading one (exact same) file in each BA2 still causes the BA2 limit crash.
- Majority of players so far are hitting their BA2 limit with a different value, though it’s usually between a total of 350 to 500 BA2s loaded by the game. Even then, some players can load their 700 BA2 setup without any problems and without any BA2 limit crashes whatsoever.
You might be able to reverse engineer the call stack address(es) mentioned in the crash logs and I’ll gladly provide them if you want to take a look. You know where to find me.I’ve already asked the Buffout 4 Dev ( Ryan / Fudgyduff ) about this, but no luck.
Let me know if you have any better ideas.
Hope this helps.
Fallout 4 v1.10.163
Buffout 4 v1.28.6
Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x7FF7DEEF5CC0 Fallout4.exe+09E5CC0
[Compatibility]
F4EE: true
[Crashlog]
AutoOpen: true
PromptUpload: true
[Fixes]
ActorIsHostileToActor: true
CellInit: true
CreateD3DAndSwapChain: true
EncounterZoneReset: true
GreyMovies: true
MagicEffectApplyEvent: true
MovementPlanner: true
PackageAllocateLocation: true
SafeExit: true
TESObjectREFRGetEncounterZone: true
UnalignedLoad: true
UtilityShader: true
[Patches]
Achievements: true
ArchiveLimit: false
BSMTAManager: true
BSPreCulledObjects: true
BSTextureStreamerLocalHeap: false
HavokMemorySystem: true
INISettingCollection: true
InputSwitch: true
MaxStdIO: -1
MemoryManager: true
MemoryManagerDebug: false
ScaleformAllocator: true
SmallBlockAllocator: true
WorkshopMenu: true
[Warnings]
CreateTexture2D: true
ImageSpaceAdapter: true
SYSTEM SPECS:
OS: Microsoft Windows 11 Home v10.0.22631
CPU: GenuineIntel Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz
GPU #1: Nvidia GP107M [GeForce GTX 1050 3 GB Max-Q]
GPU #2: Intel CoffeeLake-H GT2 [UHD Graphics 630]
GPU #3: Microsoft Basic Render Driver
PHYSICAL MEMORY: 6.12 GB/7.84 GB
PROBABLE CALL STACK:
[0] 0x7FF7DEEF5CC0 Fallout4.exe+09E5CC0 -> 28088+0x30
[1] 0x7FF7DEEF59E5 Fallout4.exe+09E59E5 -> 947232+0x95
[2] 0x7FF7DF24CF4F Fallout4.exe+0D3CF4F -> 1525013+0x13F
[3] 0x7FF7DF246A6E Fallout4.exe+0D36A6E -> 665510+0x9CE
[4] 0x7FF7DF245947 Fallout4.exe+0D35947 -> 668528+0x17
[5] 0x7FF7E0E47157 Fallout4.exe+2937157 -> 1104651+0x143
[6] 0x7FF8B754257D KERNEL32.DLL+001257D
[7] 0x7FF8B8B4AA48 ntdll.dll+005AA48
REGISTERS:
RAX 0x1 (size_t)
RCX 0x0 (size_t)
RDX 0x66696E6E2B8BF2 (size_t)
RBX 0x7FF7E3FCC110 (void* -> Fallout4.exe+5ABC110)
RSP 0x9BED10FC50 (void*)
RBP 0x0 (size_t)
RSI 0x0 (size_t)
RDI 0x26B48B17C70 (char*) "B"
R8 0xFFFFFFFF (size_t)
R9 0x0 (size_t)
R10 0x41 (size_t)
R11 0x42 (size_t)
R12 0x0 (size_t)
R13 0x0 (size_t)
R14 0x9C0 (size_t)
R15 0x0 (size_t)
STACK:
[RSP+0 ] 0x9C0 (size_t)
[RSP+8 ] 0x7FF7E4A87CB0 (void* -> Fallout4.exe+6577CB0)
[RSP+10 ] 0x26B2F9EC180 (void*)
[RSP+18 ] 0x7FF7DEFF5AA5 (void* -> Fallout4.exe+0AE5AA5)
[RSP+20 ] 0x0 (size_t)
[RSP+28 ] 0x0 (size_t)
[RSP+30 ] 0x1 (size_t)
[RSP+38 ] 0x7FF7E055CAEB (void* -> Fallout4.exe+204CAEB)
[RSP+40 ] 0x7FF7E115A948 (void* -> Fallout4.exe+2C4A948)
[RSP+48 ] 0x9BED10FB90 (char*) "meshes\Interface/Objects/LoadScreen/LoadScreenTranslucent.nif"
[RSP+50 ] 0x0 (size_t)
[RSP+58 ] 0x9C0 (size_t)
[RSP+60 ] 0x26B48B17C70 (char*) "B"
[RSP+68 ] 0x7FF7DEEF59E5 (void* -> Fallout4.exe+09E59E5)
[RSP+70 ] 0x2 (size_t)
[RSP+78 ] 0x2 (size_t)
[RSP+80 ] 0x7FF7E3FCC110 (void* -> Fallout4.exe+5ABC110)
[RSP+88 ] 0x2 (size_t)
[RSP+90 ] 0x0 (size_t)
[RSP+98 ] 0x3D (size_t)
[RSP+A0 ] 0x26B48B17C70 (char*) "B"
[RSP+A8 ] 0x7FF7DF24CF4F (void* -> Fallout4.exe+0D3CF4F)
[RSP+B0 ] 0x2 (size_t)
[RSP+B8 ] 0x9BED10FE40 (void*)
[RSP+C0 ] 0xA (size_t)
[RSP+C8 ] 0xA (size_t)
[RSP+D0 ] 0x26B48B172B0 (void*)
[RSP+D8 ] 0xA (size_t)
[RSP+E0 ] 0x26B48B172B0 (void*)
[RSP+E8 ] 0x7FF7DF246A6E (void* -> Fallout4.exe+0D36A6E)
[RSP+F0 ] 0x321C (size_t)
[RSP+F8 ] 0x321C (size_t)
[RSP+100] 0x0 (size_t)
[RSP+108] 0x0 (size_t)
[RSP+110] 0x0 (size_t)
[RSP+118] 0x26B4BD83100 (void*)
[RSP+120] 0x0 (size_t)
[RSP+128] 0x0 (size_t)
[RSP+130] 0x73726573555C3A43 (size_t)
[RSP+138] 0x445C626B63696C5C (size_t)
[RSP+140] 0x73746E656D75636F (size_t)
[RSP+148] 0x656D614720794D5C (size_t)
[RSP+150] 0x756F6C6C61465C73 (size_t)
[RSP+158] 0x6F6C6C61465C3474 (size_t)
[RSP+160] 0x7366657250347475 (size_t)
[RSP+168] 0x696E692E (size_t)
[RSP+170] 0x7FF7E111BD60 (void* -> Fallout4.exe+2C0BD60)
[RSP+178] 0x17000 (size_t)
[RSP+180] 0x0 (size_t)
[RSP+188] 0x7FF8B60F3DAB (void* -> KERNELBASE.dll+0023DAB)
[RSP+190] 0x0 (size_t)
[RSP+198] 0x7FF7E1128670 (void* -> Fallout4.exe+2C18670)
[RSP+1A0] 0x6C420CE7F973 (size_t)
[RSP+1A8] 0x0 (size_t)
[RSP+1B0] 0x9BED10FEC0 (void*)
[RSP+1B8] 0x7FF8746843B8 (void* -> MSVCR110.dll+00243B8)
[RSP+1C0] 0x26B00000000 (void*)
[RSP+1C8] 0x26B4BBE06D0 (void*)
[RSP+1D0] 0x9BED10FED0 (void*)
[RSP+1D8] 0x0 (size_t)
[RSP+1E0] 0x4 (size_t)
[RSP+1E8] 0x7FF87468432B (void* -> MSVCR110.dll+002432B)
[RSP+1F0] 0x9BED10FEC0 (void*)
[RSP+1F8] 0x7FF86BCD7600 (void* -> Buffout4.dll+0187600)
[RSP+200] 0x26B4BD52F90 (void*)
[RSP+208] 0x301E0 (size_t)
[RSP+210] 0x9BED10FEC0 (void*)
[RSP+218] 0x7FF87469CF7F (void* -> MSVCR110.dll+003CF7F)
[RSP+220] 0x26B4BD52F90 (void*)
[RSP+228] 0x7FF86BC1E9D8 (void* -> Buffout4.dll+00CE9D8)
[RSP+230] 0x26B4BD52F90 (void*)
[RSP+238] 0x7FF700000000 (size_t)
[RSP+240] 0x0 (size_t)
[RSP+248] 0xA (size_t)
[RSP+250] 0x0 (size_t)
[RSP+258] 0x0 (size_t)
[RSP+260] 0x0 (size_t)
[RSP+268] 0x7FF7DF245947 (void* -> Fallout4.exe+0D35947)
[RSP+270] 0x26B00000000 (void*)
[RSP+278] 0x703CA (size_t)
[RSP+280] 0x664C9558 (size_t)
[RSP+288] 0x26B48B1B1DA (void*)
[RSP+290] 0x0 (size_t)
[RSP+298] 0x7FF7E0E47157 (void* -> Fallout4.exe+2937157)
[RSP+2A0] 0x26B48B1B1D9 (char*) """
[RSP+2A8] 0xA (size_t)
[RSP+2B0] 0x0 (size_t)
[RSP+2B8] 0xA (size_t)
[RSP+2C0] 0x0 (size_t)
[RSP+2C8] 0x26B48B1B1DA (void*)
[RSP+2D0] 0x0 (size_t)
[RSP+2D8] 0x7FF8B754257D (void* -> KERNEL32.DLL+001257D)
[RSP+2E0] 0x0 (size_t)
[RSP+2E8] 0x0 (size_t)
[RSP+2F0] 0x0 (size_t)
[RSP+2F8] 0x0 (size_t)
[RSP+300] 0x0 (size_t)
[RSP+308] 0x7FF8B8B4AA48 (void* -> ntdll.dll+005AA48)
[RSP+310] 0x0 (size_t)
[RSP+318] 0x0 (size_t)
[RSP+320] 0x0 (size_t)
[RSP+328] 0x0 (size_t)
[RSP+330] 0x0 (size_t)
[RSP+338] 0x0 (size_t)
[RSP+340] 0x585897E900000000 (size_t)
[RSP+348] 0x0 (size_t)
[RSP+350] 0x4F0FFFFFB30 (size_t)
[RSP+358] 0x7FF8B622CBB0 (void* -> KERNELBASE.dll+015CBB0)
[RSP+360] 0x9BED10ED00 (void*)
[RSP+368] 0xFC773D2E2C80003F (size_t)
[RSP+370] 0x7FF8EE7A5C59 (size_t)
[RSP+378] 0x9BED10ED00 (void*)
[RSP+380] 0x0 (size_t)
[RSP+388] 0x0 (size_t)
[RSP+390] 0x0 (size_t)
[RSP+398] 0x0 (size_t)
[RSP+3A0] 0x0 (size_t)
[RSP+3A8] 0x0 (size_t)
MODULES:
XINPUT1_3.dll 0x000000400000
X3DAudio1_7.dll 0x0000770C0000
steam_api64.dll 0x0000770D0000
BetterConsole.dll 0x026B50280000
wsfw_identifier.dll 0x026B5A120000
Fallout4.exe 0x7FF7DE510000
steamclient64.dll 0x7FF85F870000
gameoverlayrenderer64.dll 0x7FF861B20000
WmkActiveEffects.dll 0x7FF861DC0000
transfer_settlements.dll 0x7FF861E40000
WINHTTP.dll 0x7FF862110000
terminal+.dll 0x7FF862450000
ShadowBoostFO4.dll 0x7FF8625A0000
mcm.dll 0x7FF8628A0000
LongLoadingTimesFix.dll 0x7FF862940000
f4ee.dll 0x7FF8629D0000
nvwgf2umx.dll 0x7FF867A10000
Buffout4.dll 0x7FF86BB50000
tier0_s64.dll 0x7FF86BEB0000
vstdlib_s64.dll 0x7FF86D280000
flexRelease_x64.dll 0x7FF86F020000
nvspcap64.dll 0x7FF86F290000
HighFPSPhysicsFix.dll 0x7FF873240000
MSVCR110.dll 0x7FF874660000
VoltekLib.Detours.dll 0x7FF877C90000
GFSDK_SSAO_D3D11.win64.dll 0x7FF8782E0000
MSVCP110.dll 0x7FF878370000
nvgpucomp64.dll 0x7FF879E10000
bink2w64.dll 0x7FF87CB90000
WeaponDebrisCrashFix.dll 0x7FF87E9C0000
SprintStutteringFix.dll 0x7FF87F2A0000
cudart64_75.dll 0x7FF87F640000
GFSDK_GodraysLib.x64.dll 0x7FF87FB60000
f4se_steam_loader.dll 0x7FF8817A0000
VoltekLib.RelocationDatabase.dll 0x7FF885070000
flexExtRelease_x64.dll 0x7FF885140000
X3DAudio1_7.dll 0x7FF885780000
PowerGridTools.dll 0x7FF886600000
VoltekLib.UnicodeConverter.dll 0x7FF886E30000
Ghoulification.dll 0x7FF886E60000
deviceaccess.dll 0x7FF887AC0000
VoltekLib.MemoryManager.dll 0x7FF88C2E0000
nvldumdx.dll 0x7FF890F30000
AchievementsModsEnabler.dll 0x7FF8978B0000
OneCoreCommonProxyStub.dll 0x7FF897A90000
MSVCP140.dll 0x7FF898DF0000
COMCTL32.dll 0x7FF899860000
VCRUNTIME140_1.dll 0x7FF89B0B0000
VCRUNTIME140.dll 0x7FF89B0C0000
NvMessageBus.dll 0x7FF89C280000
Windows.UI.dll 0x7FF89E670000
nvapi64.dll 0x7FF8A0B90000
dbghelp.dll 0x7FF8A15B0000
xinput1_4.dll 0x7FF8A3200000
gdiplus.dll 0x7FF8A3960000
XAudio2_7.dll 0x7FF8A3D50000
f4se_1_10_163.dll 0x7FF8A4760000
inputhost.dll 0x7FF8A5190000
AUDIOSES.DLL 0x7FF8A5E10000
MMDevApi.dll 0x7FF8A77C0000
igc64.dll 0x7FF8A7B60000
igdgmm64.dll 0x7FF8A9ED0000
igd10iumd64.dll 0x7FF8AA0D0000
OneCoreUAPCommonProxyStub.dll 0x7FF8AB370000
drvstore.dll 0x7FF8AC460000
nvToolsExt64_1.dll 0x7FF8AC5D0000
VERSION.dll 0x7FF8AC760000
cryptnet.dll 0x7FF8AC830000
CoreUIComponents.dll 0x7FF8ADFA0000
WINMM.dll 0x7FF8AE570000
textinputframework.dll 0x7FF8AE950000
WINHTTP.DLL 0x7FF8AED70000
directxdatabasehelper.dll 0x7FF8AEEB0000
avrt.dll 0x7FF8AF9D0000
MSIMG32.dll 0x7FF8B1400000
D3DCOMPILER_47.dll 0x7FF8B17B0000
d3d11.dll 0x7FF8B24C0000
dcomp.dll 0x7FF8B2720000
CoreMessaging.dll 0x7FF8B2DA0000
apphelp.dll 0x7FF8B31E0000
UxTheme.dll 0x7FF8B3390000
dxcore.dll 0x7FF8B3470000
dxgi.dll 0x7FF8B34C0000
dwmapi.dll 0x7FF8B37A0000
resourcepolicyclient.dll 0x7FF8B3820000
wintypes.dll 0x7FF8B3C10000
windows.storage.dll 0x7FF8B3D50000
HID.DLL 0x7FF8B4650000
IPHLPAPI.DLL 0x7FF8B48B0000
Secur32.dll 0x7FF8B4C10000
rsaenh.dll 0x7FF8B4D90000
kernel.appcore.dll 0x7FF8B4E30000
ntmarta.dll 0x7FF8B4E50000
SSPICLI.DLL 0x7FF8B5090000
MSWSOCK.dll 0x7FF8B52A0000
CRYPTSP.dll 0x7FF8B5500000
CRYPTBASE.DLL 0x7FF8B5520000
wldp.dll 0x7FF8B5630000
UMPDC.dll 0x7FF8B5680000
NTASN1.dll 0x7FF8B5700000
POWRPROF.dll 0x7FF8B5740000
ncrypt.dll 0x7FF8B5790000
msasn1.dll 0x7FF8B5AA0000
devobj.dll 0x7FF8B5AC0000
CFGMGR32.dll 0x7FF8B5B10000
profapi.dll 0x7FF8B5D40000
win32u.dll 0x7FF8B5E10000
CRYPT32.dll 0x7FF8B5E40000
ucrtbase.dll 0x7FF8B5FB0000
KERNELBASE.dll 0x7FF8B60D0000
bcryptPrimitives.dll 0x7FF8B6480000
gdi32full.dll 0x7FF8B6500000
wintrust.dll 0x7FF8B6620000
bcrypt.dll 0x7FF8B6750000
msvcp_win.dll 0x7FF8B6780000
sechost.dll 0x7FF8B6820000
IMM32.DLL 0x7FF8B68E0000
imagehlp.dll 0x7FF8B6920000
SHLWAPI.dll 0x7FF8B6940000
combase.dll 0x7FF8B69B0000
msvcrt.dll 0x7FF8B6D40000
WS2_32.dll 0x7FF8B6E60000
ADVAPI32.dll 0x7FF8B6EE0000
MSCTF.dll 0x7FF8B6FA0000
shcore.dll 0x7FF8B71B0000
COMDLG32.dll 0x7FF8B72B0000
RPCRT4.dll 0x7FF8B7410000
KERNEL32.DLL 0x7FF8B7530000
OLEAUT32.dll 0x7FF8B7600000
USER32.dll 0x7FF8B76E0000
SETUPAPI.dll 0x7FF8B7890000
SHELL32.dll 0x7FF8B7D20000
PSAPI.DLL 0x7FF8B8580000
clbcatq.dll 0x7FF8B8750000
ole32.dll 0x7FF8B8880000
GDI32.dll 0x7FF8B8A80000
ntdll.dll 0x7FF8B8AF0000
F4SE PLUGINS:
BetterConsole.dll
Buffout4.dll v1.28.6
f4ee.dll
Ghoulification.dll
HighFPSPhysicsFix.dll
LongLoadingTimesFix.dll v1.1.1
mcm.dll
PowerGridTools.dll
ShadowBoostFO4.dll
SprintStutteringFix.dll v1.3
terminal+.dll
transfer_settlements.dll
WeaponDebrisCrashFix.dll v1.3
WmkActiveEffects.dll
wsfw_identifier.dll
PLUGINS:
I posted a crash log in the past and gave up at one point but now I'm getting this kind of one constantly after I stopped playing for a while. With the only thing I'm noticing is ""meshes\Interface/Objects/LoadScreen/LoadScreenTranslucent.nif"". Which has constantly been in every crash log ever since.
The crash happens before the main menu (like my previous comment) and I tried everything.
- Removing Mods that affect the loading screen. With the exception being the mod that, through configuration, I made it so that the screens freeze in place instead of showing the 3D models later. It worked beforehand so I don't see it being the problem.
- Verifying the game files. And downgrading back to the update I was on, which was the one right before the Next Gen Update.
- Editing F4SE plugins. Like Buffout's config file.
- Removing THIS mod's files but I just get the regular CTD without Buffout's fatal error message.
- Reducing my BA2 file limit and extracting the more smaller ones manually.
- Cleaning my dirty plugins with xEdit.
- And where I am now. Where I restarted my PC, hoping it's a over time problem with my laptop.
When I look up LoadScreenTranslucent.nif, I get nothing but people's pastebin logs and a single reddit post that had a solution but didn't work for me. What the hell is this file and why am I thinking it's the cause of my crashes?
https://pastebin.com/SEttAiSi
Crashes on startup right before title screen.
https://pastebin.com/GcQyXJnB
https://pastebin.com/3RN3T1MB
i need help with what to do
Crash Log:
https://pastebin.com/zNbR4eag