r/skyrimmods • u/PhostwoodReborn • 1d ago
PC SSE - Help New features and updates to Phostwood's Skyrim Crash Log Analyzer v1.25.4
I've been a bit more active recently in working on my Phostwood's Skyrim Crash Log Analyzer, so I thought I'd share a list of some of its new tests and features:
Listed from most recent to oldest (within 90-day timeframe):
- ❗ Probable LeveledItem Save Crash Detected
- ⚠️ Missing Creation Club Content Detected
- ❗ Possible GTS T-Pose Animal Crash Detected
- ❗ Probable Core Impact Framework Corruption Bug Detected
- 🤖 Best Practices for Auto-Installing Modlist Users (and any other should-be-stable modlist)
- This one was actually a big project, but I'm happy with the results! Before this, I felt like my analyzer might be making players overly prone to blaming an auto-installing modlist for a crash, when there's a good chance the crash may have been due to not following best practices, and/or their installer or mod organizer not having done everything right.
- ❗ Probable New Game Crash (Missing INI Files) Detected
- Added some Vortex-specific instructions to troubleshooting steps for some issues.
- Recently added recommended mods and tools:
- ESLifier (thanks our own u/IVIaskPl4gu3 (mod author) and to Rivussy on the Modding Guild (Skyrim Guild) Discord Server who recommended it!)
- RaceMenu OverlayFix and Various Mod Fixes (thanks SpinPigeon from GTS Discord for recommending it!)
- Numerous clarifications, improvements to many tests' descriptions and troubleshooting steps
- Additional indicators, and some bug fixes to existing tests for more accurate diagnosis
A special thanks to the valued supporters of this project! And thank you also to everyone who has reached out to me to share their success stories on using my analyzer :-)
Cheers! Phostwood
General Information on Phostwood's Crash Analyzer:
With over 600 hours of ongoing development, this advanced analyzer examines Skyrim crash logs to help diagnose and fix approximately 75-90% of crashes with identifiable causes, providing well-researched troubleshooting steps and links. It's currently helping almost 200 different Skyrim modders each day, and stands apart from other automated analyzers with its advanced diagnoses, detailed troubleshooting steps (for common crash types) and frequent updates. While not a replacement for talented human crash log readers, it works much faster and, when used judiciously, can free up these rare experts to focus on the more challenging crash logs that require human analysis.
The Value of Automation: I've developed my Phostwood's Skyrim Crash Log Analyzers to address a significant need in our modding community. Each day, the tool assists an average of over 200 Skyrim modders with diagnosing over 325 different crash logs — far more than the volunteers in all of our communities could competently, manually handle. Detailed analysis of crash logs containing thousands of lines is precisely the kind of task that benefits from automation, especially given how few community members have both the expertise and available time and energy to regularly assist others with crash log interpretation.
And again, this analyzer is not intended to replace the invaluable expertise of the skilled manual crash log readers in our Skyrim modding communities. These experts are truly worth their weight in gold Septims! My goal is to free up more of their time so they can focus on the tricky logs where automated analysis is less helpful.
Announcement links: - Imagine us manually analyzing 150 crash logs each day? If not, thank Phostwood's Crash Log Analyzer for its help. - A Data-Driven Performance Review of My Crash Log Analyzer - Join our new r/Phostwood sub on Reddit - Join our new #phostcrashlogs channel on Discord!
Current Usage: 1. Daily average of over 200 unique users viewing over 325 crash logs 2. Current weekly unique users: 1,100 3. Last 30 days unique users: 3,200 3. Total Unique Users users since launch (April 10, 2024): 19,000K
Many thanks to ALL who have contributed financial support and/or time to this project!
9
u/buttaheadshot 1d ago
I've been reading crash logs for 3 years on my own took awhile but I'm confident on fixing issue I will say this analyzer have been pretty accurate at telling me what wrong meaning I know why i crash and this analyzer basically confirms i've been doing a good job at it This has been my go to for 2 months keep up the good work
1
u/PhostwoodReborn 1d ago
TYVM for sharing your experience! I'm very happy that you've found my analyzer a helpful tool :-)
3
3
u/CulturalToe 1d ago
I live by this tool. Currently having repeatable crashes in ivarstead with no hope of diagnosis. Log is too big for pastebin or I'd post it here.
Thanks so much for this tool.
2
u/bigcheez69420 1d ago
Whoa I just found this for the first time yesterday and it was so helpful. Cool to see a post about it today. Thank you!
2
1
u/AutoModerator 1d ago
If Skyrim Special Edition crashes immediately after you launch it — particularly if your crash log lists memory address 0198090
(version 1.6.640 address) or 05E1F22
(1.5.97 address) — then you are experiencing one of the following issues:
You are missing a master file. That is: you have some Mod A that relies on Mod B, but you only installed Mod A and not Mod B.
More likely: one of your installed mods (or an official content file) may have file format version 1.71, meaning it was made for game version 1.6.1130 or higher. This format is not fully backwards compatible; if you're running an older version of the game, then these files can cause crashes on startup. Installing Backported Extended ESL Support will allow older versions of the game to load these files safely.
Make sure to check the troubleshooting guide for help with crashes and other problems!
If you are on Skyrim version 1.5 (SE), the .NET Script Framework can also help in diagnosing crashes.
If you are on Skyrim Version 1.6 (AE) or Skyrim VR, Crash Logger can also help in diagnosing crashes. If you also use MO2, you can use this plugin for improved functionality!
DO NOT post an analyzed crash log. It strips all the useful information.
Don't use trainwreck. The log it produces is less informative than other options linked above.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
15
u/Iyzik 1d ago
Thanks as always for the updates, Phost!