- exit code -1073741515 (0xc0000135)
1 Jun 2012 10:57:45 UTC
Topic 196369
(moderation:
I am getting this error and cannot run ant GPU work from Einstein on my system. All error out immediatly. Windows 7 64 bit.
All other GPU projects work fine.
- exit code -1073741515 (0xc0000135)
Upon some research I found an old post from Rom Walton, below.
My question is, how do I go about adding to the "Users" Group ?
http://boinc.berkeley.edu/trac/changeset/22977/boinc#
•WINSETUP: Avoid a 0xc0000135 error by giving the boinc_master and
boinc_project membership in the 'Users' group. Dynamic linking
to nvcuda.dll was failing because the project applications were
being denied access to DLLs in the system directory.
win_build/installerv2/redist/Windows/Win32/
boinccas.dll
boinccas95.dll
win_build/installerv2/redist/Windows/x64/
boinccas.dll
boinccas95.dll
- exit code -1073741515 (0xc0000135)
)
"exit code -1073741515 (0xc0000135)" almost certainly means that you are missing a DLL, or lacking access rights to a DLL.
But don't assume that it's this DLL, or that the cause is the missing group membership. Many people google 0xc0000135, and come back with the answer that it's a Windows .NET framework error: again, possibly true in some cases, but far from the full story. And for the record, no part of BOINC, and no science application that I'm aware of, uses .NET - so forget I ever mentioned it, .net won't be relevant here.
It's not easy to set group memberships manually on a 'home' version of Windows, as yours are. The usual way is to re-run the BOINC installer, and allow it to re-make the permissions assigned to the science apps, especially with a version of BOINC made after that bug was fixed. I see you're running v6.10.60 on one machine, v7.0.28 on the other - which is the one giving problems?
And what, apart from the very general error number, led you to suspect this particular cause? Do the errors only occur when one particular user is logged on to the machine in question?
Edit - found the source of your quote - it's in the 'new features' list for BOINC v6.12.13, about 15 months ago. It isn't a suggestion for something a user should try, it's a statement of what installers from that version onwards will do for you.
I am using Boinc 7.0.28 now.
)
I am using Boinc 7.0.28 now. The old machine is retired.
Win 7 home premium, if it matters.
All other GPU projects work fine, Einstein GPU was working fine until all of a sudden I could not run GPU on it about a week ago. I have tried a project reset 2 times also.
I am the only user on this system.
I installed no new software besides maybe some Windows updates and Adaware
I have tried reinstalling Boinc also but no success at solving the problem.
Would a uninstall of boinc and manual delete of all boinc files and directories maybe help ? And reinstall from scratch.
Well, you've run "Binary
)
Well, you've run "Binary Radio Pulsar Search (Arecibo) v1.25 (BRP4cuda32nv301)" successfully in the past, so it shouldn't be an application problem. But that was under BOINC v6.10.60, on 27 May - the errors started on 28 May, by which time you were running v7.0.28: that's a good version, I'm running it here under Windows 7/64, so unlikely to be the problem. When did you upgrade to the 301.42 NVidia driver?
I installed 301.42 on 5-22,
)
I installed 301.42 on 5-22, so I ran good until 5-28 it seems.
Could AVG be a problem. I read something on notes that there is some registry protection that they provide. Would you reccomend a registry cleaner such as CCleaner ever ?
RE: I installed 301.42 on
)
Could be. That version of the application is still relatively new - installed on the server 11 May. Sometimes anti-virus products flag a new application as suspicious simply because not many of their users have rated it yet - see the sticky Microsoft Security Essentials Detection thread at the top of the bug reports board.
If AVG or AdAware had a problem with it, it should show up in their logs or history, whichever they call it: you could try a manual scan (of the executable program itself - with zero runtime and no output, it's probably the main app causing the problem, not a DLL). I doubt it's a registry problem, but I'll leave others to think about that while I break for lunch.
I also just now looked at the
)
I also just now looked at the Windows Updates I installed on the day it seems the problem started.
There was a security update for Visual C++ 2008 and Visual C++ 2010
RE: I also just now looked
)
Look to see if you got a NVidia hardware driver update from Microsoft as well.
The Microsoft versions of the drivers are reported (I haven't encountered this personally) only to include the display elements, and not the general purpose GPU computing extensions. It can't make matters any worse: try reinstalling the generic 301.42 driver for your card from the NVidia site.
Hallo Mark ! I had also such
)
Hallo Mark !
I had also such and other trouble with crunching errors on BRP4 tasks. That´s some malfunctioning of the BRP4 tasks in conjunktion with BOINC clients >= 7.0.25. Since I rolled back to 6.12.34 all things are running very well, but I can´t crunch A@H any more. As you have NVIDIA cards, you don´t need the newest BOINC clients. I invetstigated very much into this within the last 2 month and will place my observations here presumably in the next week. There are more than you and me bothered by this, but they behave silent and probably leave the project without notice.
Kind reagrds an happy crunching
Martin
I am going to try rollback to
)
I am going to try rollback to 6.10.60, i dont like the version 7 anyway. I,ll see if it fixes it.
If I understand correcetly, I have to delete Boinc directory completly to roll back to an older version 6.10.60 ?
No, just delete your
)
No, just delete your client_state.xml and client_state_prev.xml files in the BOINC Data directory.
But what about BOINC 7 is it that you don't like? OpenCL support? Its new and better way of fetching work? Its new and better way of scheduling how to run work, for CPU and GPU separately?