All fah programs = fahclient.exe, fahwrapper.exe, fahcontrol.exe, fahviewer.exe, fahcores... (although fahclient should be the only one needed to whitelist)
If bollix47's suggestion does work, we need to look in to what is being whitelisted and how. By file, by process, and/or by protocol (IP), etc.
GPU WU issues spreading to CPU WUs
Moderators: Site Moderators, FAHC Science Team
-
7im
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: GPU WU issues spreading to CPU WUs
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: GPU WU issues spreading to CPU WUs
I am not happy with the idea of completely uninstalling ZoneAlarm even for a test without some concrete reason as to why ZA is the culprit.
When ZoneAlarm is stopped, it's stopped. I looked at the processes and services lists in Task Manager, not just the application list.
If the firewall was the problem why would it work some of the time and not others. At boot up ZoneAlarm blocks all internet access until it is fully installed. Since I ALWAYS get a new WU after a reboot, I think we can rule out ZoneAlarm
MSE is NOT running. I know better than that. I have been playing around with these little beasties for 31 years now.
Here is an odd occurrence in the log file that just happened. It looks like I was given a bad WU.
When ZoneAlarm is stopped, it's stopped. I looked at the processes and services lists in Task Manager, not just the application list.
If the firewall was the problem why would it work some of the time and not others. At boot up ZoneAlarm blocks all internet access until it is fully installed. Since I ALWAYS get a new WU after a reboot, I think we can rule out ZoneAlarm
MSE is NOT running. I know better than that. I have been playing around with these little beasties for 31 years now.
Here is an odd occurrence in the log file that just happened. It looks like I was given a bad WU.
Code: Select all
22:09:03:WU01:FS00:0x17:Completed 2400000 out of 2500000 steps (96%)
22:12:11:WU02:FS01:0xa3:Completed 350000 out of 500000 steps (70%)
22:13:39:WU01:FS00:0x17:Completed 2425000 out of 2500000 steps (97%)
22:18:00:WU01:FS00:0x17:Completed 2450000 out of 2500000 steps (98%)
22:18:01:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
22:18:01:WU00:FS00:News: Welcome to Folding@Home
22:18:01:WU00:FS00:Assigned to work server 171.64.65.69
22:18:01:WU00:FS00:Requesting new work unit for slot 00: RUNNING gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:18:01:WU00:FS00:Connecting to 171.64.65.69:8080
22:18:05:WU00:FS00:Downloading 4.18MiB
22:18:05:ERROR:WU00:FS00:Exception: Transfer failed
22:18:05:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
22:18:06:WU00:FS00:News: Welcome to Folding@Home
22:18:06:WU00:FS00:Assigned to work server 171.64.65.69
22:18:06:WU00:FS00:Requesting new work unit for slot 00: RUNNING gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:18:06:WU00:FS00:Connecting to 171.64.65.69:8080
22:18:09:ERROR:WU00:FS00:Exception: Server did not assign work unit
22:19:05:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
22:19:06:WU00:FS00:News: Welcome to Folding@Home
22:19:06:WU00:FS00:Assigned to work server 171.64.65.69
22:19:06:WU00:FS00:Requesting new work unit for slot 00: RUNNING gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:19:06:WU00:FS00:Connecting to 171.64.65.69:8080
22:19:09:WU00:FS00:Downloading 4.17MiB
22:19:09:WU00:FS00:Download complete
22:19:09:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:8900 run:313 clone:7 gen:3 core:0x17 unit:0x00000008028c126651a66c5fd2ba514d
22:22:36:WU02:FS01:0xa3:Completed 355000 out of 500000 steps (71%)
22:22:38:WU01:FS00:0x17:Completed 2475000 out of 2500000 steps (99%)
22:27:06:WU01:FS00:0x17:Completed 2500000 out of 2500000 steps (100%)
22:27:22:WU01:FS00:0x17:Saving result file logfile_01.txt
22:27:22:WU01:FS00:0x17:Saving result file checkpointState.xml
22:27:24:WU01:FS00:0x17:Saving result file checkpt.crc
22:27:24:WU01:FS00:0x17:Saving result file log.txt
22:27:24:WU01:FS00:0x17:Saving result file positions.xtc
22:27:26:WU01:FS00:0x17:Folding@home Core Shutdown: FINISHED_UNIT
22:27:27:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
22:27:27:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:8900 run:628 clone:5 gen:10 core:0x17 unit:0x00000013028c126651a6b267bd9df65f
22:27:27:WU01:FS00:Uploading 12.96MiB to 171.64.65.69
22:27:27:WU00:FS00:Starting
22:27:27:WU01:FS00:Connecting to 171.64.65.69:8080
22:27:27:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" "C:/Users/Edward Rodman/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe" -dir 00 -suffix 01 -version 703 -lifeline 4292 -checkpoint 15 -gpu 0 -gpu-vendor ati
22:27:27:WU00:FS00:Started FahCore on PID 8120
22:27:27:WU00:FS00:Core PID:7412
22:27:27:WU00:FS00:FahCore 0x17 started
22:27:28:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
22:27:28:WU00:FS00:Sending unit results: id:00 state:SEND error:FAULTY project:8900 run:313 clone:7 gen:3 core:0x17 unit:0x00000008028c126651a66c5fd2ba514d
22:27:28:WU00:FS00:Uploading 1021B to 171.64.65.69
22:27:28:WU00:FS00:Connecting to 171.64.65.69:8080
22:27:28:WU03:FS00:Connecting to assign-GPU.stanford.edu:80
22:27:28:WU00:FS00:Upload complete
22:27:28:WU00:FS00:Server responded WORK_ACK (400)
22:27:28:WU00:FS00:Cleaning up
22:27:28:WU03:FS00:News: Welcome to Folding@Home
22:27:28:WU03:FS00:Assigned to work server 171.64.65.69
22:27:28:WU03:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:27:28:WU03:FS00:Connecting to 171.64.65.69:8080
22:27:32:WU03:FS00:Downloading 4.18MiB
22:27:32:ERROR:WU03:FS00:Exception: Transfer failed
22:27:32:WU03:FS00:Connecting to assign-GPU.stanford.edu:80
22:27:33:WU01:FS00:Upload 10.12%
22:27:33:WU03:FS00:News: Welcome to Folding@Home
22:27:33:WU03:FS00:Assigned to work server 171.64.65.69
22:27:33:WU03:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:27:33:WU03:FS00:Connecting to 171.64.65.69:8080
22:27:39:WU01:FS00:Upload 21.21%
22:27:41:WU03:FS00:Downloading 4.18MiB
22:27:41:ERROR:WU03:FS00:Exception: Transfer failed
22:27:45:WU01:FS00:Upload 29.89%
22:27:51:WU01:FS00:Upload 41.46%
22:27:57:WU01:FS00:Upload 52.07%
22:28:03:WU01:FS00:Upload 62.19%
22:28:09:WU01:FS00:Upload 71.83%
22:28:15:WU01:FS00:Upload 82.92%
22:28:21:WU01:FS00:Upload 93.52%
22:28:32:WU03:FS00:Connecting to assign-GPU.stanford.edu:80
22:28:33:WU01:FS00:Upload complete
22:28:33:WU01:FS00:Server responded WORK_ACK (400)
22:28:33:WU01:FS00:Final credit estimate, 26178.00 points
22:28:33:WU01:FS00:Cleaning up
22:28:33:WU03:FS00:News: Welcome to Folding@Home
22:28:33:WU03:FS00:Assigned to work server 171.64.65.69
22:28:33:WU03:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:28:33:WU03:FS00:Connecting to 171.64.65.69:8080
22:28:36:WU03:FS00:Downloading 4.17MiB
22:28:36:WU03:FS00:Download complete
22:28:37:WU03:FS00:Received Unit: id:03 state:DOWNLOAD error:NO_ERROR project:8900 run:628 clone:5 gen:11 core:0x17 unit:0x00000014028c126651a6b267bd9df65f
22:28:37:WU03:FS00:Starting
22:28:37:WU03:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" "C:/Users/Edward Rodman/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe" -dir 03 -suffix 01 -version 703 -lifeline 4292 -checkpoint 15 -gpu 0 -gpu-vendor ati
22:28:37:WU03:FS00:Started FahCore on PID 7948
22:28:37:WU03:FS00:Core PID:8072
22:28:37:WU03:FS00:FahCore 0x17 started
22:28:37:WU03:FS00:0x17:*********************** Log Started 2013-11-27T22:28:37Z ***********************
22:28:37:WU03:FS00:0x17:Project: 8900 (Run 628, Clone 5, Gen 11)
22:28:37:WU03:FS00:0x17:Unit: 0x00000014028c126651a6b267bd9df65f
22:28:37:WU03:FS00:0x17:CPU: 0x00000000000000000000000000000000
22:28:37:WU03:FS00:0x17:Machine: 0
22:28:37:WU03:FS00:0x17:ERROR:112: calculated hash = 1aa53983-ecc45380-88b667df-c7a45a38-553da852
22:28:37:WU03:FS00:0x17:ERROR:work unit hash = 1415ff6d-617b3eff-446a886c-bd144c1f-1a72e6ee
22:28:37:WU03:FS00:0x17:ERROR:Bad work unit. Digital signatures don't match
22:28:37:WU03:FS00:0x17:Saving result file logfile_01.txt
22:28:37:WU03:FS00:0x17:Saving result file log.txt
22:28:37:WU03:FS00:0x17:Folding@home Core Shutdown: BAD_WORK_UNIT
22:28:37:WARNING:WU03:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
22:28:37:WU03:FS00:Sending unit results: id:03 state:SEND error:FAULTY project:8900 run:628 clone:5 gen:11 core:0x17 unit:0x00000014028c126651a6b267bd9df65f
22:28:38:WU03:FS00:Uploading 1.00KiB to 171.64.65.69
22:28:38:WU03:FS00:Connecting to 171.64.65.69:8080
22:28:38:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
22:28:38:WU03:FS00:Upload complete
22:28:38:WU03:FS00:Server responded WORK_ACK (400)
22:28:38:WU03:FS00:Cleaning up
22:28:39:WU00:FS00:News: Welcome to Folding@Home
22:28:39:WU00:FS00:Assigned to work server 171.64.65.69
22:28:39:WU00:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:28:39:WU00:FS00:Connecting to 171.64.65.69:8080
22:28:42:WU00:FS00:Downloading 4.18MiB
22:28:42:WU00:FS00:Download complete
22:28:42:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:8900 run:266 clone:0 gen:257 core:0x17 unit:0x0000012d028c126651a661bb618e52fa
22:28:42:WU00:FS00:Starting
22:28:42:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" "C:/Users/Edward Rodman/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe" -dir 00 -suffix 01 -version 703 -lifeline 4292 -checkpoint 15 -gpu 0 -gpu-vendor ati
22:28:42:WU00:FS00:Started FahCore on PID 5836
22:28:42:WU00:FS00:Core PID:7560
22:28:42:WU00:FS00:FahCore 0x17 started
22:28:43:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
22:28:43:WU00:FS00:Sending unit results: id:00 state:SEND error:FAULTY project:8900 run:266 clone:0 gen:257 core:0x17 unit:0x0000012d028c126651a661bb618e52fa
22:28:43:WU00:FS00:Uploading 1023B to 171.64.65.69
22:28:43:WU00:FS00:Connecting to 171.64.65.69:8080
22:28:43:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:28:43:WU00:FS00:Upload complete
22:28:43:WU00:FS00:Server responded WORK_ACK (400)
22:28:43:WU00:FS00:Cleaning up
22:28:44:WU01:FS00:News: Welcome to Folding@Home
22:28:44:WU01:FS00:Assigned to work server 171.64.65.69
22:28:44:WU01:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:28:44:WU01:FS00:Connecting to 171.64.65.69:8080
22:28:47:WU01:FS00:Downloading 4.18MiB
22:28:48:ERROR:WU01:FS00:Exception: Transfer failed
22:28:48:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:28:48:WU01:FS00:News: Welcome to Folding@Home
22:28:48:WU01:FS00:Assigned to work server 171.64.65.69
22:28:48:WU01:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:28:48:WU01:FS00:Connecting to 171.64.65.69:8080
22:28:52:WU01:FS00:Downloading 4.17MiB
22:28:52:ERROR:WU01:FS00:Exception: Transfer failed
22:29:48:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:29:48:WU01:FS00:News: Welcome to Folding@Home
22:29:48:WU01:FS00:Assigned to work server 171.64.65.69
22:29:48:WU01:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:29:48:WU01:FS00:Connecting to 171.64.65.69:8080
22:29:52:ERROR:WU01:FS00:Exception: Server did not assign work unit
22:31:25:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:31:25:WU01:FS00:News: Welcome to Folding@Home
22:31:25:WU01:FS00:Assigned to work server 171.64.65.69
22:31:25:WU01:FS00:Requesting new work unit for slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970] from 171.64.65.69
22:31:25:WU01:FS00:Connecting to 171.64.65.69:8080
22:31:29:WU01:FS00:Downloading 4.18MiB
22:31:29:WU01:FS00:Download complete
22:31:29:WU01:FS00:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:8900 run:783 clone:7 gen:7 core:0x17 unit:0x00000011028c126651a6d4f4ed183400
22:31:29:WU01:FS00:Starting
22:31:29:WU01:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" "C:/Users/Edward Rodman/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe" -dir 01 -suffix 01 -version 703 -lifeline 4292 -checkpoint 15 -gpu 0 -gpu-vendor ati
22:31:29:WU01:FS00:Started FahCore on PID 6756
22:31:29:WU01:FS00:Core PID:7324
22:31:29:WU01:FS00:FahCore 0x17 started
22:31:30:WU01:FS00:0x17:*********************** Log Started 2013-11-27T22:31:29Z ***********************
22:31:30:WU01:FS00:0x17:Project: 8900 (Run 783, Clone 7, Gen 7)
22:31:30:WU01:FS00:0x17:Unit: 0x00000011028c126651a6d4f4ed183400
22:31:30:WU01:FS00:0x17:CPU: 0x00000000000000000000000000000000
22:31:30:WU01:FS00:0x17:Machine: 0
22:31:30:WU01:FS00:0x17:Reading tar file state.xml
22:31:30:WU01:FS00:0x17:Reading tar file system.xml
22:31:31:WU01:FS00:0x17:Reading tar file integrator.xml
22:31:31:WU01:FS00:0x17:Reading tar file core.xml
22:31:31:WU01:FS00:0x17:Digital signatures verified
22:31:31:WU01:FS00:0x17:Folding@home GPU core17
22:31:31:WU01:FS00:0x17:Version 0.0.52
22:34:15:WU01:FS00:0x17:Completed 0 out of 2500000 steps (0%)
22:34:15:WU02:FS01:0xa3:Completed 360000 out of 500000 steps (72%)
22:34:15:WU01:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
22:38:53:WU01:FS00:0x17:Completed 25000 out of 2500000 steps (1%)
-
7im
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: GPU WU issues spreading to CPU WUs
Basically it comes down to this. If the client was the problem, we would have 100s of reports of this problem. If the servers were the problem, we would have 1000s of reports of this problem. So far, in running v7 for a year, we have 1 report of this issue. This points to a localized problem.
Clearly you are running fah on more than one PC. How many of the other PCs are using the V7 client and the ZA suite?
Clearly you are running fah on more than one PC. How many of the other PCs are using the V7 client and the ZA suite?
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: GPU WU issues spreading to CPU WUs
If you need reasons why, type zonealarm in the F@H search box at the top of every forum page and you will see pages of posts discussing ZA problems and some of those posters tried just disabling it but it wasn't until they uninstalled it that their problems went away.
Re: GPU WU issues spreading to CPU WUs
Fundamentally, ZA is a very sophisticated firewall which is very good at blocking things, even when you don't want it to. It can identify FAHClient and prevent it from creating a connection to the internet. You can add an exception permitting FAHClient to make that connection, but if you then install a new version, it recognizes that FAHClient.exe is not the same copy of FAHClient.exe and you'll have to add a new exception. There may be other semi-related issues -- we're not experts in firewall functionality.
You don't have to turn off ZA, but you will have to deal with a period of re-validation of what it's blocking and decide if it's doing what you want it to do. There's a setting in ZA which will open a popup every time something is blocked. It is undoubtedly turned off or you'd be spending a lot of time answering questions about whether you want to permit or block various things. Turn that setting on. When FAH attempts to get a new WU but fails, was there a ZA popup and if so, what did you answer?
You don't have to turn off ZA, but you will have to deal with a period of re-validation of what it's blocking and decide if it's doing what you want it to do. There's a setting in ZA which will open a popup every time something is blocked. It is undoubtedly turned off or you'd be spending a lot of time answering questions about whether you want to permit or block various things. Turn that setting on. When FAH attempts to get a new WU but fails, was there a ZA popup and if so, what did you answer?
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
PantherX
- Site Moderator
- Posts: 6986
- 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:
Re: GPU WU issues spreading to CPU WUs
If you are indeed having another PC folding which isn't encountering this issue, then please identify all the differences between the two set-ups. It would help us narrow down the list and hopefully, determine the root cause and fix it permanently.7im wrote:...Clearly you are running fah on more than one PC. How many of the other PCs are using the V7 client and the ZA suite?
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
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
Re: GPU WU issues spreading to CPU WUs
All three PC are running licensed copies of ZoneAlarm and F@HClient 7.3.6.
The wife's computer has an NVIDIA Graphics card and a 4 core CPU.
The third one is an old machine that only folds on a 2 core CPU and does nothing else.
So far I have been getting WUs normally for the past 24 hours with no recent changes to my system other than a Windows update yesterday morning.
Happy Thanksgiving y'all. Thanksgiving is a real family story for us. I had 7 ancestors on the Mayflower. Since I am now the oldest, I get to tell the story each year.
The wife's computer has an NVIDIA Graphics card and a 4 core CPU.
The third one is an old machine that only folds on a 2 core CPU and does nothing else.
So far I have been getting WUs normally for the past 24 hours with no recent changes to my system other than a Windows update yesterday morning.
Happy Thanksgiving y'all. Thanksgiving is a real family story for us. I had 7 ancestors on the Mayflower. Since I am now the oldest, I get to tell the story each year.
-
7im
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: GPU WU issues spreading to CPU WUs
After a WU has been folding for hours, the system is at it's warmest...
I know one or two things that are different after a reboot. The PC is cooler, and all the memory has been flushed. There may be a stability issue with this computer causing data corruptions, possibly caused by heat. Or there may be a loose connection. It's time to open the PC and check for loose cables, loose memory chips, etc. Then clean it out, and run a memtest session on it. And check the CPU/system temps.
I know one or two things that are different after a reboot. The PC is cooler, and all the memory has been flushed. There may be a stability issue with this computer causing data corruptions, possibly caused by heat. Or there may be a loose connection. It's time to open the PC and check for loose cables, loose memory chips, etc. Then clean it out, and run a memtest session on it. And check the CPU/system temps.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: GPU WU issues spreading to CPU WUs
7im,
How you flushed memory on my computer affect whether or not the server 3000 miles away issues a WU
My computer is brand new as of 9/7/2013. It has four cooling fans and additional cooling for the GPU. Even at 100% usage, none of my CPU cores exceed 61C. My GPU does not exceed 74C under full load.
I have no other computer usage issues outside of the timely receipt of WUs and third parties trying to install tool bars and redirect my browser homepage every time I install something.
I built my first PC in 1982 and have been dealing with them ever since. I keep my PCs clean and well off the floor to reduce dust and airflow issues. Cards, cables, etc. stay screwed down where appropriate. It can be a pain at cleaning time but I don't get loose connections.
How you flushed memory on my computer affect whether or not the server 3000 miles away issues a WU
My computer is brand new as of 9/7/2013. It has four cooling fans and additional cooling for the GPU. Even at 100% usage, none of my CPU cores exceed 61C. My GPU does not exceed 74C under full load.
I have no other computer usage issues outside of the timely receipt of WUs and third parties trying to install tool bars and redirect my browser homepage every time I install something.
I built my first PC in 1982 and have been dealing with them ever since. I keep my PCs clean and well off the floor to reduce dust and airflow issues. Cards, cables, etc. stay screwed down where appropriate. It can be a pain at cleaning time but I don't get loose connections.
Re: GPU WU issues spreading to CPU WUs
We don't need any arguments about who is right and who is wrong. You two have different opinions and we don't need to know about them.
Topic closed.
Topic closed.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.