Really hoping for another patch that will address the crashing issue in Japantown when ray/path tracing is enabled

+
While it's very possible that this could be the source of crashing, I find it unlikely (not impossible, but unlikely) that a CPU defect would result in reliably re-created instability. This sort of hardware defect would almost certainly be more random and spasmodic. It is possible that this portion of the game (Japantown) is simply putting the correct sort of strain on the CPU and manifesting a hardware issue, but I would bet that there would still be a degree of randomness involved.

The original descriptions of the crash occurring at very specific locations or under very specific conditions (like driving over a certain speed) are far more indicative of a software / driver / API error, whether in the game, OS, or 3rd-party code. If what you're seeing is able to be re-produced reliably, keep sending the reports in whenever you can detect a change.

If what you're seeing is random, scattered, and hard to reproduce...then and only then would I start worrying about returning hardware. On the whole, it sounds like Intel is honestly unsure about what actually happened.
 
Seeing the Error and crash report would make troubleshooting much easier.
But if you're on a 13/14 gen intel, that is most likely the issue. I changed my Power settings for my 14900kf, which fixed the crashes for me.
can you tell me what power settings you changed?
The thing is if I roll back to 2.0 or turn off ray tracing, the crashing immediately stop. I also have 300+ hours in this game pre 2.1 with zero crashes with the exact same setup.
Now I would love if it's actually a CPU issue that I can just fix with some settings, but it just doesn't seem to be the case.
 
So far with Nvidia Optimizing taking Path Tracing to full Ray tracing, seems to have done the job. As of this moment. I completed all the Wakako gigs and all the sides in Japantown, and no crashes yet.
 
From what updates I've heard, like this one, the problems sum up to overvoting CPU units and other physical defects.

Intel should release or has released microcode update that will solve the former. Some CPUs are scre**d for real, though, since physical defects means it's not good to begin with.

The CPUs that were running with excessive voltages for a while might even run fine, but personally I'd RMA and swap as soon as that option is offered. I wouldn't want to update it now, and let this whole thing go away, and then it dies much sooner than it would otherwise. It should be on Intel to bear the cost of this mess.

Once Intel has fixed the issue, it doesn't mean that all CPUs will be updated from then on... the market still has loads of CPUs that were already made before the update was released, and all of those need to receive the update to their microcode... performed by their owner.
Post automatically merged:

Besides that, a reason why things might crash in a specific spot could indeed be broken game resources.

Imagine that there is a hole created, and V ends up in a loop of falling through to the bottom of the space, and touching of the ground happens so fast that it looks like the game is constantly loading, stopping to load, then loading again and there is no end to it. Doubtlessly, that cycle could also crash the game. And someone who doesn't experience those things on a daily basis (say, by not pushing the boundaries of the game on a daily basis) will be none the wiser of what is going on. So, indeed, it's possible that some defect keeps crashing the game. For that, one may have to repair files (and also undo all mods first in the process), or they could install a fresh copy of the game in another location and try to see how things go there with a save. Just beware, some mods alter game saves and then those saves will remain broken.
Post automatically merged:

About the issue from another author

 
Last edited:
So far with Nvidia Optimizing taking Path Tracing to full Ray tracing, seems to have done the job. As of this moment. I completed all the Wakako gigs and all the sides in Japantown, and no crashes yet.
wait bro what are you talking about? How did the crash go away for you? Is there a new GPU drivers update or something?
 
This AI in the Nvidia optimized in the GeForce Experience pop up box. This is the settings Nvidia chose:

Ambient Occlusion: High
Anisotropy: 16
Cascade Shadows Range: High
Cascade Shadows Resolution: High
Contact Shadows: On
Crowd Density: High
Display Mode: Full Screen
Distance Shadows Resolution: High
FidelityFX Super Resolution (FSR): Disabled
Improve Facial Lightning Geometry: On
Level of Detail (LOD) High
Local Shadow Mesh Quality: High
Local Shadow Quality: High
Max Dynamic Decals: Ultra
Mirror Quality: High
Resolution: 3840x2160
Resolution Scaling: NVIDIA DLSS
Screen Space Reflection Quality: Psycho
Subsurface Scattering Quality: High
Texture Quality : Auto
Volumetric Cloud Quality: Ultra
Volumetric Fog Resolution: Ultra
VSync: off
Xe Super Sampling (XeSS): Disabled

NVIDIA

Reflex: On
RTX DLSS Performance
RTX DLSS Frame Generation: On
RTX DLSS Ray Reconstruction: On
RTX: Path Tracing: OFF (this is a setting I set in game, and Nvidia shut down)
RTX: Ray Trace Lightning: Psycho
RTX Ray Traced Local Shadows, Traced Reflections, Traced Sun Shadows, and Ray Tracing: all are on

So far, it is going okay..... I am not overly knowledgeable to give any answers, so I did it the long way to show you what it did, hopefully it helps. I did it on a lark, "lets try this" and push the button, and so far, it is doing fine. I say 'so far' as I am not all that trusting. The Card is a GeForce RTX 4080

FAILED
 
Last edited:
From what updates I've heard, like this one, the problems sum up to overvoting CPU units and other physical defects.

Intel should release or has released microcode update that will solve the former. Some CPUs are scre**d for real, though, since physical defects means it's not good to begin with.

The CPUs that were running with excessive voltages for a while might even run fine, but personally I'd RMA and swap as soon as that option is offered. I wouldn't want to update it now, and let this whole thing go away, and then it dies much sooner than it would otherwise. It should be on Intel to bear the cost of this mess.

Once Intel has fixed the issue, it doesn't mean that all CPUs will be updated from then on... the market still has loads of CPUs that were already made before the update was released, and all of those need to receive the update to their microcode... performed by their owner.
Post automatically merged:

Besides that, a reason why things might crash in a specific spot could indeed be broken game resources.

Imagine that there is a hole created, and V ends up in a loop of falling through to the bottom of the space, and touching of the ground happens so fast that it looks like the game is constantly loading, stopping to load, then loading again and there is no end to it. Doubtlessly, that cycle could also crash the game. And someone who doesn't experience those things on a daily basis (say, by not pushing the boundaries of the game on a daily basis) will be none the wiser of what is going on. So, indeed, it's possible that some defect keeps crashing the game. For that, one may have to repair files (and also undo all mods first in the process), or they could install a fresh copy of the game in another location and try to see how things go there with a save. Just beware, some mods alter game saves and then those saves will remain broken.
Post automatically merged:

About the issue from another author

yeah the Path tracing setting has been turned off, what a surprise. I have been aware for months that this is the culprit that's causing the crashes. Only problem is getting CDPR to see this and fix it. :(
 
Okay... scratch my last post..... oy back to square one. Crashes happening have reoccurred. Now testing: A mod FSR3 Frame Gen.
Let you know how that turns out. As of this post, I have not tested it yet, but will shortly
 
Okay... scratch my last post..... oy back to square one. Crashes happening have reoccurred. Now testing: A mod FSR3 Frame Gen.
Let you know how that turns out. As of this post, I have not tested it yet, but will shortly
Are you getting crashes even with path tracing turned off? Is it a reproducible crash or it happened randomly? Where did it occur?

I have done comprehensive testsing about my own reproducible crashes, maybe you can check it out and see if it could help you and save some time.

 
Yes, Path Tracing was turned off, the same settings I posted. Weird that it took some time before it started crashing.
Anyways spent a number of hours trying out the mod, and thus far so good, but then I said that before. I shall do more tomorrow. The only complaint is it causes a 'buttoning' effect at high speeds, but does not interfere with game play. Just looks strange.
I thought to see about independent mods as I found some that 'fixed' Valerie. I posted a unmoded Valerie with default clothing, as you can see her body just does not line up with her legs, and Path Tracing picks it up. I did test to see unmoded Valerie naked on the bike and no shadow is visible, everything lines up. Only when wearing clothing does it show up. I found a Valerie vanilla body mod with higher polygons, which helped, and with Moded clothing the shadow does not appear.
So that is my thesis to see if the crashes can be eliminated without roll back.
 

Attachments

  • GraphicError.jpg
    GraphicError.jpg
    1.2 MB · Views: 65
I had crashes in Japantown specifically, but I did a verify/repair and that seems to have fixed that issue. I'm assuming it was a missing texture or something similar.

I still get crashes randomly, sometimes on startup, sometimes during the game. Issues I didnt have a month ago. One other game I play seems to have similar issues. But I think I'll have to blame Intel here and await their microcode patch, which they say they'll have ready by mid August.

In the other game, changing the settings(lowering/turning off features) fixes the issue and then the next day it crashes again. In CP2077 I lowered some of the graphics settings and the game ran fine. I did not turn off Raytracing, though. Its all a bit weird, I have trouble making sense of it.
All I can conclude is that its not a hardware malfunction.
 
All I can conclude is that its not a hardware malfunction.
And yet these issues:
I still get crashes randomly, sometimes on startup, sometimes during the game. Issues I didnt have a month ago.
One other game I play seems to have similar issues.
In the other game, changing the settings(lowering/turning off features) fixes the issue and then the next day it crashes again.
...are all pretty heavily indicative of a potential hardware issue. When stuff happens "sometimes but not other times" or "usually around this spot but sometimes in other places", that's a sign that something outside the program is causing issues. The more random it is, the more likely it is to be hardware related.

So, I think that you (and probably a lot of other people) are seeing both software and hardware issues...which makes diagnosing which problems are caused by what a real pain.

My major concern on your end is where you say that you didn't have certain issues a month ago. That's not a great sign. Really hoping that Intel and the mobo manufacturers can sort this out with that microcode patch.


_______________


@all,

In the meantime, it sounds like there may be an issue with Japantown crashing that's coming directly from the game. If other people see the crashing stop after verifying, please do send that info into CDPR Support.
 
And yet these issues:



...are all pretty heavily indicative of a potential hardware issue. When stuff happens "sometimes but not other times" or "usually around this spot but sometimes in other places", that's a sign that something outside the program is causing issues. The more random it is, the more likely it is to be hardware related.

So, I think that you (and probably a lot of other people) are seeing both software and hardware issues...which makes diagnosing which problems are caused by what a real pain.

My major concern on your end is where you say that you didn't have certain issues a month ago. That's not a great sign. Really hoping that Intel and the mobo manufacturers can sort this out with that microcode patch.


_______________


@all,

In the meantime, it sounds like there may be an issue with Japantown crashing that's coming directly from the game. If other people see the crashing stop after verifying, please do send that info into CDPR Support.
I just go by the news,

 
I just go by the news,

While a nice timeline of events surrounding the processors, how does this relate to an individual user's ability to assess whether the issue they're seeing is software vs. hardware?

My main point is that I wouldn't recommend people jump to conclusions about an issue in Cyberpunk 2077 being a result of a faulty CPU -- especially not if the crashing or other issues they're seeing are able to be reliably re-created.

The Japantown crashing does not appear to be a result of hardware issues in any way that I can see.
 
An update......... with all the graphics options to max, and many hours in game, both in the original and the expansion. DLSS on, but both Ray Tracing and Path Tracing turned off: no crashes. Therefore, simon_93 is correct; something is wrong with the Ray Tracing, and Path Tracing in regards to Cyberpunk 2077.
 
An update......... with all the graphics options to max, and many hours in game, both in the original and the expansion. DLSS on, but both Ray Tracing and Path Tracing turned off: no crashes. Therefore, simon_93 is correct; something is wrong with the Ray Tracing, and Path Tracing in regards to Cyberpunk 2077.
Have you tried downclocking your processor? In my case, not only did that completely cease the crashes, but also instantly increased the game's stability to a full 100% consistently.

To downclock your processor:

1) Download the Intel Extreme Tuning Utility and run it
2) Start Cyberpunk 2077 Phantom Liberty 2.12
3.a) Go to SETTINGS, GRAPHICS, and select the Quick Preset: Ray Tracing: Overdrive
3.b) Scroll down and eventually increase the Screen Space Reflections Quality to Psycho, and Level of Detail (LOD) to High
4) Go to the actual gameplay and stand still. Do not go into Inventory or Menu. Just let the game run.
5) Go to the IETU and check the Package Temperature. If it doesn't exceed 87 °C or turn red, then your processor is fine.

6) But if it does exceed 87 °C and even turns red, then check the Max P-Core Frequency. Should be at 5,5 or 5,8 GHz for the 13900.
7) Reduce the Performance Core Ratio from 55 to 45 with the intent to reduce the Max P-core Frequency to 4,5 GHz
8) Now check the Package Temperature again

If it stays at around 75 °C and not once turning red while the CPU Utilization fluctuates between 30 - 40%, the crashes should no longer occur. If they still do, then I would advise to bring your PC to your dealer to have it examined for any hardware issues.

This is all based on my own experiences, investigations, experiments and tests concerning these crashes and what I did to permanently solve them. Hope it works for you and anyone else that are no longer able to play.

P.S: Any setting in the Intel Extreme Tuning Utility needs to be reapplied after each time the computer is started.
P.P.S: Yeah, I wrote this post before checking the rest of the thread and saw that you already tried this. Consider it never written.
 
Last edited:
Are you getting crashes even with path tracing turned off? Is it a reproducible crash or it happened randomly? Where did it occur?

I have done comprehensive testsing about my own reproducible crashes, maybe you can check it out and see if it could help you and save some time.

Have you tried downclocking your processor? In my case, not only did that completely cease the crashes, but also instantly increased the game's stability to a full 100% consistently.

To downclock your processor:

1) Download the Intel Extreme Tuning Utility and run it
2) Start Cyberpunk 2077 Phantom Liberty 2.12
3.a) Go to SETTINGS, GRAPHICS, and select the Quick Preset: Ray Tracing: Overdrive
3.b) Scroll down and eventually increase the Screen Space Reflections Quality to Psycho, and Level of Detail (LOD) to High
4) Go to the actual gameplay and stand still. Do not go into Inventory or Menu. Just let the game run.
5) Go to the IETU and check the Package Temperature. If it doesn't exceed 87 °C or turn red, then your processor is fine.

6) But if it does exceed 87 °C and even turns red, then check the Max P-Core Frequency. Should be at 5,5 or 5,8 GHz for the 13900.
7) Reduce the Performance Core Ratio from 55 to 45 with the intent to reduce the Max P-core Frequency to 4,5 GHz
8) Now check the Package Temperature again

If it stays at around 75 °C and not once turning red while the CPU Utilization fluctuates between 30 - 40%, the crashes should no longer occur. If they still do, then I would advise to bring your PC to your dealer to have it examined for any hardware issues.

This is all based on my own experiences, investigations, experiments and tests concerning these crashes and what I did to permanently solve them. Hope it works for you and anyone else that are no longer able to play.

P.S: Any setting in the Intel Extreme Tuning Utility needs to be reapplied after each time the computer is started.
P.P.S: Yeah, I wrote this post before checking the rest of the thread and saw that you already tried this. Consider it never written.
Okay.. again, this is not the problem. I did have the problem but that is resolved, without checking the heat, and only need to reduce the P-cores to X52 from X55. This kind of issue causes crashes from start up, to 5 to 10 min into the game, at any zone, (side note without the P-core reduction x52 Hogwarts refuses to run at all, stating lack of memory).
These crashes, simon_93 is talking about, is in Japantown (only) and normally in a car, though I had it happen while walking.
Now from what I gathered, simon_93 rolled his game back, to get the game from crashing. Me, I kept the game at 2.12 and have no crashing (like over 50 hours now) because turning Ray and Path tracing off completely. I do have DLSS on, and all the graphic settings at max settings.
Logically: simon_93 is correct. With my different approach resulting stability, combine his solution. No doubt something is wrong with the ray and path tracing in Cyberpunk 2077
 
Downclocking or overclocking is never a solution to a problem. It may work as a workaround -- so do go ahead and use it for the interim -- as it's not directly harmful to anything if managed correctly.

But needing to change the voltage and clock frequencies from factory defaults is indicative that something else is wrong with your system. It could be as simple as an incorrectly setup BIOS, perhaps an issue with Windows configuration, or it could be something wrong with the actual hardware. Work around it, by all means, but also make sure to figure out why it's really happening and fix it. These are the types of issues that can result in much more serious problems down the road.

Logically: simon_93 is correct. With my different approach resulting stability, combine his solution. No doubt something is wrong with the ray and path tracing in Cyberpunk 2077
Unlikely, especially if you've done a CLEAN reinstallation and GPU driver install, started a new game, and are still seeing the issues. That type of crashing may be down to something like present drivers conflicting with calls from the game or the GPU firmware not cooperating correctly with an API. Remember, if there is an issue with the game itself, every player on planet Earth will see the same issues.

For example, the city stuttering and NPC pop-in in DD2 is universal -- all platforms / all settings. This is an issue with the game. The problem is 100% universal, systemic, and consistent with no exceptions. Conversely, there are only an extremely small percentage of players on any platform reporting the crashing you're describing in this thread. Obviously, CDPR will want to figure it out and fix it if possible, but it's not going to be a few lines of code. It's being caused by something else on those systems that conflicts with the game working as intended. (As it does work correctly on the vast majority of other platforms and system configurations.)

Personally, I still think it's either corrupted files or a threading issue. The (by the sound of it) almost absolute consitency and placement of the crashing for the players it affects says we have a problem with the software. As it does not occur on most systems and consoles, that says it's not a direct result of Cyberpunk's software -- but that doesn't mean that the Cyberpunk software can't be edited to fix it.
 
Downclocking or overclocking is never a solution to a problem. It may work as a workaround -- so do go ahead and use it for the interim -- as it's not directly harmful to anything if managed correctly.

But needing to change the voltage and clock frequencies from factory defaults is indicative that something else is wrong with your system. It could be as simple as an incorrectly setup BIOS, perhaps an issue with Windows configuration, or it could be something wrong with the actual hardware. Work around it, by all means, but also make sure to figure out why it's really happening and fix it. These are the types of issues that can result in much more serious problems down the road.
This may be true, but there is no solution to the issue, other than this, at this time. The sad truth it is not only Hogwarts Legacy and Cyberpunk 2077 are having these issues. A fair amount of games are having this issue, with the 12/13 + gen cpu's and quite frankly Intel has placed it on the companies like CDPR, to alter the software to recognizes the new architecture of the 12/13+ gen cpu's have. Read it right on Intel's forums.

That said, as mention in the past, my Laptop has a I9 13980 cpu, and though it has been some time I played on it, what I remember I had no crashing like my desk top had with a I9 13900. The Laptop CPU has no alterations to the CPU functions.... I am shooting into the dark, I guess it has to do with the 80 extra digits somehow.

Unlikely, especially if you've done a CLEAN reinstallation and GPU driver install, started a new game, and are still seeing the issues. That type of crashing may be down to something like present drivers conflicting with calls from the game or the GPU firmware not cooperating correctly with an API. Remember, if there is an issue with the game itself, every player on planet Earth will see the same issues.

For example, the city stuttering and NPC pop-in in DD2 is universal -- all platforms / all settings. This is an issue with the game. The problem is 100% universal, systemic, and consistent with no exceptions. Conversely, there are only an extremely small percentage of players on any platform reporting the crashing you're describing in this thread. Obviously, CDPR will want to figure it out and fix it if possible, but it's not going to be a few lines of code. It's being caused by something else on those systems that conflicts with the game working as intended. (As it does work correctly on the vast majority of other platforms and system configurations.)

Personally, I still think it's either corrupted files or a threading issue. The (by the sound of it) almost absolute consitency and placement of the crashing for the players it affects says we have a problem with the software. As it does not occur on most systems and consoles, that says it's not a direct result of Cyberpunk's software -- but that doesn't mean that the Cyberpunk software can't be edited to fix it.
Why is CDPR the only company I delt with who suggests a clean reinstall right off the get go. Others, in a nutshell, will tell you, to make sure the drivers are up to date, but reinstall ONLY as a last resort.
With all due respect, you still have 2 solutions that resulted in stability. Your answer does not address:
1.) simon_93 roll back his game, I think to 2.0, with Ray or Path Tracing on. (if I remember correctly, he DID do a complete reinstall, and it did not work, roll back was his only solution to keep Path/Ray Tracing on )
2.) Me; keeping it at 2.12, setting all the graphic options to max, keeping DLSS on, but have Ray and Path tracing off..
 
This may be true, but there is no solution to the issue, other than this, at this time. The sad truth it is not only Hogwarts Legacy and Cyberpunk 2077 are having these issues. A fair amount of games are having this issue, with the 12/13 + gen cpu's and quite frankly Intel has placed it on the companies like CDPR, to alter the software to recognizes the new architecture of the 12/13+ gen cpu's have. Read it right on Intel's forums.
Again, I need to stress that the issues stated in the OP of this thread are not indicative of any hardware issue. The crashing is too particular. That doesn't mean it can't be caused by that, but it's almost 100% guaranteed not to be, since the crashing is so exact and re-creatable. Exactly the same spots every time.

But, what you're saying on the other side of that coin is exactly the type of thing I mean as far as identifying and fixing the real issue. Different scenario:

Let's say someone was receiving system-wide crashes, on all games, at random times, and perhaps also while doing less intensive things, like typing in MSWord or surfing the net, but those crashes were not as frequent. They then undervolt their CPU a bit, and everything seems to become more stable. THAT would be indicative of hardware issues. By all means, undervolt. In this case, I would strongly recommend people get that system checked out at a shop and figure out if their 13/14 gen Intel CPU is suffering from the "microcode" issue, and how many cores have already been fried. (Then, I'd work on replacing that chip.)

_______________


One or two games, only, always crashing in roughly the same spots (or in exactly the same spots) every time, while other programs remain stable: that doesn't sound like hardware in any way, shape, or form. That sounds like a drivers that are failing to handle certain type of call being made to the GPU, or an API that isn't cooperating with a driver, or there might be an issue with the installation package on a certain platform resulting in corrupted data. Whenever a crash is easy and straightforward to re-create, it's almost always software. It can just be very tricky to pin down exactly which software or combinations of software are responsible.

_______________


There's also a third scenario here. It's both. There is a software issue between the game, API, and drivers...and there's hardware issue somewhere in the system. It doesn't even need to be that the 13 / 14 gen Intels are suffering from the voltage/degradation issues, as it apparently is only about 20% of the chips produced. The other 80% are apparently fine even with the microcode goof. True, the microcode fix is still needed, as that type of voltage will eventually decrease the lifespan of the hardware for essentially no reason. But it's not unheard of for there to be something with a processor design (the way it handles threading...the way it handles big data calls...the way it handles lots of little, rapid data calls at the same time...) that conflicts with the design of a particular GPU or driver package. It could literally just be a hiccup with a few games on those particular combinations of hardware / firmware / API / software...and have nothing to do with the other problems on 13/14 gen chips.

Why is CDPR the only company I delt with who suggests a clean reinstall right off the get go. Others, in a nutshell, will tell you, to make sure the drivers are up to date, but reinstall ONLY as a last resort.
Because the updatesincluded in the next-gen patches to Cyberpunk and The Witcher 3 did not just "tweak graphics" and "fix bugs". They introduced a complete re-working and rebuilding of large swaths of the games, both what is apparent to the player and even bigger things under the hood. (I can't provide specific details or examples because I don't know the specifics. But the CLEAN installation thing was a very important part of the release and support.) Basically, you'll rarely see this sort of update from other studios. If they suggested something like this to their producers, the response would probably be, "Hell, no! We're not spending that sort of time and money on a game released 3-5 years ago." It would be a "remake/remaster edition" sort of venture and would be re-sold as a different product.

But the nature of such a massive update on this scale creates a real potential for the game's existing installation to have become littered with problems: file conflicts that may have occurred over multiple updates or data corruption while replacing so many critical files (due to bandwidth issues, the power going out, etc. while the game was trying to compare, verify, and update so many.) Because of the popularity of modding, especially, it would be extremely likely for modded installations to result in a next-gen update that didn't manage to get everything installed correctly.

Hence, the CLEAN installation (all caps -- extremely important.)

Also, who tells you not to reinstall a game? I would most certainly not start with that, and I wouldn't rush to it as a third or fourth option. But if you're seeing glaring issues with a game, cannot seem to find the problem online, and the studio doesn't seem to know...reinstall the game. A reinstallation is not in any way harmful. Especially if you're aggressively modding, you'll be reinstalling all the time when (not if) things get botched.
 
Last edited:
Top Bottom