I have not yet encountered the bug while using nvidia-driver 390.25 from experimental. Hasn't occurred in four or five suspensions. It predictably occurred about in about half of the suspensions with 384.111. Thanks.