Hello, I wanted to share my recent problem with bsod crashing when using BOINC for Einstein@Home. (only on GPU assisted data)

Last week I performed a video driver update, it was about 10 days after release at that point. A little sooner than I usually do, but oh well.
After that, when BOINC ran the GPU jobs, I would eventually get a bsod crash. Occasionally there were be some listed as computational error.

I rolled back the driver to the previous version. No fix.
I completely uninstalled the driver and did a clean install. No fix.
I started analyzing the minidumps, various problems reported. Nothing I disabled was a fix either.
I ran several file system checks and fixes: sfc, dism, chkdsk. (safe mode and regular) No fix.

Then I finally noticed that a bsod occurred after the BOINC screensaver had just started. BINGO!
Set it to a blank screensaver (or none) and the problem was solved.

I run a pretty clean system, no overclocking, and keep 'crazy' setups to the virtual machines. I do IT work, and enjoy a stable system.

Can I say it was due to the driver update? No, not for sure. Because rolling back didn't fix it. It was also patch Tuesday week, so there were Windows system updates too.
I run a built system: ASUS motherboard, i7 7700K, RTX 2080 graphics card, no overclocking on motherboard/processor/RAM/graphics.
W10 1903, all OS updates within a week of release. Driver updates usually wait for a month at least. (and sometimes skip a few)

TLDR: The BOINC screensaver may be the problem for you too, disable it and see.

I always turn off screensavers and just have the monitor turn off. Drawing pretty pictures on the screen takes resources when they could be spent crunching even if it's a small amount of resources.

I always turn off screensavers and just have the monitor turn off. Drawing pretty pictures on the screen takes resources when they could be spent crunching even if it's a small amount of resources.

+1.

I'd be interested to know if blank screen saver is taking more resources, than just to turn off the monitor after eg: 2 minutes or so....

Blanking the screen SHOULD take very little in the way of resources, but.....