I have been contributing with this machine for several months and suddenly this weekend I started getting messages saying that fahcore_17.exe has stopped working. I tried looking up the problem but have not found anything useful. All but one of the problems that I found related to people who had just changed/upgraded the GPU in their computer = which is not my situation. The other case I found said it might be a bad WU download, but I have dropped the work unit using instructions I found elsewhere on the forum, but still no luck.
Here is the last log I have collected:
---------------------------------------------------------
Did you upgrade your driver recently? What GPU are you running?
F@h is now the top computing platform on the planet and nothing unites people like a dedicated fight against a common enemy. This virus affects all of us. Lets end it together.
If you are absolutely 100% sure that nothing has changed, can you please look through the log file and see if the first time you encountered this error was when you downloaded FahCore_17 version 0.0.52? If you only encountered this issue with FahCore_17 version 0.0.52 and not with the previous versions, you can try the deleting the FahCore_17 so that it will force downloading a new one. If that too failed, it could be possible that a bug went undetected during the testing so will have to inform the developer about this.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
It would make sense that it happened when the new core downloaded. In any case, I deleted the fahcore_17 exe as you suggested and let it download a new copy and I am getting the same result. How/what do I need to do to report this to the developers?
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Is it possible that you check the previous logs present in C:\Users\mporter\AppData\Roaming\FAHClient\logs to verify that the issue only appeared once the new version was downloaded. Please note that the previous version will not have any version number which is how you can differentiate between the two versions. Also, by chance, did Windows Update install any updates which may have caused this issue? Can you check the Events Manager to see if there are any Windows related error which might be triggering this error?
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
I can confirm the same behaviour starting immediately after the core 17 .52 upgrade. Two gtx 465's for me, fixed on one system by deleting the client-type advanced parameter, thereby reverting to Core 15's (temp solution only I realize) and on the other by outright reverting to the earlier Core 17.