undone shell
When Playing with friends on RV There yet i receive random freezing's. Game doesn't typically crash but I do have crashes from recent games. Freezing Occurs every 10 to 15 minutes of gameplay. The steps for reproducing is none because it happens randomly.
PC Specs
CPU- Intel Core I9 14900K
GPU- Nvidia GeForce RTX 4080 Super
Ram- 64 Gigs of DDR5 Ram
I have provided crash files for the provided crash. Reach out to me if your needing any more important details
At this point it makes the game unenjoyable and unplayable for someone who has high end specs
fierce rain
At this point it makes the game unenjoyable and unplayable for someone who has h...
i also get these crashes ALOT
pliant night
Hi @undone shell, this looks to be an Intel issue that they are aware of regarding i9 13900K and 14900K CPUs affecting Unreal Engine games (which RV There Yet? is made with). The only current proposed solution I've seen is to underclock the CPU in the bios.
According to this article: "Underclocking the SVID behavior to Intel Fail Safe in the BIOS of Asus, Gigabyte, or MSI Motherboards" may help.
However, that cites an Epic article, which doesn't actually mention that (perhaps the page has been updated). The page now suggests trying to launch the game in DirectX 11 mode. You should have the option to launch in DX11 mode when you launch RV, but if you don't, you can right click on RV There Yet in steam > Properties > enter -d3d11 in the Launch Options (or -dx11, i actually forget which, they might both work)
undone shell
What’s interesting is play modern Unreal Engine Games like, Satisfactory, Demonologist, Fortnite, and lots of others and I have no issues with those games crashing. I don’t believe it’s a specific hardware issue i believe it has to do with something with the game
Is there a way I can provide additional information? Because I also have been getting decompressed shader crashes too on RV There Yet
If it has to do with something with my CPU then the other unreal games would’ve crashing as just the same.
pliant night
That's not necessarily true. Instabilities like this are rarely consistent, because if they were they they would've been A) caught in quality assurance, B) patched instantly, or C) FAR more widespread than we see when we google. As I google the error you seem to be getting i repeatedly get reports from various people in various games get the same error, even in different engines, and they all have 1 thing in common: Intel 13th & 14th gen CPUs.
The relevant errors, in case you want to google around yourself:
Oodle: OODLE ERROR : LZ corruption : OodleLZ_Decompress failed (0 != 88635)```
I've also found a post by Intel outlining the issue and some next steps (check this for information on how to get a BIOS update + compatibility tool): https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633239
I googled your error message and "Satisfactory" since you mentioned it, and I even found this post with responses from one of the programmers (and my former coworker, as I worked on that game!) there saying the same thing (and even citing the same post I found): https://questions.satisfactorygame.com/post/6710b917ddb9d97e072025b2
So while you might not get it when you play those games, other people do get it when they play those games, and we have a lot of evidence pointing at the CPU.
So to me, there are 2 things worth ruling out before redirecting our programmers away from what they are currently working on to dig into this problem:
1) Verify integrity of files on Steam (as I've seen others report that helped them)
2) look into this BIOS update
Because if it *is* a file integrity or CPU issue, they would likely spend a long time looking into it and never finding the solution.Thank you for your reply.
I have already verified the integrity of the game files, and the issue persists. I would like to clarify that this is the only game on my system experiencing crashes. I regularly play a wide range of titles, including both Unity and Unreal Engine games, without any stability issues whatsoever. I also actively use the latest version of Unreal Engine for development projects and do not experience crashes in that environment.
Given that this problem is isolated specifically to your game, I would respectfully ask whether it is reasonable to expect a non-technical user to update their BIOS solely to resolve an issue occurring in a single title—especially when no other games or software exhibit similar behavior.
While I understand that BIOS updates can resolve certain system-level issues in some cases, the fact that every other game runs reliably suggests that the root cause may be specific to this application rather than a broader hardware or firmware problem.
I would appreciate if we could focus on troubleshooting steps more directly related to the game itself.
Thank you for your assistance.
pliant night
Thank you for your reply.
I have already verified the integrity of the game fil...
Hi again!
I've run this by one of our programmers and ultimately they have come to the same conclusion I (and the other programmer from the Satisfactory team) have reached. All signs point to a CPU issue. I understand that logically it follows that if the issue only occurs in one game, then it must be a fault with the one game, but that is not necessarily true. It's important to look at what the issue is so that a fix can be determined. But if the root cause of an issue is a misbehaving CPU - even if that instability in your case doesn't fire in other applications - then there is nothing we can do. I cannot stress this enough: we cannot write code to support defective and unpredictable hardware. This is why it is important to either confirm it's a CPU issue or rule it out entirely so we know which domain the problem lies.
From further research, we've seen that this error is a sign of the CPU rapidly aging (https://www.radgametools.com/oodleintel.htm), which may imply permanent damage over time. The BIOS update is meant to prevent that aging - meaning it may not even help in this particular case if your CPU has in fact been affected by this. After googling around more and checking on youtube, this is actually a far more widespread known issue than I had previously thought. And so to me personally if I were in your shoes, I would try and diagnose this as quick as possible and, if necessary, begin potentially looking at getting a replacement from your retailer or Intel directly (if possible), or in the worst case scenario, ensuring that you have the BIOS update to prevent any/further damage to your CPU. However, it's not a process I can walk you through. I can help you find resources, but that's as far as I can go.
I think the absolute first thing to try is to run Intel's diagnostic tool to see if that comes up with any information. According to some comments on the Intel post I shared in an earlier post, it was designed to spot these issues: https://www.intel.com/content/www/us/en/download/15951/intel-processor-diagnostic-tool.html - a pass or fail result from this would be very interesting to hear either way.
I've never used it before though, so I'm not sure how it works.
Another thing you can try is to do a deep reinstall of the game to triple check that there are no corrupted files:
%localappdata%\Ride\Saved\SaveGames)Another small thing to try is to unplug your headset and any other non-necessary devices (as we saw some evidence of some audio related issues in your log but they Shouldn't™ be related to the crash you were having - but it's worth a try).
I understand that this must be frustrating to hear, and that you just want the solution to the problem, but I cannot stress enough that with all the evidence pointing at a faulty CPU, there is nothing further that I can think of to suggest. Please let me know how it goes!
undone shell
I will be reviewing your information and provide additional information later on
pliant night
OH, i actually had one more thought: try running the game on the lowest settings possible and using d3d11/dx11 mode. I don't think it will make a difference, but if that prevents the crashes it could be a good data point to consider
undone shell
May I ask what Version of Unreal Engine 5 that you are using?
undone shell
Sounds good ill reach out to you here in a few hours on my findings and i appreciate your time with this matter 🙂
pliant night
Great! I appreciate your patience and understanding
undone shell
Hi again!
I've run this by one of our programmers and ultimately they have come...
Sure thing i do have an Audio Mixer i use for my XLR microphone ill take a look at those too while im at it
Just completed my test
pliant night
Awesome! thanks for sharing that. I will not really be around for the rest of today and much of tomorrow unfortunately but I'll be sure to follow up on this as soon as I can. Feel free to continue to share any other information you get!
undone shell
Sound's great. Will provide more information once discovered 🙂 I appreciate your time again and look forward to help solving this issue together.
undone shell
Awesome! thanks for sharing that. I will not really be around for the rest of to...
Update regarding information I have no other information to give you at this time. I will wait patiently for your response back from the passed Intel Diagnostics Test I know you noted about your absence and wanted to let you know that 🙂
pliant night
Update regarding information I have no other information to give you at this tim...
Awesome! Did you also try the steps to completely reinstall?
undone shell
Awesome! Did you also try the steps to completely reinstall?
Correct and still having the same issue. So besides the error code in the log pointing a CPU Error how can you factor a "Faulty CPU" as the issue for the crashing after doing the Intel Diagnostic Test? Also Given that the system passes Intel’s official diagnostic tool and the problem only occurs with RV There Yet?, this would seem to rule out a hardware defect. I understand hardware instability can sometimes present in isolated cases, but with the CPU passing Intel’s own validation tool, I believe it would be helpful to bring this up to your team to determine if it your game. Even though you tell your Co-Workers about my log and the specific error codes, Yes they will agree to it reading to a Faulty CPU however I have done the necessary test to confirm its not a hardware issue. Keep in mind. This is not your first case with crashes involving this game. I have read and done research on your Reviews on RV There Yet on the steam page with people also noting crashes in stuff like that. However i cannot justify those cases as they could have issues with their hardware. Additionally, The system is stable under synthetic loads(Stress test, and benchmarking tools). I have no WHEA Errors, machine check exceptions, or hardware faults. If the processor were degrading I would expect to see broader instability across workloads, especially under sustained AVX or high-frequency load scenarios — which is not occurring. Thank you for your time and would appreciate if you can address this issue soon with me.
pliant night
Correct and still having the same issue. So besides the error code in the log po...
Did you also try my suggestion of playing on absolute lowest settings? Obviously not as a solution but because this could be a good data point. If the issue goes away, then we may be able to start narrowing down the issue by slowly upping quality until we see the crash return.
As for whether we can/can’t rule out hardware defect, we can’t, but passing the diagnostics does at least justify digging in some other areas. In the meantime, I’m poking my coworkers again to see if there is more they can think of in the meantime.
brave ember
I did a bit of research, I found some information that originates from Oodle and Intel that this is a known problem with some Asus motherboard. Specifically, there is a bad device driver for Sonic Studio Virtual Mixer audio device. It's known for causing frequent crashes, especially on Windows 11 machines. Recommended fix is to uninstall Asus Sonic Studio 3 and disable Sonic Studio Virtual Mixer driver until it is fixed. Could this be something that affects you? The reason why this doesn't affect other games is that they don't create the specific circumstances that's needed for it to show up. We can't sadly reproduce it, so sadly it will show up in the wild and it punishes people like you =(.
The same thread I read also suggested that disabling Turbo mode or AVX2 in the BIOS would solve this. It might not be this issue, but if it is, I can try to reopen the old thread and see if there is some updated information about it.
I had a thought that the FPS limit might be high, so our game heats up your CPU too much, and hence creating the issue for you. If the above things doesn't help, could you try to lower the FPS limit to 60 and see if that helps or reduces the frequency of the problem
undone shell
I did a bit of research, I found some information that originates from Oodle and...
Does this involve the apparent audio issues found in my log too that Jace mentioned? Or is that an entire different thing
brave ember
The audio thing is irrelevant for this, I have just focused on the stability issue right now
undone shell
Sure let me do your recommended steps and ill reach back out on my findings 🙂
brave ember
Thank you, and thanks for your patience! Your PC shouldn't really have any problems with the game as it's quite a beast
undone shell
I did a bit of research, I found some information that originates from Oodle and...
I have limited my fps to 59 with the game settings all on low like Jace had said previously I do not recieve crashes on Single Player however i have not tested it in multiplayer like my previous crashes has been in. I do recieve a spike in CPU temperature while playing the game and that is noted for your information
I will have to do a test in multiplayer here later tonight as of I am about to head to work for the day. I'll inform you with more information to come. I did not disable the Sonic Studio Virtual Mixer at all at the moment in time until i verify that the issue is still consistent. That will be my next steps to if the game is still crashing and then will do another test with that
brave ember
Thank. Good that you did one thing at a time. Thanks for the information, that gives me something to ponder over the weekend what to do with when I'm back at work on Monday
brave ember
@undone shell How was testing? Did it seem to work? My current theory is that our FPS limiter is to high set, and hence your CPU gets too hot, and causes instability
undone shell
Hey @brave ember,
Sorry for the late response I have been extremely busy and did not mean to keep you guys held up on this for a few weeks.
It seems like the issue is resolved. However I’ve got a pretty high-end system, so I was a bit surprised that I need to manually cap my FPS to keep CPU temps and usage reasonable. Normally with hardware like mine I shouldn’t have to adjust frame limits just to keep things stable.
I have completed Benchmarking test on CPU and GPU Passed with no failures
Just wanted to point it out since it feels more like an engine/optimization issue than a hardware limitation on my side.
Is their any updates here in the near future that is going to prevent players like me with high end systems from capping their fps?
prisma flame
defiantly not an intel issue as im having the same exact issue with amd ryzen 7800xrd but i can run every other game
undone shell
Yeah it’s seems like an optimization issue
Im still awaiting a response back from them
prisma flame
me too
brave ember
Most games have a hidden FPS cap where they cap the FPS to a high number to not overheat the system. It might be that the game is too lightweight for your GPU, that the CPU never get to sleep between frames, and hence, when the CPU is pushing 200-300FPS, it get hot and unstable. Normally, games today are GPU bound, so the CPU get to rest (and hence not generating heat) while the GPU is finalizing the frame. I'm not saying that the game is super optimized, but with your beast of GPU, it can definitively generate frames super quick.
This could also be a issue of your computer beeing too "balanced" for this game. That CPU and GPU finishes generating their frames at the same time, and hance never getting rest.
I'm going to continue investigating this over at engine level and see if I can get something more out here, and if we can manage to give your CPU some rest to ensure that it doesn't overheat without capping the FPS manually.
@prisma flame Could you add a log to this issue so that I can verify that it's the same issue?
brave ember
@undone shell I have been in contact with Epic regarding this, and they state that that the issue in your log is only ever seen on defective Intel chips and that the only real solution is to RMA the defective CPU. It's widely known among devs. There is a known workaround here: https://www.quodsoler.com/blog/how-to-fix-crashes-in-unreal-engine5-games-on-intel-i7-13700k-and-i9-13900k-series . They where very interested if the user is running AMD CPU, so if @prisma flame could supply a log, I would be greatly appreciated
undone shell
Most games have a hidden FPS cap where they cap the FPS to a high number to not ...
Hey, I really appreciate the detailed explanation — that actually makes a lot of sense regarding the CPU not getting any downtime when the frame rate gets that high.
I did want to add a bit more context on my end though. I’ve had a professional IT friend take a deep look at my system, and they confirmed there aren’t any underlying hardware issues
Also, I’m not the only one seeing this. A friend of mine is experiencing the same CPU-related issue, but in his case it’s even more extreme — it affects almost every game he plays, to the point where he can only reliably run two games without problems.
To note on previous conversations we have had before I spoke with you. I talked to Jace about how I have played multiple AAA games and Indie games on Unreal Engine and Unity and no issues occur until I play this very game. I also do game development projects in Unreal Engine and Unity with no issues.
Also like I have said I have done Benchmarking test on my CPU and has passed with no crashes or failures. This is with a 100% load on the CPU for more an 48 hours.
If in the case of a result or crash from a benchmark test I would have either BlueScreened, Froze, or the Computer would have restarted itself in which this matter did not happen because I passed. So I would come to believe if it was my CPU having a failure due to temperature that needs to be ruled out because benchmarking automatically puts a high load on the CPU which then heats the CPU really hot. So how can someone rule out a hot unstable CPU is defective if it can pass a benchmark test? I use industry standard benchmarking test so I can rule out issues.
I’m not really worried about my CPU rapidly aging or effectively damaging my CPU because this issue only persist with this game. I don’t feel like I should have to update the bios just for a specific 1 title game to work efficiently without issues I feel like that is a waste of time.
undone shell
<@685875425854881798> I have been in contact with Epic regarding this, and they ...
Yeah I could see their interest as of AMD CPU’s do typically run hotter on average than Intel CPU’s
halcyon latch
Hey the weird thing about this is I'm getting this same issue but on an AMD Threadripper CPU oddly enough.