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
You have hardware which fulfills at least the minimum requirements for the game, right?
And yeah, your hardware should run the game just fine.
01:15:58:180 (00017536) > [Crash] Unhandled exception at address 0x000000005b7a8a07 (code: 0xc0000005): "Access violation"
Players of Crystal Dynamics games made with the same engine have experienced similar issues in the past. Someone seems to have fixed it by disabling dedicated fullscreen option in the launcher, so it's worth a try.
In general such errors are the game trying to access a protected part of memory, which creates a access violation crash. It can be caused by an error in the Windows registry too.
https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e
And if it's a registry error, Windows has a repair tool for these as well:
https://support.microsoft.com/en-us/topic/description-of-the-windows-registry-checker-tool-scanreg-exe-aaae4323-daa2-8477-5a4e-2a273779fdf0
Thanks for your reply Captain Worthy.
Strange thing is the launcher won't open. When I click play, it appears as if it's doing something and then nothing. It simply goes back to the play button. No option to change anything in the launcher as it never appears.
Yesterday, the launcher finally appeared for the first time after the last update to the game. Then there was a Steam update, and once again the error resumed. Seems odd the game will work perfectly fine and then break after an update to either Steam or the game itself.
This is the file from a successful launch:
17:35:07:486 (000♥♥♥♥0) > [Render] Enumerating monitors:
17:35:07:486 (000♥♥♥♥0) > [Render] Monitor 0: handle = 0000000004e10fd1, aspect = 1.78
17:35:07:486 (000♥♥♥♥0) > [Render]
17:35:07:781 (000♥♥♥♥0) > [Render] Enumerating Display Modes:
17:35:07:782 (000♥♥♥♥0) > [Render] Querying NVAPI for Surround modes
17:35:08:690 (000♥♥♥♥0) > [Render] NvAPI_Mosaic_GetDisplayViewportsByResolution() - no surround modes detected
17:35:10:589 (000♥♥♥♥0) > [NxDLSS] DLSS support test, code = 0x00000001, info: NVSDK_NGX_Result_Success
17:35:12:613 (000♥♥♥♥0) > [Intel XeSS] Failed to init XeSS on dummy device during setup. Error: 4294967286
17:35:12:613 (000♥♥♥♥0) > [Render] Monitor '1 (NVIDIA GeForce (1))' (0000000004e10fd1):
…
17:35:13:300 (000♥♥♥♥0) > [NxApp] Enumerating available display adapters:
17:35:13:301 (000♥♥♥♥0) > [NxApp] NVIDIA GeForce (active)
17:35:13:304 (000♥♥♥♥0) > [NxApp] Intel(R) HD Graphics
17:35:13:307 (000♥♥♥♥0) > [NxApp] Intel(R) HD Graphics
17:35:13:309 (000♥♥♥♥0) > [NxApp] Successfully found GPU Driver Info
It proceeds to successfully run Render tests on Monitor 1, and ultimately, it finds the GPU driver information and launches the launcher.
After turning on my AV Receiver, the game again failed to open the launcher. I clicked “Play” in Steam, and nothing happened. It returned to “Play.” This is what that log shows:
17:39:40:893 (00015776) > [Render] Enumerating monitors:
17:39:40:893 (00015776) > [Render] Monitor 0: handle = 00000000022a11d3, aspect = 1.78
17:39:40:893 (00015776) > [Render] Monitor 1: handle = 000000000b820da3, aspect = 0.56
17:39:40:894 (00015776) > [Render]
17:39:41:490 (00015776) > [Render] Enumerating Display Modes:
17:39:41:492 (00015776) > [Render] Querying NVAPI for Surround modes
17:39:42:814 (00015776) > [Render] NvAPI_Mosaic_GetDisplayViewportsByResolution() - no surround modes detected
17:39:46:109 (00015776) > [NxDLSS] DLSS support test, code = 0x00000001, info: NVSDK_NGX_Result_Success
17:39:49:641 (00015776) > [Intel XeSS] Failed to init XeSS on dummy device during setup. Error: 4294967286
17:39:51:159 (00015776) > [Render] Querying NVAPI for Surround modes
17:39:51:491 (00015776) > [Render] NvAPI_Mosaic_GetDisplayViewportsByResolution() - no surround modes detected
17:39:54:285 (00015776) > [NxApp] Failed to create Dummy D3D12CreateDevice
17:39:54:285 (00015776) > [Intel XeSS] Invalid DummyD3D12Device
17:39:54:285 (00015776) > [Intel XeSS] Invalid DummyD3D12Device using real device.
17:39:54:286 (00015776) > [Crash] Memory statistics:
…
17:39:54:286 (00015776) > [Crash] Unhandled exception at address 0x00000000bcaf8a07 (code: 0xc0000005): "Access violation"
The first instance only enumerated Monitor 0 and proceeded to Render a variety of resolution tests on Monitor 1, which registered as my primary Nvidia GPU in the successful launch log, and successfully launched the launcher. The second instance enumerated Monitor 0 and Monitor 1 and failed with a memory access violation never successfully launching the launcher. No resolution tests were run at all. It completely failed to register the Nvidia card as the primary display.
All I have to do is turn my AVR off, sleep my computer so it forgets about the “second monitor,” wake my computer from sleep, and the game will launch because the “second monitor” doesn’t exist until I turn on my AVR which is connected VIA HDMI using the integrated Intel GPU for audio pass-thru to the receiver. Since it is HDMI, it registers as a second monitor even though I am not actually using a second physical monitor.
The problem is that I want to play using the AVR for audio. Since my AVR is not 4k, I use the integrated GPU for audio pass-thru to the receiver and run my Nvidia card directly to the screen. This worked fine prior to the last patch. This seems to be broken since the patch, and I have not yet found a successful work-a-round.
If I turn on my AVR before pressing play, to which the Intel iGPU is connected, then the AVR is essentially seen as a second monitor which activates the Intel iGPU. Now the launcher will crash. Simple work-a-round is to disable the Intel iGPU in device manager prior to launching the game. Once the launcher is up, I can re-enable the iGPU and proceed to enter the game.
If anyone is having the problem where pressing play does nothing and you never see the game launcher and it crashes back to the play button, and if you have an iGPU which you may or may not actually use for anything, try disabling it in Device Manager then try to launch the game. Maybe it'll work for you as it has for me.