There are typically many WER logs available, and most aren't of any relevance. Most are about unrelated app crashes or some other Windows internal problems that aren't fatal.
You can find somewhat readable WER logs in msinfo32 under Software Environment, but it's literally WERs each in one line.
There was a one-bit corruption in some memory that was being deallocated. Because this happened once only thus far, I would not be concerned about it.
Bugcheck code 0000001A
Arguments 00000000`00041792 ffffd33f`fd553928 00000000`00010000 00000000`00000000
Debug session time: Sat Feb 4...
I have somewhat looked at the dump files, they look awfully like situations I've seen many times before yet every single time they remain to be a struggle. There have been plenty of situations where when Adobe editing programs were used, crashes occurred indicating hardware problems. It is not...
I do not recommend using Driver Easy, or any similar program. They are simply put not needed and may potentially install bad drivers too. Most drivers you need you can get from Gigabyte, mind that while their drivers may not be up to date, up to date drivers aren't guaranteed the best for your...
And there is no bug in Windows leading to a crash and there is no hardware problem.
The 0xEF (critical process died) is a good example, doesn't involve drivers yet is a fatal problem usually as a result of a hardware problem.
The frameworks used to develop kernel software are improving and getting better at what they do which is another aid in reducing the amount of BSOD crashes. So long as new(er) frameworks are used to develop kernel software, the chances of crashes overall decrease significantly.