Jump to content

williamlee

Supporter
  • Posts

    9
  • Joined

  • Last visited

Nexus Mods Profile

About williamlee

williamlee's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter

Recent Badges

0

Reputation

  1. The "CreateDXGIFactory2" error is to my understanding linked to a sweetfx compartment of some enbs, specifically to dxgi.dll. It is a proxy for DirectX 10 and 11. I got the same error too after updating to Geforce driver 355.82 and was able to "fix" it by simply renaming dxgi.dll to dxgi_backup.dll. Of course this disables sweetfx, but the graphical impact was not too big in the "Seasons of Skyrim" enb. The effect might be greater in some others so just rolling back the drivers might be best in some cases. I have to be honest though, I was pretty sure this issue was caused by windows updates that came on the same day (and was too lazy to test rolling back the drivers), but fortunately this is not the case, so we have the option of rolling back if needed. Thank you for the great information, good to have alternative fixes and let's hope Nvidia fixes this issue soon. :)
  2. For the injector version to work, you have to start the injector program separately, if I recall correctly, otherwise it won't have an effect in your game. As for the wrapper version, have you disabled all of your overlay programs, e.g. Steam overlay and things like MSI Afterburner, those will crash your game with the wrapper version of the enb. You might wan't to make sure that settings in your enblocal.ini are correct for you system too, if you haven't already. Hope this helps :)
  3. If you did everything according to the instructions, it should be installed correctly. Make sure that you have also disabled all of the overlays and other possible conflicting software, e.g. steam overlay, xbox overlay, MSI afterburner, Rivatuner Statistics Server, etc. Other than that, you should check that your enblocal.ini settings are correct for your setup. S.T.E.P. wiki and ENBseries forums can be of help when configuring it, if you don't possess the knowledge yourself. Hope this helps! :smile:
  4. I would suggest checking your load order, for ENB related crashes occur when starting the game, not while playing it. :smile: Other than that, I would suggest that you check the same things that I have described below. Did you change your load order after installing Windows 10? Did you clean install or just upgrade? If you just upgraded, make sure to get the Windows 10 drivers for chipset, LAN, GPU and audio devices. I don't see really that old versions for some of those would cause problems with the game, but they sure are not optimal for your computer. If you cannot find/don't feel confident installing drivers, get at least the GPU driver. :smile: If the problem persists (and you haven't clean installed) you could try to clean install your Windows 10. Make sure to back up your important files before this! Hope this helps :smile:
  5. I need to add to your comment because the instructions are incomplete. After following that link it gives a download for directx_Jun2010_redist.exe, which asks you for a location to unpack the files. Give it a temporary location, then find the files that were unpacked and run the DXSETUP.exe. This is what actually installs the DirectX 9 components that ENB needs to start without crashing. I'm on a fresh install of Windows 10 also and I was ready to flip the table over after struggling with this for at least 3 hours. Good clarification! I thought this would be pretty clear but if one has never installed DirectX redist packages then it might not be. I'll add this to the first post so that everyone can see it (with credits of course ;3).
  6. Hmm, interesting. My CPU doesn't even have an integrated GPU so I guess this is problem can be caused by various different things then. Well, great that we have now a few different fixes for different configurations. :)
  7. Thanks for the responses, glad I could help :smile:. Installing the DirectX 9.0c does _NOT_ replace your DirectX 12. The installer looks for components in the installation that need updating. DirectX 12 includes (or it is supposed to at least) all of the previous DirectX versions like 9.0c. Boris pointed out in one of the forum threads I came across while doing research that some updates don't include all of the files though, even though they might be needed for certain applications like enbhost.exe. The disclaimer in the first post is just to say that how you act is your responsibility and I don't want the wrath of people if they somehow managed to screw it up, though that should be pretty hard. D: After installing the DirectX 9.0c redist update linked above, DxDiag still reports DirectX version to be DirectX 12, if that acts as a proof. :D Just wanted to clarify this, for ENB has so many benefits, including ENBoost and it really add to the stability. Also for many of us running 144hz or 120hz monitors, ENB is basically a must for it is an easy and safe option for locking fps to 60. Hope this helps! :3
  8. Hello! First of all, I don't know if this damages somehow the built in DirectX 12 installation of Windows 10 but I think it doesn't and don't see the reason how it would for DirectX installers do check if components of the installations need to be updated and don't replace the whole installation. Still, if you somehow damage your Windows 10 installation or hardware by doing this, I am not responsible. So, I made a clean install of Windows 10 after upgrading to it. After getting all of the drivers and other software installed, I installed Skyrim and restored my mod setup. When I tried to boot the game, it would crash instantly, before the Bethesda logo. This could be fixed by deleting the d3d9.dll binary that is required for ENBs, so it clearly was not a load order issue (as it shouldn't have been as my load order was identical to the load order on Windows 7 installation). Well, first I tried to install the injector version of the ENB. That got me through the Bethesda logo, but crashed after that. The fix that worked for me, so I could run the wrapper version of ENB was to install the DirectX End-User Runtimes (June 2010) from Microsofts official website. https://www.microsoft.com/en-us/download/details.aspx?id=8109 There is the link for it. I haven't posted to these forums much, so I am not sure actually if we are allowed to post links, so moderators feel free to edit the post if it is against the rules and apologies for the inconvenience. D: And if the link is removed, you can find the right page (Microsoft's official website) by googling "DirectX End-User Runtimes (June 2010)", at the time of writing this. After following the link it gives a download for directx_Jun2010_redist.exe, which asks you for a location to unpack the files. Give it a temporary location, then find the files that were unpacked and run the DXSETUP.exe. This is what actually installs the DirectX 9 components that ENB neets to start without crashing. (Thanks for this clarification to Realfriend) As this is getting rambly, I hope that I helped at least someone. It took me 8 hours of stressful googling and not finding a solution. Somebody in the ENBseries forums had posted half a year ago that he had had some very similar crashing with a preview build of Windows 10 and had installed DirectX 9.0c to fix this. As the web installer DirectX 9.0c versions are unsupported on Windows 10, at least for me it popped an error, and those seem to come up very easily when searching for DirectX 9.0c, this information didn't solve the problem for me, put it pointed me to the right direction so credits to him, I guess. :3 Thanks for reading and have fun with Skyrim on Windows 10! :3
×
×
  • Create New...