Generalized CTD issue

[Surtr564]

Log Name: Application

Source: Application Error

Date: 7/20/2020 7:15:58 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: LAPTOP-AHJHLJG3

Description:

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: 0xc0000409

Fault offset: 0x00a8cd54

Faulting process id: 0x3328

Faulting application start time: 0x01d65f049a658e14

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: 3f321b45-73e4-4e99-b72c-74803b6e70af

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 Error" />

<EventID Qualifiers="0">1000</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>100</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2020-07-21T02:15:58.3204686Z" />

<EventRecordID>741</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>Application</Channel>

<Computer>LAPTOP-AHJHLJG3</Computer>

<Security />

</System>

<EventData>

<Data>FalloutNV.exe</Data>

<Data>1.4.0.525</Data>

<Data>4e0d50ed</Data>

<Data>FalloutNV.exe</Data>

<Data>1.4.0.525</Data>

<Data>4e0d50ed</Data>

<Data>c0000409</Data>

<Data>00a8cd54</Data>

<Data>3328</Data>

<Data>01d65f049a658e14</Data>

<Data>C:\Games\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>

<Data>C:\Games\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>

<Data>3f321b45-73e4-4e99-b72c-74803b6e70af</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

This is literally the only error in it's timeframe.

No other error, a few ESENT warnings I'm told are normal when updating Windows...

...there is no other error in the log...not within that timeframe.

It does look like a clean install is the only choice left, otherwise I'll just be wasting time.

[dubiousintent]

That "409" error is most likely due to corrupted Windows system file(s). In which case a "clean install" of FNV will not help. What you need to do is a Windows Repair install, which will preserve your "user" data files, but will mean you need to re-install Windows Updates. The "step-by-step" procedure is laid out here.

 

-Dubious-

[Surtr564]

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: 0xc0000409

Fault offset: 0x00a8cd54

Faulting process id: 0x3040

Faulting application start time: 0x01d6610def43791e

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: 734f6d14-7f17-4d56-acf2-30c12b5fc21f

Faulting package full name:

Faulting package-relative application ID:

It did nothing.

I did the Windows Repair Install, took most of yesterday, and it still crashes in the same place.

I am literally at the end of my rope.

[Surtr564]

So, if anyone is interested, the Vikki and Vance issue has been solved. Turns out the mesh for one of the outfits, specifically the Female Wasteland Wanderer outfit, got corrupted somehow, it caused an immediate CTD when equipped to a "living" actor, or so I suspect since I cannot remember how I obtained it, if it was a female corpse or a male one, so I had to fix it using Outfit Studio and "create" it with BodySlide.

Now it doesn't crash when equipped and at least that CTD is solved.

And that does give me a hint that maybe the crashes around NCR related places have to do with a similar thing.

[Surtr564]

Dubious, thank you kindly for your help, while it did not solve my fundamental problem, it has made my experience and my laptop run more smoothly.

And less malware is always good.

 

It was the meshes. For some ungodly reason, the NCR Trooper, MP and Fatigues were causing the game to CTD.

 

Maybe some other outfits will crop up with those same issues.

 

But now I can double and triple check them.

 

So thank you kindly, for your patient advice.

 

And thank all who took the time to see if they too could find an issue or an answer.

[dubiousintent]

Congratulations on resolving your problem, and thanks on reporting the solution. That really helps others.

 

Every mod or it's update is a potential source of problems. Which is why it is critical to install them one at a time and TEST each one separately, immediately after installing. If you have the disk space, then keep a "vanilla" copy of the game just for that purpose before you try to include it in your current game session. (You can rename the "Data" folder under the same game folder without causing problems: e.g. "Data" to/from "Data-Test" and "Data-Current").

 

Now go have some fun!

 

-Dubious-

Edited July 25, 2020 by dubiousintent