badidea wrote:In blue, with 'fatal error' and a sad smiley?
That goes without saying. <wink>
On my machine, the following web browsers all settle down to 15.625ms: Firefox, FlashPeak Slimjet, Microsoft Edge and Internet Explorer 11. This has not always been the case.
On the other hand, go to YouTube and the resolution increases to 1ms. Added: So too with www.bbc.co.uk/news - they are still using Flash, tch, tch!
So, I do not see any online/offline 'stuff' with web browsers.
One way to change the resolution in Windows is too use one of my portable utilities, both copyrighted but no license. You can use them. <smile>
In this respect, Windows 10 differs to earlier platforms but you will not find any details at Microsoft. It took me a while to 'fathom out' what was going on. We can 'dial in' any resolution we like subject to the min/max allowable. I wrote 'TimerInterval (Win10)' to prove this and followed up with 'TimerInterval2 (Win10)'. Here is a screenshot of 'TimerInterval (Win10)', setting the resolution to 9.8765ms, alongside 'TimerInterval2 (Win10)'. It is not an exact science and why we get a reading of 9.8763ms.
TimerRes was written a few years earlier for Win7 but will work to Win10. 'TimerInterval2 (Win10)' will not work with pre-Win10 and does not check the OS.
TimerRes radio buttons respond to a change in resolution and we change the resolution by clicking on a radio button.
'TimerInterval2 (Win10)' changes the resolution via the System Menu.