Cyberpunk 2077 PC Crash Issues

+
Intel Core 2 Quad Q9300 2.5GHz
8Gb RAM
GeForce GTX 1050Ti


I know its aint the best :D ,but i guest its should start and maximum i got a lot of lag with low settings or i dont know. One of my friend have a similar config and he run it with no problem

Not supported AVX.
Read back and modify with hex editor the exe file.
Two minutes and you can play.
 
Not supported AVX.
Read back and modify with hex editor the exe file.
Two minutes and you can play.

yes, i tried! But wont start, i changed in Hex and tried the download version from Nexus to. The AVX crash is happening during the game, as i read in this topic.
 
Awesome. So now my game is crashing almost every 5 minutes vs sometimes getting a good hour.

Haven't changed anything with my PC.

I'm at the part of the game where I try to find someone using the memory scan thing you can do.

How can this game be so dogshit?
 
My post was removed: just to make it clear to the mods, I tested this whilst I still owned the game on Steam. When that didn't work I just gave up and removed it all from my computer. No point in it taking up storage space if I can't play. I thought it might just help to prove that the vendor for where people obtained the game from may not actually make a difference.
 
After the last patch (ver. 1.0.4, after the first act), the game crashes consistently when traveling around the city.

i7 8700K
RTX 3080
16 Gb RAM
PSU 750W

Windows 10

There are no crashes in other games and while working on a PC.

UPD. Installed the latest Nvidia driver and everything was ok.
 
Last edited:
After 1.04 patch I have crash every 10 minutes. Sorry but I bought msi 3090 for playing this. And I cannot... what a joke CDpr. I will play Valhalla so. At least this game is stable.
 
Ok people by the looks of it this game is crashing in a lot of different ways to try and control the chaos lets get some crash reports they can be found in.

C:\Users\[YOUR ACCOUNT]\AppData\Local\REDEngine\ReportQueue
Then go into the most recent crash folder and you should see report.text and stacktrace.txt

Stacktrace.text tells you your exact crash for example mine says the following.

Error reason: Assert
Expression: <Unknown>
Message: Watchdog timeout! (120 seconds)
File: e:\r6.patch0hotfix2\dev\src\common\engine\src\enginewatchdog.cpp(198)

The better we get this organised the more people that can be helped.
 
My game was working perfectly fine, until the latest patch. Now the game continues to crash at the same exact spot in the mission, "Play it Safe". During the part-SPOILERS-where you have to escape the parade. As soon as I approach the double doors to leave, the game crashes and I get the "Whoa" pop-up. I've tried updating everything and turning down the graphics to the lowest setting, still nothing. So infuriating as I was really enjoying my time and already poured 20+ hours into the game.
 

Attachments

  • Cyberpunk 2077 Screenshot 2020.12.13 - 16.31.03.04.png
    Cyberpunk 2077 Screenshot 2020.12.13 - 16.31.03.04.png
    3.9 MB · Views: 124
Intel Core 2 Quad Q9300 2.5GHz
8Gb RAM
GeForce GTX 1050Ti


I know its aint the best :D ,but i guest its should start and maximum i got a lot of lag with low settings or i dont know. One of my friend have a similar config and he run it with no problem

Sorry to say my man, but you desperately need an upgrade if you want to play this.
The reason why the AVX fix didn't work for you is because your CPU also lacks another 2 very basic instruction sets, SSE 4.1 and 4.2. Those are used borderline everywhere nowadays so there's little chance they'll release a patch for non-SSE CPUs. AVX is more likely because it's not a jack-of-all-trades set and hardly worth the trouble for now (plus there are a few recent CPUs that don't have it).
 
Ok people by the looks of it this game is crashing in a lot of different ways to try and control the chaos lets get some crash reports they can be found in.

C:\Users\[YOUR ACCOUNT]\AppData\Local\REDEngine\ReportQueue
Then go into the most recent crash folder and you should see report.text and stacktrace.txt

Stacktrace.text tells you your exact crash for example mine says the following.

Error reason: Assert
Expression: <Unknown>
Message: Watchdog timeout! (120 seconds)
File: e:\r6.patch0hotfix2\dev\src\common\engine\src\enginewatchdog.cpp(198)

The better we get this organised the more people that can be helped.
My question is why is the file it is referencing referring to the e: drive. My error does as well and I don't have an e: drive.

Error reason: Assert
Expression: <Unknown>
Message: Gpu Crash for unknown reasons! Callstack here is probably irrelevant. Check if Breadcrumbs or Aftermath logged anything useful.
File: e:\r6.patch0hotfix2\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp(40)

CPU: 3900x
GPU: 1080ti
RAM: 32 gig DDR4 Trident Z Neo 3600 CL16
Window 10 update 20H2 Build 19042.685
Gigabyte X570 Aorus Master Mobo
Samsung M.1 500gig SSD
Display: Dell AW3418DW UltraWide 3440x1440
 
Last edited:
I am having a repeated crash at Lizzie's Bar, after I meet Evelyn. We go to the back room together, we talk for a minute, then the game crashes without warning to a BSOD.

This is what the Windows Event Log says:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal parity error
Processor APIC ID: 2

I have my Intel i5 10600K processor overclocked in the BIOS to 4.8GHz stable in every other application and game. I know my processor is AVX capable.

Should I remove the CPU overclock? Perhaps this particular workload just taxes it too much and I need to lower it or remove it. Other than this crash the game has been running OK for me.
 
Sorry to say my man, but you desperately need an upgrade if you want to play this.
The reason why the AVX fix didn't work for you is because your CPU also lacks another 2 very basic instruction sets, SSE 4.1 and 4.2. Those are used borderline everywhere nowadays so there's little chance they'll release a patch for non-SSE CPUs. AVX is more likely because it's not a jack-of-all-trades set and hardly worth the trouble for now (plus there are a few recent CPUs that don't have it).

At least i learn a few new things about my crash, thanks man, i try to hope in thoose patches then.
 
After the last patch (ver. 1.0.4, after the first act), the game crashes consistently when traveling around the city.

i7 8700K
RTX 3080
16 Gb RAM
PSU 750W

Windows 10

There are no crashes in other games and while working on a PC.
After 1.04 patch I have crash every 10 minutes. Sorry but I bought msi 3090 for playing this. And I cannot... what a joke CDpr. I will play Valhalla so. At least this game is stable.
Same problem. I played on game version 1.03 above 6 hour in a row - zero crash, after patch 1.04 game crashed every 10 minutes. My system: i7 8700 & RTX 2070. New driver, GPU underclocked and game was installed on fast NVM SSD.

Code:
Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xB978915A.
File: <Unknown>(0)
Code:
Version=1
EventType=REDEngineErrorReport
EventTime=0
ReportIdentifier=ffffffff-ffffffff-00000001-00000000
Sig[0].Name=StackHash
Sig[0].Value=0x0000000000000000
Sig[1].Name=ErrorReason
Sig[1].Value=Unhandled exception
Sig[2].Name=InternalVersion
Sig[2].Value=3.0.3217599  P4CL: 4158334  Stream: //R6.Root/R6.Patch0Hotfix2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19041.2.0.0.256.1
LoadedModule[0]=Cyberpunk2077.exe
LoadedModule[1]=ntdll.dll
LoadedModule[2]=KERNEL32.DLL
LoadedModule[3]=KERNELBASE.dll
LoadedModule[4]=apphelp.dll
LoadedModule[5]=AcLayers.DLL
LoadedModule[6]=msvcrt.dll
LoadedModule[7]=USER32.dll
LoadedModule[8]=win32u.dll
LoadedModule[9]=GDI32.dll
LoadedModule[10]=gdi32full.dll
LoadedModule[11]=msvcp_win.dll
LoadedModule[12]=ucrtbase.dll
LoadedModule[13]=SHLWAPI.dll
LoadedModule[14]=ADVAPI32.dll
LoadedModule[15]=sechost.dll
LoadedModule[16]=RPCRT4.dll
LoadedModule[17]=sfc.dll
LoadedModule[18]=WINSPOOL.DRV
LoadedModule[19]=sfc_os.DLL
LoadedModule[20]=AcGenral.DLL
LoadedModule[21]=ole32.dll
LoadedModule[22]=combase.dll
LoadedModule[23]=SHELL32.dll
LoadedModule[24]=USERENV.dll
LoadedModule[25]=MPR.dll
LoadedModule[26]=SspiCli.dll
LoadedModule[27]=IMM32.DLL
LoadedModule[28]=SETUPAPI.dll
LoadedModule[29]=cfgmgr32.dll
LoadedModule[30]=bcrypt.dll
LoadedModule[31]=WS2_32.dll
LoadedModule[32]=OLEAUT32.dll
LoadedModule[33]=VERSION.dll
LoadedModule[34]=XINPUT1_3.dll
LoadedModule[35]=dbghelp.dll
LoadedModule[36]=HID.DLL
LoadedModule[37]=bink2w64.dll
LoadedModule[38]=PhysX3Common_x64.dll
LoadedModule[39]=icuuc.dll
LoadedModule[40]=icuin.dll
LoadedModule[41]=PhysX3CharacterKinematic_x64.dll
LoadedModule[42]=PhysX3Cooking_x64.dll
LoadedModule[43]=PhysX3_x64.dll
LoadedModule[44]=redlexer_native.dll
LoadedModule[45]=Galaxy64.dll
LoadedModule[46]=POWRPROF.dll
LoadedModule[47]=d3d11.dll
LoadedModule[48]=CRYPT32.dll
LoadedModule[49]=libcurl.dll
LoadedModule[50]=WLDAP32.dll
LoadedModule[51]=Normaliz.dll
LoadedModule[52]=NRD.dll
LoadedModule[53]=WINMM.dll
LoadedModule[54]=PxFoundation_x64.dll
LoadedModule[55]=MSVCP140.dll
LoadedModule[56]=VCRUNTIME140.dll
LoadedModule[57]=dxgi.dll
LoadedModule[58]=WININET.dll
LoadedModule[59]=IPHLPAPI.DLL
LoadedModule[60]=MSWSOCK.dll
LoadedModule[61]=amd_ags_x64.dll
LoadedModule[62]=oo2ext_7_win64.dll
LoadedModule[63]=icudt.dll
LoadedModule[64]=UMPDC.dll
LoadedModule[65]=gameoverlayrenderer64.dll
LoadedModule[66]=PSAPI.DLL
LoadedModule[67]=CRYPTBASE.DLL
LoadedModule[68]=bcryptPrimitives.dll
LoadedModule[69]=kernel.appcore.dll
LoadedModule[70]=windows.storage.dll
LoadedModule[71]=Wldp.dll
LoadedModule[72]=SHCORE.dll
LoadedModule[73]=clbcatq.dll
LoadedModule[74]=wbemprox.dll
LoadedModule[75]=wbemcomn.dll
LoadedModule[76]=wbemsvc.dll
LoadedModule[77]=fastprox.dll
LoadedModule[78]=amsi.dll
LoadedModule[79]=profapi.dll
LoadedModule[80]=eamsi.dll
LoadedModule[81]=uxtheme.dll
LoadedModule[82]=RTSSHooks64.dll
LoadedModule[83]=Start10_64.dll
LoadedModule[84]=GameServicesSteam.dll
LoadedModule[85]=steam_api64.dll
LoadedModule[86]=steamclient64.dll
LoadedModule[87]=imagehlp.dll
LoadedModule[88]=Secur32.dll
LoadedModule[89]=tier0_s64.dll
LoadedModule[90]=vstdlib_s64.dll
LoadedModule[91]=CRYPTSP.dll
LoadedModule[92]=rsaenh.dll
LoadedModule[93]=napinsp.dll
LoadedModule[94]=pnrpnsp.dll
LoadedModule[95]=wshbth.dll
LoadedModule[96]=NLAapi.dll
LoadedModule[97]=DNSAPI.dll
LoadedModule[98]=NSI.dll
LoadedModule[99]=winrnr.dll
LoadedModule[100]=fwpuclnt.dll
LoadedModule[101]=rasadhlp.dll
LoadedModule[102]=d3d12.dll
LoadedModule[103]=GFSDK_Aftermath_Lib.x64.dll
LoadedModule[104]=nvwgf2umx.dll
LoadedModule[105]=dxcore.dll
LoadedModule[106]=msasn1.dll
LoadedModule[107]=cryptnet.dll
LoadedModule[108]=WINTRUST.DLL
LoadedModule[109]=nvapi64.dll
LoadedModule[110]=schannel.DLL
LoadedModule[111]=nvldumdx.dll
LoadedModule[112]=D3DSCache.dll
LoadedModule[113]=twinapi.appcore.dll
LoadedModule[114]=mskeyprotect.dll
LoadedModule[115]=NTASN1.dll
LoadedModule[116]=ncrypt.dll
LoadedModule[117]=ncryptsslp.dll
LoadedModule[118]=MMDevApi.dll
LoadedModule[119]=DEVOBJ.dll
LoadedModule[120]=dinput8.dll
LoadedModule[121]=inputhost.dll
LoadedModule[122]=CoreMessaging.dll
LoadedModule[123]=wintypes.dll
LoadedModule[124]=PROPSYS.dll
LoadedModule[125]=CoreUIComponents.dll
LoadedModule[126]=ntmarta.dll
LoadedModule[127]=Wtsapi32.dll
LoadedModule[128]=AUDIOSES.DLL
LoadedModule[129]=resourcepolicyclient.dll
LoadedModule[130]=MSCTF.dll
LoadedModule[131]=textinputframework.dll
LoadedModule[132]=Windows.Perception.Stub.dll
LoadedModule[133]=gpapi.dll
LoadedModule[134]=nvngx.dll
LoadedModule[135]=DEVRTL.dll
LoadedModule[136]=drvstore.dll
LoadedModule[137]=SPINF.dll
LoadedModule[138]=nvngx_dlss.dll
LoadedModule[139]=nvcuda.dll
LoadedModule[140]=nvcuda64.dll
LoadedModule[141]=dcomp.dll
LoadedModule[142]=dwmapi.dll
LoadedModule[143]=WINSTA.dll
LoadedModule[144]=Windows.UI.dll
LoadedModule[145]=WindowManagementAPI.dll
LoadedModule[146]=nvrtum64.dll
AppName=Cyberpunk2077.exe
 
PSA to all people with this error:
You are using Windows 8 or 8.1, is that correct? If so then the reason is that you don't have DirectX 12, and you cannot install that on your OS. You will notice that in the error log a failed render load appears.

The only chance is upgrading to Win10 (which, BTW, still was free for me). This fixed the "issue" for me, but I see that this is quite an intrusive measure.

EDIT @CDPR: it would help a lot showing that Windows 8 will not work with CP2077, instead of just showing the "flatlined!" message. This might save some people a headache or two w.r.t. why the game does not launch. :)
Problem is... I have W10, and amd rx 570... which should support Dx12. I mean, dx diag and speccy both say I'm on dx12. But I keep getting this error... even with AVX fix (yes my CPU is quite old) :/
I noticed I can't run a lot of dx12 games at all tho which might mean it's possibly MY PC and not the game.
 
Hey guys if you are still having crash issues but have followed all the troubleshooting this could be your solution.
RAM, turns out this game pushes ram to its limits. The slightest instability in your ram and your GPU drivers will crash.
Turns out one of my sticks couldn't hack it.
I removed all sticks and put one in at a time, launching the game each time. 3 out of 4 sticks launched the game with no flatline.
Now I'm running on two of the stable sticks 0 crashes in 8 hours. I have another 2 sticks on order. Hope this helps someone else !

Ps I didn't have crashes in any other games so you could also just remove the ram while your playing this then put it back in later.
Post automatically merged:

I cant even launch the game, just get a flatline error, I have an i7 8750H, 32gb ram and an RTX 2060, so no idea. tried all the fixes, any help appreciated!
Post automatically merged:

I cant even launch the game, just get a flatline error, I have an i7 8750H, 32gb ram and an RTX 2060, so no idea. tried all the fixes, any help appreciated!
Hey guys if you are still having crash issues but have followed all the troubleshooting this could be your solution.
RAM, turns out this game pushes ram to its limits. The slightest instability in your ram and your GPU drivers will crash.
Turns out one of my sticks couldn't hack it.
I removed all sticks and put one in at a time, launching the game each time. 3 out of 4 sticks launched the game with no flatline.
Now I'm running on two of the stable sticks 0 crashes in 8 hours. I have another 2 sticks on order. Hope this helps someone else !

Ps I didn't have crashes in any other games so you could also just remove the ram while your playing this then put it back in later.
 
Last edited:
Top Bottom