Page 1 of 4
I am having rampant failures with the newest NVIDIA drivers
Posted: Thu Feb 06, 2014 4:13 am
by Turbo_T
My EVGA 660Ti is shutting down from rapid fire failures on project 8018. I loaded the latest drivers 332.21 but they don't seem to help at all. the system runs fine 24/7 but lately the GPU(stock settings, no personal OC) keeps getting the error "GPU 1 failed to complete a project 8018 WU (unstable_machine) until 10 fail and it shuts down for 4 hours. the failures are within 2 minutes of starting the new project and it's all on the same WU, 8018. Help, I am a dedicated folder and have 2 GPU's folding in this particular machine. The EVGA GTX 480 FTW has no problems with the WU but the 660 TI is having fits.
Thanks,
Turbo_T
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Thu Feb 06, 2014 5:13 am
by PantherX
Welcome to the F@H Forum Turbo_T,
Is your GPU operating within normal temperatures? Is there a dust build-up in your system? If your GPU is having a factory overclock, you could try using the Nvidia stock frequencies.
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Thu Feb 06, 2014 10:03 am
by Kjetil
Use this driver on 6xx card 327.23. I have 660Ti and PPD on p8900 is 68K
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Thu Feb 06, 2014 11:53 am
by PantherX
Welcome to the F@H Forum Kjetil,
That observation applies only to FahCore_17 WUs. However, Project 8018 is using FahCore_15 and I haven't read any reports if the performance is the same or lower with the newer drivers. Moreover, the latest WHQL Drivers lowers the performance of FahCore_17, it doesn't cause the WU to error out.
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Thu Feb 06, 2014 12:59 pm
by Turbo_T
my GPU temperatures stay in the mid 60's so its not a problem. I do clean the dust out regularly. the card is a sc model so I may try reducing the clocks and see if it helps. This only happens with that one wu. I have no errors with any other WU's.
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Thu Feb 06, 2014 1:04 pm
by bollix47
If you're going to try reducing the clocks I suggest you just reduce the Memory clock to stock first and try again. I've had some success doing this and leaving the Core clock at it's o/c. Memory speed makes very little difference to folding but it can cause problems with some overclocked setups.
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Thu Feb 06, 2014 6:42 pm
by Turbo_T
Ok i'll try that first. Thanks
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Fri Feb 07, 2014 3:05 am
by Turbo_T
I have dropped my Memory clocks by a measly 50 Hz and it has performed 37% of the WU with to failures, so we may have got it. Thanks, I'll confirm after a couple WU process correctly. As far as performance though I am curious.
My system config is: ASUS P6X58D motherboard with an intel 980X CPU, 3X4GB of ram in the primary channel, b slots vacant, an EVGA GTX 480 FTW (liquid cooled) in the primary PCI EX slot and the EVGA 650TI in the second PCI EX slot, one Kingston 300 series 126GB SSD boot drive, 1X 1TB Western digital Black edition HDD, 1X 2TB storage drive, a Swiftech 3X120 radiator and high airflow fans with a custom water loop (that I made) cooling the CPU and the 480 GTX the 650 TI is air cooled. I have the CPU 24/7 stable at 4.0 GHZ with no PCI overclock and Memory running at a hair over the stock 1600 setting (1642 I think) my CPU temps never exceed 65 and average is 57 while fording on 10 of the 12 cores. I run both GPU's as well, the 480 max temp over the last 48 hours was 68C and the 660 was 69. My temps are never really a problem, I certainly don't ever get into the range you would see any throttling. But here's the catch, my CPU will run in SMP mode at 25-29K PPD and the two cards end up running identical WU's at about 15K PPD. That seems way low to me considering the numbers kjetil posted above. I had a short period back in October when both cards seemed to be getting some higher point WU's and I was pulling 29-30K PPD with either of them too, but that didn't last long for whatever reason. I have not been able to figure out why that stopped. There have been no significant configuration changes in the last year. The system was built in October of 2010 and has been in continuous use since then. I can perform all my daily functions on the last 2 CPU cores I don't have folding, and I only shut down the primary GPU when I am playing a particularly graphics intensive game on the weekends. Do you have any idea what I should expect to get with this hardware?
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Sat Feb 08, 2014 6:02 am
by n_w95482
If the cards are working on core 15 WUs, the PPD will be lower (around what you mentioned). With core 17, it'll be higher.
As Kjetil mentioned, switch to the 327.23 driver. Anything higher than that will cause your 650 to run much slower than normal when working on core 17 WUs. Using FAHBench as an example, I had a performance loss of 55% with explcit single-precision, which correlated with the huge loss in PPD that I experienced.
Right now, demand for core 17 WUs is greater than the supply of said WUs, so you'll see the cards bounce back and forth between core 15 and 17, depending on what's available at the time.
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Sat Feb 08, 2014 5:24 pm
by Turbo_T
All I see is Core 15 on my system, I don't have a core 17 even loaded. Why wouldn't the system pick up a core 17 when it is available? Is there a setting that activates that option? Thanks for all the help and information.
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Sat Feb 08, 2014 5:42 pm
by P5-133XL
No there is no setting that guarantee's Core_17. You get whatever the work servers give you. The priorities for individual projects are set by PG. The best you can do is fiddle with the client-type but that really doesn't get what you want. All it does is change the set of projects available to you to a more or less risky (more or less tested and thereby more or less likely to be a bad WU) set.
That being said, Core_15 is relatively old and its projects are well tested, and generally in general release. However, Core_17 is relatively new and thereby less tested and more risky. So if you want to try to chase Core_17 then you can change client-type to something else (beta, advanced, or non-existent for general release)
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Sat Feb 08, 2014 5:48 pm
by 7im
P5-133XL wrote:No there is no setting that guarantee's Core_17. You get whatever the work servers give you. The priorities for individual projects are set by PG. The best you can do is fiddle with the client-type but that really doesn't get what you want. All it does is change the set of projects available to you to a more or less risky (more or less tested and thereby more or less likely to be a bad WU) set.
That being said, Core_15 is relatively old and its projects are well tested, and generally in general release. However, Core_17 is relatively new and thereby less tested and more risky. So if you want to try to chase Core_17 then you can change client-type to something else (beta, advanced, or non-existent for general release)
But unless you are a member of the beta team, there is no support for using the beta setting.
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Sat Feb 08, 2014 5:50 pm
by P5-133XL
So true
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Sat Feb 15, 2014 2:51 pm
by Turbo_T
I have dialed everything back to OEM settings and continue to have regular failures on my slot 00 primary GPU. It is an EVGA GTX 480 hydro copper gpu that has been folding for 3 years with little, if any problems. I have just increased the log file setting to 4 but this version I am pasting in is from the last output while still on setting 3. It may require a change to the GPU forum as I am not certain the drivers are the problem any more. I am using the suggested drivers 327.23 and the GPU fails soon after starting, but the system is not BSOD. it just fails in the F@H control. I have no system instability during games or in previous folding using the V2tracker console to run my folding. however, that console doesn't support core 17, so I changed recently. The following is the log from yesterday.
Code: Select all
*********************** Log Started 2014-02-15T06:10:39Z ***********************
06:10:40:WU02:FS00:Connecting to assign-GPU.stanford.edu:80
06:10:41:WU02:FS00:News: Welcome to Folding@Home
06:10:41:WU02:FS00:Assigned to work server 171.64.65.69
06:10:41:WU02:FS00:Requesting new work unit for slot 00: READY gpu:0:GF100 [GeForce GTX 480] from 171.64.65.69
06:10:41:WU02:FS00:Connecting to 171.64.65.69:8080
06:10:41:WU02:FS00:Downloading 4.17MiB
06:10:44:WU02:FS00:Download complete
06:10:44:WU02:FS00:Received Unit: id:02 state:DOWNLOAD error:NO_ERROR project:8900 run:649 clone:4 gen:83 core:0x17 unit:0x00000089028c126651a6b710bf45e11f
06:10:44:WU02:FS00:Starting
06:10:44:WU02:FS00:Running FahCore: "E:\Stanford FAH\FAHClient/FAHCoreWrapper.exe" "E:/Stanford FAH/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_17.fah/FahCore_17.exe" -dir 02 -suffix 01 -version 703 -lifeline 6268 -checkpoint 30 -gpu 0 -gpu-vendor nvidia
06:10:44:WU02:FS00:Started FahCore on PID 6380
06:10:44:WU02:FS00:Core PID:6448
06:10:44:WU02:FS00:FahCore 0x17 started
06:10:45:WU02:FS00:0x17:*********************** Log Started 2014-02-15T06:10:44Z ***********************
06:10:45:WU02:FS00:0x17:Project: 8900 (Run 649, Clone 4, Gen 83)
06:10:45:WU02:FS00:0x17:Unit: 0x00000089028c126651a6b710bf45e11f
06:10:45:WU02:FS00:0x17:CPU: 0x00000000000000000000000000000000
06:10:45:WU02:FS00:0x17:Machine: 0
06:10:45:WU02:FS00:0x17:Reading tar file state.xml
06:10:45:WU02:FS00:0x17:Reading tar file system.xml
06:10:45:WU02:FS00:0x17:Reading tar file integrator.xml
06:10:45:WU02:FS00:0x17:Reading tar file core.xml
06:10:45:WU02:FS00:0x17:Digital signatures verified
06:10:45:WU02:FS00:0x17:Folding@home GPU core17
06:10:45:WU02:FS00:0x17:Version 0.0.52
06:14:04:WU02:FS00:0x17:Completed 0 out of 2500000 steps (0%)
06:14:04:WU02:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
06:34:39:WU02:FS00:0x17:Completed 25000 out of 2500000 steps (1%)
06:46:32:WU02:FS00:0x17:ERROR:exception: First periodic box vector must be parallel to x.
06:46:32:WU02:FS00:0x17:Saving result file logfile_01.txt
06:46:32:WU02:FS00:0x17:Saving result file log.txt
06:46:32:WU02:FS00:0x17:Folding@home Core Shutdown: BAD_WORK_UNIT
06:46:33:WARNING:WU02:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
06:46:33:WU02:FS00:Sending unit results: id:02 state:SEND error:FAULTY project:8900 run:649 clone:4 gen:83 core:0x17 unit:0x00000089028c126651a6b710bf45e11f
06:46:33:WU02:FS00:Uploading 2.47KiB to 171.64.65.69
06:46:33:WU02:FS00:Connecting to 171.64.65.69:8080
06:46:33:WU03:FS00:Connecting to assign-GPU.stanford.edu:80
06:46:33:WU02:FS00:Upload complete
06:46:33:WU02:FS00:Server responded WORK_ACK (400)
06:46:34:WU02:FS00:Cleaning up
06:46:34:WU03:FS00:News: Welcome to Folding@Home
06:46:34:WU03:FS00:Assigned to work server 171.64.65.69
06:46:34:WU03:FS00:Requesting new work unit for slot 00: READY gpu:0:GF100 [GeForce GTX 480] from 171.64.65.69
06:46:34:WU03:FS00:Connecting to 171.64.65.69:8080
06:46:35:WU03:FS00:Downloading 4.17MiB
06:46:37:WU03:FS00:Download complete
06:46:38:WU03:FS00:Received Unit: id:03 state:DOWNLOAD error:NO_ERROR project:8900 run:627 clone:1 gen:286 core:0x17 unit:0x00000174028c126651a6b21720aa8f18
06:46:38:WU03:FS00:Starting
06:46:38:WU03:FS00:Running FahCore: "E:\Stanford FAH\FAHClient/FAHCoreWrapper.exe" "E:/Stanford FAH/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_17.fah/FahCore_17.exe" -dir 03 -suffix 01 -version 703 -lifeline 6268 -checkpoint 30 -gpu 0 -gpu-vendor nvidia
06:46:38:WU03:FS00:Started FahCore on PID 6792
06:46:38:WU03:FS00:Core PID:6756
06:46:38:WU03:FS00:FahCore 0x17 started
06:46:38:WU03:FS00:0x17:*********************** Log Started 2014-02-15T06:46:38Z ***********************
06:46:38:WU03:FS00:0x17:Project: 8900 (Run 627, Clone 1, Gen 286)
06:46:38:WU03:FS00:0x17:Unit: 0x00000174028c126651a6b21720aa8f18
06:46:38:WU03:FS00:0x17:CPU: 0x00000000000000000000000000000000
06:46:38:WU03:FS00:0x17:Machine: 0
06:46:38:WU03:FS00:0x17:Reading tar file state.xml
06:46:39:WU03:FS00:0x17:Reading tar file system.xml
06:46:39:WU03:FS00:0x17:Reading tar file integrator.xml
06:46:39:WU03:FS00:0x17:Reading tar file core.xml
06:46:39:WU03:FS00:0x17:Digital signatures verified
06:46:39:WU03:FS00:0x17:Folding@home GPU core17
06:46:39:WU03:FS00:0x17:Version 0.0.52
06:49:44:WU03:FS00:0x17:Completed 0 out of 2500000 steps (0%)
06:49:44:WU03:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
07:06:40:WU03:FS00:0x17:ERROR:exception: The periodic box size has decreased to less than twice the nonbonded cutoff.
07:06:40:WU03:FS00:0x17:Saving result file logfile_01.txt
07:06:40:WU03:FS00:0x17:Saving result file log.txt
07:06:40:WU03:FS00:0x17:Folding@home Core Shutdown: BAD_WORK_UNIT
07:06:41:WARNING:WU03:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
07:06:41:WU03:FS00:Sending unit results: id:03 state:SEND error:FAULTY project:8900 run:627 clone:1 gen:286 core:0x17 unit:0x00000174028c126651a6b21720aa8f18
07:06:41:WU03:FS00:Uploading 2.48KiB to 171.64.65.69
07:06:41:WU03:FS00:Connecting to 171.64.65.69:8080
07:06:41:WU02:FS00:Connecting to assign-GPU.stanford.edu:80
07:06:41:WU03:FS00:Upload complete
07:06:41:WU03:FS00:Server responded WORK_ACK (400)
07:06:41:WU03:FS00:Cleaning up
07:06:42:WU02:FS00:News: Welcome to Folding@Home
07:06:42:WU02:FS00:Assigned to work server 171.64.65.69
07:06:42:WU02:FS00:Requesting new work unit for slot 00: READY gpu:0:GF100 [GeForce GTX 480] from 171.64.65.69
07:06:42:WU02:FS00:Connecting to 171.64.65.69:8080
07:06:43:WU02:FS00:Downloading 4.17MiB
07:06:45:WU02:FS00:Download complete
07:06:46:WU02:FS00:Received Unit: id:02 state:DOWNLOAD error:NO_ERROR project:8900 run:446 clone:3 gen:67 core:0x17 unit:0x0000006e028c126651a689e60b6e5447
07:06:46:WU02:FS00:Starting
07:06:46:WU02:FS00:Running FahCore: "E:\Stanford FAH\FAHClient/FAHCoreWrapper.exe" "E:/Stanford FAH/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_17.fah/FahCore_17.exe" -dir 02 -suffix 01 -version 703 -lifeline 6268 -checkpoint 30 -gpu 0 -gpu-vendor nvidia
07:06:46:WU02:FS00:Started FahCore on PID 5880
07:06:46:WU02:FS00:Core PID:5532
07:06:46:WU02:FS00:FahCore 0x17 started
07:06:46:WU02:FS00:0x17:*********************** Log Started 2014-02-15T07:06:46Z ***********************
07:06:46:WU02:FS00:0x17:Project: 8900 (Run 446, Clone 3, Gen 67)
07:06:46:WU02:FS00:0x17:Unit: 0x0000006e028c126651a689e60b6e5447
07:06:46:WU02:FS00:0x17:CPU: 0x00000000000000000000000000000000
07:06:46:WU02:FS00:0x17:Machine: 0
07:06:46:WU02:FS00:0x17:Reading tar file state.xml
07:06:47:WU02:FS00:0x17:Reading tar file system.xml
07:06:48:WU02:FS00:0x17:Reading tar file integrator.xml
07:06:48:WU02:FS00:0x17:Reading tar file core.xml
07:06:48:WU02:FS00:0x17:Digital signatures verified
07:06:48:WU02:FS00:0x17:Folding@home GPU core17
07:06:48:WU02:FS00:0x17:Version 0.0.52
07:09:54:WU02:FS00:0x17:Completed 0 out of 2500000 steps (0%)
07:09:54:WU02:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
07:30:22:WU02:FS00:0x17:Completed 25000 out of 2500000 steps (1%)
07:36:44:WU02:FS00:0x17:ERROR:exception: The periodic box size has decreased to less than twice the nonbonded cutoff.
07:36:44:WU02:FS00:0x17:Saving result file logfile_01.txt
07:36:44:WU02:FS00:0x17:Saving result file log.txt
07:36:44:WU02:FS00:0x17:Folding@home Core Shutdown: BAD_WORK_UNIT
07:36:45:WARNING:WU02:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
07:36:45:WU02:FS00:Sending unit results: id:02 state:SEND error:FAULTY project:8900 run:446 clone:3 gen:67 core:0x17 unit:0x0000006e028c126651a689e60b6e5447
07:36:45:WU02:FS00:Uploading 2.50KiB to 171.64.65.69
07:36:45:WU02:FS00:Connecting to 171.64.65.69:8080
07:36:45:WU03:FS00:Connecting to assign-GPU.stanford.edu:80
07:36:45:WU02:FS00:Upload complete
07:36:45:WU02:FS00:Server responded WORK_ACK (400)
07:36:45:WU02:FS00:Cleaning up
07:36:46:WU03:FS00:News: Welcome to Folding@Home
07:36:46:WU03:FS00:Assigned to work server 171.64.65.69
07:36:46:WU03:FS00:Requesting new work unit for slot 00: READY gpu:0:GF100 [GeForce GTX 480] from 171.64.65.69
07:36:46:WU03:FS00:Connecting to 171.64.65.69:8080
07:36:46:WU03:FS00:Downloading 4.18MiB
07:36:49:WU03:FS00:Download complete
07:36:49:WU03:FS00:Received Unit: id:03 state:DOWNLOAD error:NO_ERROR project:8900 run:294 clone:3 gen:43 core:0x17 unit:0x00000040028c126651a6680f910665fa
07:36:49:WU03:FS00:Starting
07:36:49:WU03:FS00:Running FahCore: "E:\Stanford FAH\FAHClient/FAHCoreWrapper.exe" "E:/Stanford FAH/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_17.fah/FahCore_17.exe" -dir 03 -suffix 01 -version 703 -lifeline 6268 -checkpoint 30 -gpu 0 -gpu-vendor nvidia
07:36:49:WU03:FS00:Started FahCore on PID 5456
07:36:49:WU03:FS00:Core PID:5504
07:36:49:WU03:FS00:FahCore 0x17 started
07:36:50:WU03:FS00:0x17:*********************** Log Started 2014-02-15T07:36:49Z ***********************
07:36:50:WU03:FS00:0x17:Project: 8900 (Run 294, Clone 3, Gen 43)
07:36:50:WU03:FS00:0x17:Unit: 0x00000040028c126651a6680f910665fa
07:36:50:WU03:FS00:0x17:CPU: 0x00000000000000000000000000000000
07:36:50:WU03:FS00:0x17:Machine: 0
07:36:50:WU03:FS00:0x17:Reading tar file state.xml
07:36:51:WU03:FS00:0x17:Reading tar file system.xml
07:36:51:WU03:FS00:0x17:Reading tar file integrator.xml
07:36:51:WU03:FS00:0x17:Reading tar file core.xml
07:36:51:WU03:FS00:0x17:Digital signatures verified
07:36:51:WU03:FS00:0x17:Folding@home GPU core17
07:36:51:WU03:FS00:0x17:Version 0.0.52
07:39:51:WU03:FS00:0x17:Completed 0 out of 2500000 steps (0%)
07:39:51:WU03:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
08:00:23:WU03:FS00:0x17:Completed 25000 out of 2500000 steps (1%)
08:01:33:WU03:FS00:0x17:ERROR:exception: The periodic box size has decreased to less than twice the nonbonded cutoff.
08:01:33:WU03:FS00:0x17:Saving result file logfile_01.txt
08:01:33:WU03:FS00:0x17:Saving result file log.txt
08:01:33:WU03:FS00:0x17:Folding@home Core Shutdown: BAD_WORK_UNIT
08:01:34:WARNING:WU03:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
08:01:34:WU03:FS00:Sending unit results: id:03 state:SEND error:FAULTY project:8900 run:294 clone:3 gen:43 core:0x17 unit:0x00000040028c126651a6680f910665fa
08:01:34:WU03:FS00:Uploading 2.50KiB to 171.64.65.69
08:01:34:WU03:FS00:Connecting to 171.64.65.69:8080
08:01:34:WU02:FS00:Connecting to assign-GPU.stanford.edu:80
08:01:34:WU03:FS00:Upload complete
08:01:34:WU03:FS00:Server responded WORK_ACK (400)
08:01:34:WU03:FS00:Cleaning up
08:01:35:WU02:FS00:News: Welcome to Folding@Home
08:01:35:WU02:FS00:Assigned to work server 171.64.65.69
08:01:35:WU02:FS00:Requesting new work unit for slot 00: READY gpu:0:GF100 [GeForce GTX 480] from 171.64.65.69
08:01:35:WU02:FS00:Connecting to 171.64.65.69:8080
08:01:35:WU02:FS00:Downloading 4.18MiB
08:01:38:WU02:FS00:Download complete
08:01:38:WU02:FS00:Received Unit: id:02 state:DOWNLOAD error:NO_ERROR project:8900 run:302 clone:0 gen:296 core:0x17 unit:0x0000017e028c126651a669c3592a8a93
08:01:38:WU02:FS00:Starting
08:01:38:WU02:FS00:Running FahCore: "E:\Stanford FAH\FAHClient/FAHCoreWrapper.exe" "E:/Stanford FAH/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_17.fah/FahCore_17.exe" -dir 02 -suffix 01 -version 703 -lifeline 6268 -checkpoint 30 -gpu 0 -gpu-vendor nvidia
08:01:38:WU02:FS00:Started FahCore on PID 4656
08:01:38:WU02:FS00:Core PID:5552
08:01:38:WU02:FS00:FahCore 0x17 started
08:01:39:WU02:FS00:0x17:*********************** Log Started 2014-02-15T08:01:38Z ***********************
08:01:39:WU02:FS00:0x17:Project: 8900 (Run 302, Clone 0, Gen 296)
08:01:39:WU02:FS00:0x17:Unit: 0x0000017e028c126651a669c3592a8a93
08:01:39:WU02:FS00:0x17:CPU: 0x00000000000000000000000000000000
08:01:39:WU02:FS00:0x17:Machine: 0
08:01:39:WU02:FS00:0x17:Reading tar file state.xml
08:01:39:WU02:FS00:0x17:Reading tar file system.xml
08:01:40:WU02:FS00:0x17:Reading tar file integrator.xml
08:01:40:WU02:FS00:0x17:Reading tar file core.xml
08:01:40:WU02:FS00:0x17:Digital signatures verified
08:01:40:WU02:FS00:0x17:Folding@home GPU core17
08:01:40:WU02:FS00:0x17:Version 0.0.52
08:04:45:WU02:FS00:0x17:Completed 0 out of 2500000 steps (0%)
08:04:45:WU02:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
08:25:12:WU02:FS00:0x17:Completed 25000 out of 2500000 steps (1%)
08:46:40:WU02:FS00:0x17:Completed 50000 out of 2500000 steps (2%)
08:46:41:WU02:FS00:0x17:Bad State detected... attempting to resume from last good checkpoint
08:46:44:WU02:FS00:0x17:ERROR:exception: First periodic box vector must be parallel to x.
08:46:44:WU02:FS00:0x17:Saving result file logfile_01.txt
08:46:44:WU02:FS00:0x17:Saving result file log.txt
08:46:44:WU02:FS00:0x17:Folding@home Core Shutdown: BAD_WORK_UNIT
08:46:47:WARNING:WU02:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
08:46:48:WU02:FS00:Sending unit results: id:02 state:SEND error:FAULTY project:8900 run:302 clone:0 gen:296 core:0x17 unit:0x0000017e028c126651a669c3592a8a93
08:46:48:WU02:FS00:Uploading 2.54KiB to 171.64.65.69
08:46:48:WU02:FS00:Connecting to 171.64.65.69:8080
08:46:48:WU02:FS00:Upload complete
08:46:48:WU02:FS00:Server responded WORK_ACK (400)
08:46:48:WU02:FS00:Cleaning up
******************************* Date: 2014-02-15 *******************************
14:23:06:FS00:Paused
14:24:27:FS00:Unpaused
14:24:27:FS00:Finishing
Re: I am having rampant failures with the newest NVIDIA driv
Posted: Sat Feb 15, 2014 4:01 pm
by PantherX
I haven't come across these errors before:
06:46:32:WU02:FS00:0x17:ERROR:exception: First periodic box vector must be parallel to x.
07:06:40:WU03:FS00:0x17:ERROR:exception: The periodic box size has decreased to less than twice the nonbonded cutoff.
I assume that it could successfully fold FahCore_15 WUs and now, is throwing up errors only on FahCore_17 WUs?