Problems with F@H after GPU change

[trustdark]

Hi, i faced with such problem:
I have replaced AMD RX570 with new RTX 2060. Also, there is GTX1060 in another slot. Then i uninstalled AMD drivers and cleaned Windows 7 via DDU.Installed new NVIDIA drivers. Reinstalled F@H. And got such error:
06:29:31:ERROR:WU02:FS01:Failed to start core: OpenCL device matching slot 1 not found, try setting 'opencl-index' manually
06:29:35:ERROR:WU04:FS02:Failed to start core: OpenCL device matching slot 2 not found, try setting 'opencl-index' manuall

If i change value "-1" to "1" in "Configure" - "Slots"- "opencl-index" for one GPU i get this:
06:36:12:WU02:FS01:0x21:ERROR:126: Bad platformId size.
06:36:12:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
06:36:29:WU01:FS01:0x21:ERROR:126: Bad platformId size.
06:36:29:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
06:36:39:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)

Can smbd help me?
Before replacing AMD card everything works fine.

[foldy]

There maybe are some registry values leftover vor OpenCL which conflict with the nvidia OpenCL.

Nvidia says it should be enough to edit the khronos registry keys.

HKLM\SOFTWARE\Khronos\OpenCL\Vendors (for 64-bit applications)
or
HKLM\SOFTWARE\Wow6432Node\Khronos\OpenCL\Vendors (for 32-bit applications)

These registry keys should contain one REG_DWORD value for each OpenCL platform. If you change the REG_DWORD value for a platform from 0 to 1 then that platform will no longer enumerate. The nice thing about this method is that if you change your mind, you can re-enable the platform by simply changing the value from 1 back to 0.

[JimboPalmer]

I bet that if you uninstall the F@H client including deleting data, then re install. The installation will find the right slots.

[trustdark]

I bet that if you uninstall the F@H client including deleting data, then re install. The installation will find the right slots.

Did it already, forgot to mention it.

[bruce]

Did it already, forgot to mention it.

But you have not posted the first two pages of FAH's log where FAHClient initializes itself after changing the setup. It describes FAH's perception of your system and that really helps us with many issues like this one.

[trustdark]

Did it already, forgot to mention it.

But you have not posted the first two pages of FAH's log where FAHClient initializes itself after changing the setup. It describes FAH's perception of your system and that really helps us with many issues like this one.

Sorry, i read about first 100 strings after posting(

[toTOW]

Clean everything (mostly AMD OpenCL Platform) from previous installations (or other OpenCL platforms like Intel) with AMD Cleanup Utility : https://www.amd.com/fr/support/kb/faq/gpu-601

A reboot is welcome here.

Then download NV drivers from NV website and install them.

Another reboot is welcome here ...

FAH should work fine after.

[trustdark]

There maybe are some registry values leftover vor OpenCL which conflict with the nvidia OpenCL.

Nvidia says it should be enough to edit the khronos registry keys.

HKLM\SOFTWARE\Khronos\OpenCL\Vendors (for 64-bit applications)
or
HKLM\SOFTWARE\Wow6432Node\Khronos\OpenCL\Vendors (for 32-bit applications)

These registry keys should contain one REG_DWORD value for each OpenCL platform. If you change the REG_DWORD value for a platform from 0 to 1 then that platform will no longer enumerate. The nice thing about this method is that if you change your mind, you can re-enable the platform by simply changing the value from 1 back to 0.

I didn't find such subdirectories as OpenCL. I have Vulkan inside Khronos dir.
I removed Nvidia drivers via DDU and installed it again, and it helped. ¯\_(ツ)_/¯
Thanks.

[trustdark]

Thanks all for help