Buffer Over run Error when unlocking PC - not the first time

Hi,

My computer never sleeps or hibernates, I lock it when I am done and only the displays go black. They do not sleep either, I turned that function off, so it is just Windows blacking out my displays in the absence of a screensaver.

When I first started using this version of star dock I would get a situation where, when I woke up my displays from sleep, I could clearly see a flash of my desktop. About a 2-3 second flash then it was gone and I was presented with the username / password prompt.

How many times this happened I cannot remember but it was frequent enough that I thought, I hope this security leak is only a local thing. Because in my mind, if I can see my desktop before logging in, then some hacker could take advantage of that to bypass my logon - I am a simple man.

I often received some kind of error after seeing this happen. I cannot remember what those errors where. I do remember they were the same error and I thought nothing of it but, weird bug and clicked it closed each time.

Yesterday while waking up the displays again I saw the flash of my desktop for a good 15 or 20 seconds.

then I received the logon screen and I did my ting and started to logon.

Before I reached the desktop I had three errors in a row, each one popping up immediately after closing the previous. I attached pictures of these errors below in the order in which they appeared to me on-screen.

I found no dumps or mini-dumps on my system; this is most likely not driver or hardware related, but software related and possibly a security risk. I believe it is a security risk simply because I could see my desktop before logging in, even before I saw the username password prompt.

This happened immediately after tapping my space bar a few times to turn my displays from black to their normal logon background picture but I saw my desktop first, THEN it went away and I saw my normal logon prompt.

This is a security issue and it needs to be patched.

I cannot be the only one in the world who has experienced this?

My only question is: does the patch come from Star Dock or Microsoft?

I have not looked into this in anyway shape or form so who knows the cause of these errors other than Groupy and MS files are involved.