c0c0c0 Posted December 25, 2014 Posted December 25, 2014 This is not strictly a "STEP" issue, but I'm counting on you guys to have some ideas on how I might approach this. I'm at around 25th level on my current game, too far to just start over, and I am crashing at what appears to be random times. Maybe every 10 minutes outside, and every 30 minutes inside. Worse in some areas. It's driving me nuts and I need some ideas on where to look to fix it. I'm playing what started out to be a basic STEP install, that has grown to 161 esps (counting the bashed patch). I'm running in LOOT order, with 12 GB of memory, and a brand new GTX 970. I'm running the latest SKSE, + uGridsToLoad, MindfluxParticles, and SafetyLoad. I believe my ini's are STEP default, but I may have made a few minor tweaks setting up my ENB (Phinix) or trying to figure out why I keep crashing. Neither the SKSE nor the Papyrus logs make any noise just prior to the crash. I ran a script cleaner on my save, but nothing came up as orphaned or otherwise odd. I should note that I am running one ESP with a single missing navmesh (Eagle's Nest). I think that's why I crash a lot along the road from Helgen to Riverwood. I've run it before with no major issues, though, so it's hard to fault this for me having a CTD while checking out my inventory in a dungeon. I can be doing anything when I crash. Mousing over my inventory, running down the road, looking around, whatever. Combat seems to be the largest cause of crashes, but by no means the only one. So, is this just what I should expect playing a 32 bit game with 161 esps, or is there something else I can look at? Is there any truth to some of these quick-fixes I've seen on the boards about extreme memory settings that make better use of my PC's resources? I'm not asking for anyone to fix this for me (I made this mess), but I'd like a few more ideas on what I can look for.
hishutup Posted December 25, 2014 Posted December 25, 2014 Download and install memory blocks log. Open your game and then exit and share the memoryblockslog.log
c0c0c0 Posted December 25, 2014 Author Posted December 25, 2014 Phew. A good link, leading to other links. And a 42 minute video. This'll take a while. :-)
hishutup Posted December 25, 2014 Posted December 25, 2014 I don't know what you are talking about but I guess here is a link.https://www.nexusmods.com/skyrim/mods/50471/?
c0c0c0 Posted December 25, 2014 Author Posted December 25, 2014 No, that's what I was talking about. Your suggestion leads to a good chunk of viewing material. Who knows? it might even point to the solution without the need for posting the log. Thanks for the info.
hishutup Posted December 25, 2014 Posted December 25, 2014 I have posted the same thing about 10 times on this site so the info is around :/
c0c0c0 Posted December 26, 2014 Author Posted December 26, 2014 Okay, went to a save where things got wonky fast and was able to generate this fast: [spoiler=MemoryBlocksLog.log]logging of blocks enabledlogging max values onlyTimer disabledBlock1 Block2256MB 256MB85 885 885 985 1085 1185 1285 1385 1485 1585 1685 1785 1885 1985 2085 2185 2285 2385 2485 2585 2685 2785 2885 2985 3085 3185 3285 3385 3485 3585 3685 3785 3885 3985 4085 4185 4285 4385 4485 4585 4685 4785 4885 4985 5085 5185 5285 5385 5485 5585 5685 5785 5885 5985 6085 6185 6285 6385 6485 6585 6685 6785 6885 6985 7085 7185 7285 7385 7485 7585 7685 7785 7885 7985 8085 8185 8285 8385 8485 8585 8685 8785 8885 8985 9085 9185 9285 9385 9485 9585 9685 9785 9885 9985 10085 10185 10285 10385 10485 10585 10685 10785 10885 10985 11085 11185 11285 11385 11485 11585 11685 11785 11885 11985 12085 12185 12285 12392 12392 12492 12592 12692 12792 12892 12992 13092 13192 132100 132100 133100 134100 135100 136100 137100 138100 139100 140100 141100 142100 143100 144100 145100 146114 146116 146116 147119 147122 147127 147127 148127 149128 149129 149130 149131 149132 149133 149134 149135 149136 149136 150137 150138 150139 150140 150141 150142 150143 150144 150150 150151 150152 150153 150154 150155 150156 150157 150158 150163 150164 150165 150166 150167 150168 150169 150169 151170 151175 151177 151177 152178 152179 152179 153180 153181 153182 153183 153184 153185 153185 154186 154187 154188 154189 154189 155189 156189 157189 158190 158191 158191 159192 159193 159194 159195 159196 159197 159198 159199 159200 159201 159202 159203 159204 159205 159206 159207 159208 159209 159210 159211 159212 159213 159214 159215 159216 159217 159218 159219 159220 159221 159222 159223 159224 159225 159226 159227 159228 159229 159230 159231 159232 159233 159234 159235 159236 159237 159238 159239 159240 159241 159242 159242 160243 160247 160248 160249 160250 160251 160252 160253 160254 160255 160256 160256 161256 162256 163256 164256 165256 166256 167256 168 Now, that surprises me. Here's my memory setting from skse 1.07.01: [Memory]DefaultHeapInitialAllocMB=768ScrapHeapSizeMB=256 Looks like it's being ignored, no?
hishutup Posted December 26, 2014 Posted December 26, 2014 Is that with the force steam loader argument What are your enblocal memory settimgs
c0c0c0 Posted December 26, 2014 Author Posted December 26, 2014 I'm not familiar with the "force steam loader argument". Where's that? enblocal.ini memory settings: [MEMORY]ExpandSystemMemoryX64=trueReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=256VideoMemorySizeMb=2944EnableCompression=trueAutodetectVideoMemorySize=false
c0c0c0 Posted December 26, 2014 Author Posted December 26, 2014 Some users on the memory blogs page are saying that skse may not be implementing the memory patch, and to go back to SSME. I tried that, that SSME says that something is still loading the patch (presumable skse) even though I removed the memory settings in the ini. At this point, I'm wondering if skse may be bugged.
c0c0c0 Posted December 26, 2014 Author Posted December 26, 2014 Fixed it! Gave up on SSME, and tried skse 1.7.2b. That didn't make a difference, either. Then I took the skse.ini file *out* of MO, and dropped it directly in "Skyrim\Data\SKSE\skse.ini", and now I'm getting the memory patch.Dunno why I'm the only person this is happening to, but it might be worth remembering for the next guy having crashes. Thanks for the pointers. It got me started.
hishutup Posted December 26, 2014 Posted December 26, 2014 Its happening so often... If someone is crashing randomly post SSME patch and then the answer that I have come up with is generally that the memory tweaks are not applying. Like just recently, I have had three (four - five now) people with the same issue within a day :/ This is kinda the reason I want to make memory blocks log part of STEP Core rather than in a pack. I have discussed the -forcesteamloader argument over here on this thread...regardless, can you post a followup of if it worked or did not work.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now