So a blue screen of death is often caused by a driver or hardware. Your suspicion on being the GPU could be what it is. I highly doubt it's the CPU as those typically don't fail. They can, it's just not something that happens all that often compared to a GPU or RAM or some other piece of hardware.
I'm not well versed in reading massive dump logs. What I do is just run a program called
Who Crashed and see what it tells me to further help zero in on the source of the issue. The Nirsoft website has his version as well. Both could be used to help find the cause. It's called
BlueScreenView.
Is the video card new?
Are you using the latest driver?
Go back and retrace everything you did prior to the BSOD occurring. Like, was there new software introduced to the system? New hardware (even USB)? An update to software, and anti-virus or Windows its self.
One way to uninstall the video driver with minimal stuff left behind for a clean install of the latest driver, is to first boot into safe mode and then run
Revo Uninstaller to remove the GPU driver. Just be careful on the registry part. If it doesn't look related to the GPU driver, then I wouldn't remove it. If you see a registry key folder there related to your driver software (in this case AMD) then that whole folder can probably be deleted with zero issues. Unless of course you have something else AMD related on the computer so you'd want to take caution as some of the registry values may be shared. By in large, I've had very little trouble with Revo Uninstaller, but I did see it present to me registry keys that were shared among other software I had installed. That's why I mention this minor warning.
To get into safe mode, reboot the computer and keep taping the F8 key once a second. (Safe mode invokes after the quick BIOS/UEFI launch, and right before the Windows OS boots). Then you'll want to chose just the 'safe mode' option. Not with networking or any of that. With networking allows you to use the network and Internet in a safe mode environment all the while the network drivers are loaded in the system. If you were trying to iron out a possible network driver issue you'd use just the 'safe mode' option without networking so the network drivers aren't loaded for testing.
I looked at your dxdiag log and everything seems alright. When you were in dxdiag, did you check the 64 bit option as well? Go to each tab and see if any problems are found in both the 32 and 64 bit versions. The 64 bit option is at the bottom. The difference is due to drivers that are coded in 32 or 64 bit code thus thus you'd want to check the 32 and 64 bit versions of dxdiag. You may not have a 32 bit driver issue, but there could be a 64 bit driver issue. Not saying this is true in your case however. If you do see a non-WHQL driver, those
could pose issues. So make note of that.
