Jump to content

Recommended Posts

Posted (edited)

Hello, I have been getting this error for weeks now, and I believe it is a rage issue, not client side as I was always able to play. Now suddenly I keep running into this issue, I'm not sure what could lead to this but my guess is the new Nvidia APP, as since downloading that the game has been crashing for me. I have run all possible fixed on the pc and have achieved nothing please help!


Actions Taken:
1. Windows was Reinstalled twice once locally, but the issue persisted a second time from the cloud (totally new install .iso)
2. Fully Updated all Drivers with Driver Booster PRO and Nvidia App
3. Ran all the following commands:
sfc /scannow
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /restorehealth
chkdsk /r /f /b
(All resulted in 0 corruption)
4. Reinstalled Epic Games, RageMP, Rockstar Games, and GTA.
5. High Priority Set to Epic Games & RageMP
6. Set RAGEMP to compatible with Windows 8
7. All overlay apps disabled
8. Ran Memtest to check RAM (Perfect Conditions)
9. Ran Windows SSD Scan (Perfect Conditions)

PC Specs:
Intel Core i7-14700K 3.4/5.6GHz
Gigabyte GeForce RTX 4060 Ti AERO OC 16GB GDDR6 DLSS3
Asus Prime Z790-A Wifi
Deepcool LT720 360 Kit
Corsair Vengeance DDR5 6400MHz PC5-51200 32GB 2x16GB CL32
Corsair RM White Series RM850 850W 80 Plus Gold Full Modular
Samsung SSD 980 PRO PCle 4.0 NVMe M.2 2TB

Edited by graavvee
  • 1 month later...
Posted
On 3/21/2024 at 4:16 PM, graavvee said:

and I believe it is a rage issue, not client side as I was always able to play

If it was rage issue, many other servers and users would experience it and it would get solved. RAGEMP added better error handling, before errors like these would just silently crash. I just hope it is being worked on to get at least a bit more details on where error occurred. Try closing all background processes before running RAGEMP to rule out any conflicts.

Posted
1 hour ago, Kopra said:

If it was rage issue, many other servers and users would experience it and it would get solved. RAGEMP added better error handling, before errors like these would just silently crash. I just hope it is being worked on to get at least a bit more details on where error occurred. Try closing all background processes before running RAGEMP to rule out any conflicts.

Well even I am getting that error since the past 2 days and I know a friend of mine who's also getting same error again and again literally tried everything

  • 2 weeks later...
  • 2 months later...
  • 5 months later...
Posted

I am facing exactly the same issue mentioned in this thread. On my two machines, the one running without any problems is running Windows 10 Pro. On the machine running Windows 11 Home, the exact same error described in this thread occurs. Has a solution been found yet?

Posted

I was really having trouble opening the story mode. In the properties of the game’s executable, I disabled the "Run as Administrator" option and managed to open the game in both story mode and online mode. This week, I’ll have more time to play and will provide feedback to see if the crashes are fixed or at least reduced.

I would also like to add that I had significant difficulties joining servers that use C# on the client side, because the notification forces the player to double-click "OK" to allow C# scripts to run on the client machine. However, if the game is not started in windowed mode or minimized before the notification appears, the player is unable to open the notification screen to allow C# scripts to run before they can play on the server. I find this notification completely unnecessary, forcing the player to accept running C# scripts before playing, because before even connecting to any server, the player should already be aware that playing on unknown servers can be risky. It also creates a barrier of complexity for beginners, as many have trouble or cannot even play on C# servers because they cannot access the notification to click "OK" twice and accept the risks of playing on unknown servers.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...