v 1.06b
I have been playing on two different computers with the same issue, one is brand new with a pretty decent specs. This has been ongoing for 2 weeks.
I have yet to narrow down “what” causes it to crash because up to this point it crashed forcing the computer to hang up (old one) or force reboot (new one).
Today it finally crashed without doing the BSOD and created a crash file.
The only thing with the latest crash that is different is I was playing in mono mode so maybe that let it be a non-reboot crash?
Here is the crash file https://drive.google.com/file/d/1ihTk3uYgvOK3woYdQ98AHgWdSfqWx56l/view?usp=drive_link
Had same issue, tried many things and nothing works except doing a clean install of windows 22h2, now I only get a few crash back to desktop which I’m still looking into but much better than before where I got constant BSOD.
Every update after Windows 23h2 get worse
A BSOD or a system restart cannot be caused by software on its own. Both are indicative of hardware or driver issues.
I mean sure. I did include the crash file once I finally got it to crash without doing a full restart.
After my initial report 3 days ago I have since had 2 other big crashes that gave files.
Here is the link now to just a folder containing farthest frontier crashes. Farthest Frontier Crash Dumps - Google Drive
Feedback to your response: Well yeah, sure your knowledge is awesome; but for a user thats super unhelpful. The software is triggering the response in the hardware just as likely as its just the hardware/driver issue. Whether its an issue on Crate’s end or the backbone platforms end of Unity, something isn’t communicting correctly. Reading the forums with several people stating issues (read likely enough people see at least 1 or 2 posts and don’t post their own issues thus the full magnitude isn’t seen), discord has it mentioned a bunch, and the interwebs has it mentioned a bunch. But sure, just tell a user who is taking the time to try and troubleshoot to the best they can, states the history of what its doing (to include the BSOD because all data might be relevant) and just offhandly tell him “its your hardware/drivers”. In my original post I gave sufficient detail to give you a starting point, saying this was happening across multiple computers not just one, so “just a hardware/driver” alone diminishes.
Almost always a BSOD or system restart is caused by driver or hardware issue. A BSOD occurs when a severe unrecoverable error has happened and the OS basically gives up and displays the exception. A restart is even more severe as the OS doesn’t even get the chance to throw the exception.
Modern architecture in operating systems limits what software can do, setting guardrails for both stability and security reasons. By design regular software (like a game) should not be able to cause a BSOD. Often when a BSOD occurs it’s caused by a bug in a driver, OS function or other higher level function that’s (correctly) called by the game, with the graphics driver being a likely suspect. It may also be that a hardware error causes the issue. That kind of bug is not within control of the developers.
What they might be able to do is to determine what call causes the BSOD and work around it. But only if that doesn’t affects the core functionality of the game. They can’t break their game for thousands of other people to fix a rare BSOD issue that a graphics driver may have.
If you haven’t already: try updating your BIOS, your graphics driver and ideally all your drivers and OS. If you overclocked your system, you may have stretched it too far: try the base settings. I hope these actions help resolve the issue.
^ This.
I’m not dismissing your issue or passing the burden onto you. We literally can’t fix a BSOD or system restart for you with a patch, no matter how much you want to blame the game or the engine. And the sooner you accept this, the sooner you can get to the bottom of the actual problem.
I’ve included the crash files as stated earlier. If I could read them and try and sus out the “why” I would, since I can’t…
Also I’ve said it twice now: its not JUST BSOD, so thats the part for your end, the BSOD I get is on my end sure.