• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

SOLVED error help

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

caddi daddi

Godzilla to ant hills
Joined
Jan 10, 2012
I have a couple of pascal rigs giving me this error, any ideas?
I have reinstalled driver, 378.66 I think.
I have removed and reinstalled the clients all to no avail...............
it downloads, starts, stops and downloads another and so on and so on.
I have the two racers to page one closing fast so I need to run a few million to hold my own spot and my own rig is doing the same, but only pascal cards, my maxwell cards are all chugging right along.

from one of the logs.

03:22:50:Enabled folding slot 01: PAUSED gpu:0:GP106 [GeForce GTX 1060 6GB] (paused)
03:22:53:3:127.0.0.1:New Web connection
03:23:07:WARNING:Exception: 5:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
03:23:07:WARNING:Exception: 6:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
03:23:07:WARNING:Exception: 7:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
03:23:08:WARNING:Exception: 8:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
03:23:10:WARNING:Exception: 9:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
03:23:14:WU01:FS01:Starting
03:23:14:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" "C:/Users/CADDI DADDI/AppData/Roaming/FAHClient/cores/fahwebx.stanford.edu/cores/Win32/AMD64/NVIDIA/Fermi/Core_21.fah/FahCore_21.exe" -dir 01 -suffix 01 -version 703 -lifeline 3044 -checkpoint 15 -gpu 0 -gpu-vendor nvidia
03:23:14:WU01:FS01:Started FahCore on PID 10672
03:23:14:WU01:FS01:Core PID:10652
03:23:14:WU01:FS01:FahCore 0x21 started
03:23:14:WU01:FS01:0x21:*********************** Log Started 2017-02-22T03:23:14Z ***********************
03:23:14:WU01:FS01:0x21:project: 9175 (Run 23, Clone 8, Gen 306)
03:23:14:WU01:FS01:0x21:Unit: 0x000001ceab436c6957b24c28f7686f5a
03:23:14:WU01:FS01:0x21:CPU: 0x00000000000000000000000000000000
03:23:14:WU01:FS01:0x21:Machine: 1
03:23:14:WU01:FS01:0x21:Reading tar file core.xml
03:23:14:WU01:FS01:0x21:Reading tar file integrator.xml
03:23:14:WU01:FS01:0x21:Reading tar file state.xml
03:23:14:WU01:FS01:0x21:Reading tar file system.xml
03:23:14:WU01:FS01:0x21:Digital signatures verified
03:23:14:WU01:FS01:0x21:[email protected] GPU Core21 [email protected] Core
03:23:14:WU01:FS01:0x21:Version 0.0.17
03:23:19:WU01:FS01:0x21:ERROR:exception: Error downloading array interactionCount: clEnqueueReadBuffer (-5)
03:23:19:WU01:FS01:0x21:Saving result file logfile_01.txt
03:23:19:WU01:FS01:0x21:Saving result file log.txt
03:23:19:WU01:FS01:0x21:[email protected] Core Shutdown: BAD_WORK_UNIT
03:23:23:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
03:23:23:WU01:FS01:Sending unit results: id:01 state:SEND error:FAULTY project:9175 run:23 clone:8 gen:306 core:0x21 unit:0x000001ceab436c6957b24c28f7686f5a
03:23:23:WU01:FS01:Uploading 7.00KiB to 171.67.108.105
03:23:23:WU01:FS01:Connecting to 171.67.108.105:8080
03:23:23:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:23:23:WU01:FS01:Upload complete
03:23:23:WU01:FS01:Server responded WORK_ACK (400)
03:23:23:WU01:FS01:Cleaning up
03:23:23:WU00:FS01:News:
 
Last edited:

HayesK

Member
Joined
Oct 11, 2008
FS01:0x21:ERROR:exception: Error downloading array interactionCount: clEnqueueReadBuffer (-5)

FS01:0x21:Version 0.0.17

driver, 378.66

Looks like the problem is new nvidia driver with old core_21 version 17.
Deleting the old FahCore_21.exe from your host will cause the newest version to download, currently version 18. Also, driver 373.06 works with version 17.
 
OP
caddi daddi

caddi daddi

Godzilla to ant hills
Joined
Jan 10, 2012
I deleted the FahCore_21.exe file from the roaming folder and this one is off to the races once again.
I guess i just broke the old rule, if it ain't fixed, don't broke it.
 

HayesK

Member
Joined
Oct 11, 2008
core version is displayed in the log just after a work unit starts. In your opening post, you mentioned the driver and your log with the error showed core_21 version 0.0.17, which is why I suspected that the issue was the driver + old core. Verifying that you now have version 18 will confirm that old core version 17 was the issue.