General Crash problems post-Mod-Organizer

[Ragnarok101]

SOLVED:

 

Installing the latest C++ Visual Redistributable fixed it for me: I also deleted some old x86 versions that were inhabiting my computer, it seems to have fixed the problem.

 

My take:

Outdated version conflicted with mods, and worked via KERNELBASE.dll and ntdll.dll to shut down FNV at random moments. Once updated this was no longer the case.

[dubiousintent]

Thanks for reporting your solution. Not having the "correct" libraries is not easy to detect. Just another reason it's important to keep them updated.

 

Just a point of interest: Libraries for x86 (32-bit) and x64 (64-bit) are BOTH necessary. They are not interchangeable and reside in different paths. (I make it a point to always download both.) Usually the older versions are safe to leave in place, because some programs still need them. They actually check the version number (either internally or externally). For an example of this, see "Cause-1" in the "Issue: Vanilla game Hangs on startup" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the DirectX library.

 

-Dubious-

[Ragnarok101]

Thanks for reporting your solution. Not having the "correct" libraries is not easy to detect. Just another reason it's important to keep them updated.

 

Just a point of interest: Libraries for x86 (32-bit) and x64 (64-bit) are BOTH necessary. They are not interchangeable and reside in different paths. (I make it a point to always download both.) Usually the older versions are safe to leave in place, because some programs still need them. They actually check the version number (either internally or externally). For an example of this, see "Cause-1" in the "Issue: Vanilla game Hangs on startup" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the DirectX library.

 

-Dubious-

Umm...

Okay, it's not C++.

It popped up again, I read the logs of the SYNTAX errors...it looks more like 2 mod (The North Road and The Living Desert) were causing it. Once I uninstalled them the game has run fine.

I think the error-fixing ability of Merge Plugins might've been used on them at some point (I think I was trying to fix a different error) and that borked it up? Dunno.

[dubiousintent]

Use Merge Plugins Standalone. It is much better the the earlier "Merge Plugins" script in FNVEdit. I played through "The North Road" without any major problems. But it does conflict with "War Zones" in the area of "Corn Creek".

 

Don't attempt to merge "compatibility patches" together with the main parent (e.g. "The North Road"). Do not attempt to merge "quest" mods either. Certainly not two different quest mods together into one merge plugin. It can be done with the optional plugins for a parent plugin, but is a magnitude harder than merging several patch files into one I am told.

 

-Dubious

[Ragnarok101]

Use Merge Plugins Standalone. It is much better the the earlier "Merge Plugins" script in FNVEdit. I played through "The North Road" without any major problems. But it does conflict with "War Zones" in the area of "Corn Creek".

 

Don't attempt to merge "compatibility patches" together with the main parent (e.g. "The North Road"). Do not attempt to merge "quest" mods either. Certainly not two different quest mods together into one merge plugin. It can be done with the optional plugins for a parent plugin, but is a magnitude harder than merging several patch files into one I am told.

 

-Dubious

 

Uninstalled the mods, and problems have cropped up again. I'm thinking it actually is a registry issue on my computer at this point...

 

EDIT:

 

Okay, restarted my computer after running sfc /scannow and the DISM thing...it seems to be stable for the moment. Will reply here if any more problems crop up.

Edited June 6, 2018 by Ragnarok101

[dubiousintent]

Okay. I'll see any further posting.

 

FYI: The Eventlog errors "around the time" of the crashes are not directly related to the game, and while you should be investigating the "errors" as opposed to the "Warnings", as something you like to resolve, there do not appear to be something that will help with the game stability. But you never know just what is causing a problem "behind the scenes", which is why you want to clean up errors when you become aware of them., Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article for what you want as your "key word search" on the the Internet..

-Dubious-

[Ragnarok101]

Okay, it popped up again.

Searching on the Internet, it's likely NVidia or New Vegas itself causing the problem, NVidia and it's drivers being the most likely. Will install latest drivers from there, report back on what happens. If NVidia fails, will reinstall New Vegas and work from there.

 

EDIT: At this point this topic belongs more on the 'Technical Support' subforum given that it probably isn't the mods actually causing it...

 

EDIT EDIT: Alright, NVidia driver complete replacement seems to have worked. Nope, not that either. It feels like a pattern: first opening of game after restarting computer, everything works fine. Second time round without restarting, it fails.

Edited June 7, 2018 by Ragnarok101

[Ragnarok101]

Still kicking around even after a repair install.

07233410 _ NewVegasAntiCrash FalloutNV.exe

07233410 _ 08820000 07050000 nvac.dll

07233410 _ 0D800000 05010040 nvse_1_4.dll

07233410 _ 770D0000 0A0042EE ntdll.dll

07233632 h 00A5DDF1 8B068B90 FalloutNV.exe

07233632 h 00A5DDF3 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DDFF

07233632 r 00A5DDFF 00000000 FalloutNV.exe

07233632 h 00A5DDFF 8B462085 FalloutNV.exe

07233632 h 00A5DDF3 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DDFF

07233632 r 00A5DDFF 00000000 FalloutNV.exe

07233632 m 33333F33 00A5DDFF

07233632 r 00A5DDFF 00000000 FalloutNV.exe

07233632 h 00A5DE0C 83780C00 FalloutNV.exe

07233632 h 00A5DE81 8B068B90 FalloutNV.exe

07233632 h 00A5DE83 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DE8F

07233632 r 00A5DE8F 00000000 FalloutNV.exe

07233632 h 00A5DEA3 8B762085 FalloutNV.exe

07233632 h 00A5DE81 8B068B90 FalloutNV.exe

07233632 h 00A5DE83 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DE8F

07233632 r 00A5DE8F 00000000 FalloutNV.exe

07233632 h 00A5DEA3 8B762085 FalloutNV.exe

07233632 h 00A5DE81 8B068B90 FalloutNV.exe

07233632 h 00A5DE83 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DE8F

07233632 r 00A5DE8F 00000000 FalloutNV.exe

07233632 h 00A5DEA3 8B762085 FalloutNV.exe

07233632 h 00A5DE81 8B068B90 FalloutNV.exe

07233632 h 00A5DE83 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DE8F

07233632 r 00A5DE8F 00000000 FalloutNV.exe

07233632 h 00A5DEA3 8B762085 FalloutNV.exe

07233632 h 00A5DE81 8B068B90 FalloutNV.exe

07233632 h 00A5DE83 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DE8F

07233632 r 00A5DE8F 00000000 FalloutNV.exe

07233632 h 00A5DEA3 8B762085 FalloutNV.exe

07233632 m 8BFC4D89 00A5DE8F

07233632 r 00A5DE8F 00000000 FalloutNV.exe

07233632 h 00A5DE81 8B068B90 FalloutNV.exe

07233632 h 00A5DE83 8B90A400 FalloutNV.exe

07233632 n 00000000 00A5DE8F

07233632 r 00A5DE8F 00000000 FalloutNV.exe

07233632 h 00A5DEA3 8B762085 FalloutNV.exe

07233632 m 20656882 00082065

07233632 r 00A5DE8F 00000005 FalloutNV.exe

07233632 h 00A5DEB0 837E0C00 FalloutNV.exe

07233632 h 00A5DEB0 837E0C00 FalloutNV.exe

07233632 h 0019FA54 84950B40

07233632 m 0019FA5A C098C7B3

07233632 r 00493CF7 00000004 FalloutNV.exe

07233632 a 0055945A 00493CFA FalloutNV.exe

07233632 h 00493D00 8B4DDC83 FalloutNV.exe

07233632 a 0055945A 00493D06 FalloutNV.exe

07233632 h 00A5C004 8B730C57 FalloutNV.exe

07233632 a 0055945A 00493D15 FalloutNV.exe

07233632 h 00493D1B 8B45DC8B FalloutNV.exe

07233632 h 00493D1E 8B480CE8 FalloutNV.exe

07233632 h 00A5C004 8B730C57 FalloutNV.exe

07233632 h 00493D26 C645FC00 FalloutNV.exe

07233632 h 0045CEC0 83390074 FalloutNV.exe

07233632 h 00493D32 C745FCFF FalloutNV.exe

07233632 h 0045CEC0 83390074 FalloutNV.exe

07233632 h 00493D41 8B4DF464 FalloutNV.exe

And here's the event viewer:

Faulting application name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed

Faulting module name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed

Exception code: 0xc0000005

Fault offset: 0x00093d4e

Faulting process id: 0x2a58

Faulting application start time: 0x01d3fed9901fce56

Faulting application path: C:\games\steam\steamapps\common\Fallout New Vegas\FalloutNV.exe

Faulting module path: C:\games\steam\steamapps\common\Fallout New Vegas\FalloutNV.exe

Report Id: 41324de7-9fec-4d03-9eb9-5162308d0a32

Faulting package full name:

Faulting package-relative application ID:

Suggestions?

[dubiousintent]

Believe it or not, you are making progress. New error messages mean you have gotten past earlier problems. Don't get discouraged.

Those are a lot of NVAC errors pointing to "Fallout.exe" as the source. So to start with you need to look for patterns in the "type" codes:

* "h" entries are exceptions identified Heuristically by NVAC's "global" exception handler, sometimes handled unsuccessfully.
* "n" entries are Null pointer call exceptions, sometimes handled unsuccessfully.
* "r" entries are informative, relaying the next Return address.
* "m" entries are "Middle of nowhere" exceptions, sometimes handled unsuccessfully.

And that's all. The vast majority of them are "h" codes, which means something that NVAC has decided is an error and it's telling the game to ignore it instead of CTD. That's one of the major benefits of using NVAC, so don't panic over it. The others are similar in nature: handled by NVAC to prevent CTDs, but as they all say, "sometimes unsuccessfully". That seems to be case here. Which leads us to the Windows Exception code.

"Windows Exception code: 0xc0000005". The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source. Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running. Run AV from multiple sources when checking for infections.

Solve that error code and most likely the NVAC errors will disappear. Go back to my first reply to you. Referenced that same solution there. Resolving the NTDLL.DLL file problem made progress. But it apparently hid yet another similar issue. See the bullet point about "Meltdown and Spectre Vulnerabilities". Fair chance you need to employ that fix.

If not, try any of the other bullet points you skipped because you thought they didn't apply. Also, search for more recent reports on the "Exception code: 0xc0000005" error for Win10.

-Dubious-

[Ragnarok101]

Okay, thus far:

Installed Sheson's patch and compensated for the patch re: Meltdown/Spectre, as instructed. Didn't accomplish anything.

 

Tested memory, it's fine. scannow and DISM bring up no problems.

I think it's the NVidia drivers still, am rolling back to the January version....

Well, rolling back drivers just brings back the problem with KERNELBASE.dll...fun...

 

08224845 _ NewVegasAntiCrash FalloutNV.exe

08224845 _ 038B0000 07050000 nvac.dll

08224845 _ 0D800000 05010040 nvse_1_4.dll

08224845 _ 77680000 0A0042EE ntdll.dll

08225040 m 6166206C 0019F830

08225040 r 0085317A 00000001 FalloutNV.exe

08225040 h 00853165 8B420450 FalloutNV.exe

08225040 m 00000008 0085317A

08225040 r 0085317A 00000000 FalloutNV.exe

08225040 h 00853193 8B118955 FalloutNV.exe

08225040 h 27732529 02040706

08225040 h 2773253D 03030202

08225040 m 27732567 3F88002B

08225040 r 005675E7 00000003 FalloutNV.exe

08225040 h 27732529 02040706

08225040 h 2773253D 03030202

08225040 m 27732567 3F88002B

08225040 r 005675E7 00000003 FalloutNV.exe

08225040 m 61662083 005C0760

08225040 r 005C0760 00000000 FalloutNV.exe

08225040 h 005C0760 8B08894D FalloutNV.exe

08225040 h 005C0765 8B500489 FalloutNV.exe

08225040 h 005C076B 8B400889 FalloutNV.exe

08225040 h 00484E97 8B008945 FalloutNV.exe

08225040 a 0072607A 00484E9F FalloutNV.exe

08225040 M 5039E3C0 C0000096

08225040 r 00575B5D 00000000 FalloutNV.exe

08225040 U 76D2D722 E06D7363 KERNELBASE.dll

08225040 ^ 00ECD240 0000000F FalloutNV.exe

So, bets on this being a corrupt user profile and me having to move everything?