For all we know it could actually be a combination of GPU drivers with another driver that's causing the issue, but we'll see.
Hopefully I haven't jinxed it, but let us know if the problem returns, it's just a matter of elimination
Actually, I searched for other workarounds in fixing the nvlddmkm.sys which requires me to rename it to something like nvlddmkm.sys.old then copying the nvlddmkm.sy_ then expanding it in CMD, like creating a new nvlddmkm.sys file in case the older is corrupted.
Upon searching first for nvlddmkm.sys, There are 2 instances where 2 nvlddmkm.sys appeared.
1st is in the folder nv_dispi......
2nd is inside the folder nv_ref...........
both in System32/Drivestore/FileRepository
I noticed the folder nv_dispi... has the current driver version 431.16 (not rolling back yet (current: 425.31)).
and the folder nv_ref has the older driver which from 2017 (tried rolling back to fix with a 2017 nvidia driver).
I deleted the nv_ref folder because as far as I know, both folders has the same contents and nv_dispi... is newer.
didn't really experienced any problems deleting nv_ref folder.
Then I removed the latest nvidia update then roll back to the most stable driver I can remember (current driver 425.31)
Maybe that was the cause of the issue? conflicting nvlddmkm.sys?
Or it's just really the problem with the latest driver itself?