Jump to content
  • 0

Question

Posted

Whenever I try loading at Knifepoint Ridge, or near and run towards it, I will CTD. This begun when I was on my way to do the Glenmoril Witches quest for The Companions. I came across the camp, cleared it out, went into the cave looking for ores, and when I tried to leave I would CTD before it finished loading. Tried several times, same outcome. Decided that maybe it was some sort of temporary bug, and used 'coc Whiterun' to teleport to whitrun and vendor off all my items. Tried going back to Knifepoint ridge to continue on to Gelnmoril, but before the loading screen finished I CTD'd again. Tried loading into locations near the camp, that would work - but as I traveled towards Glenmoril, when I get within a certain range of Knifepoint I CTD once again.

 

System specs are in my signature, but here is my wiki link if necessary: https://wiki.step-project.com/User:Holymartyr/SystemSpecs

 

Here's my BOSS load order:

 

  Reveal hidden contents

 

 

Using almost the entire STEP:Extended guide as of 2.2.8 (Not using Fores New Idle System or Dual Sheath Redux), fresh install of Skyrim, new save game. Only using STEP Ini tweaks ATM, including the Z-Fighting Ini tweaks. 

 

AFAIK, there shouldn't be any NPC's around - I cleared out the whole camp and didn't see any neutral NPC's around. CTD Happens either on fast travel to Kniferidge Point, or while approaching on either foot or horse. 

 

I'm not maxing out my RAM or CPU, GPU is maxxed giving a near constant 58 FPS. Using SSME (Skyrim Startup Memory Editor).

4 answers to this question

Recommended Posts

  • 0
Posted (edited)

In situations like this, I start the process of elimination if I suspect it is a mod related issue...versus a corrupt save or rogue script. (It may be worth looking into active scripts via the Save game script cleaner by Hadoram) Not (at least initially) for actually using to clean, but for its ability to show you the active script instances you have running in a particular save.

 

All the appropriate warnings apply, if you should choose to use this nifty tool, make a backup of the save file first and read the instructions for the utility.

 

Back to elimination process: systematically uncheck in Mod Organizer blocks of mods and load the game up and see when and if the CTD occurs. Repeatable issues are the easiest to resolve in most cases.

 

Another thing: You use SSME but do you also run ENBoost and have it configured?

Edited by Kuldebar
  • 0
Posted (edited)
  On 4/14/2014 at 3:58 AM, Kuldebar said:

Another thing: You use SSME but do you also run ENBoost and have it configured?

Yes, I am also running ENBoost, and I have configured it according to the STEP guide.

 

I thought that loading saves while just unchecking (disabling) mods in Mod Organizer will cause even more CTD's and issues? Hence the need for a 'clean save' when mods update/you remove a mod? 

 

Edit: If I'm using/understanding this script editor properly, the only 'Active Script' is the footprint script from 'Footprints' mod.

Edited by Holymartyr
  • 0
Posted
  On 4/14/2014 at 7:58 AM, Holymartyr said:

 

I thought that loading saves while just unchecking (disabling) mods in Mod Organizer will cause even more CTD's and issues? Hence the need for a 'clean save' when mods update/you remove a mod? 

 

Not necessarily, obviously it depends on the mod, and we aren't trying to play the game so much as see if the specific CTD problem changes or is eliminated by the absence of a particular mod. Depending on the mod, it might not be possible to disable and load a save, but for most mods, that is not the case and we can use mod disabling as a troubleshooting method. If you are CTD'ing in a predictable manner, we need to change the scenario to see what, if any mod, is causing the repeatable CTD in that specific area in the game.

 

Curious you bring up footprints, because that has caused issues in the past, but not having used the mod, I don't personally know its current stability status.

  • 0
Posted

Sorry for the late reply - got caught up in some stuff, been a long week. Anyways I decided that the save wasn't worth the extra hour of time I had put into the game after I encountered the CTD, and decided to revert back to a previous save before I came across Knifepoint Ridge. I'll avoid that place as long as I can, and if/when I come back to it, if I get the CTD again I'll delve deeper into the issue. Thanks for your time.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.