Jump to content

"Program has stoped working"


X1Wetwork1X

Recommended Posts

So my Fallout:NV just wont start a new game, and I keep getting kicked out of the full screen and a "Program has stopped working" popup happens.It reads"FalloutNV has stopped working A program has caused the program to stop working correctly. Windows will close the program and notify you if a solution is available".(This only happens when I tried to load a save, or start a new game) I couldn't load any of my old saves, so I deleted them and decided to start a new game. But I cant seem to figure out why this error keeps happening. I've also tried FNV edit and nothing seems to come up. I'll put my load order below. I have NVSE and FNV 4GB installed as well, and I use NMM. I'm new to pc gaming and using mods, so sorry for any stupid errors I may have made.

 

GameMode=FalloutNV
FalloutNV.esm=1
TribalPack.esm=0
MercenaryPack.esm=0
ClassicPack.esm=0
CaravanPack.esm=0
DeadMoney.esm=1
HonestHearts.esm=1
OldWorldBlues.esm=1
LonesomeRoad.esm=1
GunRunnersArsenal.esm=1
JIP Selective-Fire.esm=1
Caliber.esm=1
FCOMaster.esm=1
Interior Lighting Overhaul - Core.esm=1
NVStripOpen.esm=1
Project Nevada - Core.esm=1
Project Nevada - Cyberware.esp=1
Project Nevada - Rebalance.esp=1
FreesideOpen.esm=1
NevadaSkies.esm=1
CompanionInfAmmo.esm=1
NVR-Strip.esm=1
YUP - Base Game + All DLC.esm=1
Weapons.of.the.New.Millenia.esm=1
rePopulated Wasteland.esm=1
The Weapon Mod Menu.esp=1
Dead Money - Automatic Rifle fix.esp=1
Vz61 Ver1.1.esp=1
vz58(No CaliberX).esp=1
vz58.esp=1
Type89v4.esp=1
Type64.esp=1
MosinNagant.esp=1
M40a5.esp=1
Ww2K98.esp=1
Glock17.esp=1
ClassicCombatShotgun.esp=1
Classic10mmSMG.esp=1
Classic10mmPistol.esp=1
GS Barrett 95.esp=1
Type38 arisaka.esp=1
AK_AR15WP.esp=1
LeverActionFireRateFix.esp=1
GunRunnersArsenal Integration Mod.esp=1
Readius_NV.esp=1
The Mod Configuration Menu.esp=1
FCO - NPC Changes.esp=1
FCO - OHSB NPC Edits.esp=1
populatedcasino-medium.esp=0
Project13 - Populated Wasteland.esp=0
Vurt's WFO.esp=1
dD - Enhanced Blood Main NV.esp=1
EVE FNV - ALL DLC.esp=1
Interior Lighting Overhaul - Ultimate Edition.esp=1
FNV Realistic Wasteland Lighting - Reduced Sunlight.esp=1
PipBoyLight.esp=1
Tutorial Killer.esp=1
StripOpenMain.esp=1
Sprint Mod.esp=1
Simple Reputation and Disguises.esp=1
Project Nevada - Dead Money.esp=1
Project Nevada - Gun Runners' Arsenal.esp=1
Project Nevada - Honest Hearts.esp=1
Project Nevada - Lonesome Road.esp=1
Project Nevada - Old World Blues.esp=1
FreesideOpenPatch.esp=1
PerkEveryLevel.esp=1
NevadaSkies - Basic Edition.esp=1
NevadaSkies - Ultimate DLC Edition.esp=1
CAGE 1.9.3.2.esp=1
XFO - 6aa - Epic Skills - Effects Over 100 (NVSE req).esp=1
UnlimitedCompanions.esp=1
CompanionInfAmmoCheat.esp=1
CompanionInfAmmoOptional.esp=1
NVR-NPCs.esp=1
NVR-Version_10.esp=1
YUP - NPC Fixes (Base Game + All DLC).esp=1
YUP - Hunting Rifle texture patch.esp=1
Desert Ranger Armor Fix.esp=1
Ranger Armor Fix.esp=1
Riot Armor Fixes.esp=1
Delay DLC - DM + HH + OWB + LR + GRA.esp=1
Riot Gear Upgrade.esp=1
Sneak Sight Disabler.esp=1
GRA WRP Compatibility Patch.esp=1
M1897.esp=1
S-Ranger Pack.esp=1
Simple Saves.esp=1
Colt N99 10mm.esp=1
BinocularUpgrade.esp=1
Mission Mojave - Ultimate Edition.esp=0
Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp=1
Real Recoil.esp=1
MMUE-CP-EVE.esp=1
MMUE-CP-rePopulated.esp=1
Reload Sounds.esp=1
WotNM-CalXVer5-Patch-WhiskeyCustom.esp=1
WotNM-CalXVer5-Patch.esp=1
WotNM+HeffyAnim-CalXVer5-Patch-WhiskeyCustom.esp=1
WotNM+HeffyAnim-CalXVer5-Patch.esp=1
Weapons.of.the.New.Millenia.Store.LITE.esp=1
Weapons.of.the.New.Millenia.Store.esp=1
Weapons.of.the.New.Millenia.Leveled.Lists.esp=1
Weapons.of.the.New.Millenia.Cheat.Cabinet.esp=1
AK_AR15WP_Tasha_Ext.esp=1
Link to comment
Share on other sites

Did you try to start the game before you added any mods? In particular, did you run the vanilla launcher and configure your hardware and exit at the Main Menu (which saves your "Prefs" file) before installing FNV4GB or mods?

 

Which version of Windows are you running? There are some errors in Windows 10 device drivers that can prevent the game from starting. The "New Vegas Anti-Crash" (NVAC) mod as of v7.5.0.0 (released 25 Oct 2016) has been reported to fix the conflict with the latest video drivers from nVidia and AMD.

 

Have you checked the Windows "Event Viewer" for errors under the "System" or "Applications" filters? (See this article on reporting Windows Errors.)

 

Did you enable the game logfile in NVSE, and have you checked those logs for any errors? (See item 4 in the "Checklist" of the "Fallout NV Mod Conflict Troubleshooting" guide.)

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

Did you try to start the game before you added any mods? In particular, did you run the vanilla launcher and configure your hardware and exit at the Main Menu (which saves your "Prefs" file) before installing FNV4GB or mods?

 

Which version of Windows are you running? There are some errors in Windows 10 device drivers that can prevent the game from starting. The "New Vegas Anti-Crash" (NVAC) mod as of v7.5.0.0 (released 25 Oct 2016) has been reported to fix the conflict with the latest video drivers from nVidia and AMD.

 

Have you checked the Windows "Event Viewer" for errors under the "System" or "Applications" filters? (See this article on reporting Windows Errors.)

 

Did you enable the game logfile in NVSE, and have you checked those logs for any errors? (See item 4 in the "Checklist" of the "Fallout NV Mod Conflict Troubleshooting" guide.)

 

-Dubious-

 

 

I appreciate the help, and I apologize for the late response. I tried disabling all mods and using the vanilla shortcut, but when I do this it crashes when I press play.

I cant seem to find the NVSE logs...

My current Windows version is 1607 of Windows 10, 64 bit.

I have NVAC in NMM. I don't know if it still works that way.

I fount the error report on Windows Event Viewer.
It says,
Log Name: Application
Source: Application Error
Date: 11/16/2016 7:48:18 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: TS-27
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: 0xc0000005
Fault offset: 0x0006158a
Faulting process id: 0x1fa4
Faulting application start time: 0x01d2406c47da13ab
Faulting application path: D:\Steam DND\steamapps\common\Fallout New Vegas\FalloutNV.exe
Faulting module path: D:\Steam DND\steamapps\common\Fallout New Vegas\FalloutNV.exe
Report Id: 5754f560-6472-4362-9e6b-9e742e2471d4
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="2016-11-17T00:48:18.209123000Z" />
<EventRecordID>578</EventRecordID>
<Channel>Application</Channel>
<Computer>TS-27</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>c0000005</Data>
<Data>0006158a</Data>
<Data>1fa4</Data>
<Data>01d2406c47da13ab</Data>
<Data>D:\Steam DND\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>
<Data>D:\Steam DND\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>
<Data>5754f560-6472-4362-9e6b-9e742e2471d4</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Again, thank you for your help.
Edited by X1Wetwork1X
Link to comment
Share on other sites

"Exception code: 0xc0000005" generally means the program is trying to access memory outside of the space allocated to it. It's one of the most common errors seen. In this case it appears the game is failing to start as a result. Right now I would suspect recent video drivers or Win10 updates developed using the current WDDK to be the cause, which the latest (Nov 2016) Win10 updates should fix. Try that system update first. Then see this article under "application was unable to start correctly" on other things to do to fix it.

 

-Dubious-

Link to comment
Share on other sites

  • 2 weeks later...

The November 2016 updates to Win10 fixed the problems with the latest drivers. Have you updated?

 

"Disabling mods" is a reasonable first step, but it doesn't always get you back to a "vanilla" game. If everything else has failed, your best bet is to run the "verify local files" option from the Steam Client Library screen (which will take you back to "vanilla"), and start from the vanilla launcher to see if you still get the same Window Event Viewer message. You may want to try renaming both the INI files in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder before you "verify" files, and let the game rebuild them when you use the vanilla launcher.

Note that if you are currently or have used "Mod Organizer", MO uses its own copies of "Fallout.ini" and "FalloutPrefs.ini" (from when the MO profile was created), located in "\Steam\steamapps\common\Fallout New Vegas\Mod Organizer\profiles\<Your Profile Name>". These files need to be changed as well.

 

See this section of the "Fallout NV Mod Conflict Troubleshooting" guide for the most common solutions to problems getting the game to start.

 

If you can't get the vanilla game to start, it certainly isn't going to work with mods. If you tried setting DEP to exclude the FNV executable as suggested in the article I referenced in my previous post, and it still didn't work, then you need to speak with Steam support about it.

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

  • 4 weeks later...
  • Recently Browsing   0 members

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