I agree. If they had just said to people "Yeah, we're changing our minimum requirements to Win10 because DirectX 12 is a requirement and the wrapper for Win7 is simply not workable." I would have said "Okay, that sucks for me but whatever." That appears to be the de-facto cause of the "gpuapidx12error.cpp(40)" crash in nearly all cases, and in cases where it occurs in Win10, a clean reinstall of windows appears to be the fix based on people in this thread.Same flatlined issue on my side, sometimes when starting the game, sometimes after 20 minutes, sometimes after an hour. Submitted a ticket with dxdiag infor event loger info, etc... - there was no response. From my understanding there are hundreds, if not thousands of people, having the same issue.
There is no meaningful response from CDPR, just a couple of obvious steps for troubleshooting (check drivers, check win version, some amateur stuff), besides my favorite "we are looking into this". I went though all of the steps, needeless to say there was no improvement, but I think that everybody from this thread is aware of that.
This is too frustrating to bother with, so I wont play this game anymore. By the way I had no issue before 1.4 patch, which makes the whole situation even more ridiculous. I just wanted to provide an off topic suggestion to CDPR PRs and damage control staff. May be some moderatore can pass it upwards. Here is what they should have stated:
1. Say to all users with this problem "Don't play this game in the next month/half a year/year". Our patches are making things worst, we are focused on consoles now, because we screwed there even worse.
2. Offer refunds. Since there is soo neglectible numer of people experiencing this problem, that it is not your current priority, you won't suffer and financial loss.
3. And this is the most important for me, fire the person that wrote this "Cyberpunk 2077 is a DirectX 12 game — DirectX 12 works on Windows 7 thanks to porting tools and some features may be limited. Keep in mind that official support for Windows 7 from Microsoft ended in January 2020. " Are you f***ing kidding me? Stating this in a way like it is my problem that I am still running win 7? IT IS WRITTEN IN THE SYSTEM REQUIREMENTS THAT IT IS SUPPORTED!!! If this was enterprise SW you could have been sued for such an ignorant statemant.
Lets see how much time it will take for somebody to delete this for being off topic. I bet that is going to be a lot faster than addressing he issue itself!
Which firmly puts the root cause in DirectX 12 for "gpuapidx12error.cpp(40)" issues. I personally would like a clear statement from CDPR about if they intend to fix the wrapper issues or an admission they can't get the final product working on Win7 as originally intended, along with an update to the minimum requirements to clearly show Win10 as a requirement.
Edit: Seems that not even every version of Win10 is applicable, due to DirectX 12 changes over the life of Win10, only the main line of development (as opposed to enterprise editions and whatnot) has the proper functions that 2077 is making calls for. Thus the Win10 instances of the "gpuapidx12error.cpp(40)" crash are explained at least in part.
Last edited: