Joat_Mon

Look at cause #4, first solution What is the full path and file name for the file you want to delete?

That is correct. You still need the other fixes in SKSE.ini. Crash Fixes allocates memory dynamically unlike the memory allocation method used by the game engine as patched by Sheson, which is why I think it is worth the extra effort.

It could also be because the total path length is too long. This link can help you get around that problem: https://support.microsoft.com/en-us/kb/320081

The root partition directory is "special" and is subject to limitations that other partitions are not subject to. Often users have no problem loading everything into root, but the potential for problems is real and it is a good idea to avoid them. The directory structure that TechAngel85 recommended is fine and will avoid any problem.

After Win 10 was released Microsoft changed the way it allocated memory for 32 bit programs like Skyrim. Win 10 is now limited to a total 4 Gb memory for 32 bit. That change when it happened will show up a flawed set up that might have run okay before.

If the windows disk manager snap in will let you shrink the existing partition enough then you should be fine, Still I always clone the drive first. Sometimes windows will not let you shrink the partition and there are solutions for that too.

Your sD3DDevice= will be different from TechAngel85's. That the line is missing from your skyrimprefs.ini means that you did not set the game up correctly the first time. I was mistaken about your video card info, because I did not take into account that your "desktop" computer might be an all in one. @TechAngel85 Will SpINI fix a game that was not installed correctly, with .inis initially set by Bethesda on first run?

One more thing I would recommend is to set up a separate partition for Skyrim while you're at it. Remember to clean out all the skyrim and MO file in your user profile and follow the STEP guide and Gamer Poets videos.

Sheson's memory patch was incorporated into SKSE so a separate download of the patch is no longer needed, but is not activated by default. Thats probably why you're confused. About the same time meh321 released Crash Fixes which uses a different approach to memory management. Either one works. I've been using Crash Fixes for a while on four very different machines and I like it better than Sheson's memory patch.

That setting in your enblocal.ini was for much older AMD video cards and drivers. It should not be necessary for your video card and if you enable it ENB uses more of your memory to manage the driver functions.

As Nebulous112 said you need to use one or the other. I would recommend Crash Fixes. You can probably set DisableDriverMemoryManager=false as it should not be necessary on your GPU, setting it to true will have performance impact.

Why did you choose this setting? DisableDriverMemoryManager=true

So you've followed the read me for that ENB, you have the right binary? Are you using Crash Fixes or Sheson's memory patch?

Although it should not cause a ILS or stuttering, CoT is not compatible with that ENB. Win 10 is limited on memory and while everybody wants to devote as much memory to video as possible that isn't always where the problem is. You have ReservedMemorySizeMb=512 which is probable unnecessarily high and maybe just one thing contributing to poor performance. For Win 10, do you have fast start disable and hibernation shut off? Have you trimmed services to the bone?

Well there are some things that can be done to help in Win 10. My gaming rig is very robust and it doesn't need to run anything but Skyrim, still I have to make compromises in Win 10 that weren't necessary in Win 7. I was all set to revert to Win 7, to give ENBoost some room, when the 64 bit DX11 version was announced. Your experience looks like a memory issue and maybe a setup/install problem. If you not overly invested in a play through a fresh install of everything and some changes to Win 10 might be the best way to go.

If your game is installed in the root directory, C:\, then you might be running into a UAC (file permissions) problem. Did the game run smooth before you added the mods on top of STEP?

I have Skyrim set on a friend's computer that is like your's. I experienced something similar because I was running out of disk space in game. I would not have found it just checking windows file manager, but I happened to have CUPID HWMonitor running to monitor temps and noticed that my SSD utilization had gone to nearly 100%. Is Skyrim on a separate partition?

Are you using Win 10? Is your OS on the same SSD as Skyrim?

The one thing that jumps out at me is your monitor is 1920 x 1080, but you are telling Skyrim that you are running at 1600 x 900. I'm not seeing anything in the way of a bios update either, nor any driver downloads either. The GPU is proprietary so you might try the original driver that you were using with win 8.1. Everything about your computer is geared toward energy efficiency.

You had a gray screen problem with NMM, switching to MO didn't fix it. I think you need to sort out your computer setup before you move forward with correcting your game setup. Your computer is misidentifying your video card. 1. AMD HD 7800 M series. 2. In PCI slot. 3. One Gb vram. Those three statements can't all be true. Since your computer is a desktop it should not be reporting an mobile GPU. An AMD HD 7800 series GPU should be reporting TWO Gb vram. I am going to suggest that: You may have an incompatible driver. You may need a BIOS update. You may be experiencing hardware failure. You may have your monitor hooked to the on-board graphics. If your computer was manufactured by an OEM like Dell or HP or etc. did your check the manufacturer's support page for Window's 10 upgrade compatibility requirements and issues? If it has a proprietary BIOS it may need a proprietary GPU driver only available through the OEM. If this is a DIY or custom built computer, what hardware is actually in the box (not what Windows is reporting)?

Link to thread for a better understanding of why Boris released v0.308: https://enbseries.enbdev.com/forum/viewtopic.php?f=21&t=5126

I think I know which sound you're talking about, when I kill the bass enough to keep my windows from rattling that 'scream' stands out. It also occurs at other locations in Skyrim, in the STEP-Extended game set-up. I think I've heard it in vanilla also but I'd need to check again to be sure.

I apologize TechAngel85, I did not see your link when I posted. I'll step out and let you finish this.

Yes, except his mod load isn't anything like STEP and it sounds like he ported over from NMM to MO and brought his problems along. My next suggestion, so he does not leave a lot of gotchas, would be to start over using the STEP Core guide.

That's probably the problem, that .ini should be at some thing like common\Skyrim\Mod Organizer\mods\skse 1 07 03\SKSE depending on how you installed, definitely should not be in SKSEScripts. This is also telling me that SKSE is setup wrong.