Well, since it appeared that the problem occurred after updating the graphics driver, I wondered if simply rolling back the driver. An less than a minute in Device Manager, I did that and the problem is fixed.
I guess "If it ain't broke, don't fix it" should be applied to driver updates.