Meeres

CTD. And when using the Skyrim Launcher to change some settings, like turning off antialiasing, it automatically sets to low settings. I'm thinking there's more to it though. I've been playing around with it and there are more problems cropping up, which leads me to believe something is messed up in my system and not MO or ENBseries, so I'll just have to approach it from that angle. Thanks for the input thus far, I do appreciate it.

So I don't know a whole lot about how to interpret things like the MO logs, but I just looked through the most recent one (injector through MO, then SKSE) and found this line: This was in the section where it was injecting to the skse loader. What comes to mind is the problem with the directory. There shouldn't be two backslashes before TESV.exe. I have no idea what could be the cause of that.

I took your advice and switched to these programs instead of Symantec -- still having the same problem. I also gave reinstalling MO a try, without any results. I added my Skyrim folder to their exclusion lists as well. Yeah, I try to check that ini just about every time I try and start the game haha. It's definitely set to the right GPU. This just keeps getting more and more bizarre to me.

I use Symantec. Does it commonly cause issues like this?

I edited the ini, but still had the same issue. Here's the log:

Alright. I did it with as many options as possible, so it was too long to paste under a spoiler. This was the order: -Launched injector outside of MO, launched SKSE -Launched injector from MO, launched SKSE -Removed skse_loader process from injector ini -Launched injector outside of MO, launched TESV.exe -Launched injector outside of MO, launched SkyrimLauncher.exe (this worked) -Launched injector from MO, launched TESV.exe -Launched injector from MO, launched SkyrimLauncher.exe (this worked) I'm using .308 -- I can only assume that the appearance of the white copyright text for the enb series showing up during the game startup is how I know if it's working or not. If not then this is one silly venture, lol. mologs.txt

Still nothing. I made sure to run it as administrator as well, even though my account is an admin account and I turned off UAC.

My specs: Alienware 17 Processor: Intel® Core i7-4710MQ CPU @ 2.50GHz 16GB RAM Windows 7, 64-bit Integrated card: Intel® HD Graphics 4600 Dedicated card: NVIDIA GeForce GTX 880M With that out of the way... I'm having issues getting the ENBInjector to work with Mod Organiser. I'm not using the wrapper version because the d3d9.dll is a problem for me. I have searched for quite a while (days) for a solution but I've found nothing that seems to be working. Nor am I new at modding. I've just begun the journey of starting fresh. (I couldn't tell you what I had working before. It's really been a couple of years before I've done anything with Skyrim.) I'm currently testing on a new profile within MO to see if I can get the injector to work. I've put the injector into my Skyrim directory (which is not in Program Files), and have the appropriate .ini files set up for ENBoost. But that's when it gets weird. I set up the injector as an executable within MO, but it only actually... well, injects, when I launch the Skyrim Launcher from MO. Launching TESV.exe directly will not work, neither will launching SKSE. This profile is, at the moment, entirely empty save for USLEEP, SkyUI, and iHud while I test this. I was only able to get it to go this far by placing a shortcut to MO in my Skyrim directory and setting it as the first process the injector has to go through (as seen in the attached .ini). So, to recap as concisely as possible: -Profile in MO only has USLEEP loaded. No other mods at this time. -ENBInjector launched from MO. -Game detects the injector when I launch the Skyrim Loader, also from MO. -Game does not detect injector when I launch TESV.exe from MO. -Game does not detect injector when I launch SKSE from MO. what do enblocal.ini enbinjector.ini