I have a vanilla Dell All-in-One 8 core desktop running Windows 10.

Recently, I started getting a Blue Screen of Death - stop code is Memory Management

I added Science United recently. Currently have several SU projects running. Never got BSOD before SU projects started running.

I have been exiting from BOINC to prevent the BSOD, and BSOD stopped. If I run BOINC, BSOD happens withing a couple of hours, or less time.

Are there specific projects that are known to be less well written than the ones I originally had (Seti, Einstein, Milkyway, Cosmology, Universe, LHC). These 6 projects never gave me any problems.

---

I don't know of any, but this post could be the start of a useful exchange of knowledge and investigation.

Despite being attached via Science United, you will be running a normal, unchanged, BOINC client and BOINC Manager. You have full access to all the science project data that you had before.

Could you please post here the names of all the projects that Science United has currently attached you to? You could either gather that from BOINC Manager (advanced view, projects tab), or from the Event Log immediately after startup. By comparing the 'before' list that you have already posted, with the 'after' list attached by Science United, we can ask the community to start the process of elimination.

Also worth running memtest to see if it shows up any problems. Some projects stress the memory of a machine much more than others and if memory is really being stressed, it might show up a problem that normally isn't visisble.

Although bad memory isn't usually the case. I've had systems that threw bad memory codes - by just running Windows, not even stress it out - and upon returning the memory and getting new, I had the exact same trouble. For me it disappeared when I changed the motherboard (which was tested by the manufacturer and deemed not broken). Memory troubles are very notorious to figure out, as Windows will just throw one because memory is addressed outside of a scope it likes. Or because any application that runs is using memory and there's no specific code for whatever happened there, so the nearest error is used, which is memory.

---

Since the original poster mentioned that they are running an "all in one" Dell PC, it also can't be discounted that a memory error could actually be a THERMAL or OVER HEATING issue caused by a project app that is running extremely intensive computations.

All in one computers tend to run hotter than a standard desktop computer and may not have adequate cooling / ventilation.

Since the original poster mentioned that they are running an "all in one" Dell PC, it also can't be discounted that a memory error could actually be a THERMAL or OVER HEATING issue caused by a project app that is running extremely intensive computations.

All in one computers tend to run hotter than a standard desktop computer and may not have adequate cooling / ventilation.

Agreed. I think it most likely a hardware issue and that we will find the project that is causing it is the one that stresses the system the most.

OP again

SU projects are Amicable Numbers, Citizen Science Grid, NFS@home, PrimeGrid

Fan does run a lot with BOINC running. I also had 11 projects active, which just might be too much.

I'm culling some of the SU projects to reduce the stress on hardware

BOINC will run (as a simplified generality) one task per 'device' - a device being a single core of a (nowadays) muilti-core CPU, a discrete GPU, or an integrated GPU within a CPU package. It doesn't matter how many projects you have available to pick from - simply having more projects won't increase the number of active tasks.

Amicable Numbers and PrimeGrid will both stress the CPU and GPU to the maximum; NFS@home is CPU only and also will Max out the CPU... They will also put extreme stress the other parts of your computer especially the power supply.

Citizen Science Grid has not been sending work for over a year or so.