>>723154564
Install windbg (grab the gui version from the MS Store) as well so you can look at the likely crash dump that's available. Once you load the dump (drag it onto windbg), click the "!analyze -v" link that pops up in the console and see what the faulting module is. That's your issue. If it is the GPU driver, it could be a myriad of things (try using DDU and clean reinstalling your driver first, then using DDU and rolling back a bit).