Crash Analyzer [Enhanced / Legacy] 1.0.1
![Rune Ruble (VAZ-2105) [Add-On | Tuning | Liveries]](https://img.gta5-mods.com/q75-w500-h333-cfill/images/rune-ruble-vaz-2105-add-on-tuning-liveries/44e58e-1.jpg "Rune Ruble (VAZ-2105) [Add-On | Tuning | Liveries]")
906
45
906
45
GTA V Crash Analyzer is an ASI plugin that stays in the background while you play. If the game crashes, it opens a window that tells you:
What it detects
Installation
You need an ASI Loader. You already have one if OpenIV.asi or ScriptHookV work.
Copy CrashAnalyzer.asi, CrashAnalyzer.exe and CrashAnalyzer.ini into the game folder.
Supports both versions: Legacy and Enhanced
Settings (CrashAnalyzer.ini)
Enabled=1: turns the plugin on or off.
WriteMinidump=1: writes a .dmp file for each crash.
ChainToGameHandler=0: passes the exception on to the game's own handler after analysis (usually not needed).
Language=auto: report language. auto uses the game's language; you can also set en-US, ru-RU, de-DE and so on.
Changelog
1.0.1
- Fixed: if your ASI Loader is named `version.dll` (or another DLL that CrashAnalyzer.exe uses), the watcher loaded all .asi plugins into itself and started copies of itself without end, which slowed the PC down and opened many windows. CrashAnalyzer.exe now loads system DLLs only from System32, and the plugin runs only inside GTA5.exe / GTA5_Enhanced.exe (not in launchers).
1.0.0
- First release.
- Where it crashed
- The probable cause, with a confidence level
- What to do: concrete steps based on what you already have installed (gameconfig, Packfile Limit Adjuster, Heap Adjuster, game version)
- Other problems found in your mods, even if they didn't cause this particular crash
- Technical details for mod authors: exception code, faulting module and offset, call stack, memory, and the archives and files opened last
What it detects
- Exceeded game limits: no extended gameconfig.xml, or the original encrypted Rockstar one, while add-on DLCs are installed.
- Packfile limit: the number of mounted archives (from OpenIV.log) compared with the limit from Packfile Limit Adjuster.
- Damaged archives: bad RPF7 header, truncated or incompletely downloaded archives, broken nested .rpf files, damaged compressed resources (.yft, .ytd. etc.).
- Config errors inside RPFs: XML errors with line numbers in setup2.xml, content.xml, .meta and .xml; content.xml entries pointing to missing files; two packs with the same deviceName; errors, duplicates and missing packs in dlclist.xml; a damaged gameconfig.
- Crashes in mods: .asi plugins, mod DLLs, ScriptHookV, ReShade/ENB, including a mod that appears in the call stack.
- Graphics drivers and overlays: NVIDIA/AMD/Intel drivers, RTSS, Discord, Steam overlay and others, including instant "fail-fast" crashes (read from the Windows event log).
- Game errors ERR_*: ERR_MEM_*, ERR_GFX_*, ERR_FIL_PACK, ERR_STR_*, ERR_SYS_INVALIDRESOURCE and more, each with an explanation.
- Other: out of memory, disk read errors, ScriptHookV not supporting your game version, modified original archives, a mods folder without OpenIV.asi.
Installation
You need an ASI Loader. You already have one if OpenIV.asi or ScriptHookV work.
Copy CrashAnalyzer.asi, CrashAnalyzer.exe and CrashAnalyzer.ini into the game folder.
Supports both versions: Legacy and Enhanced
Settings (CrashAnalyzer.ini)
Enabled=1: turns the plugin on or off.
WriteMinidump=1: writes a .dmp file for each crash.
ChainToGameHandler=0: passes the exception on to the game's own handler after analysis (usually not needed).
Language=auto: report language. auto uses the game's language; you can also set en-US, ru-RU, de-DE and so on.
Changelog
1.0.1
- Fixed: if your ASI Loader is named `version.dll` (or another DLL that CrashAnalyzer.exe uses), the watcher loaded all .asi plugins into itself and started copies of itself without end, which slowed the PC down and opened many windows. CrashAnalyzer.exe now loads system DLLs only from System32, and the plugin runs only inside GTA5.exe / GTA5_Enhanced.exe (not in launchers).
1.0.0
- First release.
Primo Caricamento: 3 giorni fa
Ultimo Aggiornamento: 1 giorno fa
Last Downloaded: 5 minuti fa
34 Commenti
More mods by andre500:
GTA V Crash Analyzer is an ASI plugin that stays in the background while you play. If the game crashes, it opens a window that tells you:
What it detects
Installation
You need an ASI Loader. You already have one if OpenIV.asi or ScriptHookV work.
Copy CrashAnalyzer.asi, CrashAnalyzer.exe and CrashAnalyzer.ini into the game folder.
Supports both versions: Legacy and Enhanced
Settings (CrashAnalyzer.ini)
Enabled=1: turns the plugin on or off.
WriteMinidump=1: writes a .dmp file for each crash.
ChainToGameHandler=0: passes the exception on to the game's own handler after analysis (usually not needed).
Language=auto: report language. auto uses the game's language; you can also set en-US, ru-RU, de-DE and so on.
Changelog
1.0.1
- Fixed: if your ASI Loader is named `version.dll` (or another DLL that CrashAnalyzer.exe uses), the watcher loaded all .asi plugins into itself and started copies of itself without end, which slowed the PC down and opened many windows. CrashAnalyzer.exe now loads system DLLs only from System32, and the plugin runs only inside GTA5.exe / GTA5_Enhanced.exe (not in launchers).
1.0.0
- First release.
- Where it crashed
- The probable cause, with a confidence level
- What to do: concrete steps based on what you already have installed (gameconfig, Packfile Limit Adjuster, Heap Adjuster, game version)
- Other problems found in your mods, even if they didn't cause this particular crash
- Technical details for mod authors: exception code, faulting module and offset, call stack, memory, and the archives and files opened last
What it detects
- Exceeded game limits: no extended gameconfig.xml, or the original encrypted Rockstar one, while add-on DLCs are installed.
- Packfile limit: the number of mounted archives (from OpenIV.log) compared with the limit from Packfile Limit Adjuster.
- Damaged archives: bad RPF7 header, truncated or incompletely downloaded archives, broken nested .rpf files, damaged compressed resources (.yft, .ytd. etc.).
- Config errors inside RPFs: XML errors with line numbers in setup2.xml, content.xml, .meta and .xml; content.xml entries pointing to missing files; two packs with the same deviceName; errors, duplicates and missing packs in dlclist.xml; a damaged gameconfig.
- Crashes in mods: .asi plugins, mod DLLs, ScriptHookV, ReShade/ENB, including a mod that appears in the call stack.
- Graphics drivers and overlays: NVIDIA/AMD/Intel drivers, RTSS, Discord, Steam overlay and others, including instant "fail-fast" crashes (read from the Windows event log).
- Game errors ERR_*: ERR_MEM_*, ERR_GFX_*, ERR_FIL_PACK, ERR_STR_*, ERR_SYS_INVALIDRESOURCE and more, each with an explanation.
- Other: out of memory, disk read errors, ScriptHookV not supporting your game version, modified original archives, a mods folder without OpenIV.asi.
Installation
You need an ASI Loader. You already have one if OpenIV.asi or ScriptHookV work.
Copy CrashAnalyzer.asi, CrashAnalyzer.exe and CrashAnalyzer.ini into the game folder.
Supports both versions: Legacy and Enhanced
Settings (CrashAnalyzer.ini)
Enabled=1: turns the plugin on or off.
WriteMinidump=1: writes a .dmp file for each crash.
ChainToGameHandler=0: passes the exception on to the game's own handler after analysis (usually not needed).
Language=auto: report language. auto uses the game's language; you can also set en-US, ru-RU, de-DE and so on.
Changelog
1.0.1
- Fixed: if your ASI Loader is named `version.dll` (or another DLL that CrashAnalyzer.exe uses), the watcher loaded all .asi plugins into itself and started copies of itself without end, which slowed the PC down and opened many windows. CrashAnalyzer.exe now loads system DLLs only from System32, and the plugin runs only inside GTA5.exe / GTA5_Enhanced.exe (not in launchers).
1.0.0
- First release.
Primo Caricamento: 3 giorni fa
Ultimo Aggiornamento: 1 giorno fa
Last Downloaded: 5 minuti fa
5mods on Discord
Does it include the functions in PoolManager?
Strangely enough starts my game 5 times and throws loads of error that causes my PC to get bricked..I like the idea though. (Enhanced)
@Enzo95 Do you remember what kind of errors they were, roughly?
same for me but no errors unfortunatly
CrashAnalyzer.exe keeps launching my game over and over, opening a bunch of windows, which makes my computer really slow. Unfortunately, there aren't any error reports.
@Moxii Same thing!
that work with fivem ?
@Moxii Same thing, I't doesnt work only relaunch my game in while
@Moxii Same thing.
@Moxii @Enzo95 @SamShoker @egorsidorovich54 @Akram11 @x2er3o Thanks for the reports, and sorry for the trouble. Fixed in 1.0.1.
Hi! First of all, thank you for developing Crash Analyzer. It's a very useful tool for troubleshooting GTA V crashes.
I'm currently testing GTA V Legacy 1.0.3725.0 with more than 2700 add-on vehicle DLCs, and I have a few suggestions:
1. **Prioritize the actual crash cause:** The reports can contain hundreds of DLC-related warnings, making it difficult to distinguish the real cause of a crash from unrelated or pre-existing issues.
2. **Improve crash correlation:** It would be extremely helpful if the analyzer could identify the most likely cause based on the exception code, call stack, loaded modules, and what the game was doing immediately before crashing.
3. **Separate critical errors from general warnings:** A summary showing confirmed errors, suspected causes, and informational warnings would make troubleshooting much easier.
4. **Reduce repeated warnings:** Grouping duplicate or similar DLC warnings could make large reports significantly easier to analyze.
5. **Provide actionable recommendations:** For crashes such as 0xC0000005 and ERR_MEM_EMBEDDEDALLOC_GUARD_1, it would be helpful to know which findings are supported by the crash data and which are only possible explanations.
The goal is to identify genuine stability problems without unnecessarily removing working vehicle mods.
Thanks again for your work and for considering these suggestions!
Excellent idea! Unfortunately, it seems to prevent my game from loading. It complains that I don't have OpenIV installed, which is technically true, because I use RageOpenV instead. It also seems to be unable to interpret any RPF archives that have been NG Encrypted.
@andre500 https://imgur.com/a/zo58Crl
Crash Analyzer sees referrals to files that don't exist in the pack in content.xml, but when I look in the content.xml file, I can see those referrals are there, but they're commented out. It does this with multiple vehicle mods, like https://www.gta5-mods.com/nl/vehicles/ocelot-ardent-turbo-add-on and https://www.gta5-mods.com/nl/vehicles/dinka-serena-add-on-tuning-liveries-sounds, so I get a long list of false positives.
@Pizzahut Thanks for the report. I'll fix it in the next patch.
You're the best 🏆
Thanks for this man, I really like this🔥🔥👌
This is gonna be a lenghty comment in regards to this particular mod so bare with me. I feel the need to explain what's being happening with this so let me first just say, this mod has a lot of potential, it has the capacity to become or develop into something truly essential for all of us but at this early stage it seems as if it's not exactly addressing the actual problem of the crash itself. If your game crashes this mod will show you a full "crash" report but it DOES NOT addresses the actual cause of the crash because this only detects software issues and many of those issues in the report has nothing to do with the crash itself. I'll give you an example, my gaming laptop has two bad cores, they tend to heat up so I had to use ThrottleStop in order to tweak the voltage going into my cpu, to maintain those cores at an even keelish level. So sometimes, whenever a lot of activity happens in game the cpu may not handle it and crash the game, this is something that I"m aware of and this is a hardware issue not a "software" issue. This mod doesn't adress "hardware" issues, it only addresses "software" and some of those have nothing to do with the crash itself.
Don't get me wrong, all those problems shown on the Crash Analyzer report are legitimate, which means they're all true and all those minor issues on the report you can fix on your own but what I'm trying to say is that not all crashes are "software" based, some crashes are caused by hardware, your cpu or gpu not being able to handle a particular situation in the game and therefor it crashes. This mod won't give you that information, it will only give you information on "Probable" software related causes of the crash and other miscellaneous stuff. It just basically scans your entire archive in milliseconds just after the crash happens and creates a report. So again, this mod has a lot of potential but addressing little problems like missing tags in a file, texture issues and this and that and the other thing that doesn't addresses the real root cause of the problem. By the way, all the problems shown on the report are legitimate and you should fix 'em all, one by one, but you can run the game for up to two hours or longer with minor issues like that without the game crashing. Game crashes have much more serious causes and this mod doesn't necessarily pinpoints it directly. What we need is a strong crash detector that tells you immediately after a crash what caused it and it must show whether it was a software or hardware issue. This is not an easy mod to create, no wonder it hasn't been done by anyone prior and that's why I give andre500 a lot of credit for creating something like this.
Anyways, I'll give this 4 stars and I will only ask andre500 to keep working on this, this is one of a kind mod that we all need, specially if we play gta 5 pc, with a lot of potential in sight.
@JAM102970 I'm afraid while this mod has potential, it is creating too many false positives and confusing people way more than helping and all these people are just gonna ask on the GTA 5 mods discord. There's already been a few people who mistakenly thinks this mod is finished and are following the report to fix. This still gives too many errors that don't exist, and doesn't actually detect any crashes other than what the clr is reporting which is useless. This mod has potential for very basic beginner problems like no gameconfig installed or heap, but for %90 of the problems this is only gonna confuse more people who think the report is accurate. None of those errors in the report are accurate or need to be addressed for a crash free game. This is just adding confusion on an already difficult process. Start at the ground up, correct a few errors, but don't confidently say you know what the errors are when this software is just reading logs that has nothing to do with the crash.
@InfiniteQuestion Well, some of the stuff that showed on my report was actually legitimate, I checked it out but, like I said it just gives you a spectrum of minor stuff that doesn't necessarily pinpoints directly to the cause of the crash. This dude just has to keep working on it, this is on the early stages. How about you InfiniteQuestion, I know you, you and I go way back...why don't you create something like this on your own and make it work.
@InfiniteQuestion I completely agree with you. This mod is generating far too many false positives, flagging issues that, in practice, have absolutely no impact on the game's functionality. In my case, for example, it reports problems with over 300 vehicles, yet I can spawn, drive, and use all of them perfectly fine without any issues.
I believe development should focus primarily on identifying genuinely critical problems, such as crashes that unexpectedly close GTA V, prevent the game from launching, or seriously affect gameplay.
These overly alarming reports end up confusing less experienced users, who may spend hours trying to fix supposed errors that don't actually cause any problems.
This mod definitely has potential, but it needs to do a much better job of distinguishing informational warnings from actual critical failures. The priority should be identifying the real causes of crashes, not treating every minor irregularity as something that urgently needs to be fixed.
@JAM102970 Because a person shoudn't need an exe just to read logs, but for the people who do need it I guess this might help someone. Problem is it will currently confuse more than help as it confidently tells you whats wrong when its not.
WHERE THE CRASH HAPPENED
During gameplay, 1 min 6 s after launch
Last mounted DLC pack: "1mods" (add-on), 43 s ago
Last archive according to OpenIV.log: platform:/levels/gta5/interiors/v_int_19.rpf (4 s before the crash)
Last disk read: F:\Grand Theft Auto V Inf\mods\update\update.rpf
PROBABLE CAUSE (Confidence: medium)
Crash in a .NET script (ScriptHookVDotNet)
The exception occurred in the .NET runtime (clr.dll+0x5F8D10) that runs the scripts from the scripts folder.
WHAT TO DO
1. Look at ScriptHookVDotNet.log: it names the script with the error.
2. Update or temporarily remove the most recently installed scripts.
OTHER PROBLEMS FOUND
Damaged files in the DLC "1lights/whitelights" (1)
mods\update\x64\dlcpacks\1lights\whitelights\dlc.rpf:
• /x64/levels/gta5/whitelights/lodlights.rpf/smboat_distantlights.ymap: damaged resource header (no RSC7 signature): the model/texture is corrupted
→ Reinstall the DLC "1lights/whitelights" (download it again): the archive is damaged or incompletely downloaded.
→ If you built the pack yourself, rebuild it in OpenIV/CodeWalker.
Stack overflow
Infinite recursion, usually a bug in a script or an ASI plugin.
→ Disable the most recently installed scripts/plugins.
WHAT WAS CHECKED
• 5 minor findings that could not have caused this crash are not shown. For a full check run CrashAnalyzer.exe from the game folder.
• gameconfig.xml: modified (custom), 67.5 KB
• dlclist.xml: 414 packs, 18 of them add-ons
• DLC packs checked in mods: 49 (encrypted, header checked only: 0), XML/meta files: 663
• Packfile Limit Adjuster: installed, limit 13000 (default 3928)
• Heap Adjuster: installed, heap 1024 MB (default 466 MB)
• Archives mounted (according to OpenIV.log): 3466
Game uptime: 1 min 6 s
Crash indicator: unhandled exception caught by the plugin
Code: 0xC00000FD — STACK_OVERFLOW — stack overflow
Faulting module: clr.dll+0x5F8D10 [.NET (SHVDN scripts)] C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Registers: RIP=00007FFDC5D38D10 RSP=0000001EED4FE5B8 RAX=0000001EED4035C0 RCX=00007FFE3D5CDA04 RDX=0000000000000000
Process exit code: 0xC00000FD (3221225725)
This isn't helping anyone. This happens even if you exit the game normally so this wasn't even a crash report yet its reporting as one. This is more confusing than helpful.
Although it does catch xml parsing errors i made on purpose which is helpful for badly made mods
Configuration errors in the DLC "1addon/25f80" (1)
mods\update\x64\dlcpacks\1addon\25f80\dlc.rpf:
• /data/vehiclelayouts.meta: XML error on line 4720: closing tag </CVehicleMetadataMgr> does not match the open tag <CVehicleMetadataMgra> (line 3)
→ Fix the listed files inside dlc.rpf (OpenIV → edit mode) or reinstall the mod.
→ Check every .meta/.xml in the pack: even one unclosed tag or typo causes a crash on loading.
So at minimum this is an xml parser with a support file checker and log reader. It is not a crash detector like pool manager attempted to be and is not actually detecting anything other than when gta closes. This cannot detect when the gameconfig values are wrong. It cannot detect which files are wrong besides xml parsing. This tool needs to be more clear on what errors it can actually detect and not rely on an AI writing the description to be a catch all crash detector.