Why does FAH throw out work with a new graphics driver?
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 62
- Joined: Mon Apr 13, 2020 11:47 am
Why does FAH throw out work with a new graphics driver?
I've noticed this a couple times. Maybe I'll be 50% through a work unit, I'll shut down FAH, update the Nvidia drivers, and restart FAH...then it starts over from 0%. Why?
-
- Posts: 2522
- Joined: Mon Feb 16, 2009 4:12 am
- Location: Greenwood MS USA
Re: Why does FAH throw out work with a new graphics driver?
Hmmm
I pause the Work Unit I am working on, then go back to folding after the driver is updated. I lose up to 5%, just like anytime I pause a WU.
I pause the Work Unit I am working on, then go back to folding after the driver is updated. I lose up to 5%, just like anytime I pause a WU.
Code: Select all
07:00:14:WU01:FS01:0x22:Checkpoint completed at step 4700000
07:02:58:WU01:FS01:0x22:Completed 4750000 out of 5000000 steps (95%)
07:05:42:WU01:FS01:0x22:Completed 4800000 out of 5000000 steps (96%)
07:05:43:WU01:FS01:0x22:Checkpoint completed at step 4800000
07:08:54:WU01:FS01:0x22:Completed 4850000 out of 5000000 steps (97%)
07:09:25:FS01:Paused
07:09:25:FS01:Shutting core down
07:09:26:WU01:FS01:0x22:WARNING:Console control signal 1 on PID 26792
07:09:26:WU01:FS01:0x22:Exiting, please wait. . .
07:09:26:WU01:FS01:0x22:Folding@home Core Shutdown: INTERRUPTED
07:09:26:WU01:FS01:FahCore returned: INTERRUPTED (102 = 0x66)
07:09:52:Removing old file 'configs/config-20210816-202406.xml'
07:09:52:Saving configuration to config.xml
07:09:52:<config>
07:09:52: <!-- HTTP Server -->
07:09:52: <allow v='127.0.0.1'/>
07:09:52:
07:09:52: <!-- Network -->
07:09:52: <proxy v=':8080'/>
07:09:52:
07:09:52: <!-- Slot Control -->
07:09:52: <power v='full'/>
07:09:52:
07:09:52: <!-- User Information -->
07:09:52: <passkey v='*****'/>
07:09:52: <team v='14'/>
07:09:52: <user v='JimboPalmer'/>
07:09:52:
07:09:52: <!-- Folding Slots -->
07:09:52: <slot id='0' type='CPU'>
07:09:52: <cpus v='2'/>
07:09:52: <pause-on-start v='True'/>
07:09:52: <paused v='true'/>
07:09:52: </slot>
07:09:52: <slot id='1' type='GPU'>
07:09:52: <paused v='true'/>
07:09:52: <pci-bus v='1'/>
07:09:52: <pci-slot v='0'/>
07:09:52: </slot>
07:09:52:</config>
07:15:26:FS01:Unpaused
07:15:26:WU01:FS01:Starting
07:15:26:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\User\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.18/Core_22.fah/FahCore_22.exe -dir 01 -suffix 01 -version 706 -lifeline 9384 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor nvidia -gpu 0 -gpu-usage 100
07:15:26:WU01:FS01:Started FahCore on PID 20020
07:15:26:WU01:FS01:Core PID:20212
07:15:26:WU01:FS01:FahCore 0x22 started
07:15:27:WU01:FS01:0x22:*********************** Log Started 2021-12-21T07:15:26Z ***********************
07:15:27:WU01:FS01:0x22:*************************** Core22 Folding@home Core ***************************
07:15:27:WU01:FS01:0x22: Core: Core22
07:15:27:WU01:FS01:0x22: Type: 0x22
07:15:27:WU01:FS01:0x22: Version: 0.0.18
07:15:27:WU01:FS01:0x22: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
07:15:27:WU01:FS01:0x22: Copyright: 2020 foldingathome.org
07:15:27:WU01:FS01:0x22: Homepage: https://foldingathome.org/
07:15:27:WU01:FS01:0x22: Date: Sep 28 2021
07:15:27:WU01:FS01:0x22: Time: 05:55:05
07:15:27:WU01:FS01:0x22: Revision: cfe3d7d990e8f456e371f8ce63b5fcc6daab2103
07:15:27:WU01:FS01:0x22: Branch: HEAD
07:15:27:WU01:FS01:0x22: Compiler: Visual C++
07:15:27:WU01:FS01:0x22: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
07:15:27:WU01:FS01:0x22: -DOPENMM_VERSION="\"7.6.0\""
07:15:27:WU01:FS01:0x22: Platform: win32 10
07:15:27:WU01:FS01:0x22: Bits: 64
07:15:27:WU01:FS01:0x22: Mode: Release
07:15:27:WU01:FS01:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
07:15:27:WU01:FS01:0x22: <peastman@stanford.edu>
07:15:27:WU01:FS01:0x22: Args: -dir 01 -suffix 01 -version 706 -lifeline 20020 -checkpoint 15
07:15:27:WU01:FS01:0x22: -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor
07:15:27:WU01:FS01:0x22: nvidia -gpu 0 -gpu-usage 100
07:15:27:WU01:FS01:0x22:************************************ libFAH ************************************
07:15:27:WU01:FS01:0x22: Date: Sep 28 2021
07:15:27:WU01:FS01:0x22: Time: 05:53:43
07:15:27:WU01:FS01:0x22: Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
07:15:27:WU01:FS01:0x22: Branch: HEAD
07:15:27:WU01:FS01:0x22: Compiler: Visual C++
07:15:27:WU01:FS01:0x22: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
07:15:27:WU01:FS01:0x22: Platform: win32 10
07:15:27:WU01:FS01:0x22: Bits: 64
07:15:27:WU01:FS01:0x22: Mode: Release
07:15:27:WU01:FS01:0x22:************************************ CBang *************************************
07:15:27:WU01:FS01:0x22: Date: Sep 28 2021
07:15:27:WU01:FS01:0x22: Time: 05:52:38
07:15:27:WU01:FS01:0x22: Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
07:15:27:WU01:FS01:0x22: Branch: HEAD
07:15:27:WU01:FS01:0x22: Compiler: Visual C++
07:15:27:WU01:FS01:0x22: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
07:15:27:WU01:FS01:0x22: Platform: win32 10
07:15:27:WU01:FS01:0x22: Bits: 64
07:15:27:WU01:FS01:0x22: Mode: Release
07:15:27:WU01:FS01:0x22:************************************ System ************************************
07:15:27:WU01:FS01:0x22: CPU: Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
07:15:27:WU01:FS01:0x22: CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
07:15:27:WU01:FS01:0x22: CPUs: 4
07:15:27:WU01:FS01:0x22: Memory: 7.92GiB
07:15:27:WU01:FS01:0x22:Free Memory: 4.82GiB
07:15:27:WU01:FS01:0x22: Threads: WINDOWS_THREADS
07:15:27:WU01:FS01:0x22: OS Version: 6.2
07:15:27:WU01:FS01:0x22:Has Battery: false
07:15:27:WU01:FS01:0x22: On Battery: false
07:15:27:WU01:FS01:0x22: UTC Offset: -6
07:15:27:WU01:FS01:0x22: PID: 20212
07:15:27:WU01:FS01:0x22: CWD: C:\Users\User\AppData\Roaming\FAHClient\work
07:15:27:WU01:FS01:0x22:************************************ OpenMM ************************************
07:15:27:WU01:FS01:0x22: Version: 7.6.0
07:15:27:WU01:FS01:0x22:********************************************************************************
07:15:27:WU01:FS01:0x22:Project: 18432 (Run 29, Clone 2, Gen 98)
07:15:27:WU01:FS01:0x22:Unit: 0x00000000000000000000000000000000
07:15:27:WU01:FS01:0x22:Digital signatures verified
07:15:27:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
07:15:27:WU01:FS01:0x22:Version 0.0.18
07:15:27:WU01:FS01:0x22: Checkpoint write interval: 100000 steps (2%) [50 total]
07:15:27:WU01:FS01:0x22: JSON viewer frame write interval: 50000 steps (1%) [100 total]
07:15:27:WU01:FS01:0x22: XTC frame write interval: 250000 steps (5%) [20 total]
07:15:27:WU01:FS01:0x22: Global context and integrator variables write interval: disabled
07:15:28:WU01:FS01:0x22:There are 4 platforms available.
07:15:28:WU01:FS01:0x22:Platform 0: Reference
07:15:28:WU01:FS01:0x22:Platform 1: CPU
07:15:28:WU01:FS01:0x22:Platform 2: OpenCL
07:15:28:WU01:FS01:0x22: opencl-device 0 specified
07:15:28:WU01:FS01:0x22:Platform 3: CUDA
07:15:28:WU01:FS01:0x22: cuda-device 0 specified
07:15:33:WU01:FS01:0x22:Attempting to create CUDA context:
07:15:33:WU01:FS01:0x22: Configuring platform CUDA
07:15:36:WU01:FS01:0x22: Using CUDA and gpu 0
07:15:36:WU01:FS01:0x22:Completed 4800000 out of 5000000 steps (96%)
07:15:58:Removing old file 'configs/config-20210817-024056.xml'
07:15:58:Saving configuration to config.xml
07:15:58:<config>
07:15:58: <!-- HTTP Server -->
07:15:58: <allow v='127.0.0.1'/>
07:15:58:
07:15:58: <!-- Network -->
07:15:58: <proxy v=':8080'/>
07:15:58: <!-- Slot Control -->
07:15:58: <power v='full'/>
07:15:58:
07:15:58: <!-- User Information -->
07:15:58: <passkey v='*****'/>
07:15:58: <team v='14'/>
07:15:58: <user v='JimboPalmer'/>
07:15:58:
07:15:58: <!-- Folding Slots -->
07:15:58: <slot id='0' type='CPU'>
07:15:58: <cpus v='2'/>
07:15:58: <pause-on-start v='True'/>
07:15:58: <paused v='true'/>
07:15:58: </slot>
07:15:58: <slot id='1' type='GPU'>
07:15:58: <pci-bus v='1'/>
07:15:58: <pci-slot v='0'/>
07:15:58: </slot>
07:15:58:</config>
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
-
- Posts: 62
- Joined: Mon Apr 13, 2020 11:47 am
Re: Why does FAH throw out work with a new graphics driver?
Ah, not mine. It goes back to 0%.
-
- Posts: 1996
- Joined: Sun Mar 22, 2020 5:52 pm
- Hardware configuration: 1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21 - Location: UK
Re: Why does FAH throw out work with a new graphics driver?
A reboot after installing the nVidia drivers will ensure FaH picks up the new drivers ... It may be that both this and the other issue you post are linked to FaH trying to use old drivers after driver update?
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)
-
- Site Moderator
- Posts: 6349
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: Why does FAH throw out work with a new graphics driver?
Which OS do you use ?
Do you use drivers downloaded from nVidia website (and not from Windows Updates) ?
When I update drivers (which doesn't occur very often since FAH doesn't need all the game ready updates), I do the following :
- download drivers from nVidia website
- exit FAHClient
- update drivers
- reboot
- restart FAHClient
Do you use drivers downloaded from nVidia website (and not from Windows Updates) ?
When I update drivers (which doesn't occur very often since FAH doesn't need all the game ready updates), I do the following :
- download drivers from nVidia website
- exit FAHClient
- update drivers
- reboot
- restart FAHClient
-
- Site Admin
- Posts: 7922
- 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: Why does FAH throw out work with a new graphics driver?
Examination of the F@h client log files from before and after the driver update may give a clue to what problem is being seen with the WUs causing them to be restarted from the beginning. Otherwise everyone is just guessing. In general updating the drivers should not cause this to happen.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
-
- Posts: 62
- Joined: Mon Apr 13, 2020 11:47 am
Re: Why does FAH throw out work with a new graphics driver?
Yeah, I use latest drivers from Nvidia's site. I'll check the log next time I see it happen and see if there are any clues.
Re: Why does FAH throw out work with a new graphics driver?
Depending on which OS your running your working folders could in one of three locations:-
Windows up to FAH Client 7.6.13 - C:\Users\<username>\AppData\FAHClient\
Windows FAH Client 7.6.21 - C:\ProgramData\FAHClient\
Linux - /var/lib/FAHClient/
By default your current log.txt file is stored in the parent directory and your previous 16 logs are stored in a subfolder called logs.
Windows up to FAH Client 7.6.13 - C:\Users\<username>\AppData\FAHClient\
Windows FAH Client 7.6.21 - C:\ProgramData\FAHClient\
Linux - /var/lib/FAHClient/
By default your current log.txt file is stored in the parent directory and your previous 16 logs are stored in a subfolder called logs.