Crashes Windows 10 x64

Since nobody is able to see what you see, it would be helpful if you could list the various things you have done and what has shown on your screen as a result.  As well as listing error messages, etc., you should include things like any preference changes you have made and which particular searches you have selected to run.

It would be helpful to know exactly what caused you to reach this determination.  I had a look at the list of tasks assigned to your computer.  There is only one task currently showing, issued on 15th Feb.  On 12th March, your computer contacted the project and at that point, since the task hadn't even been started, the scheduler immediately canceled it.

I decided to see what the scheduler recorded as a result of that 12th March contact.  You can easily do this for yourself.  There is a full set of instructions for accessing scheduler (server) logs listed in a pinned thread in the 'Getting Started' forum.  To save time, here is a direct link to that log entry.  Whilst the full log is rather daunting, here are some key points.

There are 6 examples of the message, "... setting outcome ERROR".  One of the 6 relates to the currently still showing task (see first link above) that was canceled by not being started before the deadline.  So the message here is that your computer didn't even try to start to process that task.  My guess is that all six were probably in the same condition and that 5 have subsequently been removed from the online database after being reprocessed by other computers.  This will also happen to the last one shortly, when its quorum is finally completed.  If you click on the WU ID link for that one remaining task, you will see the other computers involved and that there is (at the time of writing) still one outstanding task yet to be returned.  So this quorum should hang around for a couple more days at least before being removed.

Of greater concern are the 52 examples of the message "... can't find result".  When your computer makes contact with the project's scheduler, it sends a full list of all the tasks, data, apps, etc., that are present on your computer and the scheduler checks that list against its own records.  It would appear that, outside of the normal BOINC procedures for aborting/returning tasks, you have somehow intervened and caused the BOINC client to lose track of 52 tasks.  Perhaps you might remember taking some action that caused that to happen?  Even if tasks crash and burn, the client will return the debris and there will be information about what went wrong.  If you just delete stuff, there will be no information about the cause of the problem.

The 52 missing tasks belong to either the FGRPB1G search or the BRP4 (Arecibo) search.  Both of these are GPU searches.  Whilst the FGRPB1G search isn't really suited to Intel GPUs, the BRP4 search should work, provided that you had taken care to choose a suitable driver.  Past experience suggests that there are many driver versions that cause results not to be valid within the required accuracy.  Because no results, valid or otherwise, currently exist, it's impossible to say if selecting just the BRP4 search might work for you.

If you really wish to process GPU tasks, trying to use an Intel GPU might be quite a restriction.  If your computer has an available PCIe x16 slot, upgrading with a cheap discrete GPU might be a relatively simple exercise.  There are models that don't even require an external PCIe power connector that could work well and be very productive.  I'm sure there would be plenty of people willing to give advice on something suitable.

There was no evidence in the scheduler log of any CPU tasks.  Have you tried running CPU tasks?  Your computer should have no problem with those.  If you decide to use your CPU, you should select one only of the two available CPU searches, the FGRP5 search for Gamma-ray pulsars or the O2MD search for gravitational waves (GW), using a small work cache size until you see how things progress.  Whilst the GW search is of the highest scientific interest to the project, the data download requirements are much larger and might cause issues for volunteers with a limited internet connection.