GRA Challenge "Nyah! See?" Broken-- mod conflict?

[Frozenwolf150]

I could have sworn I did all that last time. It happened again, so I'll provide the details.

 

From the Windows Event Viewer, the log for the particular crash doesn't have any information more specific than:

 

 

Log Name: Application
Source: Application Hang
Date: 8/18/2017 10:19:23 AM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: Home
Description:
The program FalloutNV_4GB.exe version 1.4.0.525 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 4114
Start Time: 01d318278c6c76ef
Termination Time: 3
Application Path: C:\Program Files (x86)\Steam\SteamApps\common\Fallout New Vegas\FalloutNV_4GB.exe
Report Id: 422ec95b-dbc0-434a-ac2b-ea451d06fcda
Faulting package full name:
Faulting package-relative application ID:

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-08-18T14:19:23.292062500Z" />
<EventRecordID>20425</EventRecordID>
<Channel>Application</Channel>
<Computer>Home</Computer>
<Security />
</System>
<EventData>
<Data>FalloutNV_4GB.exe</Data>
<Data>1.4.0.525</Data>
<Data>4114</Data>
<Data>01d318278c6c76ef</Data>
<Data>3</Data>
<Data>C:\Program Files (x86)\Steam\SteamApps\common\Fallout New Vegas\FalloutNV_4GB.exe</Data>
<Data>422ec95b-dbc0-434a-ac2b-ea451d06fcda</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>

 

 

This time though, falloutnv_error.log did have something unusual. The following messages were repeated multiple times leading up to the crash, although not necessarily in this order.

 

 

 

Audio: Could not open file data\sound\fx\fol\powerarmor_walkrun\

MODELS: Could not get file for texture textures\characters\facemods\aworldofpain(preview).esm\f00000019_00055ce5_0.dds.
MODEL ERROR: Could not find file 'RagdollConstraint\default.rdt'.
MODELS: Could not get file for texture textures\characters\mouth\mouthraider_n.dds.
MODELS: Could not get file for texture textures\characters\mouth\teethlowerraider_n.dds.
MODELS: Could not get file for texture textures\characters\mouth\teethupperraider_n.dds.
MODELS: Could not get file for texture textures\characters\mouth\tongueraider_n.dds.

AI: Could not initialize FootIK system for Cazador.
AI: Could not initialize FootIK system for Black Wasp.

AI: Could not initialize FootIK system for Huge Yellow Jacket.

 

 

 

I've noticed one of the most frequent circumstances where a crash is involved is when the game attempts to load a cell where it either has to re-randomize the Monster Mod creatures, or remember the specific dead Monster Mod creatures for maps I've just cleared out. When these maps do load correctly, there's sometimes a half second delay before the creatures appear properly. I've uninstalled a few of my other mods, and the frequent crashes didn't start occurring until after I'd installed Monster Mod. Though I'm not familiar enough to know how to interpret those error messages above.

[dubiousintent]

From that eventlog I see you have the game installed to the default "C:\Program Files (x86)" folder tree. Please read the "Installing Games on Windows Vista+" article in my signature and move it. Lots of mysterious problems are resolved simply by getting out of the "system protected" areas of "Program Files". Take heart from the fact that Steam no longer installs there as the default location; as validation that this was a bad practice.

 

The Windows Eventlog error is reporting that the game is hanging: "win10 Application event 1002 error 0x80000000000000". "Stopped interacting" is another way of saying "hung". Unfortunately it does not give any indication as to the solution. Looking at past reports on the web, sometimes it is caused by Windows updates or lack of same. You should look at any other errors in the Eventlog and take what measures you can to eliminate them.

 

Windows system updates automatically create a "Windows restore checkpoint" after installing. You might want to try reverting to the checkpoint before the last one and see if your problem goes away. That is a reasonable indication that you are having a problem related to a recent update. In which case you might want to wait until the next update to see if they correct the problem.

 

The "missing files" entries in "falloutnv_error.log" are warnings. The game proceeds without those files. You will find that the FalloutNV.ESM has a number of such errors. Nothing you can really do about them.

 

-Dubious-

[Frozenwolf150]

From that eventlog I see you have the game installed to the default "C:\Program Files (x86)" folder tree. Please read the "Installing Games on Windows Vista+" article in my signature and move it. Lots of mysterious problems are resolved simply by getting out of the "system protected" areas of "Program Files". Take heart from the fact that Steam no longer installs there as the default location; as validation that this was a bad practice.

 

I've heard that advice before, but at the time I installed the game, that was the default directory and I assumed there was nothing wrong with it. I didn't want to uninstall and reinstall the entire game just to change the directory. Is there a way to move it without going through the entire process?

[dubiousintent]

Steam (and a lot of other developers) made the same assumption, and have been proven wrong.

 

As for any shortcut to the process, afraid not. You need to have the registry point to the correct (new) location, and the only way to ensure that is to follow the process and reinstall.

 

You can copy your "Data" folder elsewhere first, and then replace the newly installed one with the old one as long as your mod manager can be corrected to point to the right locations as well. As far as the game is concerned, everything mod related is "relative" to the "Data" or "Game" folder, so the parent path doesn't matter to them.

 

It's a pain in the rear I know, but it will never be any easier to do than now.

 

-Dubious-