Yes I did.
Thanks for the confirmation.
I would bet on one of the 2 following explanations then:
- The driver update architecture, somehow modifies the way VRAM is handled, and it's not correctly supported by the OS.
If true, it could be fixed by a later driver and/or OS update (hopefully in a near future).
- The driver update either modified a graphic setting, or introduced a new one.
If true, playing with the settings might solve the problem.