Hi,
I read BEagle's rant and have a solution. I had exactly the same problem with my HP 10-e011sa with exactly the same symptons. The solution turned out to be some nitwit at MicroSoft who has designated the display driver for this machine with W10 as being from AMD/Radeon version 21.19.137.1 of September 16 this year. If you delete the driver it briefly (15 minutes or so) works exactly as it should with a Generic uSoft display driver. However after ~15 minutes correct operation, W10 decides it needs the 'Correct' driver and re-installs the dodgy version from AMD. The actual solution is to then 'Roll-Back' the driver to the previous version from uSoft and it should continue to work correctly. (I have had 2 weeks good operation since my remedial action.) The run-around from Currys/PCW/etc just goes to show their general incompetence.
https://support.microsoft.com/en-us/kb/3073930 goes some way towards explaining why the Roll-Back works over the driver deletion.