Jump to content

Recommended Posts

Posted

Hi again, thanks for the responses guys. I was never on a dark brother hood quest, im pretty sure that was from the dark brotherhood ressurected mod I had.

 

Chesko's lanterns does keep searching for that ESP but according to his main page its a known thing and doesnt cause crashes, and he'll fix it soon.

 

HOWEVER. I just reinstalled completely and dropped most modes I didn't really need. (dark brotherhood one, moonpath, etc) and now I am getting CTDs again....but the papyrus log seems a little more consistant, as in a lot of the same stuff but I still dunno what it means.

 

http://pastebin.com/MT0zvpGv

 

edit* I editted asis to not use Skyre_survivalism.esp to give mobs perks, and it got me passed the one point I was crashing at, now I crashed again -_-

 

http://pastebin.com/RgWGknkB

 

New Load order

 

 

  Reveal hidden contents

 

  • Replies 90
  • Created
  • Last Reply

Top Posters In This Topic

Posted

I disagree with the BOSS thing again, but only because I believe its a matter of wording, and not an argument on BOSSes function. In my view, if something changes something else, and that action generates problems, then its caused the problem. Wither the problem actually exists due to a lack of information, or because two things don't get along together is another matter. Its like saying I died in a game because the game is bad, when in fact it's not that the game is bad, its that my cat jumped on my lap and caused me to push the controller in the wrong direction. Outside force influencing events, causing issues, and thus creating problems. Simple cause and effect. Better example might be cables on a car battery touching and causing an electric shock because I slipped while changing the battery. The cables conflict with each other naturally, but are in a state of neutrality due to relative locations, however, when I slipped while holding them, pushing them together, I'm placed them in a state of conflict, and thus the shock and problematic reaction.

 

Sorry if I'm going to much into this. I just spent half my day staring at CK weapon sheets changing the same things over and over and over, so thinking about something else is nice.

 

 

Topic related stuff:

---------------------------------------------------------------------------------------------------------

Interesting thing. I had this part in to in a log a few days ago.

 

"[01/10/2013 - 04:50:19AM] Cannot open store for class "dlc1scwispwallscript", missing file?"

 

I had to reinstall skyrim, and then deactivate each mod via NMM (Deactivate, not just turn off.), then reactivate them one at a time. You may have to do the same thing.

So you've reinstalled, but did you deactivate all your mods and then reactivate on the ones you want? If not, try that and see what happens. Could be one of the mods your using has done something for some reason that it shouldn't have. I remember reading some place once that reinstalling and then trying skyrim with all your mods activate at once from the beginning can cause Skyrim to have a cry.

Posted

I deactivated all my mods via NMM, uninstalled via steam, deleted the skyrim folder to get rid of remaining data. Deleted the my games / skyrim folder.

 

REinstalled, reinstalled my mods. Playing again

 

Also got rid of all the mods that I didnt feel I needed.

 

I played through Helgen with notihng buy SkyRe modules on cause you gotta, then activated all the others after I finished Helgen and got to Riverwood.

Posted (edited)
  On 1/10/2013 at 11:40 AM, Selvec said:

I disagree with the BOSS thing again, but only because I believe its a matter of wording, and not an argument on BOSSes function. In my view, if something changes something else, and that action generates problems, then its caused the problem.

 

That doesn't mean it's an issue of "mod -conflict-." I am not trying to be a jerk about this, so let me explain why we are even bothering to correct your 'opinion' on this:

 

Some of us are trying to make suggestions to new and inexperienced mod users how they can better manage their load orders to deal with mod conflicts (e.g. "I CTD when I try to start the game?" "It's because you are loading an esp with dependencies before it's master"). BOSS is not a miraculous cure for mod conflicts (and it never claimed to be) but it is one of the necessary utilities for mitigating the aggravation of having to organized and reorganized the load order. Even for people who generate their own compatibility patches (and aren't really weighed down by load order issues), it's still a good idea to use a BOSS load order as a template for mod dependencies and sheer simplicity. But you are telling new mod users that BOSS creates mod "conflicts" when in fact it does not.

 

Your analogy therefore comes across as some sort of 'superstition.' Excitement can exacerbates a person's existing heart condition but that does not mean excitement is one of the causes of cardiovascular diseases. To blame BOSS as a cause for mod conflicts is like blaming a medical physician for telling you that you've developed a heart condition after years of poor diet and lack of exercise, because you didn't know you had a heart condition and didn't start feeling the signs until the physician told you.

Edited by ripple
Posted

so annoying, still happening, and its so random I cant even begin to pinpoint a starting point. Sometimes when i start a conversation. crash. sometimes when I use the forge. crash. sometimes when i try to sneak, crash. sometimes when I'm just walking around randomly, crash.

 

siiiigh.

Posted (edited)

159.

[01/10/2013 - 05:20:44AM] Error: File "Dragonborn.esm" does not exist or is not currently loaded.

 

I have no idea what you are using that would cause this error to come up lol. It was present in both logs. I don't think its the issue, but any ideas what is calling this? Were you a beta tester lol.

 

407.[01/10/2013 - 05:35:55AM] Error: Unable to bind script _DE_Campfire2FuelTrigger to (10025BC2) because their base types do not match

 

This was the last line before your crash in the second log. If I'm right, this script is from the frostfall mod.

 

In the second log, what exactly were you doing when you crashed? According to the log, you save three to four times in less than 30 seconds. Why? Was this autosave or manual saving? It is always better to have the autosave off and use the quicksave feature as the autosave does cause skyrim to crash more often (primarily when loading new areas).

 

Did you use any of your old saves? Script problems can become stuck in a save even if the mod that caused them is no longer there.

 

At this point, you should really deactivate the more game changing mods in order to determine what is part of the problem (Skyre and Asis. I would start with Asis). Once you find one that lets you go longer without crashing, then we can figure out if it is the mod itself or if it isn't playing well with another mod.

 

Edit: I went back and looked over your load order again. You do have a few mods that do sort of the same thing, but this could just be straining your system. What is your framerate like both while you are playing and right before a crash?

Edited by bigv32
Posted

I run around 42 frames per second.

 

I dunno why it shows 4 saves in a row, honeslty I hardly quicksave (which I should do more often -_-)

 

I dont have any mods that do the same thing?

 

This is the only save I have, I got a new PC , this is a fresh install of skyrim, and the only characters I've been playing.

 

I sent my papyrus logs to Chesko and t3nd0, the authors of the two biggest mods I use and they said they're clean, very clean in fact. The dragonborn.esm and campfire stuff is from frostfall auto checking for compatibility, Chesko said.

 

My FPS when I crash remains constant. Theres no warning, no rhyme or reason, just completely random crashing. I can be running along, fighting a monster, going into a dungeon, talking to an NPC, and the game is just like GUESS WHAT LOL CRASH.

 

There is absolutely NO warning via fps hit, stutter, anything, just BAM. If it was constant I could at least figure out where to START looking in my mod list :(

 

running TES5EDIT I get this after babette.esp (this esp is added by the eyes of beauty....

 

 

  Reveal hidden contents

 

 

no idea what it all means tho

Posted
The esp's giving your 'unexpected subrecords' need to be uninstalled from your load order. They actually can cause CTDs. It may be that those mods were made using pre-CK tools (JFYI, I use to have 'Eyes of Beauty' installed, and it didn't have an esp, just meshes and textures for the eyes, but that might be an older version). It may be possible to repair them in TES5Edit, depending on what sort of records, but it's really much simpler to just remove them.
Posted (edited)
  On 1/11/2013 at 7:05 PM, ripple said:

The esp's giving your 'unexpected subrecords' need to be uninstalled from your load order. They actually can cause CTDs. It may be that those mods were made using pre-CK tools (JFYI, I use to have 'Eyes of Beauty' installed, and it didn't have an esp, just meshes and textures for the eyes, but that might be an older version). It may be possible to repair them in TES5Edit, depending on what sort of records, but it's really much simpler to just remove them.

 

Agreed.

 

As for the multisaving issue, do you have autosave on? I am not sure if you have answered this before lol, so sorry if you have. All I know is Skyrim's default autosave system can cause CTD's overtime during a playthrough. It was the same thing in Fallout New Vegas, which is why the CASM mod was so popular. Not sure if there is one for Skyrim yet.

Edited by bigv32
Posted (edited)
  On 1/11/2013 at 9:03 PM, bigv32 said:

All I know is Skyrim's default autosave system can cause CTD's overtime during a playthrough. It was the same thing in Fallout New Vegas, which is why the CASM mod was so popular. Not sure if there is one for Skyrim yet.

 

The problem was that every autosave would continually save to the same savegame file, thus increase the chance of save game corruption over time. Adding the following line to your Skyrim.ini will increase the number of autosaves:

 

[saveGame]
iAutoSaveCount=#

 

Where # is the maximum number of autosaves you want the game to generate before it starts recycling the old ones.

 

This will make a new quicksave every time you hit the quicksave hotkey rather than continually save to the same quicksave file.

Edited by ripple
  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...