Hi,
Recently i decided to install cyberpunk 2077, and enjoy some of the night city again after brief hiatus of few months
(it was playable in 1.5x something)
But right now it just flatlines...

report id 20230313-131158-10788-7468

I tried looking for solutions on the net, but none have worked.


Registered crash info file...
InternalVersion: 3.0.4506101 P4CL: 5661751 Stream: //R6.Root/R6.Release
!!!CRASHED!!!
Error Reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF.
File: <Unknown>
Line: 0

"uptimeSeconds":1

i love the 0 interests from devs about the issues the game has recently. I mean screw customers right?

If you're looking for help from other players as well, then you need to include, at minimum, your hardware, Windows version and game patch.

If you're trying to play on patch 1.61 DLS without a RTX 40xx-series GPU, then that is known to cause crashes. And, as far as I know, without a known solution.

Game runs great, even a heavily modded one, on a RTX 3080, Windows 10 Pro, Nvidia driver 526.47 and game patch 1.6.

i was hoping for some cdpr support since they literally ignore their own forums - its like whole company went to sh**ter.

running on

5900x
7900xtx (latest drivers 23.3.1 clean install)
64GB DDR4 3600MHz
Windows 10 Enterprise LTSC 1809
Samsung 1440p HDR600 144Hz Monitor

Game is running from sas ssd.
Latest version on GOG; game was working fine pre 1.6 patch.

A week goes by, and 0 support.

Can't you just roll back to previous verison of cp77? If it worked
Also

Any issues with any other games

Memtest86 test for your ram. Is oc of ram too high?
Run occt tests

Is your cpu oced? Same with gpu. Check if you can run stock.

My crashes last year was a result of defective ram. Ram I used for 5 years but with new gpu and cpu it was giving me issues.
Got new ram and it fixed the issue in cp77 and other games

Can't I downgrade?
No, client doesn't give me option to go below 1.6...

Witcher 3 hairworks doesn't work on dx12 and dx11

No issues in any other game.

Doom Eternal works like a charm,
Warthunder works like a charm,
League of Legends works like a charm,
Quake 2 RTX works like a charm,
Hogwarts Legacy works like a charm,
Crysis 1-3 work like a charm,
Elden Ring works like a charm,
M&B Bannerlord works like a charm

(and few others random titles)

CPU always since inception been running at stock,
(I made sure there's no mobo oc etc running.)

ram kit i have was meant for 3600MHz, i did run memtest resulting in 0 issues.
Its also not an issue with overheating, or poor quality of electrical signal.
System sits in a server rack, in AC regulated environment, with datacenter quality UPS.
With CPU sitting on 100% load gets only 40'C, and GPU 7900xtx at 62'C. (ambient of 45-50'F - ~7'C)

So it's not hardware.

U sure you don't have a mod installed from previous playthrough?

Old cet was crashing my game immediately as well. Removal fixed it and a new version of cet worked.
A lot of mods were broken by 1.6 update.

The mod was there even when reinstalling the game. As galaxy didn't remove the non game files.

I did a clean install - even removing userdata cb2077 folder, and doing offline install and directly trying to start cb2077 exec; In new location. (to ensure its not syncing some broken settings.)

~ short of cleaning up registry for any cb 2077 mention.

i did find this in red engine log when it crashes.
(I tried to run the game on micron 3400 nvme gen4, and raid1 sas ssd's, in past it ran just fine.)

03/21/2023 22:17:48 -05:00|INFO|Redbug.Reporter.CP2077.Preparation.CrashDataLocator|Searching for most recently created directories in 'C:\Users\cyklondx\AppData\Local\REDEngine\ReportQueue'.
03/21/2023 22:17:48 -05:00|INFO|Redbug.Reporter.CP2077.Preparation.ReportCreator|Matching crash data directory: 'Cyberpunk2077-20230321-221747-19520-31120'.
03/21/2023 22:17:48 -05:00|INFO|Redbug.Reporter.CP2077.Preparation.ReportCreator|Game version has been resolved to: '3.0.4506101 P4CL: 5661751 Stream: //R6.Root/R6.Release '.
03/21/2023 22:17:48 -05:00|INFO|Redbug.Reporter.CP2077.Preparation.ReportCreator|Looking for ClientId in 'C:\Users\cyklondx\AppData\Local\REDEngine\CrashClientId.txt'.
03/21/2023 22:17:48 -05:00|INFO|Redbug.Reporter.CP2077.Preparation.ReportCreator|ClientId file exists. Trying to read cached id.
03/21/2023 22:17:48 -05:00|INFO|Redbug.Reporter.CP2077.Preparation.ReportCreator|ClientId resolved to 'beed37c70bfaaaed03f2443b958731b36653a89c'.
03/21/2023 22:17:48 -05:00|TRACE|Redbug.Reporter.CP2077.Preparation.SystemInformationCollector|WMI Query: select AddressWidth, Architecture, Caption, CurrentClockSpeed, Description, DeviceID, Family, Manufacturer, MaxClockSpeed, Name, NumberOfCores, NumberOfLogicalProcessors, Status from Win32_Processor
03/21/2023 22:17:49 -05:00|TRACE|Redbug.Reporter.CP2077.Preparation.SystemInformationCollector|WMI Query: select Capacity, Description, Manufacturer, Model, PartNumber, Speed from Win32_PhysicalMemory
03/21/2023 22:17:49 -05:00|TRACE|Redbug.Reporter.CP2077.Preparation.SystemInformationCollector|WMI Query: select AdapterDACType, Caption, CurrentBitsPerPixel, CurrentHorizontalResolution, CurrentRefreshRate, CurrentVerticalResolution, Description, DeviceID, DriverDate, DriverVersion, InstalledDisplayDrivers, Name, Status, VideoProcessor from Win32_VideoController
03/21/2023 22:17:49 -05:00|TRACE|Redbug.Reporter.CP2077.Preparation.SystemInformationCollector|WMI Query: select Caption, CodeSet, CountryCode, CurrentTimeZone, Locale, OSArchitecture, OSLanguage, OSType, Version from Win32_OperatingSystem
03/21/2023 22:17:49 -05:00|TRACE|Redbug.Reporter.CP2077.Preparation.SystemInformationCollector|WMI Query: select BytesPerSector, Caption, DeviceID, FirmwareRevision, Index, Model, Size, Status from Win32_DiskDrive
03/21/2023 22:17:49 -05:00|TRACE|Redbug.Reporter.CP2077.Preparation.SystemInformationCollector|WMI Query: select AllocatedSize, BusType, DeviceId, FirmwareVersion, FriendlyName, HealthStatus, MediaType, Model, Size, SpindleSpeed from MSFT_PhysicalDisk
03/21/2023 22:17:49 -05:00|WARN|Redbug.Reporter.CP2077.Preparation.SystemInformationCollector|Could not retrieve drives information.
System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
at Redbug.Reporter.CP2077.Preparation.SystemInformationCollector.GetLogicalDiskToPhysicalDiskAssociations()
at Redbug.Reporter.CP2077.Preparation.SystemInformationCollector.AddSystemInformation(DirectoryInfo crashDataDir)
03/21/2023 22:17:49 -05:00|INFO|Redbug.Reporter.CP2077.Preparation.ReportCreator|Crash report summary: [Data directory: C:\Users\cyklondx\AppData\Local\REDEngine\ReportQueue\Cyberpunk2077-20230321-221747-19520-31120] [ClientId: beed37c70bfaaaed03f2443b958731b36653a89c] [ProductVersion: 3.0.4506101 P4CL: 5661751 Stream: //R6.Root/R6.Release ]

This isn't wmi corruption issue either. I also don't know why it tries to get this kind of info... Even so its bit f'd up to scan all user drives and partitions.

well anyway, running wmi for exact info the engine gets... looks just fine.

PS C:\WINDOWS\system32> Get-WMIObject Win32_LogicalDisk | Foreach-Object {
>> Get-WmiObject -Query "Associators of {Win32_LogicalDisk.DeviceID='$($_.DeviceID)'} WHERE ResultRole=Antecedent"
>> } | Format-Table

NumberOfBlocks BootPartition Name PrimaryPartition Size Index
-------------- ------------- ---- ---------------- ---- -----
998952960 False Disk #0, Partition #2 True 511463915520 2
1562812735 False Disk #1, Partition #1 True 800160120320 1
1562812735 False Disk #2, Partition #1 True 800160120320 1
3906764800 False Disk #7, Partition #0 True 2000263577600 0
781418496 False Disk #8, Partition #0 True 400086269952 0
15627788288 False Disk #4, Partition #0 True 8001427603456 0
1953519616 False Disk #6, Partition #0 True 1000202043392 0
15628017664 False Disk #3, Partition #0 True 8001545043968 0
15627788288 False Disk #5, Partition #0 True 8001427603456 0

(Not the case of 2 disks that are same in system, as their names are Disk #1, and Disk #2 names)

(Not the case of running as administrator - already tried that.)

Removing one of the sas ssd's helped with crash reporter not erring out anymore;

...but game itself still crashes... same as ever with same useless unhelpful error.
(looks like unrelated error, only with their crash reporter, not cause of the game crashing...)

Sig[0].Name=StackHash
Sig[0].Value=0x0000000000000000
Sig[1].Name=ErrorReason
Sig[1].Value=Unhandled exception
Sig[2].Name=InternalVersion

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread caused a user-mode data execution prevention (DEP) violation at 0x0.
File: <Unknown>(0)

New amd drivers 23.3.2, issue persists.

just a bump...

Have you tried going back to the game version where it worked properly?

Also, I have not encountered many cases where an update to GPU drivers solved an issue - it's usually the opposite.
So if the game still crashes after having reinstalled version 1.5, you may also want to go back to the driver you were using when it worked.

And the "latest version" on GoG is patch 1.61 DLSS - that one has caused SO MANY PROBLEMS.
You don't want that version for any reason, apart from if owning a RTX 40xx series GPU.

and thats why i dont use amd graphic cards