Forums
Games
Cyberpunk 2077 Thronebreaker: The Witcher Tales GWENT®: The Witcher Card Game The Witcher 3: Wild Hunt The Witcher 2: Assassins of Kings The Witcher The Witcher Adventure Game
Jobs Store Support Log in Register
Forums - CD PROJEKT RED
Menu
Forums - CD PROJEKT RED
  • Hot Topics
  • NEWS
  • GENERAL
    SUGGESTIONS
  • STORY
    MAIN JOBS SIDE JOBS GIGS
  • GAMEPLAY
  • TECHNICAL
    PC XBOX PLAYSTATION
  • COMMUNITY
    FAN ART (THE WITCHER UNIVERSE) FAN ART (CYBERPUNK UNIVERSE) OTHER GAMES
  • RED Tracker
    The Witcher Series Cyberpunk GWENT
PC
XBOX
PLAYSTATION
Menu

Register

Cyberpunk 2077 PC Crash Issues

+
Prev
  • 1
  • …

    Go to page

  • 95
  • 96
  • 97
  • 98
  • 99
  • …

    Go to page

  • 133
Next
First Prev 97 of 133

Go to page

Next Last
filinkd

filinkd

Rookie
#1,921
Dec 14, 2020
Ok guys, so for me the solution was: running msi Afterburner et setting Temp. Limit on max. And I played 3 hours without any crash today.
Of course it could be exclusif solution for my config. But it works for me. So I share.
I have i7-6700k
16gb ddr4
Msi 3090 X Trio
HDD
Hope it will help some of you.
Cheers
 
  • RED Point
Reactions: SigilFey
Jaren_Johnson

Jaren_Johnson

Rookie
#1,922
Dec 14, 2020
Heads up: To those of you there were flatlining at the logo screen, I may have a fix for you.

I was getting the following error when I started the game:
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
Line: 40

I have an RTX 2060 Mobile and i7-9750H

The game was working fine up until I installed the hotfix. I'm not sure what changed between the patches to cause this, but I was then crashing at the logo screen over and over. What helped me was flashing the updated BIOS. For my model, there was an update released back in October. Check online to find and flash your latest BIOS version, if you are still having the same issue I was.

Hope this helps!
 
Darkbaz

Darkbaz

Rookie
#1,923
Dec 14, 2020
Game didn't crash for the first 20 hours of play but then started to crash very frequently. No pattern to the crashes that I can tell; seems to happen at anytime. If I uninstall and then reinstall the game, it plays fine as long as I don't close the game out. I'm able to play for hours with no crashes. As soon as I quit the game and come back to it however, it starts crashing every ten to twenty minutes. I always get the same crash:

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

I have a Ryzen 1700x and a GTX 1080 FE. I've tried nearly every fix in this thread, but still no dice. Anyone have anything similar?
 
Sayan_Mayt

Sayan_Mayt

Fresh user
#1,924
Dec 14, 2020
Hey got something for guys playing on AMD Ryzen cpu's
aperently when playing with amd processor the cyberpunk does only use phyhical core and do not use the multrithereded once
there is a fix
again with a hex editor its allows to use all the cores and u god aperently double of the FPS
here a link

https://www.reddit.com/r/cyberpunkgame/comments/kbrsta/_/gfk8af5
dint test it myself as i am playing on x5650 intel with the avx fix
i hope it helps some of you
 
Alphract

Alphract

Fresh user
#1,925
Dec 14, 2020
what crash is it for ?
 
Sayan_Mayt

Sayan_Mayt

Fresh user
#1,926
Dec 14, 2020
Alphract said:
what crash is it for ?
Click to expand...
no crash, performence
the cyperpunk on amd processord doesnt use the hyperthereded cores aperently
 
abyssalsmoke

abyssalsmoke

Rookie
#1,927
Dec 14, 2020
filinkd said:
Ok guys, so for me the solution was: running msi Afterburner et setting Temp. Limit on max. And I played 3 hours without any crash today.
Of course it could be exclusif solution for my config. But it works for me. So I share.
I have i7-6700k
16gb ddr4
Msi 3090 X Trio
HDD
Hope it will help some of you.
Cheers
Click to expand...
Sounds like your GPU is running too hot what are your temps at under load ?
Post automatically merged: Dec 14, 2020

TheSaneWonko said:
Tried that also as last resort. And was disappointed back then, as it didn't help... I'm getting really sick of that. I wonder if that offer for consoles with the refund is also accepted for PCs, when you by no means can play longer than a couple of minutes.
Click to expand...
GOG Refund policy is like 30 days unlimited play time, steam is 3hours of playtime not sure how many days.
 
bladeyama

bladeyama

Fresh user
#1,928
Dec 14, 2020
I got the avx fix it wouldn't let me load my save?
 
M

Monogram_

Rookie
#1,929
Dec 14, 2020
Hello everyone, I tell you my ordeal:

Game bought in pre-order, ramdom crashed.
No games to my specs have been broken until December 10th.

My specs:
- Macbook Pro 15.1 Mid 2019
- 16G memory RAM.
- Game installed on SSD.
- Windows 10 Pro for workstarions version 1909 (BootCamp)
- Razer Core X.
- EGVA 2070 Super Black Gamming, (no overcloack) 8G
- Monitor ViewSonic Xg2402 1080P 144 hz connected Dysplayport.
- Game installed with the latest hotfix 1.04

Obviously I have the latest version of the NVIDIA 460,79 drivers.
However, if you want to do a clean installation, I recommend the DDU program.


In case it helps someone:

- I have checked if my processor had the AVX routines, it does, the way to check it is with a program called Coreinfo, if an asterisk appears it means that it has the subroutine, if you have this problem it seems that there is an executable on the Nexus page mods, also on youtube they explain how to manually modify the executable with a HEX editor, I tried just in case but unfortunately it did not work for me since I have AVX subroutine.

- The next thing I tried was to uninstall all the windows NET framework, the thing got worse, I do not recommend it, I had to reinstall the latest version 4.80 as well as the original version of windows 10 version 3.50 I also installed some more I do not remember.

The problem I had was that the game launcher needs the C + subroutines, I had to reinstall them because if not the game does not connect to Steam, by the way if you do not want the laucher there is an option in Steam to disable it.

As a result of this problem, it seems that the game is DRM free since it can be played without Steam being active.

I had to reinstall the game through Steam, they commented on these forums that this would help, at the moment it seems that it doesn't break that much.


In case someone helps, all the crashes are stored in two main addresses, one for windows and another for the game's crash reporter:

On Windows:
ProgramData / Microsoft / Windows / WER / ReportArchive

In the game:
% User% / Appdata / Local / REDEngine / ReportQueue /

These records is the game's CrashReporter which is in the game folder (Steam) Cyberpunk2077 / bin / x64 / CrashReporter/

Analyzing what the problem could be, I find that the game crashes in various situations but very regularly outdoors and in a car or motorcycle at full speed.

The errors that I have had today as I have seen are three, this information can be seen in the stacktrace file:

1- EXCEPTION_ACCESS_VIOLATION (0xC0000005)

2- Out of Memory! from pool 'PoolRenderBlobsBuffers' using 'DefaultAllocator' File: e: \ r6.patch0hotfix2 \ dev \ src \ common \ redmemory \ src \ oomhandlerbreak.cpp (37)

3- Out of Memory! Failed to allocate 7,428,264 bytes with alignment 16 from pool 'PoolGI' using 'DefaultAllocator' File: e: \ r6.patch0hotfix2 \ dev \ src \ common \ redmemory \ src \ oomhandlerbreak.cpp (37)

In view of these out-of-memory errors, I read somewhere in this forum that the game did not take advantage of all the memory of the graphics card or of the PC itself, so I was encouraged to modify some parameters of the memory_pool_budgets.csv file. in:

"C: \ Program Files (x86) \ Steam \ steamapps \ common \ Cyberpunk 2077 \ engine \ config,

I modified it but it did not help, it was broken again while playing.

The differences that I have found from the crash since the clean installation of the game is that it lasts longer without breaking, a shame because it makes me wait to save the game every 5 minutes and breaks all the immersion that I proposed.

My intention is to continue playing doing only side missions until the brand new hotfix 1.05 is released.

Conclusion: They should already release hotfix 1.05 to fix memory accesses, which is what I think is giving us all a headache.
 
earthdrowned

earthdrowned

Fresh user
#1,930
Dec 14, 2020
Monogram_ said:
Conclusion: They should already release hotfix 1.05 to fix memory accesses, which is what I think is giving us all a headache.
Click to expand...
Yea, all errors 0xc0000005 are related to memory access violations, meaning game can't access a feature it needs. It either does not exist or the game is not allowed to access it for some odd reason.
 
  • RED Point
Reactions: Monogram_
Dominik_Lesn

Dominik_Lesn

Rookie
#1,931
Dec 14, 2020
Maybe anyone knows why my game crashed?

Here the log:

System: Win 10 (20H2) // Ryzen 5 2600 (4,1 Ghz) // RTX 2070; 460.79 Driver // running on M.2 SSD..

Never had any problem with a game until now..


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.19042.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]=USER32.dll
LoadedModule[6]=win32u.dll
LoadedModule[7]=GDI32.dll
LoadedModule[8]=gdi32full.dll
LoadedModule[9]=msvcp_win.dll
LoadedModule[10]=ucrtbase.dll
LoadedModule[11]=ADVAPI32.dll
LoadedModule[12]=msvcrt.dll
LoadedModule[13]=sechost.dll
LoadedModule[14]=XINPUT1_3.dll
LoadedModule[15]=RPCRT4.dll
LoadedModule[16]=dbghelp.dll
LoadedModule[17]=VERSION.dll
LoadedModule[18]=SETUPAPI.dll
LoadedModule[19]=cfgmgr32.dll
LoadedModule[20]=SHELL32.dll
LoadedModule[21]=icuuc.dll
LoadedModule[22]=bcrypt.dll
LoadedModule[23]=ole32.dll
LoadedModule[24]=icuin.dll
LoadedModule[25]=combase.dll
LoadedModule[26]=WS2_32.dll
LoadedModule[27]=OLEAUT32.dll
LoadedModule[28]=HID.DLL
LoadedModule[29]=bink2w64.dll
LoadedModule[30]=PhysX3CharacterKinematic_x64.dll
LoadedModule[31]=PhysX3Cooking_x64.dll
LoadedModule[32]=PhysX3Common_x64.dll
LoadedModule[33]=PxFoundation_x64.dll
LoadedModule[34]=redlexer_native.dll
LoadedModule[35]=NRD.dll
LoadedModule[36]=PhysX3_x64.dll
LoadedModule[37]=Galaxy64.dll
LoadedModule[38]=CRYPT32.dll
LoadedModule[39]=POWRPROF.dll
LoadedModule[40]=d3d11.dll
LoadedModule[41]=libcurl.dll
LoadedModule[42]=amd_ags_x64.dll
LoadedModule[43]=WLDAP32.dll
LoadedModule[44]=oo2ext_7_win64.dll
LoadedModule[45]=Normaliz.dll
LoadedModule[46]=MSVCP140.dll
LoadedModule[47]=VCRUNTIME140.dll
LoadedModule[48]=WINMM.dll
LoadedModule[49]=WININET.dll
LoadedModule[50]=IPHLPAPI.DLL
LoadedModule[51]=MSWSOCK.dll
LoadedModule[52]=dxgi.dll
LoadedModule[53]=icudt.dll
LoadedModule[54]=IMM32.DLL
LoadedModule[55]=UMPDC.dll
LoadedModule[56]=CRYPTBASE.DLL
LoadedModule[57]=bcryptPrimitives.dll
LoadedModule[58]=kernel.appcore.dll
LoadedModule[59]=windows.storage.dll
LoadedModule[60]=Wldp.dll
LoadedModule[61]=SHCORE.dll
LoadedModule[62]=shlwapi.dll
LoadedModule[63]=clbcatq.dll
LoadedModule[64]=wbemprox.dll
LoadedModule[65]=wbemcomn.dll
LoadedModule[66]=wbemsvc.dll
LoadedModule[67]=fastprox.dll
LoadedModule[68]=amsi.dll
LoadedModule[69]=USERENV.dll
LoadedModule[70]=profapi.dll
LoadedModule[71]=MpOav.dll
LoadedModule[72]=uxtheme.dll
LoadedModule[73]=GameServicesGOG.dll
LoadedModule[74]=CRYPTSP.dll
LoadedModule[75]=rsaenh.dll
LoadedModule[76]=napinsp.dll
LoadedModule[77]=pnrpnsp.dll
LoadedModule[78]=wshbth.dll
LoadedModule[79]=NLAapi.dll
LoadedModule[80]=DNSAPI.dll
LoadedModule[81]=NSI.dll
LoadedModule[82]=winrnr.dll
LoadedModule[83]=mdnsNSP.dll
LoadedModule[84]=fwpuclnt.dll
LoadedModule[85]=rasadhlp.dll
LoadedModule[86]=secur32.dll
LoadedModule[87]=SSPICLI.DLL
LoadedModule[88]=d3d12.dll
LoadedModule[89]=GFSDK_Aftermath_Lib.x64.dll
LoadedModule[90]=nvwgf2umx.dll
LoadedModule[91]=dxcore.dll
LoadedModule[92]=msasn1.dll
LoadedModule[93]=cryptnet.dll
LoadedModule[94]=WINTRUST.DLL
LoadedModule[95]=imagehlp.dll
LoadedModule[96]=nvspcap64.dll
LoadedModule[97]=ntmarta.dll
LoadedModule[98]=nvapi64.dll
LoadedModule[99]=nvldumdx.dll
LoadedModule[100]=D3DSCache.dll
LoadedModule[101]=twinapi.appcore.dll
LoadedModule[102]=MMDevApi.dll
LoadedModule[103]=DEVOBJ.dll
LoadedModule[104]=dinput8.dll
LoadedModule[105]=inputhost.dll
LoadedModule[106]=PROPSYS.dll
LoadedModule[107]=CoreMessaging.dll
LoadedModule[108]=wintypes.dll
LoadedModule[109]=CoreUIComponents.dll
LoadedModule[110]=iertutil.dll
LoadedModule[111]=ondemandconnroutehelper.dll
LoadedModule[112]=winhttp.dll
LoadedModule[113]=WINNSI.DLL
LoadedModule[114]=Wtsapi32.dll
LoadedModule[115]=schannel.DLL
LoadedModule[116]=mskeyprotect.dll
LoadedModule[117]=NTASN1.dll
LoadedModule[118]=ncrypt.dll
LoadedModule[119]=ncryptsslp.dll
LoadedModule[120]=AUDIOSES.DLL
LoadedModule[121]=MSCTF.dll
LoadedModule[122]=resourcepolicyclient.dll
LoadedModule[123]=textinputframework.dll
LoadedModule[124]=Windows.Perception.Stub.dll
LoadedModule[125]=gpapi.dll
LoadedModule[126]=nvngx.dll
LoadedModule[127]=DEVRTL.dll
LoadedModule[128]=drvstore.dll
LoadedModule[129]=SPINF.dll
LoadedModule[130]=nvngx_dlss.dll
LoadedModule[131]=nvcuda.dll
LoadedModule[132]=nvcuda64.dll
LoadedModule[133]=dcomp.dll
LoadedModule[134]=dwmapi.dll
LoadedModule[135]=WINSTA.dll
LoadedModule[136]=nvrtum64.dll
LoadedModule[137]=TextShaping.dll
LoadedModule[138]=d3d11on12.dll
LoadedModule[139]=dxilconv.dll
LoadedModule[140]=d3dx11_42.dll
LoadedModule[141]=d3dcompiler_42.dll
AppName=Cyberpunk2077.exe
 
MugenMcFugen

MugenMcFugen

Fresh user
#1,932
Dec 14, 2020
Monogram_ said:
Conclusion: They should already release hotfix 1.05 to fix memory accesses, which is what I think is giving us all a headache.
Click to expand...
Yeah this is the case. It's not AVX issue. My rig (r7 3700x/1080Ti) should be capable to run it normally. I did all imaginable shiet to try fix this issue (DDU wipe, clean install/format, etc), but in the end it's definitely not problem with my PC.

I'm not gonna risk it further and will wait for them to hotfix this.
 
earthdrowned

earthdrowned

Fresh user
#1,933
Dec 14, 2020
Dominik_Lesn said:
Maybe anyone knows why my game crashed?

Here the log:

System: Win 10 (20H2) // Ryzen 5 2600 (4,1 Ghz) // RTX 2070; 460.79 Driver // running on M.2 SSD..

Never had any problem with a game until now..
Click to expand...
In your report files there's a stacktrace.txt file, what does it say?
 
Dominik_Lesn

Dominik_Lesn

Rookie
#1,934
Dec 14, 2020
earthdrowned said:
In your report files there's a stacktrace.txt file, what does it say?
Click to expand...
it says:
Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF.
File: <Unknown>(0)
 
cnschu

cnschu

Rookie
#1,935
Dec 14, 2020
same.
can be reproduced every time.
 
SigilFey

SigilFey

Moderator
#1,936
Dec 14, 2020
balboski05 said:
Did as you suggested just to humor the troubleshooting process. Reinstalled steam fresh and the game to a root folder of my creation on the C drive outside of program files. Same exact error. I don't have a partition, the only time an e: drive is ever on my computer is when I have a USB drive plugged in. No the game was not installed with a USB drive attached, no a USB drive is not currently attached. This is obviously only something the developers are going to be able to solve.

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)
Click to expand...
Hm. Aside from that, it would most likely be wonky drivers, a DirectX issue, or missing Microsoft Redistributables. You could try DDU to completely uninstall the drivers, then ensure you install the latest version using the CLEAN installation option.

The game is apparently looking for something it can't find.


bohdanren said:
File: e:\r6.patch0hotfix2\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp(40)

DO NOT UPDATE YOUR WINDOWS 10 1607 (LTSB/2016). This is ridiculous! (Or if update, downgrade in future! When they fix it or you finish the game if you just want to try it so badly and cant wait).

CDPR must fix this! Beacause Windows 10 1607 LTSB(LTSC) is not obsolete. It still the best OS for gaming (your can find many proofs in YouTube, etc. This OS has official support by Microsoft untill October 2026. And I am have been played smoothly in Red Dead Redemption 2 on it (even before all fixes)

Windows 7 latest update was in March 2019, so ask to fix Windows 10 1607 problem by updating your OS is ridiculous! You dont ask people with Windows 7 to update to Windows 10 right? Because in your system requirements for Cyberpunk 2077 exist both Win7 and Win10(since you did not specify exact version it means all actual versions are supported, right? And Win10 1607(LTSB) and 1809(LTSC) are actual and support untill 2026 and 2029. If CDPR has asked update your Win10 to at least 1909+ only to prevent game refunds, before they are will fix this bug on 1607 in future is ok. Just give me hope. Especially it technicly possilbe, I'm sure.

Windows 7 (DirectX 12 limited since 2019, DXGI 1.1, WDDM 1.1)
Windows 1607 (DirectX 12 full since 2015, DXGI 1.6, WDDM 2.1)
The game was build on DirectX 12 as I'm heard, right..? Hhh.

Anyway Windows 7 from 2009, PS4 and XBO from 2013 support this game, and Windows 1607 is not yet. (Btw why game so laggy on old PC's that is way more powerfull then outdated consoles. Cuz it just a bad console port? :) With updated graphic features? So maybe add some new options to disable this...?

LIKE "DISABLE MOUSE ACCELERATION\SMOOTHING" ETC.
OR "DISABLE TXAA"? Ha!? Always adore this console-style undisabled TXAA mmm. Every PC gamer loves it...
OR "KEY REMAPPING" Oh boy... Those console port vibes mmm. :sneaky:

BUT! You friends, are made a revolutionary game. I have Deus Ex 1, Hitman 1, Stalker 1, Dying Light 1(also Polish game btw) vibes which is hard to create in this sh?tty nowadays game business. And I know how difficult it was for you with this limited time, angry managers and crunches. And your support F DRM movement and GOG with no drm and GOG galaxy 2.0 idea to cross-platform game shops is unprecedented. So dont listen to haters! (Sorry my mistits. My London tongue level is: NO.)

Ваші друзі wish you luck.

Wake the F up Husaria. Jeszcze Polska Nie Zginęła!
Click to expand...
Not how it works, unfortunately. DirectX 12 is no longer a standalone product. You cannot download or install it separately for either Win10 or Win7 -- it is now part of Windows Update, and anything that goes wrong with it needs to be fixed by repairing Windows itself. (Though I get why this was done, I personally don't like it at all -- it just makes fixing issues extremely problematic if they crop up.)

One thing I can say from my own experience is that the game works fine once all of the bits and bobs are in place. Yes -- hopefully this will be improved in the future, as it seems there are far too many particular problems cropping up for a lot of users -- but for now, the game definitely wants the latest version of DX12. That means users will need to install the latest Windows Updates.

As of now, I haven't had a single crash in almost 6 hours of play, beginning two new characters to test.


Missilebean said:
I'm happy this worked for you and I know you're just trying to help, but it's absolutely insane that this is something anyone should have to do to get a brand new game to run. Not blaming you at all; this rant is not directed at you!! This is just way outside reasonable troubleshooting.

Someone said it before - my PC is normally very stable, good hardware, minimum to no problems. Things like driver updates, a reboot, verifying - these are normal things.

Wiping Windows, pulling hardware, hex editing the exe - that's ridiculous. This is worse than Fallout 76 or PUBG. I'm not going to sit here and risk the integrity of my PC for this game.

I've wasted days now sitting here trying to get this game to run with literally zero progress, and it seems like getting it to launch is just the tip of the iceberg. What do I have to look forward to? 27fps? Crappy police AI? In-game crashing? Bugs and glitches everywhere I look?

If there's no sign of this game being stable in the next week or two then I'm refunding and waiting for them to get it together. It's disappointing that this is acceptable in gaming these days, but it's way less stressful that way.
Click to expand...
The RAM switching is not a fix for the game. That's a test to see if there's anything physically wrong with one of your RAM sticks. If that test somehow works, that means that you have a damaged RAM stick. (Which isn't so bad, really, as many RAM manufactorers guarantee their RAM for life, so with or without a warranty, you can probably get a replacement for nothing but shipping.)

That problem and solution would be a hardware issue. It has nothing to do with the game if it works -- it's just that CP2077 may have been the only game you play that put your PC in a situation to manifest the issue.


Gruntwill said:
Just a heads up, for me it stopped crashing when I underclocked my card by 100mhz
weird huh
Click to expand...
Underclocking and overclocking is never a solution for system stability or program errors. Even if it works, it means you have a more serious issue with your hardware or system config. One of the first steps when troubleshooting should be to disable any over-/underclocking and return all of your hardware to factory default clock speeds and voltage. Anything else can exacerbate issues or create issues that otherwise wouldn't exist.


filinkd said:
Ok guys, so for me the solution was: running msi Afterburner et setting Temp. Limit on max. And I played 3 hours without any crash today.
Of course it could be exclusif solution for my config. But it works for me. So I share.
I have i7-6700k
16gb ddr4
Msi 3090 X Trio
HDD
Hope it will help some of you.
Cheers
Click to expand...
Yup! Something that has been confirmed for a number of players already is that any program that hooks your CPU or GPU functions may create stability issues, at the moment. So if you're using MSI Afterburner, RTSS, FRAPS, etc., disable those programs completely and use the in-game settings only.


MugenMcFugen said:
Yeah this is the case. It's not AVX issue. My rig (r7 3700x/1080Ti) should be capable to run it normally. I did all imaginable shiet to try fix this issue (DDU wipe, clean install/format, etc), but in the end it's definitely not problem with my PC.

I'm not gonna risk it further and will wait for them to hotfix this.
Click to expand...
For you, perhaps not, but remember that there is almost never a universal problem or universal fix for PC issues. Far too many different configurations out there to ever account for everything. What works perfectly for one person may have no effect whatsoever for the next, and it may introduce problems for the third person.

We've just got to learn our rigs' personalities.

_______________


Just to confirm, on my end, I was absolutely unable to play without constant crashing. Until yesterday. I upgraded from Win7 to Windows 10, version 19042.685.

No crashing at all in over 6 hours.
i7-4790K
GTX 980 ti, 6 GB
16 GB RAM
Samsung EVO SSD
144 Hz monitor

Frame limit at 72: 50-70 FPS at 1080p with settings mixed between High / Ultra. (Occasional dips into the 30's.)
Frame limit at 48: extremely steady 48 FPS at 1080p with settings at full Ultra.
(No Ray-Tracing or DLSS -- the 980 ti doesn't have the capability.)
 
  • RED Point
Reactions: SorainRavenshaw and MugenMcFugen
MugenMcFugen

MugenMcFugen

Fresh user
#1,937
Dec 14, 2020
SigilFey said:
For you, perhaps not, but remember that there is almost never a universal problem or universal fix for PC issues. Far too many different configurations out there to ever account for everything. What works perfectly for one person may have no effect whatsoever for the next, and it may introduce problems for the third person.

We've just got to learn our rigs' personalities.



Just to confirm, on my end, I was absolutely unable to play without constant crashing. Until yesterday. I upgraded from Win7 to Windows 10, version 19042.685.

No crashing at all in over 6 hours.
i7-4790K
GTX 980 ti, 6 GB
16 GB RAM
Samsung EVO SSD
144 Hz monitor

Frame limit at 72: 50-70 FPS at 1080p with settings mixed between High / Ultra. (Occasional dips into the 30's.)
Frame limit at 48: extremely steady 48 FPS at 1080p with settings at full Ultra.
(No Ray-Tracing or DLSS -- the 980 ti doesn't have the capability.)
Click to expand...
You're right, many may have same issue but related to something different, but I think I learned quite a lot about my PC in last 3 days, I did Win update, driver reinstall, then DDU wipe, I disassembled my PC to check out my GPU and see if connection to PSU is proper, then switched my RAM slots on motherboard, updated my chipset, tried to boost my fan speed thinking that maybe cooling fan is an issue, I tried NVidia Debug mode, I did clean install on my Win10, I tried various fixes from AVX and Hex ones to the one where I change variables in config file. Nothing worked. Pc is 1 year old, and none of components were preowned, straight out of the box.

And its always this error:

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

I'm frankly really tired of trying to figure out what does game precisely trying to access. I appreciate your and dev's work but I'm really at my wits end atm. :giveup:
 
Alphract

Alphract

Fresh user
#1,938
Dec 14, 2020
I have reinstalled 3 times my directx drivers and using 4 times DDU, install redistributable and nothing, still broken so that can't be drivers, or they need to do an update of them... (GPU crash)
 
koster22

koster22

Rookie
#1,939
Dec 14, 2020
Guys You need to recheck the game installation. In GOG its Manage Installation -> Verify / Repair. Now its not freezing and crashing during cd projekt red logo. Hope helps.
 
MugenMcFugen

MugenMcFugen

Fresh user
#1,940
Dec 14, 2020
koster22 said:
Guys You need to recheck the game installation. In GOG its Manage Installation -> Verify / Repair. Now its not freezing and crashing during cd projekt red logo. Hope helps.
Click to expand...
All done and said, otherwise I wouldn't be in this thread and playing instead :smart:
 
  • RED Point
Reactions: Missilebean and skuldintape
Prev
  • 1
  • …

    Go to page

  • 95
  • 96
  • 97
  • 98
  • 99
  • …

    Go to page

  • 133
Next
First Prev 97 of 133

Go to page

Next Last
Share:
Facebook Twitter Reddit Pinterest Tumblr WhatsApp Email Link
  • English
    English Polski (Polish) Deutsch (German) Русский (Russian) Français (French) Português brasileiro (Brazilian Portuguese) Italiano (Italian) 日本語 (Japanese) Español (Spanish)

STAY CONNECTED

Facebook Twitter YouTube
CDProjekt RED
  • Contact administration
  • User agreement
  • Privacy policy
  • Cookie policy
  • Press Center
© 2018 CD PROJEKT S.A. ALL RIGHTS RESERVED

CD PROJEKT®, Cyberpunk®, Cyberpunk 2077® are registered trademarks of CD PROJEKT S.A. © 2018 CD PROJEKT S.A. All rights reserved. All other copyrights and trademarks are the property of their respective owners.

Forum software by XenForo® © 2010-2020 XenForo Ltd.