cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

igni
Adept II

[7900 XTX] Cyberpunk 2077 Crash on start

Hi,

It appears the cyberpunk 2077 game, crashes with following error:

Error Reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF.

 

System Spec:

igni_3-1681827742390.png

Mobo: MSI MEG x570 Unify

CPU: 5900x (stock)

RAM: 32GB DDR4 3600MHz

GPU: 7900 XTX (stock)

PSU: Seasonic 1kW Platinum

OS: Windows 10 Enterprise LTSC

 

This error persists on almost all recent drivers, only 23.1.1 and older one work, but potentially older driver has graphical glitching.

 

23.1.1 (screenshots taken from inside the game using RT & Path Tracing

(noisy shadows)

igni_0-1681826625074.png

trails (even tho i have over 60fps)

igni_1-1681826672769.png

igni_2-1681826680321.png

 

How it was tested:

AMD Cleanup Utility and DDU, within safe mode, with reboots. After each driver installation.

Tested:

20.20.29.09 - cyberpunk works but has same graphical ?glitches?

22.12.2 - cyberpunk works but has same graphical ?glitches?

23.1.1 - cyberpunk works but has graphical ?glitches?

23.1.2 - cyberpunk no longer works and crashes with "The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF."

23.2.1 - dodgy driver, cyberpunk no longer works and crashes with "The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF."

23.3.1 - cyberpunk no longer works and crashes with "The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF."

23.3.2 - dodgy driver - freezes with browser when loading images, driver crash when using parsec, and sharing screen through ms teams, cyberpunk crashes with "The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF."

23.4.1 - dodgy driver - less freezes with browser than 23.3.2, driver crash when using parsec, and sharing screen through ms teams, cyberpunk crashes with "The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF."

 

I have also taken following steps back in March.

Following steps taken one by one (i attempted running the game 1.61 after each step, and continued doing those changes without reverting others.)

Disconnecting all other displays
Turning off HDR
Turning on and then off Freesync (i have it disabled normally)
Setting lower resolution 1080p (from 1440p)
Setting lower Hz to 60Hz (from 144Hz)
Updating vc redist to latest 2015-2022 package
DDU + Removing all AMD/NV packages (including ones i have for my visual studio)
Reverting driver to older version (from 23.3.2 to 23.3.1)

Ran memtest86 again, passed.

Looked up this error, found threads in opengl application programming - a programmer error seems a variable is not being declared / should be declared in some enviroments... (maybe cdpr should look it up as well)

Ran windows updates ( 0 new updates )
(double checked, no windows is not replacing my drivers - i blocked that in GPO - pro's of enterprise LTSC edition you actually have control over your workstation)

Disabled UAC
Created new user
Downloaded new dx package from ms for visual studio.
Removing all amd driver shader caches
Creating custom amd profile
Trying to run it with Radeon Super Resolution (by default disabled, disabled after testing)
Disabled Virtual Super Resolution (by default enabled, kept disabled after testing)
Disabled GPU Scaling (by default enabled, kept disabled after testing)
Disabled Integer Scaling (by default enabled, kept disabled after testing)
Pixel Format RGB Limited RGB (by default Full RGB)
Disabled Display Color Enhancement Vivid Gaming
Set AA to Use Application Settings
AA Method from Supersampling to Multisampling
Disabled Morphological AA
Disabled Anisotropic Filtering (by default enabled x16)
Set Texture Filtering Quality to Standard (from High)
Set Tessellation from Override Application (lock to x32) to use application settings.
Disabled OpenGL Triple Buffering
Disabled 10-bit Pixel format
Disabled SAM
(Didn't use any other radeon tech, so they stayed disabled - i.e. Chill, Anti-Lag, Boost, Image Sharp, Enhanced Sync)
Disabled all Audio devices (re-enabled after)
msconfig selective startup > Load only System Services (i.e. disabled all non windows services, which are very few parsec, galaxy/gog, nordvpn, cisco anyconnect)

 

Recently i have attempted a brand-new os setup out of curiosity:

"i set up a brand new system (disconnected my other disks, with 2 sticks of 2400MHz ecc ram) with Windows 10 Enterprise LTSC, installed brand new drivers 23.4.1's, and ran windows updates - it produced same crash."

 

Thus i'm quite sure its something to do with the driver (noting it kinda works - ?glitches? - on older 23.1.1 driver.

 

 

 

15 Replies
igni
Adept II

Newest drivers 23.4.2, and latest hotfix on cyberpunk have not fixed the issue of the crash

(clean cyberpunk install)

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF.
File: <Unknown>(0)

0 Likes
igni
Adept II

This has not been resolved.

0 Likes
JackJ0n3s
Adept I

Hi @igni 

Just been looking through your post about Cyberpunk 2077.

I've been having crashing issues too. However. After speaking to a colleague who works with Nvidia, I can confirm that yous system is not the one at fault. Not sure why you would try a brand new system, just to get better results.

My colleague has stated (off the record), due to CD Projket Red's affiliation with Nvidia, they have prioritised development. Meaning, AMD, Intel - Aren't priority.

To confirm this further, I run a set-up on an RX 6600. Althought not capable to run RT and PT within Gameplay. I was able to take fantastic images within Photomode. However. Since the recent Cyberpunk 2077 hotfix, I am now unable to take images with Path Tracing. The Game crashes instantly.

So evidence within my own experience, and my colleague's information. It is clear that there may be some "favouritism" towards Nvidia Drivers/GPU's. Meaning - Whenever CD Projekt Red release an update, expect AMD/Intel to be behind and crashes will be expected.

This is unfortunately the world we live in currently.

So specifically to your post. I wouldn't mess around with your own setup like you have. It's really messy and most likely will be conflicting with a variety of objects.

PT is also their Tech Preview. It isn't the final version of the product. Therefore, I would expect crashes/graphical glitches.

I see Cyberpunk 2077 as a Preview Product. It's not really a Gaming Product anymore. As when you think about it, They've included PT within their Red Engine. But it's already been confirmed that they won't be using that Engine for any further Gaming (Apart from The Witcher 3 and Cyberpunk 2077). Everything else is UE5.

You have a great set-up. So try not to ruin that haha If you accept that Cyberpunk 2077 is being treated as a Tech Preview (Similar to Star Citizen), then you might feel abit more relaxed about it *thumps up*.

I wish you well Sir.

0 Likes
igni
Adept II

i've been mentally preparing myself to flash the bios to newest; Its one of the things i haven't done.

It could be some microcode co-relation with SAM.

0 Likes
igni
Adept II

Bios update didn't do anything; still same crash.

 

I'm about to give up.

0 Likes
ThreeDee
Paragon

What drive make/model is the game installed on?


ThreeDee PC specs
0 Likes
igni
Adept II

Tried different disks, no clue how those could matter:

NVMe Micron 3400 1TB @ PCIe Gen4 x4

RAID1 SAS3 SSD HGST HITACHI HUSMM808 CLAR800 800GB
Single SATA SSD Crucial MX500 1TB (CT1000MX500SSD1)

0 Likes
igni
Adept II

CDPR seem to no longer support Cyberpunk 2077 on Windows 10 rev. 1809.

0 Likes

Microsoft stopped supporting about a year ago too

0 Likes
igni
Adept II

The Widows 10 Enterprise LTSC (1809) is being supported until Jan next year.

 

igni_2-1684063530441.png

 

 

 

0 Likes

I doubt game devs care about enterprise versions of windows or even testing against them. The various versions of windows typically update WDDM version, and using a current driver on an older WDDM version could be a potential source of problems. 1809 is sitting at about WDDM 2.5.

https://en.wikipedia.org/wiki/Windows_Display_Driver_Model

 

0 Likes
igni
Adept II

Well they should... you can see amd still displaying 1809 in their driver stack, they will support until enterprise version expires.

0 Likes
xeda0
Journeyman III

CPU: 5800x (stock)

GPU: 7900 XTX (stock)

OS: Windows 10 Enterprise LTSC

Driver Version: 23.5.2

 

Cyberpunk 2077 still Crash on start.

analyze the dmp.

0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 515

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3368

    Key  : Analysis.IO.Other.Mb
    Value: 1

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 218

    Key  : Analysis.Init.Elapsed.mSec
    Value: 8449

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 104

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 3663

    Key  : Timeline.Process.Start.DeltaSec
    Value: 1

    Key  : WER.OS.Branch
    Value: rs5_release

    Key  : WER.OS.Timestamp
    Value: 2018-09-14T14:34:00Z

    Key  : WER.OS.Version
    Value: 10.0.17763.1

    Key  : WER.Process.Version
    Value: 31.0.14057.5006


FILE_IN_CAB:  Cyberpunk2077.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

CONTEXT:  (.ecxr)rax=0000022127a68808 rbx=0000000000000000 rcx=0000022127a67520
rdx=00007ffa0775a0c0 rsi=00000221272ad6c8 rdi=0000022127de2970
rip=00007ffa0775a35d rsp=000000e4331f5390 rbp=0000022127a7d240
 r8=00007ffa0775a140  r9=00000221272ad6c8 r10=0000000000000000
r11=fa798dd8a0851fb7 r12=0000000000000000 r13=0000000000000000
r14=0000022127a68d90 r15=000000e4331f5b10
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
amdxc64+0xca35d:
00007ffa`0775a35d ff9088000000    call    qword ptr [rax+88h] ds:00000221`27a68890=4c32bfca22c810af
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)ExceptionAddress: 00007ffa0775a35d (amdxc64+0x00000000000ca35d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

PROCESS_NAME:  Cyberpunk2077.exe

READ_ADDRESS:  ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p            0x%p                    %s

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

STACK_TEXT:  
000000e4`331f5390 00000000`00000000     : 00000221`272ad6c8 000000e4`331f53e0 00000221`272ad6c8 fa798dd8`a0851fb7 : amdxc64+0xca35d


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  amdxc64+ca35d

MODULE_NAME: amdxc64

IMAGE_NAME:  amdxc64.dll

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_amdxc64.dll!Unknown

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  31.0.14057.5006

FAILURE_ID_HASH:  {79fa917f-acce-2436-f35e-92d487d97f5f}

Followup:     MachineOwner
---------

 

It's definitely AMD Driver fault.

0 Likes
xeda0
Journeyman III

CPU: 5800x (stock)

GPU: 7900 XTX (stock)

OS: Windows 10 Enterprise LTSC

Driver Version: 23.5.2  

Cyberpunk 2077 still Crash on start. I analyze the dmp.

STACK_TEXT:  
000000ca`241f52c0 00000000`00000000     : 00000234`89197798 000000ca`241f5310 00000234`89197798 fa798dd8`a0851fb7 : amdxc64+0xca35d

QQ截图20230611150535.pngQQ截图20230611150545.pngQQ截图20230611150608.pngQQ截图20230611150639.png

0 Likes

I found a solution, which is to upgrade the system to Windows 10 21H2 LTSC.

I don't know why it doesn't work on Windows 10 1809 LTSC. It could be a problem with ray tracing.

0 Likes