App version wants Nvidia? Now using AMD rx470

Do a project reset to clear out any no longer needed Einstein related guff... The message is likely erroneous, Boinc probably thinks you still have a NVidia card hiding somewhere, especially if you didn't fully uninstall the NV drivers before swapping cards.
Whatever AMD work you have in your cache now will be re-sent, theres nothing to lose doing this :-)

Gav.

Even though this issue is resolved, I thought I would add some comments so that anybody else who happens to browse this thread will be a little less concerned by the "missing GPU" messages.

Ideally, if a GPU change is planned, the work cache settings should be reduced right down ahead of time so that if something goes wrong, very few tasks will be lost.  Then, if NNT (no new tasks) is set at the appropriate time before the changeover, perhaps there will be no affected tasks left.  Before shutting down to change the hardware, abort AND report any remaining tasks that rely on the particular item being removed - in this case just NVIDIA GPU tasks.  There is no reason to be concerned about CPU tasks as they wont be adversely affected by a GPU change.  To prevent any issues while installing new drivers, BOINC should be set NOT to restart when the machine is rebooted.

After the change with the new hardware in place and new drivers correctly working, it's time to fire up BOINC.  The event log posted earlier is exactly what you should see if things are working correctly.  The particular entry you want to see is the one showing that the new GPU is correctly recognised along with the OpenCL capability.  You look for both those bits in the message.

Of course there will be an informational message about the fact that there is no longer an NVIDIA GPU.  It's not an error message, it's just information that shows that BOINC has recognised the change.  Notice there are three messages.  That simply means there were three separate entries for different app versions that relied on the NVIDIA GPU.  That's not surprising because there have been a number of versions (including beta versions) in recent times.  If you browse BOINC's state file (client_state.xml) you will probably find literally dozens of <app_version> .... </app_version> blocks in there which refer to all the previous versions of all the different apps that have been used on the machine.  This is no big deal.

The information about the missing GPU is given only at startup.  Once the client talks to the server and informs about the new GPU, appropriate new tasks should immediately be sent for it.  The CPU tasks should simply restart where they left off at the time of the shutdown.  I know this because I have changed several machines recently to a different brand of GPU and not had any issues with either CPU or GPU tasks.

I suspect (but don't know for sure) that you will see the missing GPU information each time BOINC is restarted.  It may be that the exchanges between client and server may eventually get rid of the message.  I don't know because I've never given it a chance to go that far.  Before restarting BOINC after a GPU change, I simply edit the state file to remove any <app_version> blocks that refer to the former GPU, seeing as they are definitely not needed anymore.  I'm not encouraging anyone else to do this as there are always risks in tampering with things you don't fully understand.  I'd be interested in knowing if anybody has seen whether or not you keep getting the message each time BOINC is restarted even after the new hardware has well and truly settled in.  I'll check myself next time I change a GPU.

The final point I'd like to make is that whilst a project 'reset' can cure many ills, it is often a 'sledgehammer to crack a peanut' and it does come with some consequences.   If you have to do a reset, you will trash everything, including all the CPU tasks that should have been quite OK.  You will lose all currently downloaded files, like apps, large data files, associated static files, templates, etc.  Everything will need to be downloaded afresh.  For many, this may be relatively insignificant in the overall scheme of things but for people on slow links with restrictive quotas it may be an issue.