New computer build and nothing but CTD

[Zephyrrey]

Hi all, I'm hoping to get some assistance here as I have very limited spare time, and for the past week it's been 90% devoted to fixing this with very little to be shown for it.  

I recently finalized a new computer build with some decent parts, so I wanted to get my skyrim up and running and see those crisp high end textures and finally be able to use an enb.  Unfortunately, I live in a pretty rural area and have limited satellite internet, so I tried doing something I read about and looked like it was possible; just copy my mod organizer folder from one machine to the next, rather than download all 200 something mods over again.  

After getting everything there, I started tweaking to make sure everything was correct (reinstalling key mods with configurables like Perkus Maximus Patches, cbbe, etc), reran fnis, patchus maximus, bodyslide, ran into a few issues that were solved by an Integrity of Game Files check, and got skyrim basic working.  Next on to mods.  

Making a new save was pretty hit or miss.  Nothing but crashes but it was odd in that sometimes I would crash before reaching the initial character creation screen for Live Another Life, and sometimes I would make it through char creation (never crashed during) and would then crash upon mod initialization.  
Firstly, here is my load order.  I understand it is long, but I think (stress the word think) I've done my due diligence in looking for conflicts, missing masters, and the like.

loadorder.txt

 

I began going through all my mods to isolate the trouble maker.  Initial results pointed at Perkus Maximus, as I could get through mod initialization and watch all my other mods load.  Keen, it's PerMa.  I reinstalled all of my perma pieces except for the patcher, loaded up, and kept having issues.  Reinstalled a lot of mods that I could find the old install files for, or downloaded a few that seemed likely to cause issues (ignored things like follower mods, and armors, did thinks like script utils, racemenu, xpmse).  Started making it through to mods loading.  I did my PerMa patch again, and it seemed to work on my dummy character (most tests are used by making default male nord) so I closed my game, added a few jslot presets into my patchus maximus mod (which I did normally on my old build without issue), and now I'm running into the same issue as original.  I've attempted removing the perkus maximus items again but that doesn't seem to be working this time, and I'm hesitant to do another full mod audit because with my large mod order, it takes most of a night or two to get through all of them without getting sloppy.  

I know full well that this is not a perkus maximus support forum, and I'm not 100% convinced it is the sole culprit (as I had a few odd intermittent issues with MilkMaid as well, but nothing consistent), but I am hoping that someone can go through the papyrus logs I'll post at the bottom (and maybe give me some tips on what to look for).

Any help is extremely appreciated.

Crash logs after seeming success:
Script.7z

Crash Logs after removing PerMa and that didn't fix the issue:

ScriptNoPerkusMaximus.7z 

[27X]

If you were using win7 and are now using win10 you're going to crash like fuck until such time as the win10 fix comes out of founders and become available to everyone.

 

If you don't have CFix and Fallrim tools, you're going to want them.

 

and probably Utopium's load fix as well.

[Zephyrrey]

If you were using win7 and are now using win10 you're going to crash like fuck until such time as the win10 fix comes out of founders and become available to everyone.

 

If you don't have CFix and Fallrim tools, you're going to want them.

 

and probably Utopium's load fix as well.

 

I did go from win7 to win10, can you elaborate on what that issue is, or perhaps throw a link?  I wasn't aware of a windows 10 issue, but perhaps that's just because it was never a problem for me before.

[27X]

Basically going all 4K high rez and a billion polygons per labia is literally undoable in win10 currently because of the way dx9 is emulated under win10; there's a fix coming but essentially anything over 4gigs, even with an ENB is going to be problematic and outright crash prone until september when the founder's fix comes online for everyone.

 

This affects ALL dx9 software, not just Skyrim, so those fancy Mass Effect and DooM mods are just as affected.

 

After the fix is deployed ENBoost should work as normal and you can have all the super aychdee vajerjers you could want and an ENB that will fuck your framerate to 15 fps.

 

So ironically enough, your old gross looking skyrim will probably play fine... as long as you don't go over the ram limit.

 

[Zephyrrey]

Thanks for the information, that's quite unfortunate. I'll attempt that when I get home (at work at the moment), but I was encountering the initial issues before adding things like water / texture mods, so I'm not entirely sure if they are the main culprits.  I will update my findings here after I test it

[C5Kev]

If you were using win7 and are now using win10 you're going to crash like fuck until such time as the win10 fix comes out of founders and become available to everyone.

 

If you don't have CFix and Fallrim tools, you're going to want them.

 

and probably Utopium's load fix as well.

 

As 27X said, you need CRASH FIXES  and  LOAD GAME CTD FIX  .  I have Win10 and seldom CTD now that I have these installed. Sometimes the game just drops out for unknown reasons, but I restart, no problems.

 

[27X]

They may not be the main issues those issues will still be there in addition to anything else; when moving to a new OS the chances of a Bethbryo game under your previous load order being unscathed are about the same as winning the lottery, fucking a supermodel and being hit by lightning all at the same time.

 

Your best bet is to get a "working order" now while you can't do anything drastic or fancy, and then do drastic and fancy once win10 actually is compatible with dx9.

[C5Kev]

"...about the same as winning the lottery, fucking a supermodel and being hit by lightning all at the same time."  LOL!

[Zephyrrey]

Here's the progress of tonight's troubleshooting

 

Installed the packages suggested, made a few tweaks as recommended in those mod's profiles. First got the r6025 Pure Virtual Function call error, VCRedist seems to have resolved.  Still crashing on load.

 

Removed Realistic Water2 and the 2k texture mod I had added, got virtual function call again.  Again, VCRedist seems to have resolved that, still crashing.  Ran repairs on all c++ installs, because why not, restarted.

 

I ended up getting a large windows update (took me about an hour and a half to download/install), but still crashing.

Disabled Perkus Maximus, anything that depended on it, and the patcher.  Still crashing, and now I can't even hit character creation.  Tried reenabling them, same deal.  

 

Will probably do another go round of mod auditing... Maybe I'll revert back to SkyRe if I can get everything but Perma working again.

[C5Kev]

You've got some kinda old mods in there, like Estrus (which you don't need enabled - just there - if using EC) and SLUTS. Not saying they are the problem, but you might want to consider cleaning house a bit (do you really need ALL those followers? Just asking ) and also managing your load order a bit as it's kind of a mess.

 

What version of SexLab do you have?  Try 1.62 and turning of actor scaling.

[Ashkandii]

If you were using win7 and are now using win10 you're going to crash like fuck until such time as the win10 fix comes out of founders and become available to everyone.

 

If you don't have CFix and Fallrim tools, you're going to want them.

 

and probably Utopium's load fix as well.

 

Wait how long was this issue known for, I know people say win10 is unstable for 32bit games but they never really delved into why.

 

So like if I installed a 4k Weapon It would increase my % of crashing then its 2k counterpart? 

[Zephyrrey]

You've got some kinda old mods in there, like Estrus (which you don't need enabled - just there - if using EC) and SLUTS. Not saying they are the problem, but you might want to consider cleaning house a bit (do you really need ALL those followers? Just asking ) and also managing your load order a bit as it's kind of a mess.

 

What version of SexLab do you have?  Try 1.62 and turning of actor scaling.

 

SLUTS and ESTRUS are leftovers that will be cleansed with fire sometime soon, honestly.  I was completely up to date on SexLab, but I did find the issue. (I think)

 

I've actually realized this morning that it was entirely my fault and I seem to have fixed my error.  because I never used an ENB other than one disabled for the SKSEMemBoost, when I installed the new ENB, I did not update the ENB Binary.  new ENB using old Binary is not good.  Updating that seems to have rectified this issue for me.  

 

[27X]

 

If you were using win7 and are now using win10 you're going to crash like fuck until such time as the win10 fix comes out of founders and become available to everyone.

 

If you don't have CFix and Fallrim tools, you're going to want them.

 

and probably Utopium's load fix as well.

 

Wait how long was this issue known for, I know people say win10 is unstable for 32bit games but they never really delved into why.

 

So like if I installed a 4k Weapon It would increase my % of crashing then its 2k counterpart? 

 

 

The closer you are to the 3.1 limit of Skyrim, the more bullshit you're likely to encounter, and until such time as the fix comes through ENB is of little use in mitigating it.

[Ashkandii]

 

 

If you were using win7 and are now using win10 you're going to crash like fuck until such time as the win10 fix comes out of founders and become available to everyone.

 

If you don't have CFix and Fallrim tools, you're going to want them.

 

and probably Utopium's load fix as well.

 

Wait how long was this issue known for, I know people say win10 is unstable for 32bit games but they never really delved into why.

 

So like if I installed a 4k Weapon It would increase my % of crashing then its 2k counterpart? 

 

 

The closer you are to the 3.1 limit of Skyrim, the more bullshit you're likely to encounter, and until such time as the fix comes through ENB is of little use in mitigating it.

 

 

And the fix makes the 'bullshit' go away after 3.1?

[C5Kev]

 

You've got some kinda old mods in there, like Estrus (which you don't need enabled - just there - if using EC) and SLUTS. Not saying they are the problem, but you might want to consider cleaning house a bit (do you really need ALL those followers? Just asking ) and also managing your load order a bit as it's kind of a mess.

 

What version of SexLab do you have?  Try 1.62 and turning of actor scaling.

 

SLUTS and ESTRUS are leftovers that will be cleansed with fire sometime soon, honestly.  I was completely up to date on SexLab, but I did find the issue. (I think)

 

I've actually realized this morning that it was entirely my fault and I seem to have fixed my error.  because I never used an ENB other than one disabled for the SKSEMemBoost, when I installed the new ENB, I did not update the ENB Binary.  new ENB using old Binary is not good.  Updating that seems to have rectified this issue for me.  

 

 

 

Believe it or not, I was going to ask about which ENB you were using because I had a constant CTD problem with the (old) one I was using. I found a few that used newer binaries and picked one I liked. I'm using True Vision (kinda resource heavy) and love it and have had no (or seldom) CTD issues since (along with the mods I had mentioned above). If you've discovered the source of your prob., then fantastic!   CTD'ing all the time really starts to get on one's nerves.

 

"I've actually realized this morning that it was entirely my fault..."  99.9% of the time, it's operator error. Everyone know that! 

 

 

[27X]

 

 

 

If you were using win7 and are now using win10 you're going to crash like fuck until such time as the win10 fix comes out of founders and become available to everyone.

 

If you don't have CFix and Fallrim tools, you're going to want them.

 

and probably Utopium's load fix as well.

 

Wait how long was this issue known for, I know people say win10 is unstable for 32bit games but they never really delved into why.

 

So like if I installed a 4k Weapon It would increase my % of crashing then its 2k counterpart? 

 

 

The closer you are to the 3.1 limit of Skyrim, the more bullshit you're likely to encounter, and until such time as the fix comes through ENB is of little use in mitigating it.

 

 

And the fix makes the 'bullshit' go away after 3.1?

 

 

Memory related bullshit?  

 

Absolutely.

 

Operator error?

 

Not so much.