I just found that I've been having issues with Windows and BOINC and now have had to totally take it off of like 5 of my PC. Here is the issues.

I have all my PC in the Windows 10 x64 Preview builds which means I get new Windows builds just about every week.

I have BOINC start up on all of them with (Setiathome) and have had them doing this for years without issue.

Now what happens is within a few minutes of entering Windows and this only started happening within the last 4 or so Preview builds of Windows.

The systems will get a Green Screen or BSOD with Video_Scheduler_Internal error (Nvidia GPU systems) and today on another I got Thread_Stuck_In_Device_Driver (AMD GPU). Now all these systems are AMD Processors of varying types, all have Windows Previews enabled, and had the last version of BOINC or the latest version of BOINC running.

Now on my latest PC which is a Ryzen 1800x system, it would also get during POST upon (Only) receiving the Video BSOD in Windows an Overtemp error F1 prompt on bootup.

So the only thing I can surmise is that it's overheating the processors on all of these systems which in Windows just reports some type of error since it doesn't have an error for Overheating specifically.

Something has changed in Windows that is now causing the processors to not idle or to max out and overheat is my guess. If I disable BOINC from running on all of these systems they all run perfectly fine and I can also even run stress tests on them with CPU-Z which too maxes out the processor, but I receive no errors what so ever.

I have also kept and eye on the temps and with BOINC running the temps climb to about 80C then the errors are produced, but with CPU-Z I've had the temps go well over 100C and they never produced any Windows errors.

Something strange has happened within the last few preview builds and with the combination of BOINC it's now crashing all of these systems.

Is anyone else seeing anything similar? If so, how have you fixed it besides disabling or removing BOINC?

If you look through the "number crunching" forum over on SETI you will find a number of threads talking about similar problems to yourself. From what I can gather it a whole host of different issues, all outside SETI & BOINC's control and MS just keep applying more and more sticking plasters to cover up the real underlying ones (whatever they may be).

One of the biggest groups of problems appear to be caused by MS making it very difficult to turn off the driver updates, and "insist" on updating perfectly working drivers with their reduced functionality versions.

I have all my PC in the Windows 10 x64 Preview builds which means I get new Windows builds just about every week.

So essentially you are beta testing Windows 10 versions and expecting them to be as stable as the release versions?

A public beta program for Windows 10 known as the Windows Insider Program (previously Windows Technical Preview) began with the first publicly available preview release on October 1, 2014. Insider preview builds are aimed towards enthusiasts and enterprise users for the testing and evaluation of updates and new features.

In other words, don't expect these to be stable enough. They'll contain all the kinds of pre-alpha, alpha and beta crap they can cram into it and ask you to see if that runs stable on your computer(s). In your case it doesn't, so you'll have to report that to Microsoft.

I have also kept and eye on the temps and with BOINC running the temps climb to about 80C then the errors are produced, but with CPU-Z I've had the temps go well over 100C and they never produced any Windows errors.

I must say, when I see something run at 80-100C, I'd turn it off and go find a better cooler for it. But apparently the 1800x has a +20C offset against the actual temperature. Still means you run 60 to 80C.

---

Could you list the motherboard + cpu + gpu combinations your hosts have, please? It would be interesting to see what kind of hardware the problems hit. I've been running every Fast Ring build there has been so far (currently build 16294). I've never had problems running BOINC on these hosts, if the installation of a new build was succesfull at first. I've got both AMD and Nvidia GPUs... but Intel CPUs only (about 7 years old platforms).

* I suggest checking if the uefi/bios on your motherboards are the newest version. I believe that to be extremely important with new technology like Ryzen.

Here are the systems with BOINC\SETI and Windows 10 x64 Preview issues. All currently on 16296.

Asus Crosshair VI Hero - latest BIOS and Drivers
Ryzen 1800x
PNY Nvidia 1080 GTX Ti
Corsair AIO Water Cooler
Gskill Trident Z 64 Gig RAM

Asus Crosshair IV Formula - latest BIOS and Drivers
AMD Phenom II X6 1090T
PNY Verto Nvidia Geforce GTX 780
Gskill 16 Gig DDR3-1600/PC312800

One is a Laptop with Nvidia 200M HP Pavilion DV8 - these 3 systems since all being Nvidia received the Video Stop error then reboot.

The other two are identical - These have received different error - Thread Stop error then reboot.
Asus A88X Pro
AMD A10-7850 APU - Built in Radeon 7 Video
32 Gig RAM

The only reason I point to Overtemp is because only one of the systems actually states that during POST which is the top one. All systems act exactly the same (BSOD or Green Screen) then reboot with BOINC\SETI running. No issues when not running, and gaming, and even doing serious crunching either with CPU-Z or with map making with Rising Storm 2 - Vietnam SDK.

Thanks for the info I'll check out the other posts on SETI. None of this has ever happened with any of the systems until the last 4 or so Previews. That's when this all started. Yes I'm quite aware of Windows Previews being BETA and this is what I do for a living. I'm also aware of the Ryzen +20C. I've only posted here and to all the other sites that were a commonality of the issue. All systems upon each reboot have reported these findings back to Microsoft as well.

I'm thinking that upon the release of the Windows Fall Update this is going to be a common theme if in fact it's Windows as the main culprit, but a shame for BONIC because folks will only have one course of action and that's un-installing or disabling.