Graphics glitch on startup

[Jetski]

Have a gamebreaking glitch on the main menu screen, seems related to the floating Kerbals? Major graphics glitch makes it so I can't see the menu items (Start, Credits, Quit, etc), large black and white angular glitches covering the screen and wandering around. Also no progress indicator while displaying witty loading hints, but game does eventually get to the glitched main screen.

History: I've been playing for months with no problems. Installed some mods, decided later to go back to a clean install. Fresh download from site today, new directory (no existing files). Install KSP, first startup goes normally. Second startup (now that there's a settings.cfg file) problem appears. Easy to recreate, happens every time.

All log and image files (including a KSP.log before and after glitch, DxDiag.txt, etc) available here: http://bettermarineservices.com/ksp/

Second load in full glitch:

First Startup (no problems):

During second load, no load bar showing:

[sal_vager]

Hello Jetski, your output_log.txt is flooded with this line:

d3d: failed to lock vertex index buffer, offset 0 size 384 [internal driver error]

I see your system reports a mobile Intel graphics card as well, do you have a built-in Nvidia or AMD card?

If you do my guess is you're on a power saving mode, and your main card is off, if so you'll need to make sure the laptop is plugged in, it wouldn't hurt to update your graphics drivers either

[Jetski]

Laptop is plugged in always, also been playing on this same laptop for months with a variety of mods and pure stock .90 no problems. Also strange that there's no issue the first time I start with a clean install (before it generates the settings.cfg file). I can delete the settings.cfg file and it will start up and run normally, but it sucks to do that (and reconfigure graphics options in launcher) every time I want to play KSP. Only breaks on the second startup, after the settings.cfg file exists. Running no mods, no special graphics settings, no command line options. Graphics drivers are the same as worked previously, no changes made. Only weirdness that I can think of is I tried to install ATM mod (crashed and wouldn't run), then deleted it and wiped the directory and installed a fresh download. Is it possible for a mod to permanently mess with my graphics properties even after I delete everything and do a new KSP install in a new directory?

Edited April 9, 2015 by Jetski

[sal_vager]

Okay this is a weird one, the settings.cfg shouldn't be able to cause something like this, it's writing so it can't be data execution prevention, and KSP isn't in a protected windows folder.

You have some graphics, but then it might be bugging out on a shader that is in one part of the menu and not the other, so it's still worth checking for any updated drivers for your laptop before proceeding too far, it's not unknown for Windows updates to change/break things, necessitating new drivers.

I suggest you check your power save options as well in case it's still using them even while plugged in, just being on mains is not a guarantee, there's definitely something preventing the card from working properly, trouble is finding it.

[Jetski]

Did a system restore point to roll back to 2 days ago (when I was playing KSP fine), still glitching. reinstalled graphics drivers, still no dice. I can play if I just delete the settings.cfg every time. Frustrating though.

Edit: Now it crashes even if I delete the settings.cfg - a KSP low memory crash during startup. bummer.

Edited April 10, 2015 by Jetski