SpaceDuckNeedsTheHelp Posted September 30, 2019 Share Posted September 30, 2019 I'm using KSP 1.7.3 I can normally play for about 20-60 minutes before the game "Crashes". I use quotes because it doesn't make a crash log and most the time doesn't even bring me back to the desktop. It just freezes. BUT, this time it did make a crash log to share. HERE I don't really know what all is needed to help find the problem but just tell me and I can provide that info. Thanks for any help in advance! Link to comment Share on other sites More sharing options...
VoidSquid Posted September 30, 2019 Share Posted September 30, 2019 Hi there, Can you please provide the crash.dmp and the log files? Link to comment Share on other sites More sharing options...
Lisias Posted September 30, 2019 Share Posted September 30, 2019 Uhh! In Page Errors! Check the SMART status of your hard drive. This thing use to happen when the system needs to swap back some memory, but got an I/O error from the HD on the process. If the SMART pinpoints non recoverable errors or exhaustion of sparing sectors, you will need to replace your hard disk. Link to comment Share on other sites More sharing options...
VoidSquid Posted September 30, 2019 Share Posted September 30, 2019 Yeah, that's one of the most common causes for this error, but before making statements myself, I'd prefer to have more information, in particular the crash.dmp file. In the past I've also read several issues in connection with that xinput1_3.dll, the crash.dmp should hopefully tell us if it is the HD/SSD or that file causing the issue, maybe both. Link to comment Share on other sites More sharing options...
Lisias Posted October 1, 2019 Share Posted October 1, 2019 The XInput is always involved because it is always loaded. And it's also constantly being called (to read the inputs!), so it's also very usual that it can be a (preferable) screaming victim of whatever is trashing the game. I was told something about third parties Unity Layers, as Steam and Radeon Overlay. In a way or another, that crashes are on 0xc0000005 (Access Viollation). This one is a 0x0xc0000006 (In Page Error), and the behaviour matches what I expect to see on a failing hard disk with SMART. So checking the Hard Disk is the first thing to be done, not only because it makes sense, but because if I'm right the guy needs to act fast to salvage what he can before the HD dies for good. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now