Has been fixed in 19.2.1/19.2.2.
Ignore it and wait for next driver update for your particular product.
well I will wait