I've been rolling around 3.1 / 3.1.1 for a little while now and I'm seeing a lot of people talking about the crashes to desktop. As the proud owner of a rig that isn't quite top tier, I've historically gone out of my way to adjust star citizen with user cfg's and extra settings in order to make my gameplay more enjoyable. I've had to do the same thing with these last few builds, but this time I've been mostly focused on preventing CTD's. I've come across some helpful threads and implemented useful fixes that have helped in the past, and I can say that I've been able to reduce the crashes from about 1 every 10 minutes, to 1 every 2 hours. In the spirit of helping out others in the verse, here are the changes I've made. Hopefully others can use this as a guide and find it useful: 1.) Windows 10 users: Disable windows 10 game bar and (if you're an experienced PC user) disable the xBox Game monitoring service: These two things cause an absolute boatload of crashes on star citizen and have compatibility issues with a slew of other games as well. At this time CiG has acknowledged the Game Bar only, but both fixes do appear to help. Aside from star citizen, this one may help your gaming experience all the way around. Disclaimer: To disable xBox game monitoring, you will need to edit the registry. If you fuck up and break things, it's not on my head. I take no responsibility for your efforts, and the instructions to do this are merely linked here. I will not write them myself. Follow the instructions here to disable those things: https://www.windowscentral.com/how-disable-and-remove-game-bar-windows-10-creators-update 2.) If you're an NVidia user, uninstall The 3D vision driver and 3D vision controller. Historically these two installations have always messed up Star Citizen. For me, it's been an issue since 2.6 . While many of us NVidia users think we've already uninstalled it, I noticed that mine crept back in during an update, so check again. You can find this in the add/remove programs section of your PC as two separate options - one for the driver and one for the controller. They can both be safely removed. (This driver is for those people who use the active 3D glasses that NVidia produces. For everyone else we don't need the driver and it will periodically enable for no particular reason and crash things up.) 3.) NVidia users: Correctly set your GPU settings. This can make a big difference all the way around, and these steps can be basically repeated for other games. Refer to this link: https://robertsspaceindustries.com/spectrum/community/SC/forum/4/thread/graphics-gpu-guide-for-star-citizen and this link: https://robertsspaceindustries.com/spectrum/community/SC/forum/50174/thread/nvidia-gtx1080-performance-guide 4.) Make sure you have no network-interfacing programs running Things like teamviewer can give you some glitch unwanted side effects, and often have background processes running even if it isn't obvious on your task bar. Wherever possible, make sure to stop these services, or (preferably) temporarily uninstall the application. 5.) Make sure your pagefile (if you need one) is on the same drive as your install. I've heard mixed opinions about editing a pagefile - as it only works for select people. If you fall into ALL of the following categories: -You have Star Citizen installed on an SSD with 50GBs + space to burn -You have 16GBs or less of RAM -Your processor and GPU are reasonable for SC AND you're comfortable with making edits to your system, then a pagefile can help with crashes substantially. I have mine currently set to 30GBs, and have noticed that Star Citizen will eat up a whopping 21 gigs of it. As a person with 16GBs of RAM... looks like I needed it. As before, I take no responsibility if you break your shit! For instructions, please see the link here: https://testsquadron.com/threads/improve-sc-performance-with-page-filing.12695/ ----------------------------------------------------- As I come across more universally helpful fixes I will add them here, so upvote if you found this helpful and I will continue to try and make sure that it stays relevant as we receive hotfixes. See you all flying, Calvin Reveraster