Log in to reply
 

Exit code 0xc0000005 indicates a fatal game exit (reason: STATUS_ACCESS_VIOLATION)



  • Hey all,

    Okay so this started happening around the time the new launcher came into play - I've seen many threads and the main one on GTA forums regarding this. First time for me I got rid of all mods and fresh install and was still happening, thought it could be a mod but it clearly wasn't so left GTA V alone, till now when I went back into mods after Scripthook updated today. The problem still remains, I play for around 30 mins and then it just CTD - launcher says GTA V exited unexpectedly and launcher log in my documents says [2019-09-25 13:38:01.081] [ ERROR ] [ 3620] [crashdetection] Exit code 0xc0000005 indicates a fatal game exit (reason: STATUS_ACCESS_VIOLATION)

    Anyone seeing this recently? Anyone know a fix - As I say this happens to me without mods and only in GTA V.



  • Are you sure this is the Launcher? And not the Windows update that came about three weeks ago?

    Because I also started crashing on exit, with exact same code, after said update. And it all subdued once I reverted the system.



  • Could actually be - I've done a GPU roll back as well as I've seen nvidia driver may also be issue - Gonna test this and see, what is the best/safest way to revert windows. Now you mention it could be windows or GPU as a driver update also happened around the same time.



  • I try everything but error still appearing... specially when using mod and script, it's must be gameconfig setting that cant handle mods and script running.


  • MODERATOR

    @TheMurderousCricket said in Exit code 0xc0000005 indicates a fatal game exit (reason: STATUS_ACCESS_VIOLATION):

    Are you sure this is the Launcher? And not the Windows update that came about three weeks ago?

    Because I also started crashing on exit, with exact same code, after said update. And it all subdued once I reverted the system.

    Who cares about crashing on exit?! In fact, if there's ever a good time where it's perfectly okay with me to crash, then it's on exit. :P

    ln all seriousness, happened to me a few times too. It's totally harmless. The crash seems to occur when the game has already quit. Maybe something about the launcher not catching the exit code properly (in time?).



  • Nope this is a CTD while playing - I could live with crashing when wanting to quit but this isn't that - This is while playing a game freezes for split second and just goes to desktop.



  • @meimeiriver - Well, not me. ;) You see, GTA is one thing, but I am also a die-hard LSPD:FR fan.

    After the new Windows update, I got Rage Plugin Hook Crashes, each time I engaged in a callout. Even callouts made by stars like Albo1125 were failing! And this simply was not the case before. I have my LSPD:FR copy in a perfect shape, believe me. I never experience crashes while playing.

    So, given the system revert helped, I'm inclined to think that this was the exact cause why LSPD:FR was going nuts and why I got on-exit crashes. You want evidence presented to the court? I do have evidence Your Honor! ;)

    Here's an article about this issue. Note that they mention Visual Basic:

    https://www.digitaltrends.com/computing/windows-10-update-vb-break/


  • MODERATOR

    @PracticallyGeek said in Exit code 0xc0000005 indicates a fatal game exit (reason: STATUS_ACCESS_VIOLATION):

    Nope this is a CTD while playing - I could live with crashing when wanting to quit but this isn't that - This is while playing a game freezes for split second and just goes to desktop.

    Those errors are the most annoying, and the least descriptive. Like

    Log Name:      Application
    Source:        Application Error
    Date:          25-Sep-19 20:25:37
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      DESKTOP-4PV79M4
    Description:
    Faulting application name: GTA5.exe, version: 1.0.1737.0, time stamp: 0x5d373e5a
    Faulting module name: clr.dll, version: 4.8.4010.0, time stamp: 0x5d3a249a
    Exception code: 0xc00000fd
    Fault offset: 0x000000000066e570
    Faulting process id: 0xd58
    Faulting application start time: 0x01d573cc9335537d
    Faulting application path: I:\SteamLibrary\steamapps\common\Grand Theft Auto V\GTA5.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    Report Id: ef8d6f53-f38a-4fd6-816e-b88ed438b5cc
    Faulting package full name:
    Faulting package-relative application ID:
    

    Yeah, that's real useful. :) I always suspect it's a memory issue somehow, as it happens a lot more when I have many peds loaded and such. But increasing/decreasing PedMemoryMultiplier and the one for vehicles, I can't say I ever noticed a difference.



  • FInally! I've been looking for hours since last night trying to find the same error I've been getting. I'm installing the rolled back driver right now, praying this is the fix which will actaully work after applying all the fixes which don't work.



  • This post is deleted!


  • This post is deleted!


  • This post is deleted!


  • Hey all - just an update - I've read two main solutions so far - GPU driver is the issue or windows update from around a month ago.
    I've rolled back my driver and currently seems to be not getting this error although I don't think I've played for over an hour before fucking about with mods again. Tried LSPDFR and liked it but didn't think it was epic, probably amazing online with FiveM but I'm not into that.
    Anyway off track, I've modded again with my fav mods and wanted to try map editor, got this CTD with Game exited with code 0xc00000fd

    Hopefully it was that or could be that I've just installed Liberty City Rewind - Time will tell - Pretty sure I had play time on LSPDFR with no CTD.



  • I've had good luck so far with -scOfflineOnly added to the commandline.txt. went from ~20 minutes after game start to CTD and after adding it, no crashes even after 4 hours straight.



  • To be fair, after ~ 4-5 hours it CTD on me, but that's a much easier thing to deal with than every few minutes. I'm still troubleshooting what the heck is causing it as even a vanilla install does the same thing. I've been in GTAO grinding on missions when a random CTD hits. Going to try checking my system drivers next.



  • I deleted the Rockstar Games Launcher.exe, Social Club Setup.exe, GTAV.exe, GTAVLauncher.exe, and Play GTAV.exe along with removing the GeForce experience "optimizations". Ran GTAO for 3 hours and no CTD where before it CTD in 20 minutes. Doing the same to my modded folder to see if this works as well.



  • @PracticallyGeek said in Exit code 0xc0000005 indicates a fatal game exit (reason: STATUS_ACCESS_VIOLATION):

    0xc00000fd

    On my case, common error 0xc00000fd caused by scripts (NET crash) and 0xc0000005 caused by mods (contain large prop or hight texture) also because of gameconfig that cant handle mods and scripts running. By editing gameconfig causing memory leaking maybe that why the game running in certain time until reach memory limit and than CTD.


  • MODERATOR

    @rednobel said in Exit code 0xc0000005 indicates a fatal game exit (reason: STATUS_ACCESS_VIOLATION):

    @PracticallyGeek said in Exit code 0xc0000005 indicates a fatal game exit (reason: STATUS_ACCESS_VIOLATION):

    0xc00000fd

    On my case, common error 0xc00000fd caused by scripts (NET crash) and 0xc0000005 caused by mods (contain large prop or hight texture) also because of gameconfig that cant handle mods and scripts running. By editing gameconfig causing memory leaking maybe that why the game running in certain time until reach memory limit and than CTD.

    Game crashes are notoriously hard to track properly. A few things to keep in mind, though:

    1. I hate the Rock* launcher like any other person, but it should not be subject to FUD. The launcher is not responsible for all sorts of weird errors ppl are experiencing (and attributing to it). Once the game is running, it doesn't mess with the game at all.

    2. Fixing one particular item in the gameconfig does NOT mean you 'solved' it; you may have fixed one thing, but likely broke something else in the process. Tweaking gameconfig settings is simply a beatch, and highly contigent on what you're doing with your mods. And thus a very individual matter.

    3. .NET errors may point to a script error (the .dll kind), but even that is not entirely sure. After all, SHVDN is kind of a hack (albeit it an awesome one), made to have .NET stuff run under C++. There's no telling precisely whether your own C# script went awry, or something along what makes the 'hook' work.

    4. Memory seems still the most prominent culprit for crashes (assuming you already installed the heap adjuster and such). I can mod for hours, without a single crash, and load (Menyoo) an entire car park, and 100+ peds, and see me crash within like ten minutes. What gameconfig value needs to be increased, or decreased (!) for that matter, is always a topic of much frustration.

    5. Use the true and trite process of elimination. Start big: rename your scripts folder. If the crashes are now gone, likely one of your .NET mods caused it. Then rename the scripts folder back, lower the granularity, as it were, and start remaming the extensions of the individual scripts, one by one, to see which one it might be.

    Do the same for addon packs. Remove your car addons DLC (you did consolidate them all into 1, right?!) from the dlclist.xml file. If the game no longer crashes, or less frequent, then you need tweak gameconfig settings for that area. (Indeed vague, but there's no 1-solution-to-fit-them-all).

    Tl;dr: there's no 1 cause, hence no 1 solution.


Log in to reply
 

Looks like your connection to GTA5-Mods.com Forums was lost, please wait while we try to reconnect.