X1Wetwork1X Posted November 16, 2016 Share Posted November 16, 2016 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=1TribalPack.esm=0MercenaryPack.esm=0ClassicPack.esm=0CaravanPack.esm=0DeadMoney.esm=1HonestHearts.esm=1OldWorldBlues.esm=1LonesomeRoad.esm=1GunRunnersArsenal.esm=1JIP Selective-Fire.esm=1Caliber.esm=1FCOMaster.esm=1Interior Lighting Overhaul - Core.esm=1NVStripOpen.esm=1Project Nevada - Core.esm=1Project Nevada - Cyberware.esp=1Project Nevada - Rebalance.esp=1FreesideOpen.esm=1NevadaSkies.esm=1CompanionInfAmmo.esm=1NVR-Strip.esm=1YUP - Base Game + All DLC.esm=1Weapons.of.the.New.Millenia.esm=1rePopulated Wasteland.esm=1The Weapon Mod Menu.esp=1Dead Money - Automatic Rifle fix.esp=1Vz61 Ver1.1.esp=1vz58(No CaliberX).esp=1vz58.esp=1Type89v4.esp=1Type64.esp=1MosinNagant.esp=1M40a5.esp=1Ww2K98.esp=1Glock17.esp=1ClassicCombatShotgun.esp=1Classic10mmSMG.esp=1Classic10mmPistol.esp=1GS Barrett 95.esp=1Type38 arisaka.esp=1AK_AR15WP.esp=1LeverActionFireRateFix.esp=1GunRunnersArsenal Integration Mod.esp=1Readius_NV.esp=1The Mod Configuration Menu.esp=1FCO - NPC Changes.esp=1FCO - OHSB NPC Edits.esp=1populatedcasino-medium.esp=0Project13 - Populated Wasteland.esp=0Vurt's WFO.esp=1dD - Enhanced Blood Main NV.esp=1EVE FNV - ALL DLC.esp=1Interior Lighting Overhaul - Ultimate Edition.esp=1FNV Realistic Wasteland Lighting - Reduced Sunlight.esp=1PipBoyLight.esp=1Tutorial Killer.esp=1StripOpenMain.esp=1Sprint Mod.esp=1Simple Reputation and Disguises.esp=1Project Nevada - Dead Money.esp=1Project Nevada - Gun Runners' Arsenal.esp=1Project Nevada - Honest Hearts.esp=1Project Nevada - Lonesome Road.esp=1Project Nevada - Old World Blues.esp=1FreesideOpenPatch.esp=1PerkEveryLevel.esp=1NevadaSkies - Basic Edition.esp=1NevadaSkies - Ultimate DLC Edition.esp=1CAGE 1.9.3.2.esp=1XFO - 6aa - Epic Skills - Effects Over 100 (NVSE req).esp=1UnlimitedCompanions.esp=1CompanionInfAmmoCheat.esp=1CompanionInfAmmoOptional.esp=1NVR-NPCs.esp=1NVR-Version_10.esp=1YUP - NPC Fixes (Base Game + All DLC).esp=1YUP - Hunting Rifle texture patch.esp=1Desert Ranger Armor Fix.esp=1Ranger Armor Fix.esp=1Riot Armor Fixes.esp=1Delay DLC - DM + HH + OWB + LR + GRA.esp=1Riot Gear Upgrade.esp=1Sneak Sight Disabler.esp=1GRA WRP Compatibility Patch.esp=1M1897.esp=1S-Ranger Pack.esp=1Simple Saves.esp=1Colt N99 10mm.esp=1BinocularUpgrade.esp=1Mission Mojave - Ultimate Edition.esp=0Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp=1Real Recoil.esp=1MMUE-CP-EVE.esp=1MMUE-CP-rePopulated.esp=1Reload Sounds.esp=1WotNM-CalXVer5-Patch-WhiskeyCustom.esp=1WotNM-CalXVer5-Patch.esp=1WotNM+HeffyAnim-CalXVer5-Patch-WhiskeyCustom.esp=1WotNM+HeffyAnim-CalXVer5-Patch.esp=1Weapons.of.the.New.Millenia.Store.LITE.esp=1Weapons.of.the.New.Millenia.Store.esp=1Weapons.of.the.New.Millenia.Leveled.Lists.esp=1Weapons.of.the.New.Millenia.Cheat.Cabinet.esp=1AK_AR15WP_Tasha_Ext.esp=1 Link to comment Share on other sites More sharing options...
dubiousintent Posted November 16, 2016 Share Posted November 16, 2016 (edited) 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 November 16, 2016 by dubiousintent Link to comment Share on other sites More sharing options...
Ladez Posted November 16, 2016 Share Posted November 16, 2016 Latest updates for Windows 10 has reportedly fixed the crashing issues people have been having. If you're on Windows 10, make sure that your system is fully updated. Link to comment Share on other sites More sharing options...
dubiousintent Posted November 16, 2016 Share Posted November 16, 2016 Latest updates for Windows 10 has reportedly fixed the crashing issues people have been having. If you're on Windows 10, make sure that your system is fully updated.Noted. Thanks. -Dubious- Link to comment Share on other sites More sharing options...
X1Wetwork1X Posted November 17, 2016 Author Share Posted November 17, 2016 (edited) 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: ApplicationSource: Application ErrorDate: 11/16/2016 7:48:18 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: TS-27Description:Faulting application name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50edFaulting module name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50edException code: 0xc0000005Fault offset: 0x0006158aFaulting process id: 0x1fa4Faulting application start time: 0x01d2406c47da13abFaulting application path: D:\Steam DND\steamapps\common\Fallout New Vegas\FalloutNV.exeFaulting module path: D:\Steam DND\steamapps\common\Fallout New Vegas\FalloutNV.exeReport Id: 5754f560-6472-4362-9e6b-9e742e2471d4Faulting 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> <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 November 17, 2016 by X1Wetwork1X Link to comment Share on other sites More sharing options...
dubiousintent Posted November 17, 2016 Share Posted November 17, 2016 "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 More sharing options...
X1Wetwork1X Posted November 29, 2016 Author Share Posted November 29, 2016 Ive tried everything that article suggests, aswell as uninstall it from steam. And I checked and i do have windows 10 updated. Would Uninstaling it and deleting all saves and mods work at this point? Link to comment Share on other sites More sharing options...
dubiousintent Posted November 29, 2016 Share Posted November 29, 2016 (edited) 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 November 29, 2016 by dubiousintent Link to comment Share on other sites More sharing options...
X1Wetwork1X Posted December 27, 2016 Author Share Posted December 27, 2016 Thank you for all of your help, that seemed to fix it. Link to comment Share on other sites More sharing options...
Recommended Posts