Heavy UI-Flicker both in-flight and at KSC

[Tobl]

KSP Version: KSP 1.0.0, BuildID=00830; 32-bit Steam-version running on Win7x64

What happens: All UI-elements flicker in random patterns, frequency increasing with time played. Occasionally there's also pixel-noise or random shapes flicker up, but the UI-flicker is the most consistent problem.

Mods: All Stock

Steps to replicate: Just start playing, the first flickers will appear after 10-15 minutes, after that it gets progressively worse. I've included a short video below, that was fairly early in the session because I didn't want to wait until it becomes unplayable.

It happens in flight, at KSC, inside the VAB, inside the UI-only buildings like the administration building.

It does not happen in the main menu (at least so far).

Graphics card is GTX765M, so it should easily be able to handle this. I've played default settings, minimum settings and the settings recommended by Nvidia full-screen and windowed, no effect. I also updated the graphics driver for this bug, again, the flicker persists.

Fixes/Workarounds: Restarting KSP regularly.

Other Notes:

Video of flickering over here

(https://youtu.be/KK8I2szHEPg)

Full system specs: http://pastebin.com/fKP7KkKs (I noticed that it lists my internal graphics card. Since it's a laptop, the Nvidia only gets activated for certain programs that need it, but KSP is on that list.)

Output Log: https://www./?wq0gemwfrwyn1w5

Edited May 10, 2015 by Tobl
Added Output Log

[sal_vager]

Hi Tobl, can you please see the support stickies and provide your game logs, they will show what graphics card KSP is using

[Tobl]

Sorry, I thought the log was only for crashes. But I found the most recent one and added it. I guess the really interesting part is the head, so I'll add here as well:

Initialize engine version: 4.6.4f1 (99f88340878d)

GfxDevice: creating device client; threaded=1

Direct3D:

Version: Direct3D 9.0c [nvumdshim.dll 9.18.13.5012]

Renderer: NVIDIA GeForce GTX 765M

Vendor: NVIDIA

VRAM: 1994 MB (via DXGI)

Caps: Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=0 INTZ=1 RAWZ=0 NULL=1 RESZ=0 SlowINTZ=0

Begin MonoManager ReloadAssembly

…

[sal_vager]

There's often info further down the file that we need, also we need your dxdiag output.

Though honestly, you're playing an out of date version, can you update to 1.0.2 please.

[Tobl]

Both the dxdiag as well as the full output.log were and are included at the bottom of my OP under "Other notes", just as the Bug Reporting Guide demands.

As for the version, I don't know why Steam didn't update it automatically. I've updated it now and am currently unable to reproduce, though I'm not really sure why. The change log didn't mention anything remotely to do with graphics from 1.0.0 to 1.0.2, did it? But okay, first hour says it might be fixed automagically, will update if the bug reappears.