game crash

[Pupun2542]

my game is alway crash when playing around 5 minute after start game.

there are my mod

[sumghai]

A mod list is not enough to determine the cause of the crash.

As per the support sticky topic, you need to provide the following information:

On 23/08/2014 at 7:27 PM, NathanKell said:

1. The Logs
   These are text files that the game spits out for debugging purposes as it runs; if something broke horribly in-game, there will be something in here about it. You should upload the entire log as a file (i.e. not to pastebin); you can use dropbox or an equivalent host to upload the file. Make sure the entire file gets uploaded; you may have to zip it first, as logs can be very long. Here is where you can find the log:
   • Windows: KSP_win\KSP_Data\output_log.txt (32bit) or KSP_win64\KSP_x64_Data\output_log.txt (64bit)
   • Mac OS X: Open Console, on the left side of the window there is a menu that says 'files'. Scroll down the list and find the Unity drop down, under Unity there will be Player.log ( Files>~/Library/Logs>Unity>Player.log )
   • Linux: ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log

NOTE: These logs are not the same as KSP.log, which lacks valuable data. Do not upload KSP.log; do upload output_log.txt / Player.log

[*]The Reproduction Steps

These are essentially a recipe on how to cause the bug. If you don't include reproduction steps, the modder won't be able to reproduce the bug, and then can't fix it. The more detailed you make this, the better. Leave nothing out. Leaving out details can make bugs impossible to reproduce, and thus, impossible to fix. The gold standard for reproduction steps is an unedited video of you causing the bug.

[*] Clean Environment

If the issue stems from one mod, try to replicate it with only that mod and its hard dependencies in a clean KSP install. If the issue stems from the use of several different mods (for instance, Procedural Wings are still producing lift underneath a Procedural Fairing while FAR is installed) then get a clean install of KSP and install only the mods (and their dependencies, if applicable) in question.

This may seem like an extreme measure, but it ensures that only those mods (or the stock game) is to blame. Despite how complicated it may seem, it is actually quite simple to do (even for Steam users), as you can simply copy your install directory elsewhere as needed. It's especially useful since interaction bugs are some of the hardest to nail down; something that appears to be a bug in one mod might actually be caused by something else.

Regardless of how many mods are installed, you should include a list of all mods installed with their version numbers; a screenshot of your GameData directory is not sufficient, as it does not include version information and some directory structures may hide what mods are installed. Obviously, this is easier if you reproduce the issue with fewer mods.

[VenomousRequiem]

While @sumghai is right, and a log could tell us for sure, that's a lot of mods. I'm going to take a shot in the dark and say it was an access violation(as it usually is...) and you need to lighten up your GameData a little bit. Especially things like BDA weapon packs. Those seem to take up a lot of memory.

Edit:

Taking a closer look at this, that's a lot of BDA weapon packs. I remember I had a similar install a while back, and I crashed pretty quickly too.. Just get rid of some mods, fam.

Edited April 21, 2016 by VenomousRequiem

[Pupun2542]

http://www.This website cannot be used on these forums/download/ul0xrx1vx6r601p/output_log.txt

output log

but I delete all compressed mod file from my computer

[sumghai]

7 minutes ago, Pupun2542 said:

http://www.This website cannot be used on these forums/download/ul0xrx1vx6r601p/output_log.txt

output log

but I delete all compressed mod file from my computer

Sorry, but that hosting site is not permitted on this forum, due to malware concerns.

Please upload your log file to another service e.g. Dropbox, Pastebin, Google Drive and link to it in your next reply.

[Pupun2542]

https://drive.google.com/open?id=0By8WgCWt8I0qN3ZfaUV3TURUeUU

[Padishar]

That definitely looks like it is running out of memory (more accurately, running out of address space) and the Windows DbgHelp.dll that is used to generate more useful info about the crash to add to the log is failing to initialise because it can't allocate some memory.

You will need to either reduce your mod load or do something else to reduce the memory usage (e.g. try the -force-opengl command line option).

[Pupun2542]

oh thankyou