Aza12345678910 Posted December 27, 2018 Share Posted December 27, 2018 So, whenever I load into a new area or save the game, my screen goes black and it says my display driver crashed. This is very strange considering it only happens in Fallout New Vegas. I've tried reinstalling my drivers and a couple of other fixes, and they all did not work. I'd greatly appreciate any insight into this issue. Here's my load order in case anyone is interested. Load Order:FalloutNV.esmDeadMoney.esmHonestHearts.esmOldWorldBlues.esmLonesomeRoad.esmGunRunnersArsenal.esmClassicPack.esmMercenaryPack.esmTribalPack.esmCaravanPack.esmYUP - Base Game + All DLC.esmoHUD.esmSomeguySeries.esmInterior Lighting Overhaul - Core.esmAWorldOfPain(Preview).esmNVInteriors_Core.esmNVInteriors_ComboEdition_AWOP.esmRustTownV1Master.esmdomecity.esmThe New Bison Steve Hotel.esmAWOPDeadMoney.esmD.E.I.M.O.S..esmInterior Lighting Overhaul - L38PS.esmYUP - NPC Fixes (Base Game + All DLC).espThe Mod Configuration Menu.espCentered 3rd Person Camera.espSorter - Combined.espBoostedSkills.espRustTownAdditions3.espFellout.espWeaponModsExpanded.espWMX-DLCMerged.espWMX-ModernWeapons.espWMX-POPMerged.espAWOPDeadMoneyVendorPatch.espNewVegasBounties.espNewVegasBountiesII.espNewVegasBountiesIII.espAlternative Repairing.espAlternative Repairing - Honest Hearts.espAlternative Repairing - Lonesome Road.espEasy Hacking.espFellout-OWB.espfriendofnightforfellout.espGoodspringsPlayerHome.espMiscItemIconsNV.espPerkEveryLevel.espBooneSilentRifle.espUniversal Air Tank.espUniversal Air Tank- Honest Hearts.espUniversal Air Tank- Lonesome Road.espUniversal Air Tank- Rebreather Replacer.espUniversal Air Tank- Space Suit Water Breathing.espILO - PipBoy Light.espILO - Rust Town 2.espILO - YUP Patch.espInterior Lighting Overhaul - Ultimate Edition.espILO - A World of Pain.espILO - D.E.I.M.O.S.espILO - GS Shack.espILO - New Vegas Bounties II.espILO - New Vegas Bounties.espILO - NVInteriors Project - AWOP.espGlove_be_gone.esp Link to comment Share on other sites More sharing options...
HeyYou Posted December 28, 2018 Share Posted December 28, 2018 Might want to try and OLDER driver version...... Link to comment Share on other sites More sharing options...
dubiousintent Posted December 30, 2018 Share Posted December 30, 2018 Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article. I recommend you read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to mod FNV or it's been more than a year since you last did so. * "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than all of the plugins they are designed to make compatible. ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. "LOOT" does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Masters" errors as well. Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as if you are using a "regional language version" of the game; using the FNV4GB Patch, NVSE and it's related plugins; replacements for textures (specifically their larger image sizes: 1024x1024, etc.), animations, or "bodies", etc.; and "post-processors" like ENB or SweetFX. It saves us playing "20 questions" and gets you a more specific answer more quickly. (The usual turn-around on post and reply in an older game forum is 24 hours.)* See "How to markup images (etc) in forum posts and comments" article for how to use "Spoiler tags". Assuming you are running on Windows 10, the following entries in the wiki 'Fallout NV Mod Conflict Troubleshooting' guide specifically address known problems with that OS:* 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)'* 'Issue: Incomplete save game load' (NVSR related)* 'Issue: Vanilla game Hangs on startup'; specifically "Cause-1" regarding DirectX9 drivers.* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'* 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play'* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed (or not)'. In particular "Cause-4" regarding video card settings. The latest video drivers may not be the best suited to an older game like FNV. All vendors drop testing of old games at some point. Backwards compatibility is never guaranteed, much less "optimization". Also, "Cause-7" regarding "Superfetch" and "File search indexing". Windows updates will often reset these back on.* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'* 'Issue: ENB Support for Windows versions later than Win7'* 'Issue: Problems using ENB/SweetFx on Windows 10' -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts