Jump to content

OK, so I tried a new tactic, and it didn't work. It still crashed.


Recommended Posts

It crashed on start-up, I didn't even click anything besides the .exe file.

 

My Mods:

KSP: 1.1.3 (Win32) - Unity: 5.2.4f1 - OS: Windows 10  (10.0.0) 64bit
Toolbar - 1.7.12
Advanced Jet Engine - 2.7.2
B9 Aerospace Procedural Parts - 0.40.7
Community Resource Pack - 0.5.4
Deadly Reentry - 7.4.7
Engine Lighting - 1.4.5
Ferram Aerospace Research - 0.15.7.2
Firespitter - 7.3
Forgotten Real Engines - 0.7.1
HullcamVDSContinued - 0.1.1
Kerbal Attachment System - 0.5.9
Kerbal Engineer Redux - 1.1.1
Kerbal Joint Reinforcement - 3.2
kOS - 1.0
KSP-AVC Plugin - 1.1.6.1
ModularFlightIntegrator - 1.1.6
Procedural Parts - 1.2.5
RCS Build Aid - 0.8.1
RealChute - 1.4.1.1
RealismOverhaul - 11.3.2
Real Scale Boosters - 0.14.5
RealSolarSystem - 11.4
ReentryParticleEffect - 1.1
RemoteTech - 1.7.1
RSSDateTime - 1.0.4
SCANsat - 1.1.6.6
SolverEngines - 2.3
TextureReplacer - 2.4.13
TAC Life Support - 0.12.4
Kerbal Alarm Clock - 3.7.1
TweakScale - 2.2.13

https://drive.google.com/file/d/0B-QIUTsNSBTQckVMUjdSamtRcEE/view?usp=sharing

https://drive.google.com/file/d/0B-QIUTsNSBTQRTBzbEhlRDJnSWM/view?usp=sharing

https://drive.google.com/file/d/0B-QIUTsNSBTQOEZvM0FYWGpReXM/view?usp=sharing

Edited by Dman979
Link to comment
Share on other sites

Here be your problem:
 

DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator out of memory - Could not get memory for large allocation 5592424!
Could not allocate memory: System out of memory!
Trying to allocate: 5592424B with 16 alignment. MemoryLabel: Texture
Allocation happend at: Line:379 in 
Memory overview

 

Link to comment
Share on other sites

On 9/9/2016 at 4:05 PM, JPLRepo said:

Here be your problem:
 


DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 5592424.
DynamicHeapAllocator out of memory - Could not get memory for large allocation 5592424!
Could not allocate memory: System out of memory!
Trying to allocate: 5592424B with 16 alignment. MemoryLabel: Texture
Allocation happend at: Line:379 in 
Memory overview

 

So, the problem is I'm using too much RAM? That shouldn't be happening, I have 16GB.

Link to comment
Share on other sites

3 minutes ago, Dman979 said:

So, the problem is I'm using too much RAM? That shouldn't be happening, I have 16GB.

sorry I wasn't clear enough.
Your log:

******* Log Initiated for Kerbal Space Program - 1.1.3.1289 (WindowsPlayer) *******

Which tells me you are running 32 bit KSP (which can only use about 3GB? roughly of RAM)

Run 64 bit KSP and your problem will go away.

EDIT:

Or, you are running 64 bit and you have posted the 32 bit logs (they are in different folders)... and if that is the case, then your problem could be something else entirely.
 

Edited by JPLRepo
Link to comment
Share on other sites

Just now, JPLRepo said:

sorry I wasn't clear enough.
Your log:

******* Log Initiated for Kerbal Space Program - 1.1.3.1289 (WindowsPlayer) *******

Which tells me you are running 32 bit KSP (which can only use about 3GB? roughly of RAM)

Run 64 bit KSP and your problem will go away.
 

Ah, gotcha.

Link to comment
Share on other sites

Edit: Yup, that worked. Thanks!

34 minutes ago, JPLRepo said:

sorry I wasn't clear enough.
Your log:

******* Log Initiated for Kerbal Space Program - 1.1.3.1289 (WindowsPlayer) *******

Which tells me you are running 32 bit KSP (which can only use about 3GB? roughly of RAM)

Run 64 bit KSP and your problem will go away.

EDIT:

Or, you are running 64 bit and you have posted the 32 bit logs (they are in different folders)... and if that is the case, then your problem could be something else entirely.
 

Nope, it's working.

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...