Issues encountered with FahCore_22 on Windows 10 64-bit (Folding@Home)
Issues encountered with FahCore_22 on Windows 10 64-bit (Folding@Home)
Playing with the registry isn't advisable unless you're certain about what you're doing. A complete Windows reinstall seems like a safer choice. Are you monitoring the temperatures? Overheating can happen when folding, particularly with dual GPUs. I don't know if this is connected to your problems.
I restored the registry settings to their original state but am leaning toward a fresh Windows install. Regarding thermals, the 2060 remains around 85°C, matching the limit I set in Afterburner. I plan to try a new installation tomorrow and see the impact. Update: I performed an in-place reinstall using the media creator earlier, which ended in another crash. I also recalled something about bad work units—could this be related or cause different issues?
Another crash occurred, returning to error 702 linked to GPU task timeouts. It seems the system expects a driver restart prompt, but it doesn’t appear to trigger. Consider checking GPU settings or updating drivers to resolve this issue.
You probably boosted your GPU settings, particularly with MSI Afterburner. Adjust both the GPU core and memory clock to zero and try again. The Nvidia utility will automatically overclock the card, but exceeding these defaults may lead to instability in your simulation tools.
GPU hasn't been manually overclocked, though it might have factory settings. I attempted to reduce the core clock by 25mhz, but it didn't affect performance. Since I'm not very experienced with overclocking, I'm unsure if 25mhz would make a difference or if I should try going lower.
After testing various options, it appears the issue is resolved when using the secondary GPU. The fault on the 1060 might not be affecting stability, though it's unclear how a problem there could influence the main card. This seems to work well—no crashes reported in about six hours, with no incidents since switching off the secondary GPU two days ago. Still unsure of the exact cause, but I’m marking this as a solution.