Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
drivereasy.com+1
Fix using Run System Restore
Deactivate Data Execution Prevention (DEP) for the Program
Deactivate the AppInit DLLs Mechanism in the Windows Registry
Disable antivirus and Defective RAMThe error can also be caused by a problem in your memory or a general failure to process the app's settings by your operating system.
Found your issue. One of your RAM may be defective or Dying, happened to me when i removed the dying RAM, all good.
"Application Error 0xc0000005 (Access Violation) error is usually caused by your computer not being able to correctly process the files and settings required to run a particular program or installation. Despite the error showing when you try and use particular pieces of software, it has many different causes including faulty RAM problems, errors with the files of your PC and issues with the settings of your PC.
In this case, we suggest that you check for corrupted Windows system files. System File Checker (SFC) is a utility in Windows that scans for corrupted Windows system files. If it finds a problem, it will try to replace the problematic system files from a cached version that’s on your PC.
To run System File Checker (SFC), follow these steps:
In the search box on the taskbar, type command prompt, press and hold (or right-click) Command Prompt, then select Run as administrator > Yes.
At the command prompt, type sfc /scannow (note the space between sfc and the /). Scanning will take a few minutes.
If SFC finds corrupted files and replaces them, restart your PC and check if the issue persists.
For more info about System File Checker, see Use the System File Checker tool to repair missing or corrupted system files."
More in Depth and Simple.
That is no game error. That is an OS error. The issue is on your side. Not the game's fault.
You will not find fish if you search in the middle of the desert
this game was normal in the beginning bro, it started to crash after the 80hrs play
Is not exactly exclusive to OS or Hardware issues, in fact you not the first one to run into this issue with Wilds.
Do not waste time with SFC scans, is the typical suggestion from nobodies at Microsoft Answers that don't know how to diagnose issues, there is nothing more useless.
I would recommend clearing the shader cache and re-checking your game files on Steam.
The latest NVidia driver is also known to cause crashes in multiple games right now.
In what folder?
Sorta
Both
C:\ProgramData\NVIDIA Corporation\NV_Cache
C:\Users\[USERNAME]\AppData\Local\NVIDIA with two respective folders, DXCache and GLCache
i wouldn't knew about this if i didn't change my graphic card from 3080 to 9070.
nvidia really don't want you to change it or the graphic card.
at the worse case scenario you would need to uninstall/reinstall the game + reinstall windows. *which i did cuz i changed my graphic card
Eh... if anyone wants to address the actual game related shader cache, they use tip#16 + #17 here and restart their PC
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
You never need to reinstall the game, unless you having a storage drive defect. In fact, it would not help, because the game's shader cache is unaffected by uninstallation. You have to manually remove it.
A lot of benchmark users still have a large shader cache sitting around because of that, just taking away space while doing nothing.
And Nvidia's cache - even if you do not know the path, there is a simple trick via the control panel, while AMD has it in their Adrenaline app as an option. Both methods are described (even if partially very poorly) in the pinned thread.
But either is not related to this threadstarter's issue. Threadstarter simply has an OS permission issue and they probably run some conflicting background app, as seen in another case with MSI Afterburner.