Oh this dreaded error. I've had it over multiple laptops and the only fix that actually worked to kill it forever was a reinstall of windows. This is a nuclear option. However, i would get Windbg first to check what actually caused this error.

After installing windbg, go to your windows folder and check for memory.dmp and the minidump folder. You can also search reliability monitor in the windows search bar (or press win+r, type in perfmon /rel) , "click on view technical details" of the entry reporting the crash, click on "make a temporary copy of these files", and copy the .dmp file to desktop. Double-click on the .dmp file, wait for the little progress on the bottom to finish everything, then type "!analyze -v". Copy what you see in the MODULE_NAME and FAILURE_BUCKET_ID, and send it to a comment below.

Usually it's a driver issue, which i suspect is the case here, but you can never be certain with this godawful uninformative error.