I had exactly the same problem (even resetting it every morning, great way to start the day!) and spent a few days going back and forth to Microsoft Support in an attempt to fix it. Here's what was said - hope it helps.
Please provide me with the following details.
a) I would like to know if you are using UltraMon software .
b) Please follow the steps given below :
Click on Start - Type "Msconfig" in the instant search - It will open up the system >configuration utility - choose "selective startup" - Uncheck load startup Items - go to >Services tab at the top - put a check mark on hide all microsoft services - click on >disable all . Make sure to uncheck "Windows Event Log" service from the list - click on >apply - click on close - Restart the computer .
Try to save the settings and then restart the computer to check if the settings are saved
No I'm not using UltraMon.
I followed these steps and it seemed to fix the problem. However, I
obviously can't usually operate with a selective start up routine, not
least because one of the things disabled is my virus protection. So
what's next to narrow down the potential culprit?
FYI, the non-Microsoft services that were disabled were:
- Apple Mobile Device
- Bonjour Service
- Eset HTTP Server
- Eset Service
- iPod Service
- lxcf_device (Lexmark printer)
- ServiceLayer (Nokia)
As the system is in selective startup . I will request you to put your system back on >Normal startup but make sure you keep the "Windows Event Log" service unchecked in the >services window , Then apply the changes and click on OK , Restart you computer once and >check if everything works fine . To me it seems that "Windows Event Log" service is >creating the problem . Try this and please let me know if it is works .
I tried this today and it worked. However, it caused problems with
other services. Namely, Virtual Server 2005 R2 would not connect
(giving a 'No Connection error'). I confirmed this was the sole cause,
by turning Event log on and off and rebooting a number of times.
I rely on Virtual Server 2005 in my day to day work, so this is not
currently an acceptable solution to my problem.
I gave up here, as I'd spent too much time on it already - but you might not have the problem with Virtual Server 2005.
Oh and no ... no idea why 'Windows Event Log' should affect the position of a monitor!