onefrenchguy Posted June 24, 2023 Share Posted June 24, 2023 (edited) Reported Version: v0.1.3 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 22H2 build 22621.1848 | CPU: i7-9700K not OC | GPU: RTX 2060 6GB | RAM: DDR4, 32GB@3200MHz Specs: None of the components are overclocked - i7-9700K, RTX 2060 (6GB), 32GB of DDR4 @3200MHz, KSP2 installed on an M.2 SSD Severity: Very high - renders PC unusable Frequency: Every time since Patch 3 came out Description: I have now experienced 2 system wide freezes while building a little airplane (craft file attached). I can't really gather any information about them, but the last logs will be attached. While it was frozen, I tried to: Unplug and replug HDMI cable (thought it was a GPU issue at first) Restart my monitor The command Win+Ctrl+Shift+B to reset the GPU driver, but it did nothing Randomly typing on the keyboard, Alt+Tab, Ctrl+Maj+Esc to get task manager, nothing worked After all these didn't work, I was forced to force shutdown my PC by turning the PSU off, as it had become useless in its current state. I retried in the afternoon and with the 2nd freeze, I am now too scared to launch KSP2 because all these forced shutdowns are definitely not good. In the attachment, you'll find the Player.log, and the player-prev.log, but the latter doesn't contain info about the last crash. The craft file is also attached but be careful if it's the carrier of the issue make sure not to have a program with crash-sensitive data opened. If you need additional info or logs, I'd be happy to provide them. Included Attachments: SMOLfighters.json Player-prev.log Edited July 9, 2023 by Anth12 Link to comment Share on other sites More sharing options...
onefrenchguy Posted June 24, 2023 Author Share Posted June 24, 2023 Looks like the Player.log didn't go through, here are the last 10 lines The character with Unicode value \u066A was not found in the [realtimerounded-semibold SDF] font asset or any potential fallbacks. It was replaced by Unicode character \u25A1 in text object [SecondLine]. The character with Unicode value \u066A was not found in the [realtimerounded-semibold SDF] font asset or any potential fallbacks. It was replaced by Unicode character \u25A1 in text object [SecondLine]. The character with Unicode value \u066A was not found in the [realtimerounded-semibold SDF] font asset or any potential fallbacks. It was replaced by Unicode character \u25A1 in text object [SecondLine]. [General] Putting to ground, manually-defined ground offset: 1,25 [General] Putting to ground, manually-defined ground offset: 1,85 [General] Putting to ground, manually-defined ground offset: 1,85 [General] Putting to ground, manually-defined ground offset: 1,25 [General] Putting to ground, manually-defined ground offset: 1,85 [General] Putting to ground, manually-defined ground offset: 1,85 [System] Property [isVisible] already found in context! Link to comment Share on other sites More sharing options...
linuxgurugamer Posted June 25, 2023 Share Posted June 25, 2023 Did the fans on you computer speed up after it froze? May have taken a little while to do so, might be an indication of somthing maxing out the cpu Link to comment Share on other sites More sharing options...
onefrenchguy Posted June 28, 2023 Author Share Posted June 28, 2023 On 6/25/2023 at 4:09 AM, linuxgurugamer said: Did the fans on you computer speed up after it froze? May have taken a little while to do so, might be an indication of somthing maxing out the cpu They didn't, I even had the impression that they were spooling down a bit (since it froze it's probably the gpu's fans spooling down) Link to comment Share on other sites More sharing options...
Danny_Dorito420 Posted August 30, 2023 Share Posted August 30, 2023 I am also having this problem, I don't know what causes it though Link to comment Share on other sites More sharing options...
Recommended Posts