I can't say anything on that until I see the first one.
Sometimes the driver
dump alone is enough to pick apart a seemingly random problem.
Other times it involves working your way through several fixes before it's actually resolved.
There is just really no way to know without seeing the dump.
Especially when win32k.sys is involved.