VoidSquid

Hey @Xemina, someone how speaks French, thanks a lot for helping here!

Then let me ask again: did you stage at least once?

I don't know if the release branch has also been updated for KSP 1.11.0 already, @sarbian explicitly mentioned the dev branch, didn't he?

Long story short: the tutorials are not that good, better: build and launch your own contraptions! And for questions, just ask your fellow Kerbonauts. Longer answer: the tutorials, the more versions are between them and the current KSP version, the more they are "off". Which includes physics, dv, etc. You just experienced yourself.

... - ..- .--. .. -.. .. ... .- ... ... - ..- .--. .. -.. -.. --- . ... -.--. ..-. --- .-. . ... - --. ..- -- .--. -.--.-

Yes! Settings - Compatible KSP versions Probably, yes. Hence search and find the mod causing the issue as mentioned above.

Oh, you're using 1.8.1? That's a very good and stable version! I thought you'd be already playing the latest 1.11.0, my bad. Sorry, should have read your original post better. Then I suggest to try eliminating mod issues with the method mentioned above.

That's not Morse, is it?

No, I have that mod as well, no crashes. But I have to add, I am playing KSP 1.10.1, not 1.11.0, the latter has too many bugs for my taste. Won't exclude it, I never used that mod myself though. For questions about specific mods, it's usually best to ask the mod author in the respective thread, for JC see here Do you have a complete list of your mods, including version? If you're using CKAN (highly recommended!), you can easily export the list of installed mods: File - Save installed mod list A suggestion, if I may: have you tried playing KSP 1.10.1? That version has matured and I don't know of even one mod for that version that caused issues. Like I said, KSP 1.11.0 is pretty knew, and the bug tracker (https://bugs.kerbalspaceprogram.com/projects/ksp/issues) already lists several issues...

Thought so: FAILURE_IMAGE_NAME: UnityPlayer.dll As per my experience, I think this is caused by an incompatible mod, not the graphics driver. I recommend then:

Odd, no crash.dmp or similar file this time? Well, let's check the other dump file then

Hey o/ Now that's a different error, Access Violation (0xc0000005), in old Windows terms a General Protection Fault. Most of the time caused by a problem with the graphics driver or other software that does something with graphics (e.g. Riva Tuner, or some other overlay). You have a crash dump for me to check?

Hi dear mods, if any one of you does speak french, maybe you can help here? I tried and failed, pretty sure it's a language/translation problem, not a technical one.

Well, the SRBs are not active, there is no fire or exhaust to see. Are you sure you did stage once to activate the first stage? And as @RealKerbal3x already said, the throttle for the LfOx engine is zero.

Solid Rocket Boosters, those two at the sides.

I'm wondering though, the SRBs are not active as well. Might be both, staging as well as throttle for the LfOx engine.

Might be the same as this, I suggest you ask in the scatterer thread

I've created an issue at Github https://github.com/KSP-CKAN/CKAN/issues/3252 Had to look up that word, hehe, and now I need to remember it and include it in my English vocabulary

Not true, take for example Chatterer which is also hosted at spacedock

I see, thanks.

Hey @Snark, I've been wondering, since KSP 1.11.0 came out, CKAN lists the latest couple of versions of several of your mods only to be compatible with 1.11.0, but these versions aren't new at all. In fact, I have installed those 1.11.0-marked versions months ago for KSP 1.10.1: MH 1.8.2 IL 1.7 BBT 1.10 VP 1.1 Probably just an oversight with the respective CKAN meta data.

I see, yes. Pretty good reasons to stick with 1.3.1, imo.

Very ugly error, here's the debug result ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application FAILURE_IMAGE_NAME: ucrtbase.dll That ucrtbase.dll is part of the MS C/C++ runtime library. Could be almost anything, unable to identify the culprit from this. I'm sorry. What I would do (kind of standard procedure, isn't it?): Verify that all mods are good for your KSP version Try playing without mods. If that helps, reenable half of them, see if the error reoccurs. Continue to isolate the bad mod this way Check and update GPU driver Check and verify/update all installed VC RT libraries Run sfc /scannow Run dism/online /cleanup-image /restorehealth Yeah, doesn't sound funny, it's because it isn't. As I said, I can not identify a culprit here, so I can only give general advise. Could even be a faulty RAM module (don't laugh, I had that some years ago myself).

OK, give me a moment...

Just upload the crash.dmp to some file sharing site and give the link here.