rpi_logo
Posts by Sebastian*
Posts by Sebastian*
log in
1) Message boards : News : GPU Issues Mega Thread (Message 66172)
Posted 10 Feb 2017 by Sebastian*
Hello again, and a happy new year to everybody.

I still got issues when running several WUs in parallel on the Hawaii bases GPUs. One WU at a time still runs fine.

Could someone look at my invalid WUs with the Validate errors. I can't make anything out of the text.

https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=705276&offset=0&show_names=0&state=5&appid=

Maybe some can help me figure out what is broken.

AMD drivers have improved, the WUs don't hang any longer, but there are still Validate errors.
2) Message boards : News : Scheduled Maintenance Concluded (Message 65869)
Posted 16 Nov 2016 by Sebastian*
Hello everyone,

Is anyone running a 390 or 390X (290 or 290x may have the same problem)

I still have the problem, when i run several WUs at once, then after some time (from minutes to one hour or so) some WUs start to hang, and go on for ever, while one or two crunch on.

I have tested drivers since 15.9, always the same problem, win 7 or win10 does not matter either. Tried different hardware setups, new installations of windows or old ones no difference.

I hope someone can confirm the problem, so we can start searching for the root cause and maybe even a fix.

PS. Running on the 280X or 7970 doesn't give me the error. Also running one WU at a time is fine.
Running 2 Einstein@home WUs at the same time causes calculation error (invalid tasks)
3) Message boards : News : Updated Server Daemons and Libraries (Message 65586)
Posted 3 Nov 2016 by Sebastian*
Hi everyone,

does anyone experience similar problems as i do?

Hardware, i7 3930k, not overclocked, Asus Rampage 4 Formular, 16GB 2133 memory and one R9 280X from Asus.

about 2 weeks ago, the connected display goes black when running Milkyway@home, and the computer still seems to run. When i am connected from another PC to this one via the Boinc Client, Milkyway is still runnging, but all the tasks are stuck.

I run 4 GPU-WUs at the same time, using the app_config.xml file.

Milkyway is running alongside Cosmology@home, which only uses the CPU.

I switched the GPU (with the same model), changed the Power supply Unit and completely reinstalled Windows 10. Still the same problem.

It worked all fine until 2 weeks ago, and i didn't change a thing.

When i run games on this computer, there are no problems either.

I will try the 16.10.3 hofix driver now, but my hopes are very low.

Does anybody know the cause of this problem? Or has experienced something familiar?

Computer with the problem:
https://milkyway.cs.rpi.edu/milkyway//show_host_detail.php?hostid=708929

Thank you all for answers.
4) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65402)
Posted 6 Oct 2016 by Sebastian*
For those who have a R9 390 or 390X, and want to run several workunits at once, stay away from Windows 10 right now. I tried driver 16.10.1 hotfix, 16.7.2, and 16.9.2 hotfix. All drivers crash when one WU reaches 100% and all WUs get stuck where they are. One WU sometimes keeps running, when i run 8 WUs at once.

I use the app_config.xml file to run WUs parallel on one GPU.

And i will try the 390X on Win7 tomorrow, to see if it is Win10 related, what i think. Since the Windows 10 Version 1607 the problem occurs.

Please post anyone if he experiences the same problems
5) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65401)
Posted 6 Oct 2016 by Sebastian*
For those who have a R9 390 or 390X, and want to run several workunits at once, stay away from Windows 10 right now. I tried driver 16.10.1 hotfix, 16.7.2, and 16.9.2 hotfix. All drivers crash when one WU reaches 100% and all WUs get stuck where they are. One WU sometimes keeps running, when i run 8 WUs at once.

I use the app_config.xml file to run WUs parallel on one GPU.

And i will try the 390X on Win7 tomorrow, to see if it is Win10 related, what i think. Since the Windows 10 Version 1607 the problem occurs.

Please post anyone if he experiences the same problems
6) Message boards : News : Updated Server Daemons and Libraries (Message 65391)
Posted 5 Oct 2016 by Sebastian*
Thank you very much Jake for all your hard work :)

Any update on the 4xxx series GPUs yet? Or do you just take a little timeout? ;)

Milkyway seems to run well again, well done.
7) Message boards : News : Updated Server Daemons and Libraries (Message 65363)
Posted 1 Oct 2016 by Sebastian*
After updating my HD5970 computer to Windows 10 1607 (Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3194496)), i get some strange behaviors there too. I run 4 WUs on one GPU core. So 8 WUs at once on the dual GPU card
After nearly a minute of heavy CPU-Work (3 Cores almost running at 100% of 6 Cores) the GPU gets into action.

It was running well before the update to 1607. Does anyone have information about what Microsoft changed to the drivers?

The update also affects the R9 390X, and i guess other GPUs as well.

Please post anyone, if he has trouble with it too.
8) Message boards : News : Updated Server Daemons and Libraries (Message 65362)
Posted 30 Sep 2016 by Sebastian*
captainjack is right, your GPUs don't have double precision, which is needed for Milkyway@home Will Guerin.

My 390X seems to work now, but only when running without app_config file. It is running one WU at a time for now.

After a quick sear on the web, it looks like the latest Microsoft Windows 10 Update really messed up the GPU drivers. Milkyway causes errors since the Update, and even Einstein@home (2 WUs at once). But for some reason my 280X cards seem unaffected.

Can anyone confirm this?

I guess GPUs like 280X and below still work well, while 290X and above cause problems.

Windows 10, latest update, and using an app_config to run multiple WUs at once.
These circumstances have to apply to cause WUs hanging when one WU has finished at 100% and stays there.
9) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65344)
Posted 28 Sep 2016 by Sebastian*
could anyone look at this:

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1804922945

any idea why i get the warnings? The other 2 persons running the task did not get it.

It only shows up on the Win10 computer with the 390X gpu. I've installed Boinc in the standard directory. on all my other computers i install it on D:\Boinc\...
10) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65341)
Posted 28 Sep 2016 by Sebastian*
I only used DDU and installed 16.7.3. But the problem is still there. I am running some Einstein for now, to see if something similar happens there.

Nvidia also allows you to select between windows10 and windows 10 anniversery edition, when looking for their drivers. I wonder if Microsoft changed something related to the GPU drivers.

I am using an app_config file to run 4 WUs at once. Might cause the problem, have to test it later. The strange thing is, that it worked more or less well before the windows update.
11) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65339)
Posted 28 Sep 2016 by Sebastian*
I did a clean install on the Win 10 computer with the r9 390X. Installed the 16.9.2 (21st of september) driver.

I still get the same problem. Driver crashes, and the WU which cause the crash at 100% gets stuck. Restarting just boinc only lets the WUs start from 0% but they are not running.

Vortac, which driver are you using on Win7 for Boinc?

An all my 7970s or 280X GPU don't get work any longer. The Milkyway server has 1150 WUs available currently. The 390X gets work instantly, but with the error mentioned above.

New computer ID for the PC, because of the clean install.

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=705276
12) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65328)
Posted 27 Sep 2016 by Sebastian*
Reinstalling drivers did not help.

Since the system is running on a SSD, i will try tomorrow to reset the project. It could be that the Win10 update did so much wearing on the SSD that it is starting to degrade now.

Any update on the HD 4xxx cards? (Scheduler fix for older cards)

And my 280X cards don't get work any longer at the moment. I will tell if it got better by tomorrow.
13) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65322)
Posted 27 Sep 2016 by Sebastian*
On my R9 390X computer Windows 10 just did an update to the anniversary edition i guess. Now, after one WU finishes, (several other run through fine) the GPU driver seems to crash and the WUs are stuck.
I had to install the GPU drivers again, so i am not sure what driver windows used, but boinc detectet 2 390X gpu, but only one is installed. With the official AMD driver everything runs fine, until one WU causes the driver crash.

The 280X GPUs seem to run fine on other Win10 boxes with the version. Does anyone have an idea what the root cause could be? I used DDU (Display Driver uninstaller) to get rid of the Win10 drivers.

Fow now something is really broken
14) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65300)
Posted 27 Sep 2016 by Sebastian*
Ok, the R9 390X seems to work. Getting work fine. Not sure if it will give good results. And i had to plug in a monitor to get her to run the WUs through. Without, they were stuck at 100%.

Computer: http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=704045

Let me know, when you have updated the scheduler. Then i will give the HD 4850s another try.
15) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65286)
Posted 26 Sep 2016 by Sebastian*
Looks like my HD 4850 GPUs don't get work any longer. It got work on the 24th. I now get the message when i update Boinc, that i got 0 new tasks. Has something changed between then an now? Did the Downtime cause the issue?

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=307550

The computers with the HD 7970 get work tho.

And i get a lof of that in the Event Log from Boinc:

26/09/2016 21:18:26 | Milkyway@Home | Message from task: 0

Seem it shows up once a WU is finished.

Something was changed because of the Downtime. Any ideas?
16) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65221)
Posted 20 Sep 2016 by Sebastian*
The Computer with the R9 390X isn't even initializing the Project. It does not download the .exe -file or any other files. I copied them in manually, with an app_config file. I got the message, that the app_config file contains no known executables.

There must be something wrong at the initial detection, when Boinc sends, or the server requests infos about the hardware.

Any idea how i can monitor that traffic, to give you some hints?
17) Message boards : News : GPU Issues Mega Thread (Message 65220)
Posted 20 Sep 2016 by Sebastian*
You can try the 341.96 driver. Which was displayed when i searched for the 9000 series and window 10. it is from 16th of August this year.
18) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65218)
Posted 20 Sep 2016 by Sebastian*
Hello Jake, i tried the new version on my R9 390X with the latest driver. It is requesting Tasks, but getting none. Removed an added the Project again with no success. No error Message so far. Could the error be, that the newer cards support OpenCL 2.0 instead of 1.2? And the software is only checking for 1.2 and is ignoring newer versions?

There is no driver version reported, when i check my computers in Boinc for this computer. All other from HD 4xxx cards to R9 280X cards report a driver version.

Computer ID: 704045

If you can check on the server side, why i don't get any workunits.

Edit: I added a more detailed request at the end of this message.

9/20/2016 11:51:58 PM | | Starting BOINC client version 7.6.22 for windows_x86_64
9/20/2016 11:51:58 PM | | log flags: file_xfer, sched_ops, task
9/20/2016 11:51:58 PM | | Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
9/20/2016 11:51:58 PM | | Data directory: C:\ProgramData\Boinc
9/20/2016 11:51:58 PM | | Running under account Sebastian
9/20/2016 11:51:58 PM | | OpenCL: AMD/ATI GPU 0: Hawaii (driver version 2117.13 (VM), device version OpenCL 2.0 AMD-APP (2117.13), 8192MB, 8192MB available, 3802 GFLOPS peak)
9/20/2016 11:51:58 PM | | OpenCL CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 5.2.0.10094, device version OpenCL 1.2 (Build 10094))
9/20/2016 11:51:58 PM | | OpenCL CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 2117.13 (sse2,avx), device version OpenCL 1.2 AMD-APP (2117.13))
9/20/2016 11:51:58 PM | | Host name: Hydra
9/20/2016 11:51:58 PM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz [Family 6 Model 60 Stepping 3]
9/20/2016 11:51:58 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx tm2 pbe fsgsbase bmi1 smep bmi2
9/20/2016 11:51:58 PM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.10586.00)
9/20/2016 11:51:58 PM | | Memory: 15.93 GB physical, 18.31 GB virtual
9/20/2016 11:51:58 PM | | Disk: 118.69 GB total, 93.32 GB free
9/20/2016 11:51:58 PM | | Local time is UTC +2 hours
9/20/2016 11:51:58 PM | | Config: GUI RPCs allowed from:
9/20/2016 11:51:58 PM | | 192.168.000.50
9/20/2016 11:51:58 PM | | 192.168.000.62
9/20/2016 11:51:58 PM | | Config: simulate 4 CPUs
9/20/2016 11:51:58 PM | | Config: report completed tasks immediately
9/20/2016 11:51:58 PM | PrimeGrid | URL http://www.primegrid.com/; Computer ID 514902; resource share 100
9/20/2016 11:51:58 PM | | General prefs: from http://milkyway.cs.rpi.edu/milkyway/ (last modified 15-Jun-2016 13:12:51)
9/20/2016 11:51:58 PM | | Host location: none
9/20/2016 11:51:58 PM | | General prefs: using your defaults
9/20/2016 11:51:58 PM | | Reading preferences override file
9/20/2016 11:51:58 PM | | Preferences:
9/20/2016 11:51:58 PM | | max memory usage when active: 8156.68MB
9/20/2016 11:51:58 PM | | max memory usage when idle: 14682.03MB
9/20/2016 11:51:58 PM | | max disk usage: 92.39GB
9/20/2016 11:51:58 PM | | suspend work if non-BOINC CPU load exceeds 50%
9/20/2016 11:51:58 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
9/20/2016 11:52:08 PM | | Fetching configuration file from http://milkyway.cs.rpi.edu/milkyway/get_project_config.php
9/20/2016 11:52:25 PM | Milkyway@Home | Master file download succeeded
9/20/2016 11:52:30 PM | Milkyway@Home | Sending scheduler request: Project initialization.
9/20/2016 11:52:30 PM | Milkyway@Home | Requesting new tasks for CPU and AMD/ATI GPU
9/20/2016 11:52:33 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
9/20/2016 11:52:33 PM | Milkyway@Home | No tasks sent
9/20/2016 11:52:33 PM | Milkyway@Home | Tasks for CPU are available, but your preferences are set to not accept them
9/20/2016 11:53:38 PM | Milkyway@Home | Sending scheduler request: To fetch work.
9/20/2016 11:53:38 PM | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
9/20/2016 11:53:43 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
9/20/2016 11:54:52 PM | Milkyway@Home | update requested by user
9/20/2016 11:54:53 PM | Milkyway@Home | Sending scheduler request: Requested by user.
9/20/2016 11:54:53 PM | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
9/20/2016 11:54:55 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks


9/21/2016 12:22:39 AM | Milkyway@Home | [work_fetch] set_request() for AMD/ATI GPU: ninst 1 nused_total 0.00 nidle_now 1.00 fetch share 1.00 req_inst 1.00 req_secs 1728000.00
9/21/2016 12:22:39 AM | Milkyway@Home | [work_fetch] request: CPU (0.00 sec, 0.00 inst) AMD/ATI GPU (1728000.00 sec, 1.00 inst)
9/21/2016 12:22:42 AM | Milkyway@Home | [work_fetch] backing off AMD/ATI GPU 302 sec
9/21/2016 12:22:42 AM | | [work_fetch] Request work fetch: RPC complete
9/21/2016 12:22:47 AM | | [work_fetch] ------- start work fetch state -------
9/21/2016 12:22:47 AM | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
9/21/2016 12:22:47 AM | | [work_fetch] --- project states ---
9/21/2016 12:22:47 AM | Milkyway@Home | [work_fetch] REC 0.000 prio 0.000 can't request work: scheduler RPC backoff (55.98 sec)
9/21/2016 12:22:47 AM | PrimeGrid | [work_fetch] REC 1230.459 prio 0.000 can't request work: "no new tasks" requested via Manager
9/21/2016 12:22:47 AM | | [work_fetch] --- state for CPU ---
9/21/2016 12:22:47 AM | | [work_fetch] shortfall 6912000.00 nidle 4.00 saturated 0.00 busy 0.00
9/21/2016 12:22:47 AM | Milkyway@Home | [work_fetch] share 0.000 blocked by project preferences
9/21/2016 12:22:47 AM | PrimeGrid | [work_fetch] share 0.000
9/21/2016 12:22:47 AM | | [work_fetch] --- state for AMD/ATI GPU ---
9/21/2016 12:22:47 AM | | [work_fetch] shortfall 1728000.00 nidle 1.00 saturated 0.00 busy 0.00
9/21/2016 12:22:47 AM | Milkyway@Home | [work_fetch] share 0.000 project is backed off (resource backoff: 296.59, inc 600.00)
9/21/2016 12:22:47 AM | PrimeGrid | [work_fetch] share 0.000
9/21/2016 12:22:47 AM | | [work_fetch] ------- end work fetch state -------
9/21/2016 12:22:47 AM | | [work_fetch] No project chosen for work fetch
19) Message boards : News : GPU Issues Mega Thread (Message 65216)
Posted 20 Sep 2016 by Sebastian*
Peter, from what i can see, your 9500GS (which is a 9500GT) should be able to run Einstein. It has compute capability 1.1 which should do it. For Milkyway you need 2.0 i think, which the 2xx Series had.
20) Message boards : News : GPU Issues Mega Thread (Message 65214)
Posted 20 Sep 2016 by Sebastian*
Hey BQL_FFM, what do you mean by "i buy it!"

And could you unhide your PC here in milkyway? I would be intrested in how fast the GTX 1060 runs through the Milkyway@home workunits.

Peter Hucker, you can leave your Intel integrated GPUs on Einstein. The Intel GPUS don't have double precision, so they can't run Milkyway. I am a little bit confused by you Nvidia GPU, i can only find a 9500M GS or a 9600GS. If it is a 9600GS it should be able to run at least Einstein@home.


Next 20

Main page · Your account · Message boards


Copyright © 2019 AstroInformatics Group