Darkanvas

Solved: leaving this fix here for anyone having a similar issue, for whom the listed common fixes (which failed for me) do not work Fix: I was stupidly running the latest EVGA Precision software, which (whilst it has no overlay / the overlay is disabled) seems to hook into DX9 for some reason unbeknownst to me. Exiting EVGA allows the game to run on W10 with the wrapper version of ENBSeries. What a pedantic ass this game is ------------------------------------------ Using NMM and SKSE. • My game ONLY crashes if I don't delete "d3d9.dll" from my Skyrim folder when installing the latest ENB series (wrapper version) • Oldschool Skyrim, not Skyrim SE • If I use the injector version, my game gets the same CTD and there is no fix. The injector version just seems incompatible with my machine • I do not use software overlays • The Steam Community overlay is off for Skyrim • With the wrapper version installed and "d3d9.dll" deleted from my Skyrim folder, Skyrim works but ENBSeries does not • I have tried installing the June 2010 Direct X runtime which includes DX9.0c. No dice I am afraid! Still crash to desktop before anything remotely good happens • I had RealVision installed but I un-installed it using the uninstall script, then erasing all RealVision files from my folder and re-installing stock ENB Series to make sure • W10 Pro 64-Bit, 16GB RAM, GTX980 4GB, Intel i7 - specs are not the issue here • Only having all these problems because MO1 stopped working for my Skyrim, switched to NMM - everything works fine unless I have ENB installed (either wrapper or injector) then I CTD before the logo even appears • Ripping my hair out here as have done extensive research and tried ALL • what the f***. Halp

MO2 has actually entered Beta, so stop using the Alpha version :P hehe https://github.com/TanninOne/modorganizer/releases ^ MO2 Beta 1. I have been helping, posting about bugs and helping to iron out bugs on GitHub. It's very active so keep an eye on that for MO2 releases. To repeat MO2 has been in Beta for a day or two now!

I don't necessarily know a fix but I know what's happening to your game! The clue is that objects which should be much larger (such as the red rocket you're standing near) are very very small! For some reason the game is loading 'distant' LOD objects and textures instead of the detailed meshes and textures. Sometimes you can get very strange graphics glitches as saves begin to corrupt. Try loading a really old save as the first save you load, when you boot up the game. Walk around and try to replicate the bug. If you can't then erase all your saves past that save-game and then continue. Other than that, looks like some kind of detail setting is messed up.

Game crashes when I go to complete the misc objective "Speak to Isabell". As soon as she gives me the mechanist armour the game crashes. If I kill her, the game crashes as soon as I take the armour from her inventory. I do not crash outside the mechanist's lair, inside the mechanist's lair or leaving the mechanist's lair so please don't post about that well-known bug :) thanks for your time!

... after updating my SOUND driver. What the actual hell. Ok here we go: http://s32.postimg.org/4p3kh5vhx/2016_05_15_19_49_31.jpg I have NO idea what's caused this to randomly start happening for no apparent reason. Halp! Edit: Fixed. The bug was caused by the texture optimisation project, but I don't think the mod itself was to blame. My PC suffered a serious crash previously, I believe that the crash somehow corrupted the textures and caused this bug. To fix, disable the mod / re-install it clean Edit 2: Re-installed the TexOp mod from a backup and the same error keeps happening whenever I turn it on in MO2 (Mod Organizer 2). Strange that it never used to happen... guess I'll just have to stay away from TexOp project for now! Edit 3: Hopefully the final edit, did some further experimentation loading earlier saves and it turns out that even with TexOp loaded, I can avoid this graphical error by loading an earlier save (erasing saves past that point and continuing to play). So now I'm thinking it's the save file that got corrupted, not TexOp at all...

Switch yourselves to MO: http://www.nexusmods.com/skyrim/mods/1334/? Far superior, much more stable. Decent video detailing it (and why you should use it) here:

Here's something important, if your character is pretty strong you might be killing the bandits in one hit right? So you need to determine whether you CTD on attack or whether you CTD on 'kill' (since both of these may be happening at the same time). If you're getting CTD on kill, it might be an issue with the opponents corpse data, or an item that a mod is loading into their corpse-inventory (corpseventory? lol) upon death. For example if you use Hunterborn and go to Blackreach - and kill a ... what was it ... charus hunter fledgeling, you will often CTD if you have the 'monster hunter' thing enabled (due to an issue with the mod). Figure out if it's the attack or the kill that's causing a CTD. that will narrow things down significantly.

No problem! I also get this if I tell one of my followers to carry too much stuff and then try to trade/open backpack/hold items with them. I had no idea that the weight thing could also cause it. Very interesting! Maybe a potential dirty fix would be to make a mod that makes all items weightless, but only when they're stored in a container.

This. It's well documented that this mod causes this specific problem. I had to remove it, too.

Very strange and 'specific' issue. The offending critter also refused to aggro until I smacked it. Every time I load the save and attack it, I CTD seconds later :') Pretty weird, right? Edit: Seems to happen specifically when I land the 'killing' blow. So - maybe it can't load the corpse or has other issues with the dead version of the creature? Edit2: Disabled "Monster Hunter" on "Hunterborn" and the CTD stopped.

is a specific container? I'm really bad and just dump ALL my stuff in one chest. because there's so much stuff in there, it lags when depositing or withdrawing items :') You can over-fill containers. It's a thing

If you're trying to remove orphaned scripts (which is, I think what you are saying): 1) Save the game and quit 2) Disable the mod 3) Re load the game, 'accept' the "missing content" warning by clicking yes 4) Re-save the game. NOW those scripts are officially orphaned. Before this point, they weren't 5) Use this: http://www.nexusmods.com/skyrim/mods/52363/? - don't forget to back-up your saves just in-case 6) Done, re load the game and those orphaned scripts should be gone Give it a try :)

I actually fixed the issue by myself :') here's what I did: 1) Installed a water mod that uses higher resolution textures (Realistic Water Two) 2) Enabled an FPS Limit of 70, rather than 60 which I find much nicer / smoother 3) Disabled V-Sync in the launcher and all INI files including ENB 4) Set my nVidia control panel entry to default except for one thing, v-sync! Which I set to 'adaptive' After these steps, no water flicker and higher than 60 FPS. My monitor has a refresh rate of 60Hz (awful I know) and I read that you HAD to enable v-sync and cap FPS at 60, not true for me. I still have to cap it a little lower - but with 'adaptive' v-sync only (through nVidia control panel) I was able to set a higher FPS cap. I don't know why it worked, but it did! Edit: I upped the FPS limit to 80, still no return of the flickering water. I must have been running at well over 100 FPS, amazed I wasn't also getting physics / havok glitches! Edit2: I was able to raise the FPS to 100, and then 120. Still no sign of water flicker!

I can easily resolve my water flciker (which only happens for large bodies of water, not rivers - OR when I'm underwater) by capping the frame-rate to 60 FPS and enabling V-Sync in my nVidia Control panel. However... this makes the game far less 'smooth'. I'd prefer to have V-Sync totally off and no FPS limiter. Is there an alternate method to solving the water flicker 'properly'? I'm running at 1440x900 on a 60Hz refresh rate, currently.

How irritating. Have you tried using the "coc" console command to 'warp' out?

That's probably for the best I guess, seeing as the CTDs were very 'specific' it's unlikely to be performance related. I had a similar problem a while back where I'd load a save and run in a particular direction and I'd always CTD. I went to that same location from another save and performed the same movement and didn't CTD. Turned out I'd been so over obsessing about fixing that one CTD (constantly loading, saving, closing and re-loading the same game) that I'd cluttered the save file with duplicate running scripts and stuff. Trying to fix the CTD so hard was creating the CTD :') I think I used the saved game script cleaner and then went inside somewhere, waited for 24h and then came out again. Saved, quit - re-loaded and the very specific CTD stopped happening... Skyrim can be brain melting sometimes.

I'd recommend that course of action, and reinstalling mods using MO (Mod Organizer) as it installs mods 'isolated' so you don't get loads of glitches from data-folder overwrites. No overwrites, mods installed isolated. Much better.

Do you use ENB or any memory patching mods/utilities like SSME? Funnily enough, not using these things when you have so many mods can lead to CTD as Skyrim switches from one memory block to another (which causes it to crash). You might actually need to expand Skyrim's first memory block to accommodate all the awesome mods. As you gradually add mods, the likelihood of this becoming a factor increases rapidly (especially with texture mods, etc). Try installing and running Skyrim Performance Monitor. Use it to run Skyrim until you CTD, screenshot the graph and post it here. Then we'll know if it's performance related CTD or not!

AFAIK Perma causes a lot of problems with other mods since it changes so much. It's one of those mods that has mod compatibility mods made for it :') It's great, but I don't use it for this reason. Too much of a headache. Get the Skyrim Performance Monitor installed and run skyrim using it. Play until you CTD, then screenshot the graph and post it here. That will help us to know if the crash is performance related. if it's not performance related, there's plenty of other stuff it explore. If it is performance related, there are numerous simple memory patches that help a lot of people. I play with over 160 active mods with no lag (finally, after removing one certain script-hogger) and no CTD. It's possible if you have a decent enough system. Even if you don't, making some concessions will allow you to run lots of awesome mods. let's start by determining if it's performance related or no.

it makes me wonder if I could pay a programmer/developer to amend the Skyrim engine so it uses a scripting engine that isn't papyrus :') I imagine it would cost some dolla though, if it were even possible. We desperately need a 'ReScript' mod that solves these issues. Edit: FYI to anyone reading this, finally solved the issue by removing Sands of Time. Here are the steps I took: 1) Deactivate the mod in MCM 2) Wait until it's fully deactivated, save the game and close it 3) Deactivate SoT in MO 4) Open Skyrim, reload the save and tell it to continue loading with missing content 5) Re-save the game and quit to desktop 6) Open the save with the save game script cleaner, use the primary four options along the top. Save over the old save 7) Re-open Skyrim, load the save. Stutter fully gone! ... moral of the story, Papyrus is awful, never underestimate 'script' lag. Even when you own a rig with a 4GHz i7, GTX 980 (4GB) and 16GB of DDR3 RAM. it still hurts you!

Well this certainly seems to mean something: What exactly does it mean and what should I do about it? or how can I 'check it out' and make some kind of intelligent decision? Duly noted about SoT. I think in my heart of hearts I know I have to remove it since I use so many other things I want to keep (Hunterborn, Frostfall). I still think it's a good mod and endorse it but yes it is maniacally script heavy.

Your system doesn't seem awful. In many cases (as i have found out to my detriment!) beefing up hardware only meets with limited success. This is because natively Skyrim will only use up to 4GB of RAM / VRAM (someone correct me if I'm wrong there) and without extensive tweaking you can often end up lagging hard. I advise you re-enable your ENB but set it to use the speed/performance patch without graphics (an easy to spot setting near the top of one of the ENB INI files, change from false to true). Once that's done, read this: http://wiki.step-project.com/Guide:ENBlocal_INI/Memory Specifically, the "ReservedMemorySizeMb" and "VideoMemorySizeMb" sections. Amend your ENB INI file(s) accordingly. Before you do any of that however, install and run the "Skyrim Performance Monitor". Play until you lag a bit, continue playing for five to ten seconds and then quit the game (quickly). Place a screenshot of SkyperfMon's graph here so we can see if your issue is performance related or 'something else' (scripts, system setup etc etc.) If you're using something like Mod Organizer, try to ensure that the base game and mods are both installed/located on the same HDD / SSHD / SSD. Mod list would be handy.

You may have some funky settings in ENB causing these kinds of issues It could be a mod which changes your skyscapes like CoT (Climates of Tamriel) It could be that you have multiple mods controlling skyscapes / weather which unfortunately conflict It could be that your graphics card doesn't like the particular form of sky-scape texture compression used in the native game It could be that your graphics card doesn't like the particular form of sky-scape texture compression used in various active mods Your graphics card could be on its last legs (unlikely if you see nothing abnormal in other games, and we certainly shouldn't jump to this conclusion) It could be some conflicting draw-distance information (though this would be extremely techy and unlikely unless you have really messed around with multiple INI files) It could be conflicting lighting / FX for your skyscapes, either caused by mods or INI tweaks, or ENB ... we might need more info to help you! :)

Download the mods 'manually' as zipped/7z'd/RAR'd archives and install using "Mod Organizer" instead. Seriously, it's like suddenly eating the best burger you ever ate after a life of turd sandwich. NMM was great for its time but because Skyrim has so many issues, installing mods 'isolated' as MO does works much nicer. Highly recommend switching from NMM to MO. Takes a little more time to set up but so worth it.

In extremely general terms, those at the top will load in first and those placed lower down, if they conflict with any above, will take 'priority'. that being the case, bigger more expansive mods that add a lot of stuff (new regions, new functionality, plethoras of new dungeons/quests) should go at the top as 'base plates' whilst smaller things (individual player homes, one off weapons to find, a single new NPC added to the game) should go lower down as they are more 'specific'. this is a very general rule of thumb, I have always found it to be (at least) moderately successful.