Jump to content

Generalized CTD issue


Surtr564

Recommended Posts

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: 0x3124
Faulting application start time: 0x01d65c4a893294aa
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: 1865e1f4-1ff7-4372-b14d-e641af022795
Faulting package full name:
Faulting package-relative application ID:

That's the Log at the moment of the crash.
Link to comment
Share on other sites

No one has an answer how to fix that exception other than "buy this" or "download that".

 

I caved. I bought a "fixer", that also has all those other bells and whistles, I ran it. It dected the exception.
It added the option to fix it.

So I did.

I open up the game, load the save, open the door to the Vikki and Vance, it loads. I am pleased.

Then I run my litmus test, entering Lt Hayes' tent.

You can probably guess where I am going.

It crashed.

I run the fixer again, and who do I see there but my good old friend Fallout NV.

 

So I go to Steam to revalidate the files. It tells me I have 19 files that are less than kosher. Wait for the download, patch it with the 4gb patch. Run it again.

Crash trying to enter the tent.

Fix it again.

Crash again.

 

18174517 _ NewVegasAntiCrash FalloutNV.exe
18174517 _ 04400000 07050000 nvac.dll
18174517 _ 0B670000 05010060 nvse_1_4.dll
18174517 _ 772C0000 06011DB0 ntdll.dll
18174530 e 0047CF1E C0000005 FalloutNV.exe
18174530 _ LEVELED_ LIST_ERR
18174530 e 0047CF1E C0000005 FalloutNV.exe
18174530 _ LEVELED_ LIST_ERR
18174530 e 0047CF1E C0000005 FalloutNV.exe
18174530 _ LEVELED_ LIST_ERR
18174530 e 0047CF1E C0000005 FalloutNV.exe
18174530 _ LEVELED_ LIST_ERR
18174530 e 0047CF1E C0000005 FalloutNV.exe
181745~
TRUNCATE _
18174532 _ LEVELED_ LIST_ERR
18174532 e 0047CF1E C0000005 FalloutNV.exe
18174532 _ LEVELED_ LIST_ERR
18174532 e 0047CF1E C0000005 FalloutNV.exe
18174532 _ LEVELED_ LIST_ERR
18174707 e 00E8C00D C0000005 FalloutNV.exe
18174707 r 00E8C9A9 00E8C00D FalloutNV.exe
18174707 h 00E8CD2E 8B0E8B51 FalloutNV.exe
18174707 h 00E8CD30 8B513056 FalloutNV.exe
18174707 n 00000000 00E8CD36
18174707 r 00E8CD36 00000000 FalloutNV.exe
18174716 q 00E8CD54 C0000409 FalloutNV.exe
18174716 _ CRASHSAV E_THREAD FalloutNV.exe
18174716 ! CRASHSAV E_FAIL_0 FalloutNV.exe
NVAC log is different, at least. I guess that's something.
Log Name: Application
Source: Application Error
Date: 7/18/2020 5:47:10 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: 0x2ac4
Faulting application start time: 0x01d65d65de92ac72
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: a889b9b2-bedc-4e91-8207-2064d7d7bfb6
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-07-19T00:47:10.304908300Z" />
<EventRecordID>66738</EventRecordID>
<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>2ac4</Data>
<Data>01d65d65de92ac72</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>a889b9b2-bedc-4e91-8207-2064d7d7bfb6</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Link to comment
Share on other sites

You are now seeing multiple errors (still including those "Windows Exception code: 0xc0000005" errors), but now they are not immediately stopping the process and you are getting the additional info:

 

18174530 e 0047CF1E C0000005 FalloutNV.exe
18174530 _ LEVELED_ LIST_ERR
Repeated 6 times.
That suggests to me you have a mod which is improperly handling "leveled lists", eventually leading to the crash. Please see the 'Mod Conflict Isolation' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.
ENBoost simply allocates some of your 8GB of "system RAM" for the use of the "graphics system memory" to reduce stutter. Think of is as a "supplement" to the Graphics VRAM; slower than VRAM but faster than the hard drive. It isn't going to hurt the game to use It, but it's not going to help with CTDs or "hangs".

-Dubious-
Link to comment
Share on other sites

19132410 _ NewVegasAntiCrash FalloutNV.exe

19132410 _ 03CB0000 07050000 nvac.dll

19132410 _ 07300000 05010060 nvse_1_4.dll

19132410 _ 77C70000 06011DB0 ntdll.dll

19132801 e 00E8C00D C0000005 FalloutNV.exe

19132801 r 00E8C9A9 00E8C00D FalloutNV.exe

19132801 h 00E8CD2E 8B0E8B51 FalloutNV.exe

19132801 h 00E8CD30 8B513056 FalloutNV.exe

19132801 n 00000000 00E8CD36

19132801 r 00E8CD36 00000000 FalloutNV.exe

19132805 q 00E8CD54 C0000409 FalloutNV.exe

19132805 _ CRASHSAV E_THREAD FalloutNV.exe

19132805 ! CRASHSAV E_FAIL_0 FalloutNV.exe


Good News is, I got rid of the Leveled List errors, I made a Patch Plugin with FNVEdit and manually resolved every conflict in a manner I figured would be the most optimal.

Bad news is, it's still giving me that same 0xc0000005 error and the crash is still that 0xc0000409.


Does using the BSA Decompressor help in any way?

Link to comment
Share on other sites

The BSA files are not the source of your CTD problem (because they work fine for everyone else). Unpacking them is not going to do your crash problem any good.

 

The "level list" fixes is all to the good and will improve your game. But both those remaining "hex code" errors are "Windows system exceptions". (The "005" is "attempting to access invalid memory" and the "409" is a "stack overflow", which are typical of "corrupted memory" due to another program managing to write where it isn't supposed to. Which is something the DEP/WDEG settings are intended to prevent by default.) As I mentioned in my first reply, those exceptions tend to report the "victim" of the problem (i.e. "Fallout.exe") rather than the cause. This makes them very frustrating to resolve, but the game itself is not likely the culprit now.

 

How are you coming on clearing up any other "errors" in your Windows Eventlog? One or more of those are potential sources of corrupting memory.

 

-Dubious-

Link to comment
Share on other sites

Did a repair of Windows, ran the DISM RestoreHealth, ran sfc/scannow, have "fixed" the error with Advanced System Repair Pro at least a dozen times...

 

20174138 _ NewVegasAntiCrash FalloutNV.exe
20174138 _ 0B6B0000 07050000 nvac.dll
20174138 _ 07000000 05010060 nvse_1_4.dll
20174138 _ 77810000 05010A28 ntdll.dll
20174257 e 00E8C00D C0000005 FalloutNV.exe
20174257 r 00E8C9A9 00E8C00D FalloutNV.exe
20174257 h 00E8CD2E 8B0E8B51 FalloutNV.exe
20174257 h 00E8CD30 8B513056 FalloutNV.exe
20174257 n 00000000 00E8CD36
20174257 r 00E8CD36 00000000 FalloutNV.exe
20174300 q 00E8CD54 C0000409 FalloutNV.exe
20174300 _ CRASHSAV E_THREAD FalloutNV.exe
20174300 ! CRASHSAV E_FAIL_0 FalloutNV.exe
...and the bastard keeps crashing.
All I can think now is either making a clean install, uninstalling the game from steam, deleting the folders in Steam and My Documents, and trying again.
And if this happens again, well, just put the goddamned game in the thresher and forget I spent weeks trying to make it work.
At least I learned a lot about how to fix a lot of other issues on my pc...I guess.
Link to comment
Share on other sites

Ah, hadn't seen your reply.

I've been checking the event log around the time of the crash and any error I see I search to look for a fix.

Then I restart the laptop, try again, crash again, see the event log, see the same error glaring at me.

And a lot of errors linked to the fact that the freeware AV I have running as a first line of defense is deactivated and keeps trying to turn on.

 

I think I'll uninstall it.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...