I am able to load the game up properly into story mode. I even verified my game files through steam before starting. I checked all my custom vehicles and all of them work properly including add on ones. I have tried restarting rage multiple times with only LSPDFR running and no other plugin, and continue to get a crash. I am able to start rage on it's own with no plugins no problem, but once I try and load LSPDFR it crashes. Could it be a callout pack I have installed or maybe a script? I manually updated LSPDFR first and I thought I might've installed it wrong so I used the auto installer and still no luck. I updated SHV and the packfile adjuster as well. The log is also pretty short and I'm just not sure why it's crashing so fast. Normally I've been able to resolve issues on my own or through looking at other threads but I feel I've tried a lot of things already. Maybe there's something obvious in that short log that I'm missing but I guess I don't know enough about troubleshooting if I can't find it myself so any help would be appreciated. I do have quite a bit installed, but it has been able to run just fine before the update, I haven't added anything else.RagePluginHook.log

Looks like it never reaches the point to actually load LSPDFR. Can you go to eventvwr.exe -> Windows Logs -> Application and post the corresponding GTA 5 crash details?

6 hours ago, LMS said:

Looks like it never reaches the point to actually load LSPDFR. Can you go to eventvwr.exe -> Windows Logs -> Application and post the corresponding GTA 5 crash details?

Spoiler

Faulting application name: GTA5.exe, version: 1.0.2699.0, time stamp: 0x62d9ac71
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
Exception code: 0xc00000fd
Fault offset: 0x00000000006833c0
Faulting process id: 0xc40
Faulting application start time: 0x01d8a2c1cf0692b3
Faulting application path: E:\SteamGames\steamapps\common\Grand Theft Auto V\GTA5.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 32b991e1-68d3-40c4-8241-c61ddf4fbfb3
Faulting package full name: 
Faulting package-relative application ID: 

I tried reinstalling the .NET framework and also used the repair tool after kind of glancing at this and still no luck. I tried searching for solutions to clr.dll errors and if my understanding is correct it might mean a memory problem? I'm aware that plugins like LSPDFR take a lot of memory, but if LSPDFR didn't actually load would it be the cause? Or did it simply just try to load but couldn't so it just terminated the game? Thank you.

I did a bit more testing on my own and found that I can only get LSPDFR to load when I have nothing in the Grand Theft Auto V\plugins\LSPDFR folder. If a single file is in there the game will crash and if it's empty I can load LSPDFR and go on duty. What could be causing this?

On 7/28/2022 at 11:58 PM, MisterFirestorm said:

I did a bit more testing on my own and found that I can only get LSPDFR to load when I have nothing in the Grand Theft Auto V\plugins\LSPDFR folder. If a single file is in there the game will crash and if it's empty I can load LSPDFR and go on duty. What could be causing this?

 

And this is on the most recent RPH (vehicle fix) I take it? Can you post the crash report details I asked for above?

On 7/31/2022 at 12:16 PM, LMS said:

 

And this is on the most recent RPH (vehicle fix) I take it? Can you post the crash report details I asked for above?

Yeah it's on the most recent. I've tried reinstalling it many times. I tried a number of solutions but I've only seem to made the problem worse. I used to be able to go on patrol, use EUP menu, run the spotlight plugin etc. all without any actual LSPDFR plugins installed like I mentioned, but after trying some fixes I found now when I load any plugin with RPH the game will crash in the same manner no matter what. So what I thought was for sure an LSPDFR issue, might just be either a system issue or an RPH one.

 

Are these the details you are looking for? 

 

Faulting application name: GTA5.exe, version: 1.0.2699.0, time stamp: 0x62d9ac71
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
Exception code: 0xc00000fd
Fault offset: 0x00000000006833c0
Faulting process id: 0x2c4
Faulting application start time: 0x01d8a50d9f4b7ebf
Faulting application path: E:\SteamGames\steamapps\common\Grand Theft Auto V\GTA5.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: e7c5a9a4-3a39-4809-a14a-318657f1c1a9
Faulting package full name: 
Faulting package-relative application ID: 

 

Spoiler

Fault bucket 1692291239219133616, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: GTA5.exe
P2: 1.0.2699.0
P3: 62d9ac71
P4: clr.dll
P5: 4.8.4515.0
P6: 624ce98e
P7: c00000fd
P8: 00000000006833c0
P9: 
P10: 

Attached files:
\\?\C:\Users\Oscar\AppData\Local\Temp\WER863B.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER961A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER965A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9686.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER96D5.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_GTA5.exe_1a5d906f5dd5d1317855a7dded689f4b315ae33_d3daf884_4b977d3e-a392-443e-b7ec-50a23322c846

Analysis symbol: 
Rechecking for solution: 0
Report Id: e7c5a9a4-3a39-4809-a14a-318657f1c1a9
Report Status: 268435456
Hashed bucket: 1b25e41bd359fc0ba77c39ea7a297cb0
Cab Guid: 0

 

Yeah, that is what I am looking for. It is hitting a stack overflow, though unsure why. Does RPH generate a crash report or does the process just die immediately?

1 hour ago, LMS said:

Yeah, that is what I am looking for. It is hitting a stack overflow, though unsure why. Does RPH generate a crash report or does the process just die immediately?

The process pretty much just dies immediately. No crash report is generated, the application just abruptly exits with no message of any kind from neither the system nor rage. I also have a new gameconfig and am able to load up with it, but I still get the same crash when I try to load plugins.

Could you, before loading a plugin, in the console type in "IsDeveloperModeEnabled true". Then tab out, look for the little V icon in your tray and set the logging verbosity to "Extremely Verbose". Then load a plugin and attach log here. It might not be enough to explain the stack overflow, but worth a shot.

1 hour ago, LMS said:

Could you, before loading a plugin, in the console type in "IsDeveloperModeEnabled true". Then tab out, look for the little V icon in your tray and set the logging verbosity to "Extremely Verbose". Then load a plugin and attach log here. It might not be enough to explain the stack overflow, but worth a shot.

If I did it correctly then here's the log. Not sure too much changed in it though. I tried loading EUP menu.

RagePluginHook.log

It seems it dies very early on in the plugin loading process. Can you follow the instructions under "5. Automatically create dump on Crash" (just use GTA5.exe instead of notepad.exe) and see if it generates a dump file for you: https://michaelscodingspot.com/how-to-create-use-and-debug-net-application-crash-dumps-in-2019/

 

If so, please zip and send me the dump file. If not, let me know and perhaps we need a debug build.

4 hours ago, LMS said:

It seems it dies very early on in the plugin loading process. Can you follow the instructions under "5. Automatically create dump on Crash" (just use GTA5.exe instead of notepad.exe) and see if it generates a dump file for you: https://michaelscodingspot.com/how-to-create-use-and-debug-net-application-crash-dumps-in-2019/

 

If so, please zip and send me the dump file. If not, let me know and perhaps we need a debug build.

As I was in the process of creating the keys and stuff I looked in the CrashDumps folder and found a few GTA5.dmp files already there consistent with the times of the crashes. When I zip one of them though it's still around like 18mb so how can I get that to you?

21 minutes ago, MisterFirestorm said:

As I was in the process of creating the keys and stuff I looked in the CrashDumps folder and found a few GTA5.dmp files already there consistent with the times of the crashes. When I zip one of them though it's still around like 18mb so how can I get that to you?

 

Just upload it on something like Google Drive or OneDrive.

3 hours ago, LMS said:

 

Just upload it on something like Google Drive or OneDrive.

I believe it should be here: - edited since I retrieved it and it might contain user information -

Are you using SHVDN by any chance? If so, can you try removing it and see if the issue still happens?

1 hour ago, LMS said:

Are you using SHVDN by any chance? If so, can you try removing it and see if the issue still happens?

I was indeed using SHVDN and upon removing it I can happily say I am able to load plugins and do pretty much everything else. I never thought to remove it due to SHV being updated but I guess that might not make too much sense since I don't believe they're created by the same person. I don't even remember what scripts I needed it for but I'll try playing for a bit and see if I even need it or if any other problems arise. Thank you so much for your help but I guess my question now is what happened? Is there a bug with SHVDN or maybe there's something conflicting with it? I haven't really seen this to be a common problem for other people so far. Again thanks a lot for your help, I really appreciate it and I hope I won't run into any other problems.

11 hours ago, MisterFirestorm said:

I was indeed using SHVDN and upon removing it I can happily say I am able to load plugins and do pretty much everything else. I never thought to remove it due to SHV being updated but I guess that might not make too much sense since I don't believe they're created by the same person. I don't even remember what scripts I needed it for but I'll try playing for a bit and see if I even need it or if any other problems arise. Thank you so much for your help but I guess my question now is what happened? Is there a bug with SHVDN or maybe there's something conflicting with it? I haven't really seen this to be a common problem for other people so far. Again thanks a lot for your help, I really appreciate it and I hope I won't run into any other problems.

 

Unfortunately, you hit a deep-rooted issue in SHVDN that cannot be easily solved. It has nothing to do with it being updated or not (usually it does not have to after a SHV update), but it is due to an unfortunate design mistake in how they handle script ticks. It can randomly affect anyone; however, some users (like yourself) experience the issue every time. Why that is, I am not sure. At this point I would not recommend using SHVDN. I provided a detailed rundown of the issue and how to fix it here, if you are curious: https://github.com/crosire/scripthookvdotnet/issues/976