0x22 work unit never starts, stays at 0% on Windows

It seems that a lot of GPU problems revolve around specific versions of drivers. Though AMD has their own support structure, you can often learn from information reported by others who fold.

Moderators: Site Moderators, FAHC Science Team

Post Reply
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

As of last week, my AMD R9 GPU stalls when starting new packages after sending finished work units back. The last message in the log is "Configuring platform OpenCL" but then nothing happens until I restart the PC. Has anybody seen this before? Is there something I can do to fix this?

Code: Select all

22:41:38:WU01:FS01:0x22:Folding@home Core Shutdown: FINISHED_UNIT
22:41:39:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
22:41:39:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:13444 run:1957 clone:0 gen:1 core:0x22 unit:0x000000000000000100003484000007a5
22:41:39:WU01:FS01:Uploading 7.67MiB to 18.188.125.154
22:41:39:WU01:FS01:Connecting to 18.188.125.154:8080
22:41:39:WU00:FS01:Starting
22:41:39:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.13/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 706 -lifeline 11372 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0 -gpu-usage 100
22:41:39:WU00:FS01:Started FahCore on PID 1692
22:41:39:WU00:FS01:Core PID:14316
22:41:39:WU00:FS01:FahCore 0x22 started
22:41:39:WU00:FS01:0x22:*********************** Log Started 2021-01-25T22:41:39Z ***********************
22:41:39:WU00:FS01:0x22:*************************** Core22 Folding@home Core ***************************
22:41:39:WU00:FS01:0x22:       Core: Core22
22:41:39:WU00:FS01:0x22:       Type: 0x22
22:41:39:WU00:FS01:0x22:    Version: 0.0.13
22:41:39:WU00:FS01:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
22:41:39:WU00:FS01:0x22:  Copyright: 2020 foldingathome.org
22:41:39:WU00:FS01:0x22:   Homepage: https://foldingathome.org/
22:41:39:WU00:FS01:0x22:       Date: Sep 19 2020
22:41:39:WU00:FS01:0x22:       Time: 02:35:58
22:41:39:WU00:FS01:0x22:   Revision: 571cf95de6de2c592c7c3ed48fcfb2e33e9ea7d3
22:41:39:WU00:FS01:0x22:     Branch: core22-0.0.13
22:41:39:WU00:FS01:0x22:   Compiler: Visual C++ 2015
22:41:39:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
22:41:39:WU00:FS01:0x22:             -DOPENMM_GIT_HASH="\"189320d0\""
22:41:39:WU00:FS01:0x22:   Platform: win32 10
22:41:39:WU00:FS01:0x22:       Bits: 64
22:41:39:WU00:FS01:0x22:       Mode: Release
22:41:39:WU00:FS01:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
22:41:39:WU00:FS01:0x22:             <peastman@stanford.edu>
22:41:39:WU00:FS01:0x22:       Args: -dir 00 -suffix 01 -version 706 -lifeline 1692 -checkpoint 15
22:41:39:WU00:FS01:0x22:             -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0
22:41:39:WU00:FS01:0x22:             -gpu-usage 100
22:41:39:WU00:FS01:0x22:************************************ libFAH ************************************
22:41:39:WU00:FS01:0x22:       Date: Sep 7 2020
22:41:39:WU00:FS01:0x22:       Time: 19:09:56
22:41:39:WU00:FS01:0x22:   Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
22:41:39:WU00:FS01:0x22:     Branch: HEAD
22:41:39:WU00:FS01:0x22:   Compiler: Visual C++ 2015
22:41:39:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
22:41:39:WU00:FS01:0x22:   Platform: win32 10
22:41:39:WU00:FS01:0x22:       Bits: 64
22:41:39:WU00:FS01:0x22:       Mode: Release
22:41:39:WU00:FS01:0x22:************************************ CBang *************************************
22:41:39:WU00:FS01:0x22:       Date: Sep 7 2020
22:41:39:WU00:FS01:0x22:       Time: 19:08:30
22:41:39:WU00:FS01:0x22:   Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
22:41:39:WU00:FS01:0x22:     Branch: HEAD
22:41:39:WU00:FS01:0x22:   Compiler: Visual C++ 2015
22:41:39:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
22:41:39:WU00:FS01:0x22:   Platform: win32 10
22:41:39:WU00:FS01:0x22:       Bits: 64
22:41:39:WU00:FS01:0x22:       Mode: Release
22:41:39:WU00:FS01:0x22:************************************ System ************************************
22:41:39:WU00:FS01:0x22:        CPU: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
22:41:39:WU00:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 45 Stepping 7
22:41:39:WU00:FS01:0x22:       CPUs: 8
22:41:39:WU00:FS01:0x22:     Memory: 31.92GiB
22:41:39:WU00:FS01:0x22:Free Memory: 26.01GiB
22:41:39:WU00:FS01:0x22:    Threads: WINDOWS_THREADS
22:41:39:WU00:FS01:0x22: OS Version: 6.2
22:41:39:WU00:FS01:0x22:Has Battery: false
22:41:39:WU00:FS01:0x22: On Battery: false
22:41:39:WU00:FS01:0x22: UTC Offset: -8
22:41:39:WU00:FS01:0x22:        PID: 14316
22:41:39:WU00:FS01:0x22:        CWD: C:\ProgramData\FAHClient\work
22:41:39:WU00:FS01:0x22:************************************ OpenMM ************************************
22:41:39:WU00:FS01:0x22:   Revision: 189320d0
22:41:39:WU00:FS01:0x22:********************************************************************************
22:41:39:WU00:FS01:0x22:Project: 13444 (Run 2232, Clone 36, Gen 1)
22:41:39:WU00:FS01:0x22:Unit: 0x00000000000000000000000000000000
22:41:39:WU00:FS01:0x22:Reading tar file core.xml
22:41:39:WU00:FS01:0x22:Reading tar file integrator.xml.bz2
22:41:39:WU00:FS01:0x22:Reading tar file state.xml.bz2
22:41:39:WU00:FS01:0x22:Reading tar file system.xml.bz2
22:41:39:WU00:FS01:0x22:Digital signatures verified
22:41:39:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
22:41:39:WU00:FS01:0x22:Version 0.0.13
22:41:40:WU00:FS01:0x22:  Checkpoint write interval: 50000 steps (5%) [20 total]
22:41:40:WU00:FS01:0x22:  JSON viewer frame write interval: 10000 steps (1%) [100 total]
22:41:40:WU00:FS01:0x22:  XTC frame write interval: 250000 steps (25%) [4 total]
22:41:40:WU00:FS01:0x22:  Global context and integrator variables write interval: 25000 steps (2.5%) [40 total]
22:41:40:WU00:FS01:0x22:There are 3 platforms available.
22:41:40:WU00:FS01:0x22:Platform 0: Reference
22:41:40:WU00:FS01:0x22:Platform 1: CPU
22:41:40:WU00:FS01:0x22:Platform 2: OpenCL
22:41:40:WU00:FS01:0x22:  opencl-device 0 specified
22:41:45:WU01:FS01:Upload 33.41%
22:41:51:WU01:FS01:Upload 86.38%
22:41:52:WU01:FS01:Upload complete
22:41:53:WU01:FS01:Server responded WORK_ACK (400)
22:41:53:WU01:FS01:Final credit estimate, 124923.00 points
22:41:53:WU01:FS01:Cleaning up
22:41:57:WU00:FS01:0x22:Attempting to create OpenCL context:
22:41:57:WU00:FS01:0x22:  Configuring platform OpenCL
Top
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:
Contact PantherX

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by PantherX »

Can you please post the first 100 lines which will inform us of what the system configuration is and what the client settings are. Also, was there any Windows update or Driver update done around the time this issue started happening? What happens after you reboot your system; does it magically start working or does it get a new WU?
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Top
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

PantherX wrote:Can you please post the first 100 lines which will inform us of what the system configuration is and what the client settings are. Also, was there any Windows update or Driver update done around the time this issue started happening? What happens after you reboot your system; does it magically start working or does it get a new WU?
Thanks for your reply :) I don't use much Windows so I hope the forum can help me troubleshoot this problem.

The latest driver update was in November of last year. The latest Windows updates were applied on the 13th of January. On Sunday I removed the folding@home program completely, searched the registry for anything that referenced folding@home or fahclient and removed entries that looked like settings, rebooted, reinstalled the latest version and rebooted again, to no avail.

The WU starts working when I reboot the PC. The WU also stalls when I have the WUs finish and then unpause at a later time. After downloading the WUs, he CPU WU will run immediately, but the GPU one needs a reboot before starting.

I just rebooted so the full log looks like:

Code: Select all

*********************** Log Started 2021-01-26T16:06:49Z ***********************
16:06:49:******************************* libFAH ********************************
16:06:49:           Date: Oct 20 2020
16:06:49:           Time: 13:36:55
16:06:49:       Revision: 5ca109d295a6245e2a2f590b3d0085ad5e567aeb
16:06:49:         Branch: master
16:06:49:       Compiler: Visual C++ 2015
16:06:49:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
16:06:49:       Platform: win32 10
16:06:49:           Bits: 32
16:06:49:           Mode: Release
16:06:49:****************************** FAHClient ******************************
16:06:49:        Version: 7.6.21
16:06:49:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
16:06:49:      Copyright: 2020 foldingathome.org
16:06:49:       Homepage: https://foldingathome.org/
16:06:49:           Date: Oct 20 2020
16:06:49:           Time: 13:41:04
16:06:49:       Revision: 6efbf0e138e22d3963e6a291f78dcb9c6422a278
16:06:49:         Branch: master
16:06:49:       Compiler: Visual C++ 2015
16:06:49:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
16:06:49:       Platform: win32 10
16:06:49:           Bits: 32
16:06:49:           Mode: Release
16:06:49:         Config: C:\ProgramData\FAHClient\config.xml
16:06:49:******************************** CBang ********************************
16:06:49:           Date: Oct 20 2020
16:06:49:           Time: 11:36:18
16:06:49:       Revision: 7e4ce85225d7eaeb775e87c31740181ca603de60
16:06:49:         Branch: master
16:06:49:       Compiler: Visual C++ 2015
16:06:49:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
16:06:49:       Platform: win32 10
16:06:49:           Bits: 32
16:06:49:           Mode: Release
16:06:49:******************************* System ********************************
16:06:49:            CPU: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
16:06:49:         CPU ID: GenuineIntel Family 6 Model 45 Stepping 7
16:06:49:           CPUs: 8
16:06:49:         Memory: 31.92GiB
16:06:49:    Free Memory: 27.86GiB
16:06:49:        Threads: WINDOWS_THREADS
16:06:49:     OS Version: 6.2
16:06:49:    Has Battery: false
16:06:49:     On Battery: false
16:06:49:     UTC Offset: -8
16:06:49:            PID: 12072
16:06:49:            CWD: C:\ProgramData\FAHClient
16:06:49:  Win32 Service: false
16:06:49:             OS: Windows 10 Enterprise
16:06:49:        OS Arch: AMD64
16:06:49:           GPUs: 1
16:06:49:          GPU 0: Bus:3 Slot:0 Func:0 AMD:5 Hawaii [Radeon R9 200/300 Series]
16:06:49:           CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
16:06:49:                 specified module could not be found.
16:06:49:
16:06:49:OpenCL Device 0: Platform:0 Device:0 Bus:3 Slot:0 Compute:1.2 Driver:3188.4
16:06:49:OpenCL Device 1: Platform:0 Device:1 Bus:3 Slot:0 Compute:1.2 Driver:3188.4
16:06:49:***********************************************************************
16:06:49:<config>
16:06:49:  <!-- HTTP Server -->
16:06:49:  <allow v='127.0.0.1 192.168.1.0/24'/>
16:06:49:
16:06:49:  <!-- Network -->
16:06:49:  <proxy v=':8080'/>
16:06:49:
16:06:49:  <!-- Remote Command Server -->
16:06:49:  <command-allow-no-pass v='127.0.0.1 192.168.1.0/24'/>
16:06:49:  <password v='*****'/>
16:06:49:
16:06:49:  <!-- User Information -->
16:06:49:  <passkey v='*****'/>
16:06:49:  <team v='92'/>
16:06:49:  <user v='vincent'/>
16:06:49:
16:06:49:  <!-- Folding Slots -->
16:06:49:  <slot id='0' type='CPU'/>
16:06:49:  <slot id='1' type='GPU'>
16:06:49:    <pci-bus v='3'/>
16:06:49:    <pci-slot v='0'/>
16:06:49:  </slot>
16:06:49:</config>
16:06:49:Trying to access database...
16:06:49:Successfully acquired database lock
16:06:49:FS00:Initialized folding slot 00: cpu:6
16:06:49:FS01:Initialized folding slot 01: gpu:3:0 Hawaii [Radeon R9 200/300 Series]
16:06:49:WU00:FS00:Starting
16:06:49:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit-avx-256/a8-0.0.12/Core_a8.fah/FahCore_a8.exe -dir 00 -suffix 01 -version 706 -lifeline 12072 -checkpoint 15 -np 6
16:06:49:WU00:FS00:Started FahCore on PID 10620
16:06:49:WU00:FS00:Core PID:12316
16:06:49:WU00:FS00:FahCore 0xa8 started
16:06:50:WU01:FS01:Starting
16:06:50:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.13/Core_22.fah/FahCore_22.exe -dir 01 -suffix 01 -version 706 -lifeline 12072 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0 -gpu-usage 100
16:06:50:WU01:FS01:Started FahCore on PID 12344
16:06:50:WU01:FS01:Core PID:12372
16:06:50:WU01:FS01:FahCore 0x22 started
16:06:50:WU00:FS00:0xa8:*********************** Log Started 2021-01-26T16:06:50Z ***********************
16:06:50:WU00:FS00:0xa8:************************** Gromacs Folding@home Core ***************************
16:06:50:WU00:FS00:0xa8:       Core: Gromacs
16:06:50:WU00:FS00:0xa8:       Type: 0xa8
16:06:50:WU00:FS00:0xa8:    Version: 0.0.12
16:06:50:WU00:FS00:0xa8:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
16:06:50:WU00:FS00:0xa8:  Copyright: 2020 foldingathome.org
16:06:50:WU00:FS00:0xa8:   Homepage: https://foldingathome.org/
16:06:50:WU00:FS00:0xa8:       Date: Jan 16 2021
16:06:50:WU00:FS00:0xa8:       Time: 11:56:07
16:06:50:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
16:06:50:WU00:FS00:0xa8:     Branch: master
16:06:50:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
16:06:50:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
16:06:50:WU00:FS00:0xa8:   Platform: win32 10
16:06:50:WU00:FS00:0xa8:       Bits: 64
16:06:50:WU00:FS00:0xa8:       Mode: Release
16:06:50:WU00:FS00:0xa8:       SIMD: avx_256
16:06:50:WU00:FS00:0xa8:     OpenMP: ON
16:06:50:WU00:FS00:0xa8:       CUDA: OFF
16:06:50:WU00:FS00:0xa8:       Args: -dir 00 -suffix 01 -version 706 -lifeline 10620 -checkpoint 15 -np
16:06:50:WU00:FS00:0xa8:             6
16:06:50:WU00:FS00:0xa8:************************************ libFAH ************************************
16:06:50:WU00:FS00:0xa8:       Date: Jan 16 2021
16:06:50:WU00:FS00:0xa8:       Time: 11:24:13
16:06:50:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
16:06:50:WU00:FS00:0xa8:     Branch: master
16:06:50:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
16:06:50:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
16:06:50:WU00:FS00:0xa8:   Platform: win32 10
16:06:50:WU00:FS00:0xa8:       Bits: 64
16:06:50:WU00:FS00:0xa8:       Mode: Release
16:06:50:WU00:FS00:0xa8:************************************ CBang *************************************
16:06:50:WU00:FS00:0xa8:       Date: Jan 16 2021
16:06:50:WU00:FS00:0xa8:       Time: 11:23:53
16:06:50:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
16:06:50:WU00:FS00:0xa8:     Branch: master
16:06:50:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
16:06:50:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
16:06:50:WU00:FS00:0xa8:   Platform: win32 10
16:06:50:WU00:FS00:0xa8:       Bits: 64
16:06:50:WU00:FS00:0xa8:       Mode: Release
16:06:50:WU00:FS00:0xa8:************************************ System ************************************
16:06:50:WU00:FS00:0xa8:        CPU: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
16:06:50:WU00:FS00:0xa8:     CPU ID: GenuineIntel Family 6 Model 45 Stepping 7
16:06:50:WU00:FS00:0xa8:       CPUs: 8
16:06:50:WU00:FS00:0xa8:     Memory: 31.92GiB
16:06:50:WU00:FS00:0xa8:Free Memory: 27.78GiB
16:06:50:WU00:FS00:0xa8:    Threads: WINDOWS_THREADS
16:06:50:WU00:FS00:0xa8: OS Version: 6.2
16:06:50:WU00:FS00:0xa8:Has Battery: false
16:06:50:WU00:FS00:0xa8: On Battery: false
16:06:50:WU00:FS00:0xa8: UTC Offset: -8
16:06:50:WU00:FS00:0xa8:        PID: 12316
16:06:50:WU00:FS00:0xa8:        CWD: C:\ProgramData\FAHClient\work
16:06:50:WU00:FS00:0xa8:********************************************************************************
16:06:50:WU00:FS00:0xa8:Project: 16931 (Run 58, Clone 92, Gen 172)
16:06:50:WU00:FS00:0xa8:Unit: 0x00000000000000000000000000000000
16:06:50:WU00:FS00:0xa8:Digital signatures verified
16:06:50:WU00:FS00:0xa8:Calling: mdrun -c frame172.gro -s frame172.tpr -x frame172.xtc -cpt 15 -nt 6 -ntmpi 1
16:06:50:WU00:FS00:0xa8:Steps: first=86000000 total=86500000
16:06:50:WU01:FS01:0x22:*********************** Log Started 2021-01-26T16:06:50Z ***********************
16:06:50:WU01:FS01:0x22:*************************** Core22 Folding@home Core ***************************
16:06:50:WU01:FS01:0x22:       Core: Core22
16:06:50:WU01:FS01:0x22:       Type: 0x22
16:06:50:WU01:FS01:0x22:    Version: 0.0.13
16:06:50:WU01:FS01:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
16:06:50:WU01:FS01:0x22:  Copyright: 2020 foldingathome.org
16:06:50:WU01:FS01:0x22:   Homepage: https://foldingathome.org/
16:06:50:WU01:FS01:0x22:       Date: Sep 19 2020
16:06:50:WU01:FS01:0x22:       Time: 02:35:58
16:06:50:WU01:FS01:0x22:   Revision: 571cf95de6de2c592c7c3ed48fcfb2e33e9ea7d3
16:06:50:WU01:FS01:0x22:     Branch: core22-0.0.13
16:06:50:WU01:FS01:0x22:   Compiler: Visual C++ 2015
16:06:50:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
16:06:50:WU01:FS01:0x22:             -DOPENMM_GIT_HASH="\"189320d0\""
16:06:50:WU01:FS01:0x22:   Platform: win32 10
16:06:50:WU01:FS01:0x22:       Bits: 64
16:06:50:WU01:FS01:0x22:       Mode: Release
16:06:50:WU01:FS01:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
16:06:50:WU01:FS01:0x22:             <peastman@stanford.edu>
16:06:50:WU01:FS01:0x22:       Args: -dir 01 -suffix 01 -version 706 -lifeline 12344 -checkpoint 15
16:06:50:WU01:FS01:0x22:             -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0
16:06:50:WU01:FS01:0x22:             -gpu-usage 100
16:06:50:WU01:FS01:0x22:************************************ libFAH ************************************
16:06:50:WU01:FS01:0x22:       Date: Sep 7 2020
16:06:50:WU01:FS01:0x22:       Time: 19:09:56
16:06:50:WU01:FS01:0x22:   Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
16:06:50:WU01:FS01:0x22:     Branch: HEAD
16:06:50:WU01:FS01:0x22:   Compiler: Visual C++ 2015
16:06:50:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
16:06:50:WU01:FS01:0x22:   Platform: win32 10
16:06:50:WU01:FS01:0x22:       Bits: 64
16:06:50:WU01:FS01:0x22:       Mode: Release
16:06:50:WU01:FS01:0x22:************************************ CBang *************************************
16:06:50:WU01:FS01:0x22:       Date: Sep 7 2020
16:06:50:WU01:FS01:0x22:       Time: 19:08:30
16:06:50:WU01:FS01:0x22:   Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
16:06:50:WU01:FS01:0x22:     Branch: HEAD
16:06:50:WU01:FS01:0x22:   Compiler: Visual C++ 2015
16:06:50:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
16:06:50:WU01:FS01:0x22:   Platform: win32 10
16:06:50:WU01:FS01:0x22:       Bits: 64
16:06:50:WU01:FS01:0x22:       Mode: Release
16:06:50:WU01:FS01:0x22:************************************ System ************************************
16:06:50:WU01:FS01:0x22:        CPU: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
16:06:50:WU01:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 45 Stepping 7
16:06:50:WU01:FS01:0x22:       CPUs: 8
16:06:50:WU01:FS01:0x22:     Memory: 31.92GiB
16:06:50:WU01:FS01:0x22:Free Memory: 27.74GiB
16:06:50:WU01:FS01:0x22:    Threads: WINDOWS_THREADS
16:06:50:WU01:FS01:0x22: OS Version: 6.2
16:06:50:WU01:FS01:0x22:Has Battery: false
16:06:50:WU01:FS01:0x22: On Battery: false
16:06:50:WU01:FS01:0x22: UTC Offset: -8
16:06:50:WU01:FS01:0x22:        PID: 12372
16:06:50:WU01:FS01:0x22:        CWD: C:\ProgramData\FAHClient\work
16:06:50:WU01:FS01:0x22:************************************ OpenMM ************************************
16:06:50:WU01:FS01:0x22:   Revision: 189320d0
16:06:50:WU01:FS01:0x22:********************************************************************************
16:06:50:WU01:FS01:0x22:Project: 13444 (Run 2923, Clone 21, Gen 1)
16:06:50:WU01:FS01:0x22:Unit: 0x00000000000000000000000000000000
16:06:50:WU01:FS01:0x22:Digital signatures verified
16:06:50:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
16:06:50:WU01:FS01:0x22:Version 0.0.13
16:06:50:WU01:FS01:0x22:  Checkpoint write interval: 50000 steps (5%) [20 total]
16:06:50:WU01:FS01:0x22:  JSON viewer frame write interval: 10000 steps (1%) [100 total]
16:06:50:WU01:FS01:0x22:  XTC frame write interval: 250000 steps (25%) [4 total]
16:06:50:WU01:FS01:0x22:  Global context and integrator variables write interval: 25000 steps (2.5%) [40 total]
16:06:50:WU01:FS01:0x22:There are 3 platforms available.
16:06:50:WU01:FS01:0x22:Platform 0: Reference
16:06:50:WU01:FS01:0x22:Platform 1: CPU
16:06:50:WU01:FS01:0x22:Platform 2: OpenCL
16:06:50:WU01:FS01:0x22:  opencl-device 0 specified
16:06:53:WU00:FS00:0xa8:Completed 1 out of 500000 steps (0%)
16:07:08:WU01:FS01:0x22:Attempting to create OpenCL context:
16:07:08:WU01:FS01:0x22:  Configuring platform OpenCL
16:07:24:WU01:FS01:0x22:  Using OpenCL on platformId 0 and gpu 0
16:07:24:WU01:FS01:0x22:Completed 0 out of 1000000 steps (0%)
16:07:25:WU01:FS01:0x22:Checkpoint completed at step 0
16:08:13:WU00:FS00:0xa8:Completed 5000 out of 500000 steps (1%)
16:09:31:WU00:FS00:0xa8:Completed 10000 out of 500000 steps (2%)
16:10:47:WU00:FS00:0xa8:Completed 15000 out of 500000 steps (3%)
16:11:15:WU01:FS01:0x22:Completed 10000 out of 1000000 steps (1%)
16:12:05:WU00:FS00:0xa8:Completed 20000 out of 500000 steps (4%)
Top
Neil-B
Posts: 2027
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: 0x22 work unit never starts, stays at 0% on Windows

Post by Neil-B »

32bit OS issue? .. Ignore this - looking at wrong bit of header !!! ... my bad :(
Last edited by Neil-B on Tue Jan 26, 2021 6:47 pm, edited 1 time in total.
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)
Top
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

Neil-B wrote:32bit OS issue?
This has always been a 64 bit OS, so I doubt it.
Top
Joe_H
Site Admin
Posts: 7867
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: 0x22 work unit never starts, stays at 0% on Windows

Post by Joe_H »

Neil-B wrote:32bit OS issue?
Shouldn't be that, the OS shows up as 64-bit in the log:

Code: Select all

16:06:49:  Win32 Service: false
16:06:49:        OS: Windows 10 Enterprise
16:06:49:        OS Arch: AMD64
The client is detecting two GPUs as OpenCL devices, I am assuming one is the iGPU on the i7-3820:

Code: Select all

16:06:49:OpenCL Device 0: Platform:0 Device:0 Bus:3 Slot:0 Compute:1.2 Driver:3188.4
16:06:49:OpenCL Device 1: Platform:0 Device:1 Bus:3 Slot:0 Compute:1.2 Driver:3188.4
It is possible the folding core is sending its OpenCL connection to the wrong device for some reason. Also, someone more familiar with the AMD driver versions may be knowledgable as to whether the version shown is suitable Have the video drivers been updated recently by you or Windows?
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Top
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

Joe_H wrote:
Neil-B wrote:32bit OS issue?
Shouldn't be that, the OS shows up as 64-bit in the log:

Code: Select all

16:06:49:  Win32 Service: false
16:06:49:        OS: Windows 10 Enterprise
16:06:49:        OS Arch: AMD64
The client is detecting two GPUs as OpenCL devices, I am assuming one is the iGPU on the i7-3820:

Code: Select all

16:06:49:OpenCL Device 0: Platform:0 Device:0 Bus:3 Slot:0 Compute:1.2 Driver:3188.4
16:06:49:OpenCL Device 1: Platform:0 Device:1 Bus:3 Slot:0 Compute:1.2 Driver:3188.4
It is possible the folding core is sending its OpenCL connection to the wrong device for some reason. Also, someone more familiar with the AMD driver versions may be knowledgable as to whether the version shown is suitable Have the video drivers been updated recently by you or Windows?
The AMD driver was last updated in November of 2020, and the last Windows updates were applied on the 13th of January. I can not remember seeing anything but those two OpenCL devices on this PC, and it ran fine until last Thursday of Friday (21st/22nd). The AMD card is the only video device that's in this PC. The motherboard is an EVGA X79 SLI, which does not have an iGPU,
Top
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by bruce »

1) Windows updates the drivers whenever they feel like it. When they do, they have a habit of removing "unnecessary" features tht they didn't install ... most prominently things like CUDA and OpenCL, which FAH needs. That might have happened to you.

2) Support for those packages depends on the GPU manufacturer and varies depending on what nVidia/AMD/Intel/etc. actually provide. It also depends on whether it's Windows/Linux/MacOS/etc. Often when somebody like AMD or OS_X decides to deprecate an essential component, other folks here figure out where to find the unsupported features and a method to get them working.

3) In some cases, FAH has taken responsibility for figuring out how to support the feature (e.g. - CUDA) but once they do, it adds significantly to FAH's (unfunded) systems workload ... plus that adds to our permanent support responsibilities which doesn't really fit within our primary responsibilities for SCIENCE.

My answer is too general. You're looking for Windows support for OpenCL for AMD's Hawaii devices. I don't happen to be an AMD expert, but there are a number of folks who have faced the OpenCL support problem for Hawaii GPUs if you use the search function.
Top
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

bruce wrote:1) Windows updates the drivers whenever they feel like it. When they do, they have a habit of removing "unnecessary" features tht they didn't install ... most prominently things like CUDA and OpenCL, which FAH needs. That might have happened to you.

2) Support for those packages depends on the GPU manufacturer and varies depending on what nVidia/AMD/Intel/etc. actually provide. It also depends on whether it's Windows/Linux/MacOS/etc. Often when somebody like AMD or OS_X decides to deprecate an essential component, other folks here figure out where to find the unsupported features and a method to get them working.

3) In some cases, FAH has taken responsibility for figuring out how to support the feature (e.g. - CUDA) but once they do, it adds significantly to FAH's (unfunded) systems workload ... plus that adds to our permanent support responsibilities which doesn't really fit within our primary responsibilities for SCIENCE.

My answer is too general. You're looking for Windows support for OpenCL for AMD's Hawaii devices. I don't happen to be an AMD expert, but there are a number of folks who have faced the OpenCL support problem for Hawaii GPUs if you use the search function.
Thanks Bruce :)

1) The Windows Setup log shows no entries after the last updates were applied on the 13th, two weeks before this started happening, so I don't think that's it. Although Microsoft logging is notoriously unreliable so no guaranties there.

2) I'm going to try and look into reinstalling the AMD drivers. Maybe that fixes it, especially if Microsoft did manage to touch things they shouldn't have (without mentioning it).

3) I totally get that I can't expect FAH to provide support as if I'd paid for IBM's premium within-the-hour service plan. The reboot is more of a nuisance than a severe problem, so if anybody can help me troubleshoot and see what's going on, there will be a record of it on the forum that will be available if anybody should ever experience something like this again :) I don't know a lot about opencl/cuda on Windows but if there are some commands that I can run to inspect its status I'll see what I can find.

Thanks! :)
Top
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:
Contact PantherX

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by PantherX »

I have a theory that might fit these two symptoms:
1) You have two GPUs; iGPU and dGPU
2) Issue happens after you unpause the GPU Slot

When you reboot your system, the dGPU is active and F@H is looking at the right GPU and folding works fine. When you pause the GPU Slot, the dGPU waits for a while and then powers off causing the iGPU to kick-in and display the screen and non-intensive stuff. When you unpause the GPU Slot, the iGPU doesn't automatically hand-over to the dGPU and thus, you get WU_Stalled issues.

Sometimes, you can manually select what applications use what GPU. See this Windows 10 guide: https://www.howtogeek.com/351522/how-to ... indows-10/ or this one if you're not on 20H1: https://nvidia.custhelp.com/app/answers ... process-of

BTW, for sake of ease (or laziness... I mean, efficiency), I would suggest that once you finish folding the CPU WU, to pause the slot and continue to troubleshoot with the GPU Slot... it makes posting the log file and understanding very easy :)
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Top
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

PantherX wrote:I have a theory that might fit these two symptoms:
1) You have two GPUs; iGPU and dGPU
2) Issue happens after you unpause the GPU Slot

When you reboot your system, the dGPU is active and F@H is looking at the right GPU and folding works fine. When you pause the GPU Slot, the dGPU waits for a while and then powers off causing the iGPU to kick-in and display the screen and non-intensive stuff. When you unpause the GPU Slot, the iGPU doesn't automatically hand-over to the dGPU and thus, you get WU_Stalled issues.

Sometimes, you can manually select what applications use what GPU. See this Windows 10 guide: https://www.howtogeek.com/351522/how-to ... indows-10/ or this one if you're not on 20H1: https://nvidia.custhelp.com/app/answers ... process-of

BTW, for sake of ease (or laziness... I mean, efficiency), I would suggest that once you finish folding the CPU WU, to pause the slot and continue to troubleshoot with the GPU Slot... it makes posting the log file and understanding very easy :)
So yeah, I see two GPUs as well, but there really is only one video card in this PC. Both GPUs are using the same driver version, so I'm going on a limb and say that the card has two logical GPUs. There is no GPU on the motherboard, so it really is just the card's GPU(s).

I monitor this PC's progress from a laptop using FAHControl (which has the benefit of being able to tell it what the logs show ;) ). I have this PC finish the WUs in the afternoon so it's finished by the time I go to bed (even though it's in the next room, the fans are loud enough to keep me awake). In the morning, I unpause it. This morning I noticed that it got stuck, so I RDP'd into the PC, at which point... it started running, as shown in the below log snippet...

Code: Select all

******************************* Date: 2021-01-27 *******************************
15:51:12:WU01:FS01:Connecting to assign1.foldingathome.org:80
15:51:13:WU01:FS01:Assigned to work server 18.188.125.154
15:51:13:WU01:FS01:Requesting new work unit for slot 01: gpu:3:0 Hawaii [Radeon R9 200/300 Series] from 18.188.125.154
15:51:13:WU01:FS01:Connecting to 18.188.125.154:8080
15:51:14:WU01:FS01:Downloading 7.64MiB
15:51:16:WU01:FS01:Download complete
15:51:16:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:13444 run:842 clone:56 gen:1 core:0x22 unit:0x0000003800000001000034840000034a
15:51:16:WU01:FS01:Starting
15:51:16:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.13/Core_22.fah/FahCore_22.exe -dir 01 -suffix 01 -version 706 -lifeline 12072 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0 -gpu-usage 100
15:51:16:WU01:FS01:Started FahCore on PID 1804
15:51:16:WU01:FS01:Core PID:6140
15:51:16:WU01:FS01:FahCore 0x22 started
15:51:17:WU01:FS01:0x22:*********************** Log Started 2021-01-27T15:51:17Z ***********************
15:51:17:WU01:FS01:0x22:*************************** Core22 Folding@home Core ***************************
15:51:17:WU01:FS01:0x22:       Core: Core22
15:51:17:WU01:FS01:0x22:       Type: 0x22
15:51:17:WU01:FS01:0x22:    Version: 0.0.13
15:51:17:WU01:FS01:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
15:51:17:WU01:FS01:0x22:  Copyright: 2020 foldingathome.org
15:51:17:WU01:FS01:0x22:   Homepage: https://foldingathome.org/
15:51:17:WU01:FS01:0x22:       Date: Sep 19 2020
15:51:17:WU01:FS01:0x22:       Time: 02:35:58
15:51:17:WU01:FS01:0x22:   Revision: 571cf95de6de2c592c7c3ed48fcfb2e33e9ea7d3
15:51:17:WU01:FS01:0x22:     Branch: core22-0.0.13
15:51:17:WU01:FS01:0x22:   Compiler: Visual C++ 2015
15:51:17:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
15:51:17:WU01:FS01:0x22:             -DOPENMM_GIT_HASH="\"189320d0\""
15:51:17:WU01:FS01:0x22:   Platform: win32 10
15:51:17:WU01:FS01:0x22:       Bits: 64
15:51:17:WU01:FS01:0x22:       Mode: Release
15:51:17:WU01:FS01:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
15:51:17:WU01:FS01:0x22:             <peastman@stanford.edu>
15:51:17:WU01:FS01:0x22:       Args: -dir 01 -suffix 01 -version 706 -lifeline 1804 -checkpoint 15
15:51:17:WU01:FS01:0x22:             -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0
15:51:17:WU01:FS01:0x22:             -gpu-usage 100
15:51:17:WU01:FS01:0x22:************************************ libFAH ************************************
15:51:17:WU01:FS01:0x22:       Date: Sep 7 2020
15:51:17:WU01:FS01:0x22:       Time: 19:09:56
15:51:17:WU01:FS01:0x22:   Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
15:51:17:WU01:FS01:0x22:     Branch: HEAD
15:51:17:WU01:FS01:0x22:   Compiler: Visual C++ 2015
15:51:17:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
15:51:17:WU01:FS01:0x22:   Platform: win32 10
15:51:17:WU01:FS01:0x22:       Bits: 64
15:51:17:WU01:FS01:0x22:       Mode: Release
15:51:17:WU01:FS01:0x22:************************************ CBang *************************************
15:51:17:WU01:FS01:0x22:       Date: Sep 7 2020
15:51:17:WU01:FS01:0x22:       Time: 19:08:30
15:51:17:WU01:FS01:0x22:   Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
15:51:17:WU01:FS01:0x22:     Branch: HEAD
15:51:17:WU01:FS01:0x22:   Compiler: Visual C++ 2015
15:51:17:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
15:51:17:WU01:FS01:0x22:   Platform: win32 10
15:51:17:WU01:FS01:0x22:       Bits: 64
15:51:17:WU01:FS01:0x22:       Mode: Release
15:51:17:WU01:FS01:0x22:************************************ System ************************************
15:51:17:WU01:FS01:0x22:        CPU: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
15:51:17:WU01:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 45 Stepping 7
15:51:17:WU01:FS01:0x22:       CPUs: 8
15:51:17:WU01:FS01:0x22:     Memory: 31.92GiB
15:51:17:WU01:FS01:0x22:Free Memory: 26.75GiB
15:51:17:WU01:FS01:0x22:    Threads: WINDOWS_THREADS
15:51:17:WU01:FS01:0x22: OS Version: 6.2
15:51:17:WU01:FS01:0x22:Has Battery: false
15:51:17:WU01:FS01:0x22: On Battery: false
15:51:17:WU01:FS01:0x22: UTC Offset: -8
15:51:17:WU01:FS01:0x22:        PID: 6140
15:51:17:WU01:FS01:0x22:        CWD: C:\ProgramData\FAHClient\work
15:51:17:WU01:FS01:0x22:************************************ OpenMM ************************************
15:51:17:WU01:FS01:0x22:   Revision: 189320d0
15:51:17:WU01:FS01:0x22:********************************************************************************
15:51:17:WU01:FS01:0x22:Project: 13444 (Run 842, Clone 56, Gen 1)
15:51:17:WU01:FS01:0x22:Unit: 0x00000000000000000000000000000000
15:51:17:WU01:FS01:0x22:Reading tar file core.xml
15:51:17:WU01:FS01:0x22:Reading tar file integrator.xml.bz2
15:51:17:WU01:FS01:0x22:Reading tar file state.xml.bz2
15:51:17:WU01:FS01:0x22:Reading tar file system.xml.bz2
15:51:17:WU01:FS01:0x22:Digital signatures verified
15:51:17:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
15:51:17:WU01:FS01:0x22:Version 0.0.13
15:51:18:WU01:FS01:0x22:  Checkpoint write interval: 50000 steps (5%) [20 total]
15:51:18:WU01:FS01:0x22:  JSON viewer frame write interval: 10000 steps (1%) [100 total]
15:51:18:WU01:FS01:0x22:  XTC frame write interval: 250000 steps (25%) [4 total]
15:51:18:WU01:FS01:0x22:  Global context and integrator variables write interval: 25000 steps (2.5%) [40 total]
15:51:18:WU01:FS01:0x22:There are 3 platforms available.
15:51:18:WU01:FS01:0x22:Platform 0: Reference
15:51:18:WU01:FS01:0x22:Platform 1: CPU
15:51:18:WU01:FS01:0x22:Platform 2: OpenCL
15:51:18:WU01:FS01:0x22:  opencl-device 0 specified
15:51:35:WU01:FS01:0x22:Attempting to create OpenCL context:
15:51:35:WU01:FS01:0x22:  Configuring platform OpenCL
16:22:13:WU01:FS01:0x22:  Using OpenCL on platformId 0 and gpu 0
16:22:13:WU01:FS01:0x22:Completed 0 out of 1000000 steps (0%)
16:22:14:WU01:FS01:0x22:Checkpoint completed at step 0
16:25:59:WU01:FS01:0x22:Completed 10000 out of 1000000 steps (1%)
16:29:42:WU01:FS01:0x22:Completed 20000 out of 1000000 steps (2%)
16:33:26:WU01:FS01:0x22:Completed 30000 out of 1000000 steps (3%)
16:37:10:WU01:FS01:0x22:Completed 40000 out of 1000000 steps (4%)
So it just sat there between 15:51:35 and 16:22:13 but it did start up eventually without a reboot, but with a (remote) login. If anybody has some knowledge of commands to try and poke into the OpenCL architecture and see more information, that might be helpful? :) Also, Windows' device manager shows what I believe is a pseudo-device to facilitate the remote connection. It's called "Microsoft Remote Display Adapter". Could FAH confuse that with the real card?
Top
Joe_H
Site Admin
Posts: 7867
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: 0x22 work unit never starts, stays at 0% on Windows

Post by Joe_H »

Now that you have mentioned MS's Remote Desktop, that may be where the problem exists. Remote Desktop has always been a problem with F@h, it takes over the graphics device while you are connected. People have found that using other methods of remotely connecting such as Teamviewer or VNC based connections do not interrupt folding.

GPU folding also requires a logged in user with Windows, MS security requires that the display belong to a logged in user.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Top
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

Joe_H wrote:Now that you have mentioned MS's Remote Desktop, that may be where the problem exists. Remote Desktop has always been a problem with F@h, it takes over the graphics device while you are connected. People have found that using other methods of remotely connecting such as Teamviewer or VNC based connections do not interrupt folding.

GPU folding also requires a logged in user with Windows, MS security requires that the display belong to a logged in user.
Thanks Joe! I will install VNC and see if that makes this problem go away :)
Top
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by bruce »

Joe_H wrote:Now that you have mentioned MS's Remote Desktop, that may be where the problem exists. Remote Desktop has always been a problem with F@h, it takes over the graphics device while you are connected. People have found that using other methods of remotely connecting such as Teamviewer or VNC based connections do not interrupt folding.

GPU folding also requires a logged in user with Windows, MS security requires that the display belong to a logged in user.
It could be either of those ... or (3) a problem with AMD drivers not finding the right OpenCL.

As for (2), Windows has to believe that the GPU is displaying the MS desktop. They will not let a background user have control of the GPU.
Top
vincent89147
Posts: 27
Joined: Sun Jul 14, 2019 11:46 pm

Re: 0x22 work unit never starts, stays at 0% on Windows

Post by vincent89147 »

bruce wrote:
Joe_H wrote:Now that you have mentioned MS's Remote Desktop, that may be where the problem exists. Remote Desktop has always been a problem with F@h, it takes over the graphics device while you are connected. People have found that using other methods of remotely connecting such as Teamviewer or VNC based connections do not interrupt folding.

GPU folding also requires a logged in user with Windows, MS security requires that the display belong to a logged in user.
It could be either of those ... or (3) a problem with AMD drivers not finding the right OpenCL.

As for (2), Windows has to believe that the GPU is displaying the MS desktop. They will not let a background user have control of the GPU.
Thanks Bruce, after letting it run for a couple of days without RDP-ing into the PC it has not given me any trouble. When I'm logged in via RDP I see that Windows has created pseudo devices for the display adapter and the display itself, but when I am just logged in "normally" those devices aren't there. So I'm guessing FAH gets confused when the pseudo display adapter is present, just not to the point that it breaks or crashes. It just waits for the device to be gone and then things work as expected.

This seems to be fixed by not being logged in using RDP. Thanks everybody for your time and suggestions :)
Top
Post Reply

Return to “Problems with AMD/ATI drivers”