Jump to content

Photo

JIP LN NVSE causing crash to desktop on the bethesda splash screen.

fallout new vegas nvse

  • Please log in to reply
5 replies to this topic

#1
RedFlamedragon

RedFlamedragon

    Stranger

  • Members
  • Pip
  • 3 posts

Hey so, I'd normally never ask for help because I generally know what I'm doing with modding, though if it turns out this is an easy fix I'll definitely need to rethink that. Anyway, I recently had to upgrade my pc with a new HDD and OS upgrade to Windows 10 Home.

 

I started to reinstall my FNV mods when suddenly It started to crash - to make a long story short I have reinstalled fresh twice, uninstalled all my mods and got it back to working when Vanilla. I'm now in the process again of remodding, so I've installed NVSE, the Tick Fix, YUP and the 4gb Patch. I've launched the game and tested and these all work fine, and they're the most up to date versions.

 

However, when I try to install and run the JIP LN NVSE Plugin, it causes an instant crash to desktop upon the bethesda splash screen, and I am honestly dumbfounded. I've found nothing online of people encountering the same problem. I'm stuck and have no idea what to do.

 

this is my current load order:

  0  0     FalloutNV.esm
  1  1     DeadMoney.esm
  2  2     HonestHearts.esm
  3  3     OldWorldBlues.esm
  4  4     LonesomeRoad.esm
  5  5     GunRunnersArsenal.esm
  6  6     ClassicPack.esm
  7  7     MercenaryPack.esm
  8  8     TribalPack.esm
  9  9     CaravanPack.esm
 10  a     YUP - Base Game + All DLC.esm
 11  b     YUP - NPC Fixes (Base Game + All DLC).esp

Thanks.



#2
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 8,878 posts

Please see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

In particular, note that with Win10 you will need to install the DirectX 9.0 DLLs because the game is looking for those specific files.  It knows nothing about "compatibility" in later versions.  Similar can be said about other tools that use specific DLLs, such as JIP LN NVSE.  Check the requirements for specifics.

 

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.
 

-Dubious-


Edited by dubiousintent, 05 April 2020 - 11:39 AM.


#3
RedFlamedragon

RedFlamedragon

    Stranger

  • Members
  • Pip
  • 3 posts

So, I tried to look for the error message in the event log, but it only comes up with errors related to the Nexus Mod Manager community version, which I uninstalled and started using Vortex. I don't know if those would be relevent, but the game still crashes even when using Vortex, especially with JIP. Also, I ran the Directx9 installer and tried to run the game with the JIP LN NVSE Plugin, and the game still crashed. Running it with mods while having JIP disabled works fine. I seriously don't know what I've done wrong.

 

Thanks again.



#4
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 8,878 posts

Make sure you have the correct Visual C Redistributable updates for Win 10.  With an older game, the "latest" are not always the best suited. Look for [support.microsoft.com/en-us/help/3179560/update-for-visual-c-2013-and-visual-c-redistributable-package].  Others have reported that this alone has caused problems between a Win7 to Win10 upgrade.

 

It is not uncommon to have multiple versions of redistributable DLL libraries installed at the same time.  Just make sure you have the correct "bitness" (32 vs 64-bit) for the game in question.  I personally make it a habit to install both at the same time.

 

The errors for the game might be in either the "Application" or the "System" event logs.  Always check both.

 

-Dubious-



#5
RedFlamedragon

RedFlamedragon

    Stranger

  • Members
  • Pip
  • 3 posts

Thank you so much! I fixed it! It was due to what I can assume was the Visual C Redistributables. I basically found an installer on majorgeeks.com that installed every Visual C Redis there was, and it seems to have fixed the JIP LN NVSE problems I was having. Without your input, I would have never guessed that was the problem.

 

Again, thank you so much.



#6
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 8,878 posts

Glad it solved your problem.  This is the second recent instance where that (or at least some older) VC redistributeable solved the CTD.

 

-Dubious-







Also tagged with one or more of these keywords: fallout new vegas, nvse

IPB skins by Skinbox
Page loaded in: 1.164 seconds