Joat_Mon

Yes and yes, Crash Fixes has been working well for several weeks. It was just nagging at me that the game engine was still allocating memory blocks that it wasn't using and that the size of those blocks still responded to the skse.ini memory settings.

I've been using meh321's Crash Fixes for a while and meh321 says that it isn't necessary to do any thing to “remove†Sheson's Memory Patch as it will not load. However MemoryBlocksLog.log line one still shows blocks 1 & 2 as allocated per the settings in skse.ini. And two additional lines showing 85 and 8 for memory used for blocks 1 & 2 respectively. So I commented out the lines under [Memory] in skse.ini and the log then showed the default block sizes and still two lines of 85 & 8 used. I have played like this for a while. Today I changed my skse.ini to [Memory] DefaultHeapInitialAllocMB=256 ScrapHeapSizeMB=0 and now MemoryBlocksLog.log shows 0MB and 0MB on the first line and still shows 85 & 8 used on the next two lines. Skyrim still seems to run fine. The questions are: Have I actually gained back those memory allocations for use elsewhere? Or am I flirting with disaster? Btw if you set DefaultHeapInitialAllocMB= to less than 256 MemoryBlocksLog.log will show a negative number and the game still seems to run fine.

To be clear the 1607 upgrade was okay, this problem started showing up after the most recent "fix" update was rolled out a few days later.

My Win 10 1607 machines are freezing up since the last update. I have reported the issue to Microsoft. Microsoft has acknowledged that this appears to be an issue for some users that have their OS on a SSD and their Data on a HDD. They recommend rolling back to 1511 until they can fix the issue. If you haven't upgraded to 1607 yet I recommend that you defer the upgrade for now.

Tip: If you haven't dual booted Win 10 before; With hibernation still enabled make sure you fully turn off fast boot/start in power options > system settings, select "Choose what the power buttons do" on the left, then click on "Change settings that are currently unavailable". Then un-tick the setting and then turn off hibernation on your way back through your chosen power plan. Then open elevated command prompt. Type "powercfg /h off" with out the quotes and hit enter. If you can't see the option to un-tick fast start/boot, you will need to enable hibernation, "powercfg /h on" then disable it again after your done. This avoids fast start/boot bypassing the boot manager. It has the added benefit of not starting Win 10 in a "dirty state" left over from the last shutdown.

Depending on your Mod load you may need ENBoost's extra memory just to start, or you may have left something when you removed it. I would recommend put it back. Running Win 10 you need to set VideoMemorySizeMb to 4064.

Dual boot if you can. With Win 10 and that Mod load there would be just too many compromises IMO.

Right click on the SKSE mod, select "Open in explorer" Find the SKSE folder or create one, open it. Create your skse.ini file here. Make sure it is named skse.ini, NOT skse.ini.txt

Another thing to consider is that a number of people have reported problems with the combination of FNIS, MO and Win 10 including the mod author of FNIS. So you might want to make sure your FNIS install went okay.

Which version of crash fixes are you using? In CrashFixPlugin.ini are you set to "UseOSAllocators=1"?

Do you mean the game is not responding to keyboard and mouse input?

ReservedMemorySizeMb=512 reduce this as far as possible, try 128 and if you don't stutter try 64 VideoMemorySizeMb=8000 set this to 4064

That error message from Crash fixes means that Nebulous112 most likely nailed it...You need the DX9 Runtimes or else ENBoost won't run.

Judging from the Memory Blocks Log, it looks like Sheson's memory patch is not installed correctly.

Could you just treat the corrected files as a new mod and overwrite all?

Looking at the code, the original file paths are not preserved in the user space VFS. So there is no automatic method to put the corrected files back into the correct NTFS file on disk. You would still need to intervene manually to direct the fixed file to the correct directory based on your personal knowledge of your load order, patches, forwarded assets, etc..

Pushed out to my gaming rig today. It reset all my active AMD gaming, overdrive and fan profiles to default settings (global profile also). I was already on the latest AMD driver 16.7.3. It also re-added and restarted some telemetry settings as well as several “apps†setup to run in the background. Removing some of them will likely require Windows PowerShell or a third party application. After killing the easy to get to settings and uninstalling “apps†that Windows would allow me to uninstall, Skyrim STEP Extended started and ran with no problems. Later I forced the Upgrade on three other machines, on those machines it changed settings on my NIC’s, most notably it disabled Jumbo Frames. I’m still looking for what else it might have touched.

Having no grass probably doesn't have any thing to do with DynDoLod. Adjustments can be made to minimize the visual impact of "popping".

Well I like the looks of that and the Bleak looks like what your after. The one person that's capturing skyrim video on a machine I built with spec's close to your setup is Using Bandicam.

If its just the color bias or saturation you're after you should be able to achieve the same result with out the ENB. That's not to says it won't be tedious to do but it will be less demanding on your system. Are you only using MSI Afterburner for the video capture feature?

The learning curve and capabilities of Blender are about the same as Vegas so I would just save the money. Win 10 is always going to be more problematic than Win 7 for 32bit Skyrim and even more so when you are trying to software capture video. Skyrim benefits greatly from a modest CPU over clock, do you have a decent CPU cooling solution? Some of the changes I make to Windows for Skyrim would kill your video editing software.

Looks a lot better. There are other members here that will know much more than me about the ENB you are trying to use. It sounds like you have a solid base to work off of now. I think Movie Maker is dead, would Blender work for what you want to do?

Lowering the impact of the grass should be ease to check. The ENB should not have hit you so hard. Do you still have good frame rates indoors?

Just glad I could help.

Instead of trying to rename the file try renaming some of the parent folders above it to 1 or 2 character names, then navigate back to the file you want to delete and hold down the shift key when you select delete.