[solved] nVidia 295.51 beta driver problems - Failed tasks - Cannot create a symbolic link in a registry key that already has subkeys or values. (0x3fc) - exit code 1020 (0x3fc)

Forums › Problems and Bug Reports

Claggy
Claggy
Joined: 29 Dec 06
Posts: 560
Credit: 2699403
RAC: 0

RE: Thanks for the response

26 Feb 2012 11:19:11 UTC
Message 108401 in response to message 108398
(moderation:
    )

    Quote:

    Thanks for the response guys.

    You might also consider chiming in on the nVidia Feedback thread, for the 295.73 drivers, located here:
    http://forums.nvidia.com/index.php?showtopic=223426 ... and providing as much feedback as possible. Once mine start failing, I'll post there too, and hopefully they hear us, as I roll back to 290.53 (the last ones that worked for me).

    It's sad that we haven't received responses -- either they are completely swamped with bugs, or they just don't care. Either way, it saddening and frustrating.


    I posted a report to that thread on friday, (as well as my Bug report that i've already mentioned) no response as of yet from eithier,

    Claggy

    Bob
    Bob
    Joined: 16 Nov 10
    Posts: 5
    Credit: 19938976
    RAC: 0

    Thanks for pushing the issue

    27 Feb 2012 19:41:24 UTC
    Message 108402 in response to message 108401
    (moderation:
      )

      Thanks for pushing the issue with NVIDIA. Given how long it took them to fix a driver they once put out that was shutting down the fans on their GPU's, I'm not overly optimistic as to how long they'll take to fix this problem. Unfortunately, dropping back to an earlier driver version isn't an option for some of us. But again, thanks for pushing the issue.

      Jacob Klein
      Jacob Klein
      Joined: 22 Jun 11
      Posts: 45
      Credit: 114028547
      RAC: 0

      I thought I'd chime in with

      6 Mar 2012 13:24:08 UTC
      Message 108403 in response to message 108402
      (moderation:
        )

        I thought I'd chime in with some more information.

        If you want to use 295.73 WHQL or 295.51 Beta without CUDA failures:
        The workaround for the bug is that you must set the Windows Power Options to "Turn off the display: Never". You may still use a screen saver, and you may still physically turn the monitor off, but you must not let the software power the monitor down... according to my testing.

        Also, for anyone trying to reproduce the problem, I have found that the problem occurs when Windows powers off the monitor first, and then BOINC tries to start or resume a CUDA task while the monitor is off. This means that, if you try to reproduce it using tasks that are already running before Windows powers down the monitor, those tasks will not fail. But any tasks that try to start or resume, while the monitor is off, will fail... according to my testing.

        Finally, the best news yet, I have been contacted privately by an nVidia employee, who was having trouble recreating the problem. I assisted him, and he can now repro on demand now (it's easiest to repro with Einstein@Home, and he didn't know that the monitor has to power down before BOINC begins CUDA processing), and he will be presenting information to the developers.

        I am now going to run 295.73 WHQL with a "Blank" screensaver and "Turn off the display: Never", and try to remember to physically turn the monitor off if I get up for an extended period of time.

        Regards,
        Jacob Klein

        Oliver Behnke
        Oliver Behnke
        Moderator
        Administrator
        Joined: 4 Sep 07
        Posts: 984
        Credit: 25171438
        RAC: 15

        Hi

        13 Mar 2012 16:21:32 UTC
        Message 108404 in response to message 108403
        (moderation:
          )

          Hi Jacob,

          Quote:

          Finally, the best news yet, I have been contacted privately by an nVidia employee, who was having trouble recreating the problem. I assisted him, and he can now repro on demand now (it's easiest to repro with Einstein@Home, and he didn't know that the monitor has to power down before BOINC begins CUDA processing), and he will be presenting information to the developers.

          Can you get me in touch with that guy? I just noticed this problem and it's causing us quite some trouble, since we're really loosing potential computing power (Pulsar discoveries anyone?!). It might very well be that our CUDA 3.2 app simply doesn't get along with the latest 4.1 drivers and an upgrade (on our end) might equally solve it or serve as a workaround until NVIDIA fixed the root cause.

          And by the way, sorry that it took us so long to become aware of this issue, Bernd and I are just swamped with other E@H topics like OpenCL (AMD GPUs). Time to look after CUDA again...

          Thanks,
          Oliver

          Einstein@Home Project

          Bob
          Bob
          Joined: 16 Nov 10
          Posts: 5
          Credit: 19938976
          RAC: 0

          I see Nvidia released a new

          13 Mar 2012 18:05:02 UTC
          Message 108405 in response to message 108404
          (moderation:
            )

            I see Nvidia released a new driver version today (296.10) but I didn't see anything in the release notes about the cuda issue. Hopefully now they're aware of what's causing the issue they'll be able to address it in the not too distant future.

            Richard Haselgrove
            Richard Haselgrove
            Joined: 10 Dec 05
            Posts: 2143
            Credit: 2962925789
            RAC: 698856

            RE: I see Nvidia released a

            13 Mar 2012 18:28:23 UTC
            Message 108406 in response to message 108405
            (moderation:
              )

              Quote:
              I see Nvidia released a new driver version today (296.10) but I didn't see anything in the release notes about the cuda issue. Hopefully now they're aware of what's causing the issue they'll be able to address it in the not too distant future.


              It's been tested elsewhere already. Not fixed.

              Jacob Klein
              Jacob Klein
              Joined: 22 Jun 11
              Posts: 45
              Credit: 114028547
              RAC: 0

              Oliver, I have passed the

              14 Mar 2012 2:11:53 UTC
              Message 108407 in response to message 108404
              (moderation:
                )

                Oliver,

                I have passed the request to the nVidia employee, to see if I can share his email address to you. I will let you know if/when he responds. I wanted to get his approval first, mainly for 2 reasons -- I don't want to cross him, and also I know they're swamped with other issues too.

                Hopefully you can understand, and hopefully he responds positively.
                Will let you know,
                Jacob

                Jacob Klein
                Jacob Klein
                Joined: 22 Jun 11
                Posts: 45
                Credit: 114028547
                RAC: 0

                Oliver, I have sent you a

                14 Mar 2012 3:30:10 UTC
                Message 108408 in response to message 108407
                (moderation:
                  )

                  Oliver,

                  I have sent you a Private Message that has his contact information, along with my prior communications.
                  Also, I have confirmed that the 296.10 WHQL drivers still do not work correctly unless you use "Turn off the display: Never".
                  If there's anything you need in terms of testing a potential interim solution, please don't hesitate to ask me.

                  Regards,
                  Jacob

                  Oliver Behnke
                  Oliver Behnke
                  Moderator
                  Administrator
                  Joined: 4 Sep 07
                  Posts: 984
                  Credit: 25171438
                  RAC: 15

                  Thanks Jacob, well

                  14 Mar 2012 9:04:42 UTC
                  Message 108409 in response to message 108408
                  (moderation:
                    )

                    Thanks Jacob, well done.

                    Oliver

                    Einstein@Home Project

                    Oliver Behnke
                    Oliver Behnke
                    Moderator
                    Administrator
                    Joined: 4 Sep 07
                    Posts: 984
                    Credit: 25171438
                    RAC: 15

                    FYI, we won't ship any CUDA

                    14 Mar 2012 10:01:01 UTC
                    Message 108410 in response to message 108409
                    (moderation:
                      )

                      FYI, we won't ship any CUDA tasks for systems using a driver newer than 290.53 for the time being. This decision was made to avoid unnecessary computation errors, data set downloads, daily quota reduction and volunteer frustration.

                      We're in contact with NVIDIA and we'll try to help them fix the situation as fast as possible. If there's a workaround without user-action (not like "Turn off the display: Never") we'll implement it. Until that time, please understand that the majority of our volunteers might not follow this forum/thread and we need to take care of this problem without requiring them to work around it themselves.

                      We'll keep you posted.

                      Thanks,
                      Oliver

                      Einstein@Home Project

                      Comment viewing options

                      Select your preferred way to display the comments and click "Save settings" to activate your changes.

                      Forums › Problems and Bug Reports