Jump to content

Crash on 0.24 and 0.25 with 0mb RAM detected - win7 x64


Recommended Posts

Hello everyone,

I'm afraid searching the forums and the interwebs in general wasn't of much help with the issue I'm encountering, as most posts I've found have either non-working answers or none at all.

!! SOLVED !!

This guy had a similar issue with Unity Player and a Blizzard rep narrowed it down to corrupted fonts.

Navigate to your Fonts folder and sort them by modification date.

In my case 2 fonts appeared with mod dates of 1995 : Bard.ttf and UNCL.ttf , renaming both fixed the problem.

How to rename or remove the fonts :

Start -> cmd -> right click and launch as admin

c:

cd c:\windows\fonts

rename NAME_HERE.ttf NAME_HERE.ttf.old

And you're done.

Problem description

KSP crashes with a logfile being generated that reports 0mb memory (32 bit) or loads of memory (64 bit), and an access violation trying to access it.

Affected versions (Steam)

KSP 0.24

KSP 0.25 32 bits (build id = 00642 2014-10-07_10-59-44 Branch: master)

KSP 0.25 64 bits (build id = 00642 2014-10-07_12-12-01 Branch: master)

I should note, even though this is the forum dedicated to it, that this is an entirely unmodded, fresh install.

Aside from the launcher which crashes instantly, the game executables seem to run at first, load resources and even show me the menu.

Trying to start a new game or a training tutorial however crashes the binary.

How to reproduce

Try to start the launcher

OR

Try to start a new game or training scenario

Reproductibility

Happens in 100% of the cases

System specs

The 'puter itself sports an i7-3820 CPU with 32gig of gskill RAM, corsair PSU (so none of that cheap crap), Asus HD7970 GPU and Asus motherboard, running the Win7 x64 from a Samsung 840 pro SSD and my steam library off 2x WD Red drives attached to an Areca 1200 HBA.

Both the SSD and HDDs have loads of spare space.

Basically, it is more than powerful enough to handle the game, and possibly 10 others running concurrently.

Although I believe it to be unrelated, I have Virtual CloneDrive installed.

Installed software that might play a part in this

- Microsoft Security Essentials

- Microsoft EMET

Things I've tried

- running the game in XP SP3 mode with admin privs, who knows

- removing settings.cfg to fall back to defaults

- wiping and reinstalling the game

- starting the game with "-force-opengl"

- using Compatibility Administrator to force the game to render with DirectDraw

- lowering settings to the absolute lowest minimum, graphics and audio alike

- reinstalling display drivers (which, I must add, are the latest)

- allowing windows to create a 64GB Page File, although that it entirely unnecessary with 32gb of RAM and actually slows systems down

- flashing the latest BIOS from Asus, one never knows

- remove the GPU drivers entirely and fall back to windows' bundled capabilities

- disable antivirus

- disable EMET

Things that worked

- nuh uh...

Attachments (links to MEGA)

- dxdiag 64bit

- zip of crash folder

Steps I plan to take to try to fix things

- ritual sacrifices

- investigate a Unity player issue a guy had with heartstone which seemed caused by corrupted fonts <---- WOULD YOU LOOK AT THAT, THAT WAS IT

Notes

- the 32 bit binary sees 0 RAM

- WinXPSP3 compatibility mode sees 1GB of RAM

- starting the Construction tutorial puts me in the VAB but the game crashes instantly

- trying the orbiting scenario crashes instantly with the game window being black same for the loading icon, which gets stuck

- Jagged Alliance Flashback crashes in the same fashion and is also based on Unity

Anyone experiencing a similar issue ?

Edited by Dam
FIXED !
Link to comment
Share on other sites

Can you please start the KSP.exe directly with no command line arguments and post the logs from that for us, the logs you have uploaded are from starting KSP with the launcher and using openGL mode.

It may help to see the normal logs.

Do you also have issues when starting KSP via the Steam launcher?

Link to comment
Share on other sites

Meh, my bad, will get you the correct logs.

Also updating my original post to state that I have :

- microsoft's antivirus

- microsoft's EMET

and that I plan to disable both to see if the game works any better.

Edit: god I cannot seem to do this properly, current logs are from a Win XP SP3 compatiblity run, allow me to fix this.

Edit: correct logs up

Edited by Dam
Link to comment
Share on other sites

And here you go good sir, fresh logs which should actually be meaningful this time.

I have also included a crash dump, just in case a dev happens by.

Regarding the Steam launcher, it behaves in the exact same way as starting the binary by hand, as in the game loads its resources then crashes when I try to start a new game or play a tutorial.

Link to comment
Share on other sites

Thanks :)

As a matter of fact, I believe that should get a spot in the Common Bugs and/or FAQ lists, I've seen many a post about reportedly the same issue, none of which was solved.

I've spent days trying to get this to work, and I'm probably not the only one.

The trick with this problem is that it wasn't tied to KSP in particular, but to Unity itself :/

Link to comment
Share on other sites

  • 3 months later...

Hello there,

Look, I'm going to sound condescending and/or patronizing, do not mistake me, that *is* intended.

This is how you ask people for help ?

No introductory salutation, followed by caps lock and exclamation marks ?

No additional info, no crash message, no logs, no description of the problem ?

And yet, I have a feeling you somehow expect an answer as if people could just voodoo up a magic guess.

I invite you to read this guide on how to ask questions correctly, you really do want to check it out, do not skim.

You will learn, among other things, that the first step to getting a good answer, is to ask a good question.

Now regarding your problem do note that it may stem from other additional fonts, or possibly even system fonts.

Of course it may be a totally different issue altogether.

As with every problem you want to cross-reference events and try to narrow down the possible root cause by a process of elimination.

In my case and as is stated in my original post, the problem lied with *Unity* itself and not KSP per se.

Thus, you may want to start another Unity Engine game and see if it also crashes.

If it doesn't crash then likely the problem doesn't lie with Unity but rather with KSP on its own.

While this doesn't resolve the problem, it helps find out its cause, for without the cause you cannot hope to remedy it.

Last but not least, I invite you to check this sticky thread from this very forum section, which details what information one should include when asking for help.

You have to realize that failing to include this information will just waste your time and that of the people who read your post.

Of course, you already know that since having read the guide on how to ask questions intelligently.

Link to comment
Share on other sites

Ok fair enough

I am running 0.90 with no mods and this does not happen on other unity games

my error log : Error occurred at 2015-01-29_202602. C:\Users\******\my games\KSP 0.90\Kerbal Space Program\KSP.exe, run by *******.

80% memory in use.

0 MB physical memory [1622 MB free].

0 MB paging file [0 MB free].

0 MB user address space [859 MB free].

Read from location 00007ffc caused an access violation.

I am not tech savy enough to be able to interpret this.

I am running KSP in " force-opengl" mode but it does not make a difference.

Edited by alien123
Link to comment
Share on other sites

I don,t know what else you want

I start the game it loads all the way and then it crashes in exactly the way you described. and the error log I always get is in the above comment

I am running windows 7 64bit

I have 8gb of RAM (not that that matters 32bit can only use 4)

An I5-2500K ivy bridge

Reference GTX 980

Link to comment
Share on other sites

Well now that you edited your post that's a bit more informative.

Bold text denotes actions you carry.

System text denotes commands you type.

These are the steps I followed to check my fonts :

Start menu -> Run -> cmd

This opens a shell window, navigate to the fonts directory :

cd %windir%\fonts

Now you need to adjust the shell's scrollback buffer or you may not be able to see all your fonts:

Right click on the windows' title bar -> Properties -> Layout tab

The Screen Buffer Size height is set at a default of 300 which means you can scroll up 300 lines.

If you have more fonts than that you won't be able to see them all.

I went overkill and set this to a value of 3000 (which was way too much by the way)

Adjust the value then click OK to validate.

From there, list the currently installed files :

dir

The 2 problematic fonts that caused the game to crash on me had a modification time of 01/01/1970 which is the Unix Epoch.

After removing them the problem went away.

Note that actually removing the fonts requires admin privileges so you'll want to run "cmd" a bit differently, like this :

Start menu -> search bar, type "cmd" -> right click, execute as admin

Browse back to the fonts directory :

cd %windir%\fonts

Then delete (a) the problematic fonts, or to be on the safe side just rename (B) them :

a/ del font_name_here_with_extens.ion

or

b/ ren font_name_here_with_extens.ion font_name_here_with_exten.sion.bak

Seeing however that you do not experience the problem with other Unity games, the solution I came up with may not work for you.

Edited by Dam
syntax
Link to comment
Share on other sites

Thank you for your help but you are correct the solution that worked for you did not work for me as the earliest font date I have is 1998.

I found that removing one particular mod from the game data folder prevents the crash but I have no I idea why this would be the case (I know I have not given you a lot of info I'm just asking for your thoughts)

The run of events goes as follows:

1) new clean install = no crash

2) add any mods (excluding mod previously mentioned) = no crash

3) add mod previously mentioned = crash

4) remove mod previously mentioned but keep previous mods = crash

5) remove all mods = crash

- - - Updated - - -

just something else, I found that it was mono.dll that caused an Access Violation

you can find the full error log here: http://justpaste.it/2giw

Link to comment
Share on other sites

I certainly hope you did not remove mono.dll ;)

On a side note, this specific forum is for unmodded installs.

Make sure when you encounter problems with a game, any game, to try it from a clean state first.

That way, you can assess whether the game has a problem, or a mod has a problem.

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...