Ok - in Device Manager - for your Rift DK2 Sensor Properties - does this match up?

Yes, it's a match. Sorry it took so long to reply.
Yes, to be honest, I'm considering that too. This build is only about a month old, so would not want to go through the setup again this soon. Well, I'm almost ready to order CV1 or Vive... Or put that 37" telly on the desk and play the old fashion wayIt's quite alright! I charge by the hour
Seriously though - I wonder if it's worth plugging in a secondary hard drive and a fresh install of windows / Elite / DK2 drivers just for testing. Just make sure your main OS drive is safe!
Spud is enabled normally on the CV1. It has something to do with how they calibrate the screens. The problem is they did a poor job on some units and they had a terrible red tint. So if they thought you had a problem, Oculus customer support would give you a tool to disable spud. It removed a lot of the extra red tint, but also removed some of the good red tint and made it look a bit like 256 colors banding. I don't know if the DK2 uses spud.By the way, how I enable Spud? It is not very clear to me what that even is... If I understood correctly, it removes red tint in cv1?
You're right, a sun's corona, with the ship blocking the sun, really reveals the banding. I normally scoop while looking at the sun so I don't usually see banding that strong.Sun coronas are good for banding at its worst... just jump in and scoop, turn so you're skimming the star and usually the banding will be obvious.
Update. I tested with 0.8 runtime and got brilliant, deep colors with minimal banding! Difference was like night and day. BUT performance with 0.8 and Steam VR is bad, so it is not a solution. But now I know that there really IS something wrong with the 1.8 runtime for dk2 and nothing wrong with the unit itself. I assume that promised color corrections for cv1 made it much worse with dk2. Now they are starting to really drop of dk2 support.