Rollback KSP to a previous version.

[Fengist]

Prior to .25 I was able to run about 20 mods including B9, LLL, Kethane, KAS, Infernal Robotics, RBI Tracks, Firespitter, Multiwheels etc.

Now, since .25 I'm down to Kethane, KAS and LLL and even with Active Texture Mgr running at 1/2 rez AND -force-opengl I'm still getting this crap:

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

mono.dll caused an Access Violation (0xc0000005)

in module mono.dll at 001b:10118f0a.

Error occurred at 2014-12-13_221918.

E:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program\KSP.exe, run by Fengist.

70% memory in use.

3328 MB physical memory [974 MB free].

0 MB paging file [3817 MB free].

2048 MB user address space [89 MB free].

Write to location 00800000 caused an access violation.

9 Crashes in less than 3 hours of playing.

FIX THIS! Mods are now pointless as the few I have running, even with texture reduction, gobbles up the 3.3 gigs of ram and promptly crashes Unity.

I did NOT need exploding buildings. I did NOT need bigger explosions and I did NOT need Squad to add in a mod that was already available to me.

If you can't fix this then rollback KSP to a prior version where it was actually playable!

And before you fanboys start making excuses... don't. Yea, it's alpha. Yea, there are bugs and some are caused by Unity. Irrelevant. The simple fact is, this game was a LOT more stable prior to adding crap to the game that ISN'T NEEDED.

[Vanamonde]

You've been playing the game for a while, and you know how it works. When a game is in development, each update is going to solve some problems, and it's going to create some problems. This will be fixed, maybe not in the time frame you would prefer, but it will be fixed. And nobody is going to like every feature added to the game, so things you do not consider "needed" are somebody else's favorites. And if you have kept your previous versions on your hard drive, as many of us do, you can revert yourself. In short, there's no need to get nasty about it, and the angry attitude isn't going to make anybody work faster.

[Fengist]

You've been playing the game for a while, and you know how it works. When a game is in development, each update is going to solve some problems, and it's going to create some problems. This will be fixed, maybe not in the time frame you would prefer, but it will be fixed. And nobody is going to like every feature added to the game, so things you do not consider "needed" are somebody else's favorites. And if you have kept your previous versions on your hard drive, as many of us do, you can revert yourself. In short, there's no need to get nasty about it, and the angry attitude isn't going to make anybody work faster.

a: I had a hard drive die recently and lost all previous installs.

b: This has been an issue since I started playing KSP back in .16 and it's still not fixed.

c: Apparently the politeness that everyone espouses on these forums is not getting the issue solved. Sometimes, people need to get kicked in the head by the horse in order to learn not to stand behind it.

d: I'm MORE than aware that updates fix some things and cause issues with others. THIS issue has been around a long time and what I see are things being added to the game that add nothing to the core of the game and instead, increase the likelihood of this WELL KNOWN bug being even MORE prevalent. Bigger explosions and exploding building were not NECESSARY at this time to increase the playability of the game. Infiglide has been and big 'bug' since I started playing. It seems strange to me that mods like NEAR fix this but Squad can't/won't.

As far as I'm concerned, Squad has seriously deviated away from what makes KSP special and started delving into the absurd and pointless. Am I angry? You bet. I paid for this game and I hope to pay more down the road. But it's not about the money. I really LIKE this game and I like the modding community and I'd prefer to keep playing it, with mods, for long time yet. But right now, I see it going off the road and over a cliff.

[Fengist]

And again without -force-opengl

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

mono.dll caused an Access Violation (0xc0000005)

in module mono.dll at 001b:10118f0a.

Error occurred at 2014-12-14_003946.

E:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program\KSP.exe, run by Fengist.

69% memory in use.

3328 MB physical memory [1022 MB free].

0 MB paging file [3900 MB free].

2048 MB user address space [62 MB free].

Write to location 00281000 caused an access violation.

[Fengist]

And I know I'm not the only one experiencing this and I know it's been ongoing for some time. Here's just a few of the dozens of posts I came across with the same exact problem spanning months and versions. And yes, I realize it's Unity is causing this and yes, I'm certain Squad is aware of it. Unfortunately, Squad is joined to Unity at the hip now. But, if Unity is causing the crashes when a memory limit is reached then how can adding in new, unneeded features and more parts fix this?

Fixing THIS should be priority one. That's my suggestion.

http://kerbal-tutti.blogspot.com/2014/12/support-windows-thought-i-was-running.html

http://steamcommunity.com/app/220200/discussions/0/684839199031418625/

http://forum.kerbalspaceprogram.com/threads/96579-KSP-0-25-Crashing-when-entering-buildings

http://forum.kerbalspaceprogram.com/threads/95661-I-need-help-understanding-KSP-crash-logs

http://forum.kerbalspaceprogram.com/threads/81000-Help-me-understand-Crash-logs

[RainDreamer]

Well, if any fix is going to come, it will be coming with the 0.90 update. So in any case, you have to wait.

Just wonder how it works for some and not for some others though. I am running at least 60-70 mods here, and I can play things.

[Fengist]

Well, if any fix is going to come, it will be coming with the 0.90 update. So in any case, you have to wait.

Just wonder how it works for some and not for some others though. I am running at least 60-70 mods here, and I can play things.

Yea, and I've seen what's coming in .90. If this isn't fixed by then it'll just be more unneeded junk to clutter my ram. And I WISH I knew the answer to that second question. 3 mods and 2 are relatively small and running the 32 bit version. LLL is the only large package. Prior to .25, I had tons of toys to play with. Now, I'm pretty much forced to play totally stock.

[vexx32]

Well, if you actually want some help in diagnosing the issue at hand, and/or finding a useful workaround, I'd advise you post in the Support section. Posting a Suggestion like this is not likely to help anyone, nor does it contain sufficient useful information on its own to facilitate fixing the issue from Squad's end.

[Fengist]

Well, if you actually want some help in diagnosing the issue at hand, and/or finding a useful workaround, I'd advise you post in the Support section. Posting a Suggestion like this is not likely to help anyone, nor does it contain sufficient useful information on its own to facilitate fixing the issue from Squad's end.

I don't think I said I wanted to help anyone nor did I say I required help fixing it. I know the cause and I'm pretty positive that Squad does as well. I did say I wish I knew why some are able to run dozens of mods and not have this issue while others like me can't run one. I highly suspect it's specific mods and if it is... it's like the captain of the ship taking responsibility for the actions of the entire crew. Squad needs to either stop allowing .dll files in mods and stick with just parts or, figure out how they're going to police mods and stop them from crashing their game.

I believe the posts in this section are for suggestions. And that is what I'm doing. I'm suggesting this either gets fixed or that they roll back versions or stop adding new memory hogging junk to new versions until they can fix it.

Edited December 14, 2014 by Fengist

[Kegereneku]

You realize that you are playing with an awful lot of mods, you cannot take the developers responsible for incompatible tier party even if they ideally aim for that.

Also, you do not "fix" what isn't a problem to anybody but a few person. I hope you realize how self-centered and entitled you sound.

Then there's the whole concept of a game that is strictly minimalist in itself and let other install/activate their own feature. It is not really a workable way to create and sell a game. Creating feature that you do not intend to be used is wasteful. It would force you to avoid interdependency in feature, resulting in simplistic/weak game design, yet you would still have to make sure all feature stay compatible in any combination (which is actually quite hard).

Just know the moderator is being very very understanding with you.

[DuoDex]

Joining the rage train here!

Fengist, you need to stop complaining about the game if you are using mods, AND THEY ARE WHAT IS CAUSING YOU TO CRASH. Does the stock game load for you? What was that? Did I hear a faint "yes"? Hmm?

Pure and simple.

[thereaverofdarkness]

Just download 0.24.2 and wait for 0.25.1, or suck up the bugs and report them as you see them.

When it is mod conflicts, you usually want to contact the mod developers.

[Fengist]

Joining the rage train here!

Fengist, you need to stop complaining about the game if you are using mods, AND THEY ARE WHAT IS CAUSING YOU TO CRASH. Does the stock game load for you? What was that? Did I hear a faint "yes"? Hmm?

Pure and simple.

All of you, including Mr. Smug here, are missing one VERY important fact. As I said, the captain of the ship is responsible for the ENTIRE crew. IF Squad allows mods to be developed and IF Squad allows these mods to use .dll files then SQUAD is responsible for the crashes, plain and simple. Even if the mod creator sucks at writing .dll files. Whether it's the mod, Unity or the Squad programming itself that's causing the crashes it's SQUAD'S product that's doing the crashing and is therefore SQUAD'S responsibility to fix.

If that means removing the ability to use .dll files in mods, so be it. Squad cannot afford to allow this program to go into full version with these constant crashes regardless of who's causing them. It reflects directly on Squad, not Unity, not the mod developer. People will not tolerate a game crashing to desktop, regardless of the reason.

It's just that simple.

Furthermore, there's a LOT more than just a handful of people having this issue. Do the research.

[DuoDex]

If that means removing the ability to use .dll files in mods, so be it. Squad cannot afford to allow this program to go into full version with these constant crashes regardless of who's causing them. .

Dude. Mods ≠ KSP. A lot of games don't particularly support mods, yet mods there are. Also, did you really just say that? "Squad cannot allow this program to go into full version with these constant crashes regardless of who's causing them?" Uhm, if I wrote a mod and installed it, then loaded up KSP and it crashed, I can't go to Squad and complain. Your logic dictates that I can.

Furthermore, if you read the Add-on rules through, there's something in there that says Squad isn't responsible for add-ons.

Bottom line: If you can load the stock game, you have no reason to complain to Squad.

[King Arthur]

All of you, including Mr. Smug here, are missing one VERY important fact. As I said, the captain of the ship is responsible for the ENTIRE crew. IF Squad allows mods to be developed and IF Squad allows these mods to use .dll files then SQUAD is responsible for the crashes, plain and simple. Even if the mod creator sucks at writing .dll files. Whether it's the mod, Unity or the Squad programming itself that's causing the crashes it's SQUAD'S product that's doing the crashing and is therefore SQUAD'S responsibility to fix.

So what you're saying is that Microsoft should "fix" Windows because Windows crashed thanks to a driver that was coded (presumably) in an incompetent manner.

Yeah. Go away.

If that means removing the ability to use .dll files in mods, so be it. Squad cannot afford to allow this program to go into full version with these constant crashes regardless of who's causing them. It reflects directly on Squad, not Unity, not the mod developer. People will not tolerate a game crashing to desktop, regardless of the reason.

It's just that simple.

Mods are developed at the pleasure of the mod devs. Players use mods upon their (the player's) own responsibility.

It's just that simple.

(Also, DLLs usually aren't what causes KSP to crash from running out of memory, but I'm sure you knew of that right?)

Furthermore, there's a LOT more than just a handful of people having this issue. Do the research.

The vast majority of KSP players, myself included, are modding their 32-bit installs (and 64-bit installs on Linux) and playing them without too many problems. Given that you only have 4 mods running on your copy of KSP according to your OP, I'd wager the problem is on your end and not neccesarily something to do with KSP.

Finally, chill out and lighten up or take your smug, entitled, know-it-all attitude elsewhere. Your terrible attitude is not encouraging anyone to help you, learn some humility and treat others the way you yourself would want to be treated.

Edited December 15, 2014 by King Arthur

[Whirligig Girl]

ISN'T NEEDED.

Nope nope nope nope nope nooooooooooooooooo. Nope.

[Fengist]

So what you're saying is that Microsoft should "fix" Windows because Windows crashed thanks to a driver that was coded (presumably) in an incompetent manner.

Yeah. Go away.

Mods are developed at the pleasure of the mod devs. Players use mods upon their (the player's) own responsibility.

It's just that simple.

(Also, DLLs usually aren't what causes KSP to crash from running out of memory, but I'm sure you knew of that right?)

The vast majority of KSP players, myself included, are modding their 32-bit installs (and 64-bit installs on Linux) and playing them without too many problems. Given that you only have 4 mods running on your copy of KSP according to your OP, I'd wager the problem is on your end and not neccesarily something to do with KSP.

Finally, chill out and lighten up or take your smug, entitled, know-it-all attitude elsewhere. Your terrible attitude is not encouraging anyone to help you, learn some humility and treat others the way you yourself would want to be treated.

Don't think this is 'my end'

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

mono.dll caused an Access Violation (0xc0000005)

in module mono.dll at 001b:10118f0a.

Error occurred at 2014-12-14_203028.

E:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program\KSP.exe, run by uPrompt.

70% memory in use.

3328 MB physical memory [980 MB free].

0 MB paging file [3775 MB free].

2048 MB user address space [64 MB free].

Write to location 00100000 caused an access violation.

People who purchase this game are not going to want to be forced to upgrade to 64 bit versions (which requires a complete reinstall of Windows), play with DEP or processor affinity to get it to work right.

[MisterFister]

All of you, including Mr. Smug here, are missing one VERY important fact. As I said, the captain of the ship is responsible for the ENTIRE crew. IF Squad allows mods to be developed and IF Squad allows these mods to use .dll files then SQUAD is responsible for the crashes, plain and simple. Even if the mod creator sucks at writing .dll files. Whether it's the mod, Unity or the Squad programming itself that's causing the crashes it's SQUAD'S product that's doing the crashing and is therefore SQUAD'S responsibility to fix.

If that means removing the ability to use .dll files in mods, so be it. Squad cannot afford to allow this program to go into full version with these constant crashes regardless of who's causing them. It reflects directly on Squad, not Unity, not the mod developer. People will not tolerate a game crashing to desktop, regardless of the reason.

It's just that simple.

Furthermore, there's a LOT more than just a handful of people having this issue. Do the research.

(...) it's like the captain of the ship taking responsibility for the actions of the entire crew.

Respectfully: This is not a "ship," with a "captain." This is a for-profit playspace, designed ultimately at the pleasure and whim of the designer, with feedback from users, not "input," as your tone seems to imply you want. I mean, if you don't like one set of monkey bars, you hop off and look for another set that suits your fancy, no? I mean, Minecraft is very mod-friendly (and 64-bit compatible, I think.)

Lookit, I [thread=76549]feel[/thread] [thread=94259]your[/thread] [thread=100387]pain[/thread], I [thread=94086]really[/thread] [thread=96043]do[/thread].

I don't think I said I wanted to help anyone nor did I say I required help fixing it.

I think we've identified your problem. At any rate, I for one WOULD like to help you with this problem. Yes, I know that you think you're not asking. I'm offering. My links above, if anything, establish that I'm willing to try, and reasonably capable to get you SOME progress.

Don't think this is 'my end'

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

mono.dll caused an Access Violation (0xc0000005)

in module mono.dll at 001b:10118f0a.

Error occurred at 2014-12-14_203028.

E:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program\KSP.exe, run by uPrompt.

70% memory in use.

3328 MB physical memory [980 MB free].

0 MB paging file [3775 MB free].

2048 MB user address space [64 MB free].

Write to location 00100000 caused an access violation.

This is not an error log. Period, it's not. I'm not flaming you, I'm pointing out to you that your info posted above is just as useful for identifying a crash issue with KSP as it would be for me to say, "My car broke down, here's a photo I took of the smoke coming out from my engine compartment." To diagnose my car, the mechanic needs to hook their doohicker up to the electronic port in the dashboard and look at the error codes. The error log for KSP does the same thing.

(...) forced to upgrade to 64 bit versions (which requires a complete reinstall of Windows)

This is extremely wrong. Like, mind bogglingly inaccurate. You're not stupid, as no one was "born" knowing this stuff, but you're not coherently framing your issue. Again, I volunteer to help. Either here or in PM.

Edited December 15, 2014 by MisterFister
Further activity while I was posting

[vexx32]

Well, before you get all worked up yet again (or is it too late? Ah well), I think I should point out that people are more than willing to make a few simple changes to get the game working. It's not actually that much trouble, in almost every case. And no, running a 64-bit version probably won't help your issues; the x64 builds are typically less stable. That aside, you're already running an x64 build of Windows anyway, so I don't see why you're bitter about that.

And a lot of your arguments seem to revolve around the idea that 'people are angry about this', when in fact it's quite clear that you and you alone are actually worked up about this. Getting something fixed tends to not go so well when you're shouting at it. If you want a hand sorting your issues out, you are free to (calmly and politely) ask in the Support forums; that's what they exist for. Otherwise, you can rage all you want, but it won't get you anywhere. It's certainly gotten you nowhere thus far.

I feel this is an appropriate time to quote another semi-famous little green man: "Fear is the path to the Dark Side. Fear leads to anger, anger leads to hate, hate leads to suffering."

Edited December 15, 2014 by vexx32

[MisterFister]

I feel this is an appropriate time to quote another semi-famous little green man: "Fear is the path to the Dark Side. Fear leads to anger, anger leads to hate, hate leads to suffering."

+1 ^__^ rep added

[MisterFister]

Error occurred at 2014-12-14_203028.

E:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program\KSP.exe, run by uPrompt.

70% memory in use.

3328 MB physical memory [980 MB free].

0 MB paging file [3775 MB free].

2048 MB user address space [64 MB free].

Write to location 00100000 caused an access violation.

Incidentally, note that which I highlighted here. This figure implies that you have 4GB of ram on your entire system. (First of all, if you're running a laptop, you should know that some models "cheat" by affording their video RAM from the shared system RAM.) Bear in mind that, ok, KSP is running a butt-ton of RAM, but other programs needs to run too. Like Windows, and all the modules that Windows needs in order to run. Drivers and whatnots.

[Fengist]

Incidentally, note that which I highlighted here. This figure implies that you have 4GB of ram on your entire system. (First of all, if you're running a laptop, you should know that some models "cheat" by affording their video RAM from the shared system RAM.) Bear in mind that, ok, KSP is running a butt-ton of RAM, but other programs needs to run too. Like Windows, and all the modules that Windows needs in order to run. Drivers and whatnots.

I'm aware of shared memory video cards. That's not the problem and I AM running 32 bit Win 7.

------------------

System Information

------------------

Time of this report: 12/14/2014, 21:21:21

Operating System: Windows 7 Home Premium 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)

Language: English (Regional Setting: English)

System Manufacturer: System manufacturer

System Model: System Product Name

BIOS: BIOS Date: 02/08/10 11:47:16 Ver: 08.00.15

Processor: AMD Phenom II X4 955 Processor (4 CPUs), ~3.2GHz

Memory: 4096MB RAM

Available OS Memory: 3328MB RAM

Page File: 1340MB used, 5312MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7601.17514 32bit Unicode

---------------

Display Devices

---------------

Card name: AMD Radeon HD 6800 Series

Manufacturer: Advanced Micro Devices, Inc.

Chip type: AMD Radeon Graphics Processor (0x6738)

DAC type: Internal DAC(400MHz)

Device Key: Enum\PCI\VEN_1002&DEV_6738&SUBSYS_00D01002&REV_00

Display Memory: 2424 MB

Dedicated Memory: 1016 MB

Shared Memory: 1407 MB

Current Mode: 1280 x 1024 (32 bit) (75Hz)

Monitor Name: Dell E197FP

Monitor Model: DELL E197FP

Monitor Id: DELA024

Native Mode: 1280 x 1024(p) (60.020Hz)

Output Type: HD15

Driver Name: aticfx32.dll,aticfx32.dll,aticfx32.dll,atiumdag.dll,atidxx32.dll,atiumdva.cap

Driver File Version: 8.17.0010.1315 (English)

Driver Version: 14.301.1001.0

DDI Version: 11

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 9/15/2014 16:31:38, 1113576 bytes

Edited December 15, 2014 by Fengist

[Fengist]

This is extremely wrong. Like, mind bogglingly inaccurate. You're not stupid, as no one was "born" knowing this stuff, but you're not coherently framing your issue. Again, I volunteer to help. Either here or in PM.

No, it's not inaccurate. In order to upgrade from 32 to 64 bit Win 7 you need to back up your entire drive, reinstall then restore.

[Fengist]

Joining the rage train here!

Fengist, you need to stop complaining about the game if you are using mods, AND THEY ARE WHAT IS CAUSING YOU TO CRASH. Does the stock game load for you? What was that? Did I hear a faint "yes"? Hmm?

Pure and simple.

Yes, stock runs. Memory consumption of mods is causing the crashing. Is that the mod developers fault? I hear a DISTINCT 'no'.... hummmm?

[vexx32]

Oh ho, that is a bit of a surprise. I seem to recall that 32-bit versions of Windows didn't bother having the (x86) specification on the program files folder. Weird. Oh well. Maybe I remembered wrong.

Ah, and I think MisterFister was referring to your claim that people were being forced to change to x64 versions of Windows was inaccurate, not that it required a reinstall. And, please, unless you're certain to within an inch of your life that your computer's processor actually has x64 architecture, don't attempt to install an x64 version of Windows. I'm pretty sure there are safeguards there, but anyway...

Now, then... let's begin.

First, please at least double check that your graphics card drivers are up to date.

Then, if you can find it, we'd appreciate having a full output_log.txt file to scan through -- it would be simplest to upload it to http://www.pastebin.com/ due to its length. Even a brief run spits out a lot of text :/