Jump to content
  • 0

d3d9.dll instant CTD (Skyrim LE ENB v0.377)


Vaneglorious

Question

Hello.

 

I've a problem with the ENB in Skyrim LE - d3d9.dll causes instant ctd upon opening launcher, and (0xc000001d) error code upon launching the exe or skse_loader.

 

I've had this problem before, and installing older direct X libraries solved it before, but not this time. I've been googling for hours now, nothing seems to work. At one point I used to injector version, and that worked after a lot of trial and error, and then it just didn't after relaunching the game, and I didn't change anything. Tried admin rights, compatibility modes, all that stuff. Nothing worked.

 

This was all after reinstalling Windows 10 Pro and restoring a backup of Skyrim + mods (Mod Organizer), which has worked before, but not this time.

 

Any ideas would be appreciated.

Edited by Vaneglorious
Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0

If you installed Windows 10 fresh, you need to install the June 2010 DirectX 9 runtime using the link in the "Install" section of the ENBoost guide:

https://wiki.step-project.com/ENBoost

 

You can also find some instructions for installing DirectX in the LOTD guide:

https://wiki.step-project.com/User:Darth_mathias/SRLE_Extended_Legacy_of_The_Dragonborn_Prerequisites

 

Check the properties of TESV.exe, SkyrimLauncher.exe and skse_loader.exe (File Explorer, select the file, right click, Properties) and disable Compatibility mode if it is enabled. Enabling compatibility mode for any of these three executables is known to cause a CTD with this error code so you need to ensure compatibility mode is disabled for all of them.

Link to comment
Share on other sites

  • 0

If you installed Windows 10 fresh, you need to install the June 2010 DirectX 9 runtime using the link in the "Install" section of the ENBoost guide:

https://wiki.step-project.com/ENBoost

 

You can also find some instructions for installing DirectX in the LOTD guide:

https://wiki.step-project.com/User:Darth_mathias/SRLE_Extended_Legacy_of_The_Dragonborn_Prerequisites

 

Check the properties of TESV.exe, SkyrimLauncher.exe and skse_loader.exe (File Explorer, select the file, right click, Properties) and disable Compatibility mode if it is enabled. Enabling compatibility mode for any of these three executables is known to cause a CTD with this error code so you need to ensure compatibility mode is disabled for all of them.

I did mention in my original post that I've already done all of that. It worked the last time, but not this time, and I've no idea why. Installed the DX9 runtime twice, rebooted, tried launcher, tesv and skse_loader exes with and without compatibility modes.

Link to comment
Share on other sites

  • 0

Hey everyone, 

So with regards to this issue, I was experiencing it myself and nothing was working. 

 

I noticed somehow, that my computer wasn't picking up my AMD graphics card (at least for my monitor) 

 

Long story short ladies and gents, two days ago I changed out my HDMI to HDMI cable to a  VGA/HDMI 

 

when I did this, my computer treated it as if i was adding an ADDITIONAL monitor as opposed to just changing the cord and assigned this 'additional monitor' to my default intel graphics card 

 

As soon as i changed back to my previous cord (hdmi to hdmi) i was able to run skyrim again with the d3d9.dll file no problem 

 

so if you have changed the cords you are using to connect your monitors recently, change them back to what they were before. If your system allocates the monitor you are trying to play skyrim on to your systems default graphics card (in my case it was the Intel R core 4590) then skyrim will not be able to even get to the logo before crashing. 

 

You need to make sure that your monitor is registering your gaming graphics card. to do that check out this video https://www.youtube.com/watch?v=FHCYoVB8P_Y at around 9:58 in

 

Someone far more tech savvy than I am may be able to fill you in on how to allocate your existing monitor to your gaming specific graphics card as opposed to whatever your system default is if this is the case 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.