Starfighter08

Does anybody know how to deal with access violations as described above? For the record: I did not delete anything. It was a clean install.

I tried v0.262 once with Real Vision ENB and then just with ENBoost, and the same with v0.264, With Phinix ENB and just with ENBoost. Neither worked. I verified the files through steam but that didn't help either. Afterwards I still couldn't launch the game with ENBoost but also not even without it anymore.

I have already done all of that with the exception of windowed mode and injection version. It works before I install ENBoost v0.264, but afterwards it keeps crashing. Windowed mode didn't help. Which files do I need from the injector Version?

I run Skyrim through MO using SKSE. It crashes to desktop almost immediately after launch. I don't get to the screen that lets you start a new game or load a saved one. I don't use TESV.exe.

It still crashes. Since ENBoost is an integral part of every ENB preset and I'm having trouble with ENBoost, that result isn't exactly surprising. I was still hoping it would work anyway. No, I didn't. As a matter of fact I re-installed Skyrim, Mod Organizer, the 3rd Party extensions and ENBoost from scratch again (third time is apparently not the charm). All I did was following STEP up to the point of installing ENBoost. That does include cleaning the Update.esp though. Does that file include meshes and textures? Btw, thanks for taking the time to read and interpret the minidumps for me. Much appreciated.

Above link now also contains Skyrim.ini, SkyrimPrefs.ini, enbseries.ini, enblocal.ini and SKSE.ini

O.k. Let's see if I manage to give you access to them with this link: https://onedrive.live.com/redir?resid=1CDD7548643921E5!143&authkey=!AAQcj6RrIfHsHDk&ithint=folder%2cdmp Edit: If I didn't completely fail at this OneDrive thingy, you should have access to one folder with three minidump files in it. Nothing more, nothing less.

I added [Debug] WriteMinidumps=1 into the SKSE.ini as recommended by the STEP Installation and Configuration guide and it created a report. Unfortunately I don't know how to read the .dmp format of the file and I'm not allowed to upload it. I also doubt that I could Interpret the message. Can somebody help, please?

I'm using MO and ENBoost 0.264. I assume I installed MO and SKSE correctly because I followed the tutorial videos to the letter. Besides, it's no longer the first time I'm doing it. Since I couldn't get it to work, I also tried to install Phinix ENB according to gopher's video (yes, he uses NMM) but that didn't fix the problem, so I tried to revert back to ENBoost 0.264. At least I know that I managed to make that one work at one point. Btw, is there a good "uninstall" feature/procedure for ENBs? I just opened the zip file again and manually removed all files in the Skyrim folder that also appear in the zip file. That might be where I messed up this time, though I didn't find any leftover files when retracing my steps. The source of my troubles has to be ENB related, otherwise even if MO or SKSE or LOOT etc. was completely messed up, at least vanilla Skyrim would still work. But it only does when I delete the three ENB files in the Skyrim directory.

I was there, but I'm back again, so to speak. I finally got it to work, but then I decided to try some non STEP approved mods and ENBs and made a complete mess of it. So I decided to restart from scratch. Unfortunately I now have the same problem as before. ENBoost causes an immediate CTD after launch through SKSE and vanilla reaches the Bethesda logo, where again I see the white text from the ENB dev and then it crashes. Since I never found out what the problem was before, I just re did the skyrim and prefs and enblocal ini files but the problem persists. I'm fast running out of things to try.

It works now. I reinstalled SKSE, ENB and rewrote the skyrim.ini and skyrimpreferences.ini from scratch. I thought that I had done everything right but apparently that wasn't the case. Odds are that it was an ini problem. I'd like to thank everybody who contributed to this thread. This is a great community.

I reinstalled ENBoost accorting to the instructions here and haven't touched an ENB Preset but it's still crashing to desktop. Another hunch, I removed the ENB files and started the game through MO/SKSE and it worked. I reached the main screen where you can start a new game. I'm now sure that it's ENB specific trouble. Maybe a Moderator could move this thread over there.

According to the warning in the detailed instructions, I shouldn't install full ENB but just ENBoost memory managemnt. Which I for some reason thought was being done by following the relatively short instructions there. The link to the ENB site seemed like an afterthought, so I ignored it. Apparently that was a mistake since I still have to do the actual installation of ENBoost itself. Let's see how that goes. In regards to presets (I now understand what that means) I'm undecided between Real Vision and Phinix Natural. Does Real Vision work with v0.264? If so I can go ahead and install the Memory Management and delay the decision. It sounds like MO Profiles would be a good way to try both. Always assuming of course that they both work with v0.264 which would mean that I don't need two separate STEP Core basic profiles.

I don't understand what the bolded part means, I followed the detailed instructions and put the three files from the wrapper version of enbseries_skyrim_v0264 into the Skyrim directory and modified the ini file. Nozzer, I lowered memory to 10240 but vanilla and STEP Skyrim both still crash.

On a hunch I removed the ENB files d3d9.dll, enbhost.exe, enblocal.ini (and there was a new file: enbseries.ini which I did not copy from the archive) from the Skyrim directory and now vanilla Skyrim lauches just as it should. Did I misunderstand the instructions (wouldn't be the first time) when I placed them in the same folder as the vanilla Skyrim exe file? I also put the SKSE files skse_1_9_32.dll, skse_loader.exe and skse_steam_loader.dll into the Skyrim directory. They do belong there, right? I downloaded ENB again and copied the new files into the Skyrim directory and modified the enblocal.ini as instructed but now vanilla Skyrim crashes again and the SKSE version still doesn't load. Maybe it's the enblocal.ini modification. I calculated VideoMemorySizeMb=17408, based on 16 GB system RAM and 3 GB VRAM. Could that be it? The other modifications are exactly as instructed.

It still doesn't work. I even tried to autodetect the settings, it crashed too.

As I said, neither vanilla nor STEP launch works. It still looks like it's going to start (in the vanilla version it even gets to the Bethesda logo) but then it crashes. Replacing the missing SKSE folder and file did not fix the problem.

While reinstalling I noticed that the Folder SKSE from \mods\skse 1 07 01\SKSE and the SKSE.ini file were no longer there. I know that I created them this morning but they were gone. I don't know what could have done this but even reinstalling SKSE did not solve the problem.

Now the vanilla version crashed too. It worked when I tried it before installing anything. Just a CTD after the Bethesda logo, no message or anything. It shouldn't damage any mod installation if I draw the Skyrim files from Steam again, right? Oh, boy. Now it dawned on me. If I do that all the work in the Skyrim folder is gone. What can I do? Edit: In the top left corner of vanilla Skyrim there is a text: ENB Series 0.264. I guess since ENB is in the Skyrim directory that's normal. I wrote VideoMemorySizeMb=17346 (I have 16GB System Ram and 3 GB VRam) into the enblocal.ini file but that should be right.

It still did that. The small Skyrim window opened, the Screen turned black and then quit to desktop. Should I try to launch vanilla Skyrim?

Don't I have to deal with the log file in Overwrite first?

Ok, here it is. This is hopefully more useful.

There are no warning signs in the plugin list. I have a screenshot of MO but don't know how to upload it in this post.

I followed all the STEPs up to and including 2.D Fixes. I used LOOT and the warning sign in the upper right Corner of MO was greyed out. For what it's worth there didn't seem to be any problems with the setup. I tried to lauch Skyrim through MO, the screen turned dark for a moment and then it went back to desktop. The warning sing in the upper right corner is now red and tells me that ther is content in the Overwrite Mod: A folder named SKSE > a folder named Plugins > a file named SKSE_Elys_AltF4.log The log is as follows: Plugin name: SKSE_Elys_AltF4 Plugin version: 1.0.0.0 Plugin path: C:\Program Files (x86)\Steam\steamapps\common\Skyrim\data\SKSE\Plugins\ SKSE version: 1.7.1.0 Game version: 1.9.32.0 Plugin enabled. Starting hooks sequence... Installing hook for: DirectInput8Create Original Opcodes: 8BFF558BEC81EC2C Hook installed for: DirectInput8Create Installing hook for: DirectInput8.CreateDevice Original Opcodes: 8BFF558BEC568B75 Hook installed for: DirectInput8.CreateDevice Installing hook for: DirectInputDevice8.SetCooperativeLevel Original Opcodes: 8BFF558BEC56578B Hook installed for: DirectInputDevice8.SetCooperativeLevel As I understand it, I have to first deal with this content before trying to lauch again. Neither the STEP guide nor the Mod site on Nexus say something about any of this. Unfortunately I don't understand what the log file is saying. Do I move the SKSE folder in Overwrite over to the Mod and launch again or do I just delete it and launch again? The latter seems wrong to me. I have stored my system specs as recommended by the thread starting site and I'm appending the files from my MO profile. If further data is recquired I'll gladly provide it. archives.txt loadorder.txt lockedorder.txt modlist.txt plugins.txt initweaks.ini Skyrim.ini SkyrimPrefs.ini

Thank you very much for your explanation. I managed to get it done but I will still go back to MO Wiki. Although videos are not an efficient way to look for specific information they could still be helpful in getting a general idea of how MO works.