Jump to content
  • 0

CTD across from Solitude docks


Lauren

Question

I've been testing my setup thoroughly for awhile and had a small chunk of mods left to enable/test. I haven't done anything with Skyrim for a couple weeks, so I also downloaded and installed all of the updates for the unofficial patches/Arthmoor's other mods (unwise? PERHAPS).
 
When I started testing (using the speedmult/tcl method), I used LAL to start as a patron at the Dragon Bridge inn, every time. I normally path northeast past Solitude, then go on towards Morthal/Dawnstar/Winterhold etc. for awhile. Previous tests were g2g, I could go 10, 15, 20 min+ with some hiccups but no crashes.
 
After updating aforementioned mods + enabling some of the 15 REGS mods, I would CTD as I passed the Solitude docks and crossed the river into the marsh near Folgunthur/that shack. I disabled the most recently enabled mods from REGS - still crashing (same spot). I rolled back the updated mods, but not the unofficial patches - still crashing (same spot). I enabled my Vanilla profile - no crashing. I enabled my SRLE (ish) profile, disabling all mods but vanilla + USKPs - and crashing again (yes, same spot).
 
I rolled back the USKPs to the 2.0.3 set - no crashing. I started enabling mods in small chunks - mostly no crashing. I actually got most of my mods re-enabled, but it doesn't like CRF, Falskaar, Book Covers so far, I may be forgetting one...
 
I tried again with a more awake mind today, just now. Enabled only the vanilla files, no crash. Reinstalled the newest versions of the USKPs, enabled one at a time, crash x4. [i didn't try once more with the 2.0.3 set yet, wanted to finish this post and I close Chrome when I play]
 
I really have no idea what to do at this point. I'd think I wouldn't have to wipe everything and reinstall Skyrim, since everything is in MO... I guess I could just use the older versions of the patches, but that doesn't seem like a real solution. Perhaps it's not a big deal because it's just one spot where it crashes, but it bugs me that it never happened before and I can reproduce it over and over and over... any ideas would be appreciated.
 
Relevant deets below:

  • MO 1.2.1 (started out with 1.1.2, upgraded)
  • BOSS/BUM first - switched to LOOT later on to see if that had any effect (nope)
  • Skyrim 1.9.32.0.8
  • SKSE 1.7 with memory fix
  • Enabled Memory Blocks logging, never exceeded the first block in testing
  • ENBoost enabled, SPM shows well under memory cap
  • New game started for every. single. test.
  • Most of SRLE + ~15 mods from REGS (all pretty much disabled at this point though)
  • Skyrim is on my 2nd SSD, not in Program Files (UAC is OFF)
  • Base game/MO/inis etc. set up according to SRLE

Crash location (not the exact same spot every time):

Posted Image

 

Load order:

Skyrim.esm
Update.esm
Unofficial Skyrim Patch
Dawnguard.esm
Unofficial Dawnguard Patch
HearthFires.esm
Unofficial Hearthfire Patch
Dragonborn.esm
Unofficial Dragonborn Patch

Edited by Lauren
Link to comment
Share on other sites

Recommended Posts

  • 0

It has sort of a non-standard layout, so perhaps I missed a variable when I was matching up the settings with my other ENB configs?

 

 

[PROXY]
EnableProxyLibrary=true
InitProxyFunctions=true
ProxyLibrary=d3d9_smaa.dll
 
[GLOBAL]
UsePatchSpeedhackWithoutGraphics=false
UseDefferedRendering=true
ForceFakeVideocard=false
 
[PERFORMANCE]
SpeedHack=true
EnableOcclusionCulling=true
 
[MULTIHEAD]
ForceVideoAdapterIndex=false
VideoAdapterIndex=0
 
[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=256
VideoMemorySizeMb=2560
EnableCompression=false
AutodetectVideoMemorySize=false
 
[WINDOW]
ForceBorderless=true
ForceBorderlessFullscreen=true
 
[ENGINE]
ForceAnisotropicFiltering=true
MaxAnisotropy=16
EnableVSync=true
AddDisplaySuperSamplingResolutions=false
VSyncSkipNumFrames=0
 
[LIMITER]
WaitBusyRenderer=false
EnableFPSLimit=false
FPSLimit=60.0
 
[iNPUT]
KeyCombination=16
KeyUseEffect=123
KeyFPSLimit=36
KeyShowFPS=106
KeyScreenshot=44
KeyEditor=13
KeyFreeVRAM=115
 
[ADAPTIVEQUALITY]
Enable=false
Quality=0
DesiredFPS=20.0
 
[ANTIALIASING]
EnableEdgeAA=false
EnableSubPixelAA=false
EnableTemporalAA=false
EnableTransparencyAA=false
 
[FIX]
FixGameBugs=true
FixParallaxBugs=true
FixAliasedTextures=true
IgnoreLoadingScreen=true
IgnoreInventory=true
FixSsaoHairTransparency=false
FixTintGamma=false
RemoveBlur=false
FixSubSurfaceScattering=true
FixSkyReflection=true
FixCursorVisibility=true

Link to comment
Share on other sites

  • 0

You might be a demi-wizard, at least. 

 

It looks like with ENB completely disabled, it doesn't crash. I've tried 3 ENBs so far and they've all crashed. So, perhaps on the path to the cause/solution. ENBs are kind of my weak point in modding, so I don't know what about them could produce such an issue. To the google, tomorrow.

Link to comment
Share on other sites

  • 0

So Google was not helpful, I searched through 15 pages of results and 20 pages of results just on the Nexus. Most posts were about ENB crashing the game at the Bethesda logo, or startup, etc... and most posts were just the OP and occasionally one person going "yeah I have the same problem."

 

Basically, I determined that with vanilla + ENB, I didn't crash. But once I enabled the USKPs, it crashed. Enabling mods without ENB, no crash. I don't know why stuff would interact like this, but, there it is.

 

I pretty much tried everything I could glean from what few helpful posts I found. I installed/reinstalled DX, set everything I could to admin, I reset the .inis, I tried the injector version, updated the ENB binary, wiped out my ENB Manager stuff and just copied an ENB directly from a freshly-unzipped archive into the Skyrim folder... nada. So at this point, I have nothing left that I can think of to do, besides obliterate and start over. I'm mostly updating this in case someone should stumble upon it in their own Google search for help.

 

I leave you with this:

Posted Image

Link to comment
Share on other sites

  • 0

I'm not a SR:LE kid, does that involve Skyrim Distance Overhaul? I've found that to be problematic in the Morthal swamp region (I switched to ugrids 7 and have no problems, but I don't recommend throwing that change into the mix until everything else is sorted).

 

Re- your enblocal, your values; ReservedMemorySizeMb=256, VideoMemorySizeMb=2560 seem low. I would suggest enabling autodetect, or increasing those values depending on your hardware.

 

>> (ninja'd by SRB) FWIW, I use the new binary & Serenity without issue. I've got a NVidia GTX 670 2GB & have ReservedMemorySizeMb=512, VideoMemorySizeMb=10240 which has been stable with SKSE 1.7 alpah's memory patch features.

Edited by redirishlord
Link to comment
Share on other sites

  • 0
@EssArrBee  For ENB, I was initially using QuietCool which uses 0.246. I also tried RealVision, Phinix, and Bleak Realism which all used 0.251. Right before my last post was when I had updated to the newest binary 0.254. I can't seem to find my 0.251 files now though, if someone knows where I can dl them again :- I guess it wouldn't hurt to try swapping back.
 
@redirishlord The crash happens with basically just the base game enabled, unfortunately, and I don't use Distance Overhaul.
 
 
So I decided to wait to reply after I did a complete reinstall of everything... yeaaa it's still doing it. It seems like it's crashing now when ENB is enabled period, even with just the optimized vanilla/DLC stuff. I tested vanilla + unofficial patches without ENB, no issues. I suppose I prefer a problem with ENB, rather than the game itself so to speak... maybe I'll be able to find something on the ENB forums ~_~;
Link to comment
Share on other sites

  • 0
Well, these are the only ones on there: v0.254, v0.236, v0.221, v13.7.13, v0.168, v0.132, v121212, v0.119, v0.108 TrueHDR, v0.103 Injector, v0.102 Tatsudoshi.
 
I tried using 0.236, with just Boris' files, no presets. With that + SKSE 1.7 - no crash; added optimized vanilla files - no crash; enabled unofficial patches - crashed. Disabled those and tested with just the optimized vanilla files 3x just to ensure it was really working - no crashes. I decided to enable unofficial patches one by one - with just Unofficial Skyrim Patch, it crashed.
 
Searching the ENB forums wasn't fruitful either. Mostly results similar to what I found on Google/Nexus forums. All Boris had to say in most of them was DX, "crapware" e.g. antivirus, Afterburner, EVGA Precision, or skyrimprefs.ini. I've used vanilla inis, and I don't have any of those programs running. I even completely uninstalled my AV for a bit (prior to seeing his posts). I had installed DX again in previous TS steps. 
 
I also just tried rolling back to SKSE 1.6.16 with the SSME patch. This version + optimized vanilla files + 0.236 - no crash. Enabled Unofficial Skyrim Patch, crashed. I tested the unofficial patches without the optimized textures, still crashed.
Link to comment
Share on other sites

  • 0

 

... if someone knows where I can dl them again :- I guess it wouldn't hurt to try swapping back..

Realvision author Skyrimtuner has his own archive here that contains the .251 binary

 

 

Really odd that your having this issue with the new binary, I'm running Serenity ENB with the .254, and STEP Core (Unofficial patches specifically) plus plenty additional mods without similar issue. My understanding of ENB (limited, although I've used one for some months) is difficult to reconcile with your USKP experience, I'm at a loss to come up with a conflict between those two items (they shouldn't directly interact or conflict, should they?). Wouldn't the problem need to lie elsewhere, memory shortage or mod plugins in conflict?

 

tl;dr

wouldn't this "added optimized vanilla files - no crash; enabled unofficial patches - crashed" be the most likely issue? could the optimized vanilla files be the culprit, maybe the optimizing went awry?

Edited by redirishlord
Link to comment
Share on other sites

  • 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.