gman517 Posted August 27, 2019 Share Posted August 27, 2019 (edited) We all know it. We all HATE it. Here's a simple remedy that fixes this problem for me whenever it occurs: Just Log Off and log back in again. Why does this occur?Microsoft OS users at this point will all know that they are known for shooting themselves in the foot.For some really weird reason. An applications memory in the RAM (could be ANY application) somehow gets corrupted.If you tell this to any microsoft staff they will simply tell you to do a myriad of virus scans. And everything else not related. Logging off and logging back on somehow "resets" the memory. Closing and restarting the application does not have this effect. Don't ask me how this works. But definitely don't ask Microsoft. They won't give you a straight answer. A lot of people say to reboot. I want to finish this tip by saying that Logging off and logging back can solve and even prevent a lot of problems and is quicker. I have found that this occurs on a brand new just reformatted system. I would consider reboots a more advanced... more last resort option. Edit: Another Option Before Logging off:Make sure the error is still showing. Do Not click OKIn Your Task manager (ctrl alt del) find "GECK.exe *32". Right click and "close process tree" Then try to start it again. Hope this helps someone. Edited August 27, 2019 by gman517 Link to comment Share on other sites More sharing options...
Recommended Posts