Welcome to Sysnative - to both of you!
Great to see one new member helping out another in what must be a difficult time, thanks staffy.
No, it's not looking like a real CPU problem :thumbsup2:
As I mentioned to Red elsewhere:
It's possible that the error is down to some software/driver interference or that it's a motherboard or, probably less likely, a PSU problem, rather than a CPU fault.
As far as as common drivers that are known to be involved in causing BSODs goes, ASUS/Gigabyte drivers don't have a great reputation historically, there are a number of them listed here, as well as many other known bad/suspect 'utility' drivers:
Driver Reference Table - Common BSOD related drivers
If you both follow the request to switch to pre-release updates, as requested in
#37 in the ESET forum, that should help both yourselves, and other ESET users, to get a rapid fix pushed out.
On a more general stability note - try to keep utility software drivers to a minimum, clean is good! I use DriverView, set to hide Windows drivers, to check the 3rd party drivers that Windows loads:
DriverView: Loaded Windows Drivers List
Keep us updated, please, the real analysts here might want/need to dig deeper into this issue.