Folding@home windows client crash after a while (couple hours).

[talregev]

I try your folding@home program on windows 10 64 bit with latest client v7.5.1(32bit). There isn't 64bit version folding@home for windows. The client crash every couple hours. (Didn't run at least one day). Computer run normal. The client even finish some of the tasks, but I understand I don't want to open the client every time. I switch back to boinc on my pc.

[PantherX]

Can you please jump over to https://foldingforum.org/index.php where you can create a topic and we can investigate this further for you? For posting log files, please see this thread: https://foldingforum.org/viewtopic.php?f=2&t=26036

I am closing this issue now pending further analysis in the Forum :)

[talregev]

Let me continue to give you more info here. I can post a log files here. @PantherX It more easy for me to stay here.

[PantherX]

Okay, common causes of crashes would be PSU related, temperature related, overclocking related. Have you checked them?

[talregev]

My computer don't crash. and Boinc it working just fine (with other computation). So my guess that it not my computer. but i didn't check these parameters. Where the logs of folding@home is located? I want to publish it here.

[PantherX]

Here's the topic with more details: https://foldingforum.org/viewtopic.php?f=24&t=26036

[talregev]

log.txt

log-20200406-190702.txt log-20200407-044522.txt log-20200407-050231.txt log-20200407-051244.txt log-20200407-172116.txt log-20200408-042903.txt log-20200408-112233.txt log-20200408-175417.txt log-20200409-065414.txt GPUs.txt logfile_01.txt

config - Copy.xml.txt md.log science.log

[talregev]

@PantherX I hope it help to solve the crashes. Can you open this issue for all other people?

[PantherX]

The GPU is not supported since it doesn't have Double Precision support. Thus, I would remove it.

You have installed the application in a "portable apps" folder and I am not sure why that is but it should treat is as a custom location and carry on without issues.

In your logs, I noticed that you're running on a laptop. It is likely that you're laptop might be insufficient;y cool hence, causing the crash. What temperatures are your CPU at? Do note that folding uses AVX instructions which generates significantly more heat than non AVX instructions. Please note that just because your system can crunch BONIC, doesn't mean that it can fold WUs.

Unfortunately, I can't open the issue here since this isn't a known/confirmed bug. We are still troubleshooting which would happen at the F@H Forum.

[talregev]

ok. thanks.

[talregev]

You don't support laptop? Most of of your device will be old ones. Would you consider to support old computers?

[PantherX]

As long as you have a supported CPU/GPU, you can still fold regardless of if it is a laptop, desktop, workstation, server or anything in between.

The limitations for CPU is SSE or AVX (IIRC) The limitations for GPU is OpenCL 1.2 and Double Precision

[talregev]

My cpu is supported?

[talregev]

It is likely that you're laptop might be insufficient;y cool hence, causing the crash

My laptop don't crash. If it insufficient cool, the computer will shut down. and it not the case.

[talregev]

I can't open the issue here since this isn't a known/confirmed bug

This is the point to open this issue. that other users will see it, and report it here and give there a log. I know that another person had the same symptoms like me, and I ask him to report. I don't know if he did it. So I ask you again, please open this issue, that other users can see and give you more information that you seek. If the issue is open it didn't mean it a confirm bug. We investigating.

[talregev]

Other user report:

[PantherX]

Your CPU is supported: CPU: Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz

Okay, I can open this issue and hopefully, the community can provide more information so that the developers can reproduce it reliably

[talregev]

Thank you!

[shorttack]

@talregev As of Friday last, a new client version was posted, the first in two years. You are running on the old code. So, I ask you to test on the new stable version and see if you get identical errors to what you reported. Latest version is at: https://foldingathome.org/beta/

[talregev]

I already switched to boinc. When I will have another old computer I will try that. Thanks.

[talregev]

@shorttack I switch to 7.6.9 it has the same issue: log.txt logfile_01.txt md.log science.log

[PantherX]

@talregev Does this happen with V7.6.13 too?

[talregev]

I didn't try. I think it connected to the binary that you download and run FahCore_a7.exe. Did you update that binary? If yes, I am willing to try again.

[PantherX]

There hasn't been a new FahCore_a7 release. The new releases has some Windows fixes so was hoping that your issue would be resolved in that.

[talregev]

This issue is on FahCore_a7.exe Like the log suggest. The GUI iteslf is working great.

[PantherX]

In the most recent log file (April 25), there's no error message, the WU was folding and then the percentages just stopped. Did you see any error pop-up on the screen? Also, I noticed that you're using a portable version which AFAIK, isn't from the official source. Is there a reason to do so? What would happen if you tried the installer from here (https://foldingathome.org/alternative-downloads/)?

[talregev]

It just crash without error msgs. As I say before, I will not check again without change in FahCore_a7.exe These days this link: https://foldingathome.org/alternative-downloads/ and this link: https://foldingathome.org/start-folding/ are the same version of folding home.

[PantherX]

I saw that you had this: CWD: C:\PortableAppsMenu\PortableApps\FoldingAtHomePortable\Data\FAHData which is different when you use the installers from there: CWD: C:\Users\PantherX-H\AppData\Roaming\FAHClient

Nonetheless, will keep an eye out to see if there are any changes and will update this :)

[talregev]

I was using the portableapps.com version. I also checked In the regular version. Same happened.

[PantherX]

Okay, thanks for that. We will see what we can do about that.