| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Boinc Client not connecting to localhost anymore |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
numbacruncher
Cruncher Joined: Oct 5, 2007 Post Count: 3 Status: Offline Project Badges: 
|
World Community Grid - BOINC Manager 6.10.58
Windows 7 Home Premium 64 Bit AMD Phenom 9650 Processor 4 GB RAM The BOINC-Client worked like a charm in all Versions since a year or so. Last week I upgraded my graphics card from the Onboard ATI Radeon HD 3200 to an PCI-E Nvidia GTS 450. Since then Boinc stopped working. I assume that the Boinc-Client ist not capable of adressing the RAM. With the onboard graphics I had 3,75 GB RAM available to use. Now I have exactly 4GB. Is that possible? When I start the Boinc.exe manually I get the following error message: - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x72A818E1 read attempt to addr ess 0x0000012C |
||
|
|
seippel
Former World Community Grid Tech Joined: Apr 16, 2009 Post Count: 392 Status: Offline Project Badges: 
|
Welcome to the forums numbacruncher,
This error could be caused by an incompatible graphics card device driver. Since you said you just upgraded from an ATI to Nvidia card, you may wish to make sure the onboard graphics card (ATI) is disabled and the device driver is completed uninstalled. Another work around option (if you are only connecting to World Community Grid with BOINC) is to disable GPU use in BOINC since World Community Grid does not use GPU and disable the screensaver. Seippel |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
World Community Grid - BOINC Manager 6.10.58 Windows 7 Home Premium 64 Bit AMD Phenom 9650 Processor 4 GB RAM . With the onboard graphics I had 3,75 GB RAM available to use. Now I have exactly 4GB. Is that possible? Because onboard graphics requires the other 250MB of ram to work. Now that you went to a dedicated video card that ram is freed up to use elsewhere. Welcome to WCG. 
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
numbacruncher
Cruncher Joined: Oct 5, 2007 Post Count: 3 Status: Offline Project Badges:
|
With "is that possible" I was relating to BOINC not aware of 4GB, not for the more available memory.
 I tried out everything since then, but nothing helped. -Reduced RAM to 2 GB, same error. -Set primary VGA-Adapter in BIOS to PCI-E, same error. -Uninstalled WCG Boing Manager and reinstalled, same error. -Uninstalled WCG Boing Manager, deleted data and programm directory, reinstalled, same error. -Tried uninstalling ATI-Driver again, the installer stated only that they are already deleted, same error. -As a last despaired try, I uninstalled WCG Boing Manager, and installed Boinc Manager 6.10.58 (same Version) from Berkeley.edu. It connected to the localhost client instantly. I signed on on World Community Grid and now I am up and running again.  At the moment, I can life with it, but does anyone know, whats different with the clients that leads to such quirks on my system? |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
With "is that possible" I was relating to BOINC not aware of 4GB, not for the more available memory. I tried out everything since then, but nothing helped. -Reduced RAM to 2 GB, same error. -Set primary VGA-Adapter in BIOS to PCI-E, same error. -Uninstalled WCG Boing Manager and reinstalled, same error. -Uninstalled WCG Boing Manager, deleted data and programm directory, reinstalled, same error. -Tried uninstalling ATI-Driver again, the installer stated only that they are already deleted, same error. -As a last despaired try, I uninstalled WCG Boing Manager, and installed Boinc Manager 6.10.58 (same Version) from Berkeley.edu. It connected to the localhost client instantly. I signed on on World Community Grid and now I am up and running again. At the moment, I can life with it, but does anyone know, whats different with the clients that leads to such quirks on my system? By recollection, this is the second or third time on these forums of a report where WCG skinned kit fails to connect to the core client and the Berkeley version does. Do not know of any significant differences ... skin and some extras in the config file. Maybe an installer default differential, where the Berkeley version may have both "Protected Application Execution" and "Allow all users" ticked by default (My personal installer boxes to tick as recommend, which had others connect successfully in past). There's a present discussion at developers where a new install is to check the registry settings of a previous install, and then not passing them on identically, so it's something looked at, if it is that. WCG tech knreed is the man who could tell what WCG defaults in the installer [still] are different. --//-- Thanks for pushing on and sharing the fix that worked for you. |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: 
|
If Protected Application Execution (run as a service) is used the GPU cannot be recognised by Boinc.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As discussed in another parallel thread, knreed has chipped in to find the cause of the none-connection with the WCG kit. The Berkeley version definitely has PAE as default so they will have to do the RTFM, certainly when installing 6.12 alphas (plural), but that could be because it pulls that setting from the registry... don't know.
Even with "Allow All Users" in addition to PAE no GPU recognition? Yes that's a Windows quirk and a source of BOINC ScreenSaver issues too, since the authority then would not exist for the BOINC SS which runs on the user account, to query the core client if it's not set to AAU. The behaviour between XP and Vista/W7 could be different in that on top. Now, that PAE > No GPU recognition sounds like an issue for pretty much everyone concious of security as it requires signing in before BOINC loads. We all have to make our choices. --//-- |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges:
|
With a PAE install, Windows uses its default graphics drivers and does not load the proper GPU drivers. The same applies if you do a standard remote log in, you need to use a VNC. You normally just get a missing GPU &/or disabling GPU tasks message (with the Berkeley version), but perhaps there is something else amiss, possible to do with having a GPU option.
Even with "Allow All Users" in addition to PAE no GPU recognition? Think so; Allow All Users basically just allows other users to control/exit Boinc, Boinc would still run as a service. |
||
|
|
|