13421 gets to 100% then crashes

Moderators: Site Moderators, FAHC Science Team

createcoms
Posts: 12
Joined: Sat Mar 21, 2020 10:22 pm

13421 gets to 100% then crashes

Post by createcoms »

Have seen this happen several times but not every time and it seems to be specific to 13421 (prior WUs completed fine without issue, and anything different in between 13421 is completing fine).

Log extract:

08:20:19:WU00:FS01:0x22:Completed 1000000 out of 1000000 steps (100%)
08:20:19:WU00:FS01:0x22:Average performance: 144.24 ns/day
08:20:19:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
08:20:19:WU00:FS01:0x22:Saving result file checkpointState.xml.bz2
08:20:19:WU00:FS01:0x22:Saving result file globals.csv
08:20:19:WU00:FS01:0x22:Saving result file positions.xtc
08:20:19:WU00:FS01:0x22:Saving result file science.log
08:20:19:WU00:FS01:0x22:Folding@home Core Shutdown: FINISHED_UNIT
08:20:21:WARNING:WU00:FS01:FahCore returned an unknown error code which probably indicates that it crashed
08:20:21:WARNING:WU00:FS01:FahCore returned: UNKNOWN_ENUM (-1073740940 = 0xc0000374)
createcoms
Posts: 12
Joined: Sat Mar 21, 2020 10:22 pm

Re: 13421 gets to 100% then crashes

Post by createcoms »

Full logfile_01.txt (with user directory censored)

Code: Select all

*********************** Log Started 2020-08-02T04:13:59Z ***********************
*************************** Core22 Folding@home Core ***************************
       Core: Core22
       Type: 0x22
    Version: 0.0.11
     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
  Copyright: 2020 foldingathome.org
   Homepage: https://foldingathome.org/
       Date: Jun 26 2020
       Time: 19:49:16
   Revision: 22010df8a4db48db1b35d33e666b64d8ce48689d
     Branch: core22-0.0.11
   Compiler: Visual C++ 2015
    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
   Platform: win32 10
       Bits: 64
       Mode: Release
Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
             <peastman@stanford.edu>
       Args: -dir 00 -suffix 01 -version 706 -lifeline 13732 -checkpoint 15
             -gpu-vendor amd -opencl-platform 0 -opencl-device 0 -gpu 0
************************************ libFAH ************************************
       Date: Jun 26 2020
       Time: 19:47:12
   Revision: 2b383f4f04f38511dff592885d7c0400e72bdf43
     Branch: HEAD
   Compiler: Visual C++ 2015
    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
   Platform: win32 10
       Bits: 64
       Mode: Release
************************************ CBang *************************************
       Date: Jun 26 2020
       Time: 19:46:11
   Revision: f8529962055b0e7bde23e429f5072ff758089dee
     Branch: master
   Compiler: Visual C++ 2015
    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
   Platform: win32 10
       Bits: 64
       Mode: Release
************************************ System ************************************
        CPU: AMD Ryzen 7 1700 Eight-Core Processor
     CPU ID: AuthenticAMD Family 23 Model 1 Stepping 1
       CPUs: 16
     Memory: 63.94GiB
Free Memory: 39.11GiB
    Threads: WINDOWS_THREADS
 OS Version: 6.2
Has Battery: false
 On Battery: false
 UTC Offset: 9
        PID: 15552
        CWD: C:\Users\CENSORED\AppData\Roaming\FAHClient\work
********************************************************************************
Project: 13421 (Run 1796, Clone 59, Gen 0)
Unit: 0x0000000012bc7d9a5f1f4d097afd46b5
Digital signatures verified
Folding@home GPU Core22 Folding@home Core
Version 0.0.11
  Checkpoint write interval: 50000 steps (5%) [20 total]
  JSON viewer frame write interval: 10000 steps (1%) [100 total]
  XTC frame write interval: 250000 steps (25%) [4 total]
  Global context and integrator variables write interval: 25000 steps (2.5%) [40 total]
Completed 0 out of 1000000 steps (0%)
Completed 10000 out of 1000000 steps (1%)
Completed 20000 out of 1000000 steps (2%)
Completed 30000 out of 1000000 steps (3%)
Completed 40000 out of 1000000 steps (4%)
Completed 50000 out of 1000000 steps (5%)
Completed 60000 out of 1000000 steps (6%)
Completed 70000 out of 1000000 steps (7%)
Completed 80000 out of 1000000 steps (8%)
Completed 90000 out of 1000000 steps (9%)
Completed 100000 out of 1000000 steps (10%)
Completed 110000 out of 1000000 steps (11%)
Completed 120000 out of 1000000 steps (12%)
Completed 130000 out of 1000000 steps (13%)
Completed 140000 out of 1000000 steps (14%)
Completed 150000 out of 1000000 steps (15%)
Completed 160000 out of 1000000 steps (16%)
Completed 170000 out of 1000000 steps (17%)
Completed 180000 out of 1000000 steps (18%)
Completed 190000 out of 1000000 steps (19%)
Completed 200000 out of 1000000 steps (20%)
Completed 210000 out of 1000000 steps (21%)
Completed 220000 out of 1000000 steps (22%)
Completed 230000 out of 1000000 steps (23%)
Completed 240000 out of 1000000 steps (24%)
Completed 250000 out of 1000000 steps (25%)
Completed 260000 out of 1000000 steps (26%)
Completed 270000 out of 1000000 steps (27%)
Completed 280000 out of 1000000 steps (28%)
Completed 290000 out of 1000000 steps (29%)
Completed 300000 out of 1000000 steps (30%)
Completed 310000 out of 1000000 steps (31%)
Completed 320000 out of 1000000 steps (32%)
Completed 330000 out of 1000000 steps (33%)
Completed 340000 out of 1000000 steps (34%)
Completed 350000 out of 1000000 steps (35%)
Completed 360000 out of 1000000 steps (36%)
Completed 370000 out of 1000000 steps (37%)
Completed 380000 out of 1000000 steps (38%)
Completed 390000 out of 1000000 steps (39%)
Completed 400000 out of 1000000 steps (40%)
Completed 410000 out of 1000000 steps (41%)
Completed 420000 out of 1000000 steps (42%)
Completed 430000 out of 1000000 steps (43%)
Completed 440000 out of 1000000 steps (44%)
Completed 450000 out of 1000000 steps (45%)
Completed 460000 out of 1000000 steps (46%)
Completed 470000 out of 1000000 steps (47%)
Completed 480000 out of 1000000 steps (48%)
Completed 490000 out of 1000000 steps (49%)
Completed 500000 out of 1000000 steps (50%)
Completed 510000 out of 1000000 steps (51%)
Completed 520000 out of 1000000 steps (52%)
Completed 530000 out of 1000000 steps (53%)
Completed 540000 out of 1000000 steps (54%)
Completed 550000 out of 1000000 steps (55%)
Completed 560000 out of 1000000 steps (56%)
Completed 570000 out of 1000000 steps (57%)
Completed 580000 out of 1000000 steps (58%)
Completed 590000 out of 1000000 steps (59%)
Completed 600000 out of 1000000 steps (60%)
Completed 610000 out of 1000000 steps (61%)
Completed 620000 out of 1000000 steps (62%)
Completed 630000 out of 1000000 steps (63%)
Completed 640000 out of 1000000 steps (64%)
Completed 650000 out of 1000000 steps (65%)
Completed 660000 out of 1000000 steps (66%)
Completed 670000 out of 1000000 steps (67%)
Completed 680000 out of 1000000 steps (68%)
Completed 690000 out of 1000000 steps (69%)
Completed 700000 out of 1000000 steps (70%)
Completed 710000 out of 1000000 steps (71%)
Completed 720000 out of 1000000 steps (72%)
Completed 730000 out of 1000000 steps (73%)
Completed 740000 out of 1000000 steps (74%)
Completed 750000 out of 1000000 steps (75%)
Completed 760000 out of 1000000 steps (76%)
Completed 770000 out of 1000000 steps (77%)
Completed 780000 out of 1000000 steps (78%)
Completed 790000 out of 1000000 steps (79%)
Completed 800000 out of 1000000 steps (80%)
Completed 810000 out of 1000000 steps (81%)
Completed 820000 out of 1000000 steps (82%)
Completed 830000 out of 1000000 steps (83%)
Completed 840000 out of 1000000 steps (84%)
Completed 850000 out of 1000000 steps (85%)
Completed 860000 out of 1000000 steps (86%)
Completed 870000 out of 1000000 steps (87%)
Completed 880000 out of 1000000 steps (88%)
Completed 890000 out of 1000000 steps (89%)
Completed 900000 out of 1000000 steps (90%)
Completed 910000 out of 1000000 steps (91%)
Completed 920000 out of 1000000 steps (92%)
Completed 930000 out of 1000000 steps (93%)
Completed 940000 out of 1000000 steps (94%)
Completed 950000 out of 1000000 steps (95%)
Completed 960000 out of 1000000 steps (96%)
Completed 970000 out of 1000000 steps (97%)
Completed 980000 out of 1000000 steps (98%)
Completed 990000 out of 1000000 steps (99%)
Completed 1000000 out of 1000000 steps (100%)
Average performance: 144.24 ns/day
Saving result file ..\logfile_01.txt
Saving result file checkpointState.xml.bz2
Saving result file globals.csv
Saving result file positions.xtc
Saving result file science.log
Folding@home Core Shutdown: FINISHED_UNIT
createcoms
Posts: 12
Joined: Sat Mar 21, 2020 10:22 pm

Re: 13421 gets to 100% then crashes

Post by createcoms »

I find it curious that an entry remains in the work queue at 100% Previously the only way to clear this was shutdown FAH fully.

Image
anonymous image post
Joe_H
Site Admin
Posts: 7856
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: 13421 gets to 100% then crashes

Post by Joe_H »

At the point at which it crashed, the folding slot had not finished packing up the WU to send it in. There have been a number of reports of this error code in connection with Project 134nn WUs. The client will usually reprocess the WU from the last checkpoint, or possibly from the very beginning after the WU that was downloaded and started finishes.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
mwroggenbuck
Posts: 127
Joined: Tue Mar 24, 2020 12:47 pm

Re: 13421 gets to 100% then crashes

Post by mwroggenbuck »

What is your GPU hardware? I have AMD RX 570 and have seen this issue.
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 13421 gets to 100% then crashes

Post by bruce »

The bug-fixing folks have been studying this failure and they seem to have reduced it's frequency but have not found a full fix.

My current theory points to a too-small setting if the upper limit of the paging file. Change it to unlimited and see if it helps.
mwroggenbuck
Posts: 127
Joined: Tue Mar 24, 2020 12:47 pm

Re: 13421 gets to 100% then crashes

Post by mwroggenbuck »

Bruce,

My page file is managed by the system, and is currently a little less that 5 GB. This is on top of 32 GB of physical memory. Do you think that I would need to resize anything? If yes, what do you suggest (I don't see an unlimited option in windows--only system managed).
mwroggenbuck
Posts: 127
Joined: Tue Mar 24, 2020 12:47 pm

Re: 13421 gets to 100% then crashes

Post by mwroggenbuck »

A little more information for Bruce:

I brought up the process monitor for core 22. Memory usage seems to be stable. The virtual bytes peak is ~9GB. While this is bigger than the page file, it easily fits into 32 GB of ram. The page file peak for the process is only ~190MB.

Don't know if this helps, but I though I would pass it along. I may create a recording of the process to see what happens when it is done.
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 13421 gets to 100% then crashes

Post by bruce »

When a WU passes 100%, there's a Zip/Tar-like step that compresses the "results" data before it is uploaded. I don't know how to predict how much RAM that might need. I don't think the FAHCore is unloaded before it allocates more RAM.

In Windows, the system-managed setting allows the page file (virtual ram) to grow as needed as long as it fits on the device and then it shrinks after the upload happens.
createcoms
Posts: 12
Joined: Sat Mar 21, 2020 10:22 pm

Re: 13421 gets to 100% then crashes

Post by createcoms »

I've got 64GB of RAM on this rig and half of it's just sitting around as a flexible cache that programs can use (including FAH) whenever they please. I've never seen FAH chew up the whole lot and drive virtual memory use.
Sparkly
Posts: 73
Joined: Sun Apr 19, 2020 11:01 am

Re: 13421 gets to 100% then crashes

Post by Sparkly »

As far as I have seen this 0xc0000374 only happens on rigs (in Windows) where the CPU cores are multithreaded, so typically 4 core 8 thread, 8 core 16 thread etc., which indicate heap issues in the end process of the software and not memory issues.

A workaround is to limit each FAHCore_22 process to only be allowed to use 1 logical core when running.
mwroggenbuck
Posts: 127
Joined: Tue Mar 24, 2020 12:47 pm

Re: 13421 gets to 100% then crashes

Post by mwroggenbuck »

Unfortunately, the one thread limit does not work 100%. I have other posts on this forum about this suggestion. I ran it and still had issues. :(
Sparkly
Posts: 73
Joined: Sun Apr 19, 2020 11:01 am

Re: 13421 gets to 100% then crashes

Post by Sparkly »

mwroggenbuck wrote:Unfortunately, the one thread limit does not work 100%. I have other posts on this forum about this suggestion. I ran it and still had issues. :(
The one core workaround is for this error only 0xc0000374, so if you have other error codes then it is something else.
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 13421 gets to 100% then crashes

Post by bruce »

I'm not sure you can define "...when working" since the error happens after FAHCore_22 has passed 100%.
digiTTal
Posts: 3
Joined: Sun Jun 07, 2020 5:42 am

Re: 13421 gets to 100% then crashes

Post by digiTTal »

I did have the same issue of 3 crashing 13421 WUs at 100% on my RX 470. See attached logs for 2 of them.

Code: Select all

07:34:13:WU00:FS02:Starting
07:34:13:WU00:FS02:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\user\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.11/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 706 -lifeline 6692 -checkpoint 15 -gpu-vendor amd -opencl-platform 0 -opencl-device 0 -gpu 0
07:34:13:WU00:FS02:Started FahCore on PID 10144
07:34:13:WU00:FS02:Core PID:10168
07:34:13:WU00:FS02:FahCore 0x22 started
07:34:13:WU00:FS02:0x22:*********************** Log Started 2020-08-02T07:34:13Z ***********************
07:34:13:WU00:FS02:0x22:*************************** Core22 Folding@home Core ***************************
07:34:13:WU00:FS02:0x22:       Core: Core22
07:34:13:WU00:FS02:0x22:       Type: 0x22
07:34:13:WU00:FS02:0x22:    Version: 0.0.11
07:34:13:WU00:FS02:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
07:34:13:WU00:FS02:0x22:  Copyright: 2020 foldingathome.org
07:34:13:WU00:FS02:0x22:   Homepage: https://foldingathome.org/
07:34:13:WU00:FS02:0x22:       Date: Jun 26 2020
07:34:13:WU00:FS02:0x22:       Time: 19:49:16
07:34:13:WU00:FS02:0x22:   Revision: 22010df8a4db48db1b35d33e666b64d8ce48689d
07:34:13:WU00:FS02:0x22:     Branch: core22-0.0.11
07:34:13:WU00:FS02:0x22:   Compiler: Visual C++ 2015
07:34:13:WU00:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
07:34:13:WU00:FS02:0x22:   Platform: win32 10
07:34:13:WU00:FS02:0x22:       Bits: 64
07:34:13:WU00:FS02:0x22:       Mode: Release
07:34:13:WU00:FS02:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
07:34:13:WU00:FS02:0x22:             <peastman@stanford.edu>
07:34:13:WU00:FS02:0x22:       Args: -dir 00 -suffix 01 -version 706 -lifeline 10144 -checkpoint 15
07:34:14:WU00:FS02:0x22:             -gpu-vendor amd -opencl-platform 0 -opencl-device 0 -gpu 0
07:34:14:WU00:FS02:0x22:************************************ libFAH ************************************
07:34:14:WU00:FS02:0x22:       Date: Jun 26 2020
07:34:14:WU00:FS02:0x22:       Time: 19:47:12
07:34:14:WU00:FS02:0x22:   Revision: 2b383f4f04f38511dff592885d7c0400e72bdf43
07:34:14:WU00:FS02:0x22:     Branch: HEAD
07:34:14:WU00:FS02:0x22:   Compiler: Visual C++ 2015
07:34:14:WU00:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
07:34:14:WU00:FS02:0x22:   Platform: win32 10
07:34:14:WU00:FS02:0x22:       Bits: 64
07:34:14:WU00:FS02:0x22:       Mode: Release
07:34:14:WU00:FS02:0x22:************************************ CBang *************************************
07:34:14:WU00:FS02:0x22:       Date: Jun 26 2020
07:34:14:WU00:FS02:0x22:       Time: 19:46:11
07:34:14:WU00:FS02:0x22:   Revision: f8529962055b0e7bde23e429f5072ff758089dee
07:34:14:WU00:FS02:0x22:     Branch: master
07:34:14:WU00:FS02:0x22:   Compiler: Visual C++ 2015
07:34:14:WU00:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
07:34:14:WU00:FS02:0x22:   Platform: win32 10
07:34:14:WU00:FS02:0x22:       Bits: 64
07:34:14:WU00:FS02:0x22:       Mode: Release
07:34:14:WU00:FS02:0x22:************************************ System ************************************
07:34:14:WU00:FS02:0x22:        CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
07:34:14:WU00:FS02:0x22:     CPU ID: GenuineIntel Family 6 Model 30 Stepping 5
07:34:14:WU00:FS02:0x22:       CPUs: 4
07:34:14:WU00:FS02:0x22:     Memory: 7.99GiB
07:34:14:WU00:FS02:0x22:Free Memory: 5.06GiB
07:34:14:WU00:FS02:0x22:    Threads: WINDOWS_THREADS
07:34:14:WU00:FS02:0x22: OS Version: 6.2
07:34:14:WU00:FS02:0x22:Has Battery: false
07:34:14:WU00:FS02:0x22: On Battery: false
07:34:14:WU00:FS02:0x22: UTC Offset: 2
07:34:14:WU00:FS02:0x22:        PID: 10168
07:34:14:WU00:FS02:0x22:        CWD: C:\Users\user\AppData\Roaming\FAHClient\work
07:34:14:WU00:FS02:0x22:********************************************************************************
07:34:14:WU00:FS02:0x22:Project: 13421 (Run 6728, Clone 57, Gen 0)
07:34:14:WU00:FS02:0x22:Unit: 0x0000000012bc7d9a5f224a1aad8ba882
07:34:14:WU00:FS02:0x22:Digital signatures verified
07:34:14:WU00:FS02:0x22:Folding@home GPU Core22 Folding@home Core
07:34:14:WU00:FS02:0x22:Version 0.0.11
07:34:14:WU00:FS02:0x22:  Checkpoint write interval: 50000 steps (5%) [20 total]
07:34:14:WU00:FS02:0x22:  JSON viewer frame write interval: 10000 steps (1%) [100 total]
07:34:14:WU00:FS02:0x22:  XTC frame write interval: 250000 steps (25%) [4 total]
07:34:14:WU00:FS02:0x22:  Global context and integrator variables write interval: 25000 steps (2.5%) [40 total]
...
12:35:01:WU00:FS02:0x22:Completed 1000000 out of 1000000 steps (100%)
12:35:01:WU00:FS02:0x22:Average performance: 89.1641 ns/day
12:35:01:WU00:FS02:0x22:Saving result file ..\logfile_01.txt
12:35:01:WU00:FS02:0x22:Saving result file checkpointState.xml.bz2
12:35:01:WU00:FS02:0x22:Saving result file globals.csv
12:35:01:WU00:FS02:0x22:Saving result file positions.xtc
12:35:01:WU00:FS02:0x22:Saving result file science.log
12:35:01:WU00:FS02:0x22:Folding@home Core Shutdown: FINISHED_UNIT
12:35:02:WARNING:WU00:FS02:FahCore returned an unknown error code which probably indicates that it crashed
12:35:02:WARNING:WU00:FS02:FahCore returned: UNKNOWN_ENUM (-1073740940 = 0xc0000374)


18:42:19:WU01:FS02:Starting
18:42:19:WU01:FS02:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\user\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.11/Core_22.fah/FahCore_22.exe -dir 01 -suffix 01 -version 706 -lifeline 6692 -checkpoint 15 -gpu-vendor amd -opencl-platform 0 -opencl-device 0 -gpu 0
18:42:19:WU01:FS02:Started FahCore on PID 5496
18:42:19:WU01:FS02:Core PID:1660
18:42:19:WU01:FS02:FahCore 0x22 started
18:42:19:WU01:FS02:0x22:*********************** Log Started 2020-08-02T18:42:19Z ***********************
18:42:19:WU01:FS02:0x22:*************************** Core22 Folding@home Core ***************************
18:42:19:WU01:FS02:0x22:       Core: Core22
18:42:19:WU01:FS02:0x22:       Type: 0x22
18:42:19:WU01:FS02:0x22:    Version: 0.0.11
18:42:19:WU01:FS02:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
18:42:19:WU01:FS02:0x22:  Copyright: 2020 foldingathome.org
18:42:19:WU01:FS02:0x22:   Homepage: https://foldingathome.org/
18:42:19:WU01:FS02:0x22:       Date: Jun 26 2020
18:42:19:WU01:FS02:0x22:       Time: 19:49:16
18:42:19:WU01:FS02:0x22:   Revision: 22010df8a4db48db1b35d33e666b64d8ce48689d
18:42:19:WU01:FS02:0x22:     Branch: core22-0.0.11
18:42:19:WU01:FS02:0x22:   Compiler: Visual C++ 2015
18:42:19:WU01:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
18:42:19:WU01:FS02:0x22:   Platform: win32 10
18:42:20:WU01:FS02:0x22:       Bits: 64
18:42:20:WU01:FS02:0x22:       Mode: Release
18:42:20:WU01:FS02:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
18:42:20:WU01:FS02:0x22:             <peastman@stanford.edu>
18:42:20:WU01:FS02:0x22:       Args: -dir 01 -suffix 01 -version 706 -lifeline 5496 -checkpoint 15
18:42:20:WU01:FS02:0x22:             -gpu-vendor amd -opencl-platform 0 -opencl-device 0 -gpu 0
18:42:20:WU01:FS02:0x22:************************************ libFAH ************************************
18:42:20:WU01:FS02:0x22:       Date: Jun 26 2020
18:42:20:WU01:FS02:0x22:       Time: 19:47:12
18:42:20:WU01:FS02:0x22:   Revision: 2b383f4f04f38511dff592885d7c0400e72bdf43
18:42:20:WU01:FS02:0x22:     Branch: HEAD
18:42:20:WU01:FS02:0x22:   Compiler: Visual C++ 2015
18:42:20:WU01:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
18:42:20:WU01:FS02:0x22:   Platform: win32 10
18:42:20:WU01:FS02:0x22:       Bits: 64
18:42:20:WU01:FS02:0x22:       Mode: Release
18:42:20:WU01:FS02:0x22:************************************ CBang *************************************
18:42:20:WU01:FS02:0x22:       Date: Jun 26 2020
18:42:20:WU01:FS02:0x22:       Time: 19:46:11
18:42:20:WU01:FS02:0x22:   Revision: f8529962055b0e7bde23e429f5072ff758089dee
18:42:20:WU01:FS02:0x22:     Branch: master
18:42:20:WU01:FS02:0x22:   Compiler: Visual C++ 2015
18:42:20:WU01:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
18:42:20:WU01:FS02:0x22:   Platform: win32 10
18:42:20:WU01:FS02:0x22:       Bits: 64
18:42:20:WU01:FS02:0x22:       Mode: Release
18:42:20:WU01:FS02:0x22:************************************ System ************************************
18:42:20:WU01:FS02:0x22:        CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
18:42:20:WU01:FS02:0x22:     CPU ID: GenuineIntel Family 6 Model 30 Stepping 5
18:42:20:WU01:FS02:0x22:       CPUs: 4
18:42:20:WU01:FS02:0x22:     Memory: 7.99GiB
18:42:20:WU01:FS02:0x22:Free Memory: 4.24GiB
18:42:20:WU01:FS02:0x22:    Threads: WINDOWS_THREADS
18:42:20:WU01:FS02:0x22: OS Version: 6.2
18:42:20:WU01:FS02:0x22:Has Battery: false
18:42:20:WU01:FS02:0x22: On Battery: false
18:42:20:WU01:FS02:0x22: UTC Offset: 2
18:42:20:WU01:FS02:0x22:        PID: 1660
18:42:20:WU01:FS02:0x22:        CWD: C:\Users\user\AppData\Roaming\FAHClient\work
18:42:20:WU01:FS02:0x22:********************************************************************************
18:42:20:WU01:FS02:0x22:Project: 13421 (Run 5644, Clone 1, Gen 0)
18:42:20:WU01:FS02:0x22:Unit: 0x0000000112bc7d9a5f2249ee5b6d7c9b
18:42:20:WU01:FS02:0x22:Reading tar file core.xml
18:42:20:WU01:FS02:0x22:Reading tar file integrator.xml
18:42:20:WU01:FS02:0x22:Reading tar file state.xml.bz2
18:42:20:WU01:FS02:0x22:Reading tar file system.xml.bz2
18:42:20:WU01:FS02:0x22:Digital signatures verified
18:42:20:WU01:FS02:0x22:Folding@home GPU Core22 Folding@home Core
18:42:20:WU01:FS02:0x22:Version 0.0.11
18:42:20:WU01:FS02:0x22:  Checkpoint write interval: 50000 steps (5%) [20 total]
18:42:20:WU01:FS02:0x22:  JSON viewer frame write interval: 10000 steps (1%) [100 total]
18:42:20:WU01:FS02:0x22:  XTC frame write interval: 250000 steps (25%) [4 total]
18:42:20:WU01:FS02:0x22:  Global context and integrator variables write interval: 25000 steps (2.5%) [40 total]
18:42:29:WU01:FS02:0x22:Completed 0 out of 1000000 steps (0%)
...
23:18:40:WU01:FS02:0x22:Completed 1000000 out of 1000000 steps (100%)
23:18:40:WU01:FS02:0x22:Average performance: 105.366 ns/day
23:18:40:WU01:FS02:0x22:Saving result file ..\logfile_01.txt
23:18:40:WU01:FS02:0x22:Saving result file checkpointState.xml.bz2
23:18:40:WU01:FS02:0x22:Saving result file globals.csv
23:18:40:WU01:FS02:0x22:Saving result file positions.xtc
23:18:40:WU01:FS02:0x22:Saving result file science.log
23:18:40:WU01:FS02:0x22:Folding@home Core Shutdown: FINISHED_UNIT
23:18:41:WARNING:WU01:FS02:FahCore returned an unknown error code which probably indicates that it crashed
23:18:41:WARNING:WU01:FS02:FahCore returned: UNKNOWN_ENUM (-1073740940 = 0xc0000374)
Post Reply