"KSP.exe caused an Access Violation"

[Starwhip]

I keep running into this error, which immediately crashes the game. It is becoming quite irritating.

The crash does not freeze the game. Rather, the game simply "closes" instantaneously as if I had force-quit.

I'm including the logs of several different crashes below:

ACCESS VIOLATION LOG FILES

Installed Mods:

Kerbal Engineer Redux (v 1.0.17 as far as I can tell)

HyperEdit (v 1.4.1)

Other Installed Things:

Cubeships - Working on testing this mod for someone else.

Custom miscellaneous new parts for testing.

This so far has always happened as I'm driving a rover (The "Silverfish", if you want to see it there's a link in my signature) on the surface of Kerbin. It has happened immediately after I stop the rover and quicksave, as well as in the middle of normal gameplay. It happens at intervals of around 30 minutes. The rover travels at around 60 m/s.

Running KSP v 1.0.4, Windows 32 bit.

I will try uninstalling all mods. I suspect that the error is not in KER or HyperEdit, but in the miscellaneous files I have in GameData.

[Padishar]

Well, the last 5 are all out-of-memory crashes but the first one is different. There appears to be something corrupted in the save as there is lots of spam of "Look rotation viewing vector is zero" and KER is failing to read transforms from some parts.

Are you on 32bit windows or running 32bit KSP on 64bit windows? On 32bit windows the game can only use about 1.7gig of RAM (without special boot tweaks) so you will need to reduce texture resolution, run in OpenGL mode or do something else to reduce the memory usage (and the memory leaks in KSP will still likely cause it to crash after not very long).

Do these mods you are testing use DDS textures? If not then getting these changed should save you some more memory.

[sal_vager]

Stock crashes with this error as well, but this is the first time i have seen this.

d3d: failed to create vertex buffer of size 963200 [out of memory]

d3d: VB or IB is null

d3d: failed to create vertex buffer of size 963200 [out of memory]

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: failed to create vertex buffer of size 963200 [out of memory]

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

d3d: VB or IB is null

DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!

Trying to allocate: 4194304B with 4 alignment. MemoryLabel: STL

Allocation happend at: Line:74 in

Memory overview

[ ALLOC_DEFAULT ] used: 367839502B | peak: 0B | reserved: 389788258B

[ ALLOC_GFX ] used: 993207945B | peak: 0B | reserved: 1128480540B

[ ALLOC_CACHEOBJECTS ] used: 67004B | peak: 0B | reserved: 12582912B

[ ALLOC_TYPETREE ] used: 7300B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 614196B | peak: 0B | reserved: 8388608B

Could not allocate memory: System out of memory!

Trying to allocate: 4194304B with 4 alignment. MemoryLabel: STL

Allocation happend at: Line:74 in

Memory overview

[ ALLOC_DEFAULT ] used: 367839502B | peak: 0B | reserved: 389788258B

[ ALLOC_GFX ] used: 993207945B | peak: 0B | reserved: 1128480540B

[ ALLOC_CACHEOBJECTS ] used: 67004B | peak: 0B | reserved: 12582912B

[ ALLOC_TYPETREE ] used: 7300B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 614196B | peak: 0B | reserved: 8388608B

You have a lot of "d3d: VB or IB is null" lines, thousands, and I think it's a problem with direct3d, are you alt+tabbing out of KSP?

It could also be that something is trying to use D3D at the same time, like if you were recording or running another 3D program.

The error log does show an out-of-memory error.

Error occurred at 2015-07-24_224736.

C:\Users\user\Documents\KSP1-0-4\KSP_win\KSP.exe, run by user.

82% memory in use.

0 MB physical memory [1050 MB free].

0 MB paging file [0 MB free].

0 MB user address space [72 MB free].

Write to location 00000008 caused an access violation.

But none of the loaded processes look suspicious.

I'd check my graphics driver, make sure it's up to date, other than that I don't know.

[Starwhip]

Stock crashes with this error as well, but this is the first time i have seen this.

You have a lot of "d3d: VB or IB is null" lines, thousands, and I think it's a problem with direct3d, are you alt+tabbing out of KSP?

It could also be that something is trying to use D3D at the same time, like if you were recording or running another 3D program.

The error log does show an out-of-memory error.

But none of the loaded processes look suspicious.

I'd check my graphics driver, make sure it's up to date, other than that I don't know.

I do ALT + TAB (Man, the key formatting thing is awesome. ) out of KSP a lot. Probably about five or more times in a session leading up to a crash... The only other thing I have visibly open most of the time (not a background process. There sure are a ton of those. :/) is Windows Media Player for music. It has one of those music visualization things running, maybe that's contributing to the problem? (If so, I can turn it off. Not like it does anything useful. )

[sal_vager]

WMP is really unlikely to be it, it's most likely the Alt + Tab (two can play that game) as it's a known issue from the past, so I suggest using Alt + Enter first before using Alt + Tab, or playing in windowed mode, you should be able to use -popupwindow to get a fullscreen window that won't be effected by Alt + Tab.

[Starwhip]

WMP is really unlikely to be it, it's most likely the Alt + Tab (two can play that game) as it's a known issue from the past, so I suggest using Alt + Enter first before using Alt + Tab, or playing in windowed mode, you should be able to use -popupwindow to get a fullscreen window that won't be effected by Alt + Tab.

I'm also fairly certain that I'm a few versions behind on my graphics driver. I'll check that.

I'm 100% certain that I should update Windows. Haven't done so in seven months.

EDIT:

Useless website/installer is useless. Darn you Intel.

[steve_v]

"Read from location 00000138 caused an access violation."

I've seen that address before somewhere...

The only answer I see is "reinstall / verify game integrity", might be worth a shot.

OTOH, you do appear to have OOM issues, which may well be causing this too.

[SmashBrown]

Getting this myself. Also getting out of memory, fairly sure I have a memory leak, just to add to my joys, just when you think your game is going well, all the bugs break out.