Still no luck, will have to dig deeper.

38451 Milkyway@Home 30/12/2013 16:59:59 [sched_op] Deferring communication for 00:01:01
38452 Milkyway@Home 30/12/2013 16:59:59 [sched_op] Reason: requested by project
39647 Milkyway@Home 30/12/2013 17:00:10 [coproc] NVIDIA instance 0: confirming for ps_separation_82_DR8_Rev_4_3_1383186301_18369183_0
39648 Milkyway@Home 30/12/2013 17:01:10 [coproc] NVIDIA instance 0: confirming for ps_separation_82_DR8_Rev_4_3_1383186301_18369183_0
39649 Milkyway@Home 30/12/2013 17:02:10 [coproc] NVIDIA instance 0: confirming for ps_separation_82_DR8_Rev_4_3_1383186301_18369183_0
39650 Milkyway@Home 30/12/2013 17:02:28 [coproc] NVIDIA instance 0: confirming for ps_separation_82_DR8_Rev_4_3_1383186301_18369183_0
39651 Milkyway@Home 30/12/2013 17:03:28 [coproc] NVIDIA instance 0: confirming for ps_separation_82_DR8_Rev_4_3_1383186301_18369183_0
39652 Milkyway@Home 30/12/2013 17:04:28 [coproc] NVIDIA instance 0: confirming for ps_separation_82_DR8_Rev_4_3_1383186301_18369183_0
39653 Milkyway@Home 30/12/2013 17:05:28 [coproc] NVIDIA instance 0: confirming for ps_separation_82_DR8_Rev_4_3_1383186301_18369183_0
39654 Asteroids@home 30/12/2013 17:05:35 update requested by user
39655 Asteroids@home 30/12/2013 17:05:39 sched RPC pending: Requested by user
39656 Asteroids@home 30/12/2013 17:05:39 [sched_op] Starting scheduler request
39657 Asteroids@home 30/12/2013 17:05:39 Sending scheduler request: Requested by user.
39658 Asteroids@home 30/12/2013 17:05:39 Requesting new tasks for NVIDIA
39659 Asteroids@home 30/12/2013 17:05:39 [sched_op] CPU work request: 0.00 seconds; 0.00 devices
39660 Asteroids@home 30/12/2013 17:05:39 [sched_op] NVIDIA work request: 24615.49 seconds; 1.00 devices
39661 Asteroids@home 30/12/2013 17:05:41 Scheduler request completed: got 0 new tasks
39662 Asteroids@home 30/12/2013 17:05:41 [sched_op] Server version 701
39663 Asteroids@home 30/12/2013 17:05:41 Project requested delay of 7 seconds
39664 Asteroids@home 30/12/2013 17:05:41 [state] handle_scheduler_reply(): State after handle_scheduler_reply():
40857 Asteroids@home 30/12/2013 17:05:41 [sched_op] Deferring communication for 00:00:07
40858 Asteroids@home 30/12/2013 17:05:41 [sched_op] Reason: requested by project

Please, try again. Kyong has made some changes on server side.

It works! Deleted the project and added it again.
But with strong screen lags...

It works! Deleted the project and added it again.
But with strong screen lags...

Which is your card?

Well done guys, evrything working Ok now.


51 30/12/2013 17:55:43 Fetching configuration file from http://asteroidsathome.net/boinc/get_project_config.php
52 Asteroids@home 30/12/2013 17:56:13 Master file download succeeded
53 Asteroids@home 30/12/2013 17:56:18 Sending scheduler request: Project initialization.
54 Asteroids@home 30/12/2013 17:56:18 Requesting new tasks for CPU and NVIDIA
55 Asteroids@home 30/12/2013 17:56:38 Scheduler request completed: got 1 new tasks
56 Asteroids@home 30/12/2013 17:56:38 New computer location: home
57 30/12/2013 17:56:38 No general preferences found - using defaults
58 30/12/2013 17:56:38 Reading preferences override file
59 30/12/2013 17:56:38 Preferences:
60 30/12/2013 17:56:38 max memory usage when active: 7736.73MB
61 30/12/2013 17:56:38 max memory usage when idle: 7736.73MB
62 30/12/2013 17:56:38 max disk usage: 150.00GB
63 30/12/2013 17:56:38 (to change preferences, visit a project web site or select Preferences in the Manager)
64 Asteroids@home 30/12/2013 17:56:40 Started download of period_search_10000_windows_x86_64__cuda55.exe
65 Asteroids@home 30/12/2013 17:56:40 Started download of cudart64_55.dll
66 Asteroids@home 30/12/2013 17:56:48 Sending scheduler request: To fetch work.
67 Asteroids@home 30/12/2013 17:56:48 Requesting new tasks for NVIDIA
68 Asteroids@home 30/12/2013 17:56:56 Finished download of cudart64_55.dll
69 Asteroids@home 30/12/2013 17:56:56 Started download of input_64064_24






Thanks for all your help.

Tom

31.12.2013 0:36:37 |  | CUDA: NVIDIA GPU 0: GeForce GTS 450 (driver version 327.23, CUDA version 5.5, compute capability 2.1, 1024MB, 826MB available, 637 GFLOPS peak)

Need smaller data chunks for lesser screen lags, or make it adjustable like on MilkyWay.

Nice to hear all is ok.

31.12.2013 0:36:37 |  | CUDA: NVIDIA GPU 0: GeForce GTS 450 (driver version 327.23, CUDA version 5.5, compute capability 2.1, 1024MB, 826MB available, 637 GFLOPS peak)

It's very slow card and we have high memmory controller load (cca 40-60%) also. This may be the cause of lags.

So I discontinue this project if you don't bother about mid-range cards.

So I discontinue this project if you don't bother about mid-range cards.

Simply, It's not our decision. It's hw which limits our posibilities.

Need smaller data chunks for lesser screen lags, or make it adjustable like on MilkyWay.

Grid size is calculated from number of SMX. You can look into stderr.txt, there are times of the largest kernel.

Times for GTS450 are about 100 ms:

CUDA Device: GeForce GTS 450
Compute capability: 2.1
Multiprocessors: 4
Grid dim: 32 = 4*8
Block dim: 128
mrqcof1 curve1 kernel time: 102 ms
mrqcof1 curve1 kernel time: 32 ms

100 ms should be relatively ok.

I'm getting GPU workunits now too.

31/12/2013 9:28:23 AM | Asteroids@home | Sending scheduler request: Requested by user.
31/12/2013 9:28:23 AM | Asteroids@home | Requesting new tasks for NVIDIA
31/12/2013 9:28:26 AM | Asteroids@home | Scheduler request completed: got 6 new tasks

Thanks everyone !

Hello !! I'm new, very new, I subscribed to asteroids@home just a few hours ago, and the really 1st WU I get was the "Period Search Application 101.11 (cuda55)". I left my computer for a moment, and when I came back, mouse and all others little graphic animations were eeeeextreeeemmmeeeeely sloooooowww...

My 1st reaction : I suspend all calculations, my screens turned to black during a few seconds, and turned back on with the following error message : "The NVIDIA OpenGL driver detected a problem with the display driver and is unable to continue. The application must close. Error code: 3". I rebooted my machine, and, aaarrrgg, again !! All was so slow, like trying to run a DirectX11 game on a 333MHz Intel Celeron from 1997, it worked at 4 sfasf (seconds for a single frame).

2nd reaction : I suspend GPU calculations, same result, I knew the driver was completely involved!! After searches on the web (with useless visits on many nvidia support pages), I found you, having the same kind of problems, with the same Cuda55 WU.

So, I did not understand all what you exactly did, but what (and how) can I do to see my computer completing CPU & GPU WUs for all my projects, without skipping manually all the future Asteroid's cuda55 WU I'll receive ?? FIY, my computer : Windows 8.1 Pro(x64) / Boinc 7.2.39(x64) / nVidia 332.21 Driver/ i5-3470S / GA-H77N-Wifi / GV-N650OC-2GI (GTX650) / 2x8Go@1600MHz DDR3. Thank for all, and sorry for my bad english verbs/times accords, mistakes and errors.

Sam :: from "Pays de Loire" (France) ;)

Hello !! I'm new, very new, I subscribed to asteroids@home just a few hours ago, and the really 1st WU I get was the "Period Search Application 101.11 (cuda55)". I left my computer for a moment, and when I came back, mouse and all others little graphic animations were eeeeextreeeemmmeeeeely sloooooowww...

My 1st reaction : I suspend all calculations, my screens turned to black during a few seconds, and turned back on with the following error message : "The NVIDIA OpenGL driver detected a problem with the display driver and is unable to continue. The application must close. Error code: 3". I rebooted my machine, and, aaarrrgg, again !! All was so slow, like trying to run a DirectX11 game on a 333MHz Intel Celeron from 1997, it worked at 4 sfasf (seconds for a single frame).

2nd reaction : I suspend GPU calculations, same result, I knew the driver was completely involved!! After searches on the web (with useless visits on many nvidia support pages), I found you, having the same kind of problems, with the same Cuda55 WU.

So, I did not understand all what you exactly did, but what (and how) can I do to see my computer completing CPU & GPU WUs for all my projects, without skipping manually all the future Asteroid's cuda55 WU I'll receive ?? FIY, my computer : Windows 8.1 Pro(x64) / Boinc 7.2.39(x64) / nVidia 332.21 Driver/ i5-3470S / GA-H77N-Wifi / GV-N650OC-2GI (GTX650) / 2x8Go@1600MHz DDR3. Thank for all, and sorry for my bad english verbs/times accords, mistakes and errors.

Sam :: from "Pays de Loire" (France) ;)

I am not sure but part of your problem could be the 332.21 version of drivers, I am using version 327.23 and it works fine on my XP and win7 machines for both the 560Ti and 760 models. The newer drivers have been shown in the past to cause slower crunching for some people. Another idea would be to upgrade to the newest standard version of Boinc which is now 7.2.39.

If you don't want Asteroids@home to send you CUDA tasks go to Asteroids@home preferences:
http://asteroidsathome.net/boinc/prefs.php?subset=project

... and uncheck:
Use NVIDIA GPU

You seem to not have CUDA problems on SETI@home (where the CUDA apps are much more mature):
http://setiathome.berkeley.edu/results.php?hostid=7213361&offset=0&show_names=0&state=4&appid=

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

If you don't want Asteroids@home to send you CUDA tasks go to Asteroids@home preferences:
http://asteroidsathome.net/boinc/prefs.php?subset=project

... and uncheck:
Use NVIDIA GPU

Or you can put the following in cc_config:

 <options>
	<exclude_gpu>
            <url>http://asteroidsathome.net/boinc/</url>
        </exclude_gpu>
 </options>

You seem to not have CUDA problems on SETI@home (where the CUDA apps are much more mature):
http://setiathome.berkeley.edu/results.php?hostid=7213361&offset=0&show_names=0&state=4&appid=

The main difference is here they use floating point and most of the recent GPU's from both vendors are floating point crippled by their manufacturers (to make you buy their expensive offerings). Short of using single precision maths there probably isn't a lot the developers can do.

---

BOINC blog

Thank you all for your helping answers ;o)

I am not sure but part of your problem could be the 332.21 version of drivers, I am using version 327.23

I don't know if the driver is the problem or if it have a problem. But except on Asteroids@home cuda55 tasks, everything is working very fine, and I really enjoy the "Shadow Play" feature from my actual driver revision (who can record on the fly HD videos from live game sequences, very nice).

Another idea would be to upgrade to the newest standard version of Boinc which is now 7.2.39.

I'm currently using it ;)

If you don't want Asteroids@home to send you CUDA tasks go to Asteroids@home preferences [...] and uncheck: Use NVIDIA GPU

Done, thank you ^^

Or you can put the following in cc_config: [...] The main difference is here they use floating point and most of the recent GPU's from both vendors are floating point crippled by their manufacturers (to make you buy their expensive offerings).

Hum.. I'm not sure to understand... Inserting the lines you gave me will authorize GPU works from Asteroids@home, but not if they're "cuda types" work units ??

Thanks again,
Sam :: from "Pays de Loire" (France) ;)

The lines will prevent you from receiving any GPU workunits from Asteroids@home... no CUDA, no OpenCL, no NVIDIA, no ATI, nothing, beaucoup de rien :-)

Is that what you want? I am not sure what you want because I didn't completely understand your previous post.

For more details on how the cc_config.xml file works click the Official BOINC Wiki link in my signature below, then click the Client configuration link. Note that you can exclude tasks for only NVIDIA but while allowing tasks for ATI and vice-versa. If you have multiple cards you can exclude tasks for one of your cards but allow tasks for the other(s). There are numerous possible combinations.

Note also that this project does not have tasks for ATI at this time so in reality it would not make sense to exclude ATI tasks but it would do no harm if you did exclude ATI.

P.S.

OK, now I understand, you don't want any CUDA tasks from this project. Configuring the option in your preferences on the A@H website will prevent any CUDA tasks from being sent to you. The recommended lines in a cc_config.xml file will accomplish the same thing... no CUDA tasks... plus it will exclude (exclure) AMD tasks.

It is possible that your GTX 650's double-precision power is so slow that it slows your screen updates too. Perhaps the Windows Display Driver Manager (WDDM) notices the slowness and produces the black screen to prevent a complete system lock-up? I'm just guessing, I don't know Windows very well.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

For more details on how the cc_config.xml file works click the Official BOINC Wiki link in my signature below, then click the Client configuration link. Note that you can exclude tasks for only NVIDIA but while allowing tasks for ATI and vice-versa.

Ok, I just bookmarked the page about the xml config file and I'll see what it can do :) Thanks!!

If you have multiple cards you can exclude tasks for one of your cards but allow tasks for the other(s). There are numerous possible combinations.

Sorry ^^, I just have a GTX650 card, on a mini-ITX main-board, in a tiny "Elite 120" computer case who cannot receive more than 1 card (not enough space) ;o)

OK, now I understand, you don't want any CUDA tasks from this project.

Yes, but, it's not about what I want or not, but what it works or not. I want to help Asteroids@Home as much as I already do for Seti, Poem or Milkyway@Home projects, but not if it causes troubles to my computer. I hope I'll be able to authorize GPU work units again soon.

It is possible that your GTX 650's double-precision power is so slow that it slows your screen updates too. Perhaps the Windows Display Driver Manager (WDDM) notices the slowness and produces the black screen to prevent a complete system lock-up? I'm just guessing, I don't know Windows very well.

My GTX650's double-precision power ??? I'm confused, I really don't get what this means. My GTX authorizes me to play Minecraft on a screen (1920x1080 @50-60 fps), during a Cuda Work Unit is on going for Einstein@Home, and displayed on the second screen!! All that is done without any slowing down times (or maybe very little times, like a second at 40fps on the game, 2 or 3 times an hour). About my black screens, they were done by Windows, during the 5 to 8 seconds it takes when it (successfully) kills both nvidia driver and cuda55 task, and relaunches the graphic driver. Bravo Windows 8.1, never crashed, never freezed, never ever... My graphic "slow times" were only made during Asteroids cuda55 WU !!

---

Samy : from "Pays de Loire" : N47.586147,E1.336013
CPU: i5-3470S @2.9GHz / MB: GA-H77N-Wifi / GPU: GV-N650OC w 2GB @5GHz / RAM: 16GB @1600MHz
All that gives me entertainments, movies, music, games, and more, it helps, making me smile

Precision refers to the number of bytes used to represent numbers. Single precision numbers use 32 bits whereas double precision numbers use 64 bits. More bits allows larger numbers to be represented but operations (addition, subtraction, multiplication, division, etc.) on double precision numbers are slower than operations on single precision numbers. In other words it takes more time to add 2 double precision numbers than it does to add 2 single precision numbers.

Some projects and games use predominately single precision calculations and they proceed very quickly. Asteroids@home uses a lot of double precision calculations therefore calculations proceed slower. Some GPUs have far more CUDAs with which to perform double precision calculations and they can do more double precision calculations per second than a GPU with fewer CUDAs. Your GTX 650 has relatively few CUDAS so it is relatively slow when a task has many millions of double precision calculations. In my previous post I was theorizing that perhaps your card's double precision power is so small that it cannot keep up with Asteroids tasks and the demands of the display and that the WDDM portion of Windows thinks it's so slow the driver has crashed. That's just a theory, it might not be correct.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux