Aktuelle Probleme auf einen Blick

Soll heißen, daß Du ohne Neuinstallation umgezogen bist ? Welches Betriebssystem ? Treiber sauber deinstalliert und neu drauf gezogen ?
 
phila_delphia schrieb:
Mein Inernet "tut" aber mein f@h client bekommt keine Verbingung..

Grüßephila
Zum Vergrößern anklicken....

Du meinst das hier ?

06:19:06:Trying to access database...06:19:06:Successfully acquired database lock
06:19:06:Enabled folding slot 01: READY gpu:0:TU116 [GeForce GTX 1660]
06:19:07:WU00:FS01:Connecting to 65.254.110.245:80
06:19:08:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration
06:19:08:WU00:FS01:Connecting to 18.218.241.186:80
06:19:08:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:19:08:WU00:FS01:Connecting to 65.254.110.245:80
06:19:09:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration
06:19:09:WU00:FS01:Connecting to 18.218.241.186:80
06:19:10:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:19:10:ERROR:WU00:FS01:Exception: Could not get an assignment
06:19:10:WU00:FS01:Connecting to 65.254.110.245:80
06:19:10:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration
06:19:10:WU00:FS01:Connecting to 18.218.241.186:80
06:19:11:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:19:11:WU00:FS01:Connecting to 65.254.110.245:80
06:19:11:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration
06:19:11:WU00:FS01:Connecting to 18.218.241.186:80
06:19:11:WU00:FS01:Assigned to work server 13.82.98.119
06:19:11:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:TU116 [GeForce GTX 1660] from 13.82.98.119
06:19:11:WU00:FS01:Connecting to 13.82.98.119:8080

Ist "normal" seit ein paar Wochen. Stanford kommt mit den WUs nicht nach, die Nachfrage ist deutlich größer als das Angebot. Einfach laufen lassen ... ;)
 
Moin.
Ich habe seit einer Woche das Problem das die Auslastung meiner 1080ti während des Berechnen einer WU irgendwann bei der Auslastung nur noch 70% des PL ausschöpft, wenn ich pausiere und den Rechner neustarte läuft die GTX wieder eine Weile mit knapp 100% PL. Hierunter leidet dann natürlich die Geschwindigkeit und Dauer mit der die WU berechnet wird und die Punkteausbeute. Hat hier jemand eine Idee?
 
ich hatte heute von 04:42 bis 04:46 und nochmals um 11:35 6 WUs mit demselben fehler ERROR:exception: Called setPositions() on a Context with the wrong number of positions

04:42:35:WU00:FS01:0x22:Project: 14460 (Run 0, Clone 908, Gen 66)
04:42:35:WU00:FS01:0x22:Unit: 0x0000006a03854c135eb39e44a6369377
04:42:35:WU00:FS01:0x22:Reading tar file core.xml
04:42:35:WU00:FS01:0x22:Reading tar file integrator.xml
04:42:35:WU00:FS01:0x22:Reading tar file state.xml
04:42:36:WU00:FS01:0x22:Reading tar file system.xml
04:42:37:WU00:FS01:0x22:Digital signatures verified
04:42:37:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
04:42:37:WU00:FS01:0x22:Version 0.0.10
04:42:37:WU00:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
04:42:37:WU00:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
04:42:37:WU00:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
04:42:37:WU00:FS01:0x22: Global context and integrator variables write interval: disabled
04:42:49:WU00:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
04:42:49:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
04:42:49:WU00:FS01:0x22:Saving result file science.log
04:42:49:WU00:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
04:42:50:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
04:42:50:WU00:FS01:Sending unit results: id:00 state:SEND error:FAULTY project:14460 run:0 clone:908 gen:66 core:0x22 unit:0x0000006a03854c135eb39e44a6369377


04:43:10:WU02:FS01:0x22:Project: 14451 (Run 0, Clone 1878, Gen 64)
04:43:10:WU02:FS01:0x22:Unit: 0x0000006b03854c135eac4acfc8905a21
04:43:10:WU02:FS01:0x22:Reading tar file core.xml
04:43:10:WU02:FS01:0x22:Reading tar file integrator.xml
04:43:10:WU02:FS01:0x22:Reading tar file state.xml
04:43:10:WU02:FS01:0x22:Reading tar file system.xml
04:43:11:WU02:FS01:0x22:Digital signatures verified
04:43:11:WU02:FS01:0x22:Folding@home GPU Core22 Folding@home Core
04:43:11:WU02:FS01:0x22:Version 0.0.10
04:43:11:WU02:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
04:43:11:WU02:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
04:43:11:WU02:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
04:43:11:WU02:FS01:0x22: Global context and integrator variables write interval: disabled
04:43:23:WU02:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
04:43:23:WU02:FS01:0x22:Saving result file ..\logfile_01.txt
04:43:23:WU02:FS01:0x22:Saving result file science.log
04:43:23:WU02:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
04:43:23:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
04:43:23:WU02:FS01:Sending unit results: id:02 state:SEND error:FAULTY project:14451 run:0 clone:1878 gen:64 core:0x22 unit:0x0000006b03854c135eac4acfc8905a21



04:43:42:WU00:FS01:0x22:Project: 14466 (Run 0, Clone 82, Gen 44)
04:43:42:WU00:FS01:0x22:Unit: 0x0000004903854c135eb9852eca78f749
04:43:42:WU00:FS01:0x22:Reading tar file core.xml
04:43:42:WU00:FS01:0x22:Reading tar file integrator.xml
04:43:42:WU00:FS01:0x22:Reading tar file state.xml
04:43:43:WU00:FS01:0x22:Reading tar file system.xml
04:43:43:WU00:FS01:0x22:Digital signatures verified
04:43:43:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
04:43:43:WU00:FS01:0x22:Version 0.0.10
04:43:43:WU00:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
04:43:43:WU00:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
04:43:43:WU00:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
04:43:43:WU00:FS01:0x22: Global context and integrator variables write interval: disabled
04:43:55:WU00:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
04:43:55:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
04:43:55:WU00:FS01:0x22:Saving result file science.log
04:43:55:WU00:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
04:43:56:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
04:43:56:WU00:FS01:Sending unit results: id:00 state:SEND error:FAULTY project:14466 run:0 clone:82 gen:44 core:0x22 unit:0x0000004903854c135eb9852eca78f749



04:44:17:WU02:FS01:0x22:Project: 14446 (Run 0, Clone 1000, Gen 43)
04:44:17:WU02:FS01:0x22:Unit: 0x0000005203854c135ea7b890a5d6cb39
04:44:17:WU02:FS01:0x22:Reading tar file core.xml
04:44:17:WU02:FS01:0x22:Reading tar file integrator.xml
04:44:17:WU02:FS01:0x22:Reading tar file state.xml
04:44:18:WU02:FS01:0x22:Reading tar file system.xml
04:44:19:WU02:FS01:0x22:Digital signatures verified
04:44:19:WU02:FS01:0x22:Folding@home GPU Core22 Folding@home Core
04:44:19:WU02:FS01:0x22:Version 0.0.10
04:44:19:WU02:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
04:44:19:WU02:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
04:44:19:WU02:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
04:44:19:WU02:FS01:0x22: Global context and integrator variables write interval: disabled
04:44:31:WU02:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
04:44:31:WU02:FS01:0x22:Saving result file ..\logfile_01.txt
04:44:31:WU02:FS01:0x22:Saving result file science.log
04:44:31:WU02:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
04:44:32:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
04:44:32:WU02:FS01:Sending unit results: id:02 state:SEND error:FAULTY project:14446 run:0 clone:1000 gen:43 core:0x22 unit:0x0000005203854c135ea7b890a5d6cb39



04:44:54:WU00:FS01:0x22:Project: 14465 (Run 0, Clone 288, Gen 47)
04:44:54:WU00:FS01:0x22:Unit: 0x0000004903854c135eb9853239dc8c98
04:44:54:WU00:FS01:0x22:Reading tar file core.xml
04:44:54:WU00:FS01:0x22:Reading tar file integrator.xml
04:44:54:WU00:FS01:0x22:Reading tar file state.xml
04:44:55:WU00:FS01:0x22:Reading tar file system.xml
04:44:55:WU00:FS01:0x22:Digital signatures verified
04:44:55:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
04:44:55:WU00:FS01:0x22:Version 0.0.10
04:44:55:WU00:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
04:44:55:WU00:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
04:44:55:WU00:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
04:44:55:WU00:FS01:0x22: Global context and integrator variables write interval: disabled

04:44:58:WU01:FS01:Upload complete
04:44:58:WU01:FS01:Server responded WORK_QUIT (404)
04:44:58:WARNING:WU01:FS01:Server did not like results, dumping
04:44:58:WU01:FS01:Cleaning up

04:45:07:WU00:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
04:45:07:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
04:45:07:WU00:FS01:0x22:Saving result file science.log
04:45:07:WU00:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
04:45:07:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
04:45:07:WU00:FS01:Sending unit results: id:00 state:SEND error:FAULTY project:14465 run:0 clone:288 gen:47 core:0x22 unit:0x0000004903854c135eb9853239dc8c98



04:46:21:WU01:FS01:0x22:Project: 14465 (Run 0, Clone 463, Gen 46)
04:46:21:WU01:FS01:0x22:Unit: 0x0000005103854c135eb985320a9f0597
04:46:21:WU01:FS01:0x22:Reading tar file core.xml
04:46:21:WU01:FS01:0x22:Reading tar file integrator.xml
04:46:21:WU01:FS01:0x22:Reading tar file state.xml
04:46:22:WU01:FS01:0x22:Reading tar file system.xml
04:46:23:WU01:FS01:0x22:Digital signatures verified
04:46:23:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
04:46:23:WU01:FS01:0x22:Version 0.0.10
04:46:23:WU01:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
04:46:23:WU01:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
04:46:23:WU01:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
04:46:23:WU01:FS01:0x22: Global context and integrator variables write interval: disabled
04:46:34:WU01:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
04:46:34:WU01:FS01:0x22:Saving result file ..\logfile_01.txt
04:46:34:WU01:FS01:0x22:Saving result file science.log
04:46:34:WU01:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
04:46:35:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
04:46:35:WU01:FS01:Sending unit results: id:01 state:SEND error:FAULTY project:14465 run:0 clone:463 gen:46 core:0x22 unit:0x0000005103854c135eb985320a9f0597



11:35:36:WU01:FS01:0x22:Project: 14469 (Run 0, Clone 1651, Gen 12)
11:35:36:WU01:FS01:0x22:Unit: 0x0000001203854c135eb98530ce070231
11:35:36:WU01:FS01:0x22:Reading tar file core.xml
11:35:36:WU01:FS01:0x22:Reading tar file integrator.xml
11:35:36:WU01:FS01:0x22:Reading tar file state.xml
11:35:36:WU01:FS01:0x22:Reading tar file system.xml
11:35:37:WU01:FS01:0x22:Digital signatures verified
11:35:37:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
11:35:37:WU01:FS01:0x22:Version 0.0.11
11:35:37:WU01:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
11:35:37:WU01:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
11:35:37:WU01:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
11:35:37:WU01:FS01:0x22: Global context and integrator variables write interval: disabled
11:35:48:WU01:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
11:35:48:WU01:FS01:0x22:Saving result file ..\logfile_01.txt
11:35:48:WU01:FS01:0x22:Saving result file science.log
11:35:48:WU01:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
11:35:49:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
11:35:49:WU01:FS01:Sending unit results: id:01 state:SEND error:FAULTY project:14469 run:0 clone:1651 gen:12 core:0x22 unit:0x0000001203854c135eb98530ce070231
 
Den hatte ich auch, kann laut dem offiziellen Support Forum am ausrollen von Core 22.0.0.11 liegen. Vor allem Multi-GPU Systeme hatte da wohl Fehler, wenn nicht alle Cores zeitgleich auf idle waren. Jetzt läuft er mit 22.0.0.11 auf jeden Fall wieder sehr gut.
 
leider habe ich auch mit 22.0.0.11 bereits wieder 2 BAD_WORK_UNITs auf dem einen und 5 auf dem andern system und ich habe momentan je nur eine GraKa drin - da scheint immer noch ein kleiner wurm drin zu sein

21:36:43:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
21:36:43:WU00:FS01:0x22:Version 0.0.11
21:36:43:WU00:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
21:36:43:WU00:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
21:36:43:WU00:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
21:36:43:WU00:FS01:0x22: Global context and integrator variables write interval: disabled
21:36:55:WU00:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
21:36:55:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
21:36:55:WU00:FS01:0x22:Saving result file science.log
21:36:55:WU00:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
21:36:55:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
21:36:55:WU00:FS01:Sending unit results: id:00 state:SEND error:FAULTY project:14441 run:0 clone:1583 gen:33 core:0x22 unit:0x0000003603854c135ea0a3000a7611bf

23:41:06:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
23:41:06:WU00:FS01:0x22:Version 0.0.11
23:41:06:WU00:FS01:0x22: Checkpoint write interval: 100000 steps (5%) [20 total]
23:41:06:WU00:FS01:0x22: JSON viewer frame write interval: 20000 steps (1%) [100 total]
23:41:06:WU00:FS01:0x22: XTC frame write interval: 20000 steps (1%) [100 total]
23:41:06:WU00:FS01:0x22: Global context and integrator variables write interval: disabled
23:41:18:WU00:FS01:0x22:ERROR:exception: Called setPositions() on a Context with the wrong number of positions
23:41:18:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
23:41:18:WU00:FS01:0x22:Saving result file science.log
23:41:18:WU00:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
23:41:18:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
23:41:18:WU00:FS01:Sending unit results: id:00 state:SEND error:FAULTY project:14460 run:0 clone:449 gen:54 core:0x22 unit:0x0000005a03854c135eb39e44d188a04b
 
Guten Morgen in die Runde. Habt Ihr auf euren nVidia Karten auch aktuell nur eine GPU Last von 70-75%? Hab das Phänomen seit ungefähr anderthalb Tagen wieder. Sowohl die 2070 als auch die 2080 bekommen laut MSI Afterburner nur eine GPU Last von den besagten Prozenten. Ansonsten ist alles unverändert. Dabei handelt es sich sowohl um 13416'er und 16909 Projekte... die PPD gehen natürlich entsprechend down... auf der 2070 z.B. statt 1,7 Mio PPD nur noch 820k PPD...

Wollt nur mal wissen ob ich damit nicht alleine bin?! ;-)
 
Same here mit 5700XT. Habe sonst 1,25 Mio. PPD und mit gerade 13416 nur 75-80 % Auslastung und 800k PPD. Stromverbrauch ist zumindest auch gesunken (auf 90 W + 5 W Speicher). Hin und wieder gibt es halt so Flauten WUs.
 
Das Problem habe ich aktuell auch auf allen 5700xt. Die 13416er Projekte lasten zwar 80-90% aus, aber die PPD liegen trotzdem nur bei ca. 900k.
Es handelt sich dabei aber wohl auch wieder um experimentelle Projekte, ich schau mal im offiziellen Forum.
 
Bumblebee schrieb:
Eigentlich kein Trost aber schaut euch mal meine Resultate von gestern an....
Die 13416er Projekte (jedenfalls ein Teil davon) laufen auch auf N-VIDIA-Karten unterirdisch
Zum Vergrößern anklicken....

Alter Falter, das nenn ich mal nen Punkteabsturz (das machen andere in nem ganzen Monat nicht, was bei dir nur das Minusdelta ausmacht) ;-)
Aber dann gehen wir einfach mal davon aus, dass es alle betrifft und somit alles wieder relativ ist :-)
 
Einloggen o. Registrieren zum Antworten.

Ähnliche Themen

PCGH-Redaktion
News Steam Deck OLED: Riesige Nachfrage stellt Valve und Steam vor Probleme
3 4 5
Antworten
87
Aufrufe
5K
Capucius
Capucius
B
Lags und weitere Probleme
Antworten
3
Aufrufe
922
Eol_Ruin
Eol_Ruin
Z
Probleme mit Razer Deathadder Maus / Razer Synapse Software
Antworten
0
Aufrufe
770
ZuIR4m
Z
V
Wer kann auf einer aktuellen 500+x € CPU einen Benchmark durchführen? (Benchmark einer Stundenplan-Software)
Antworten
2
Aufrufe
10K
Volker_D
V
E
Ideen Sammelung F&H
2
Antworten
31
Aufrufe
18K
Ellina
E
Oben Unten
Zurück