Boinc won't run on new install......HELP!

Message boards : Number crunching : Boinc won't run on new install......HELP!
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22160
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1803896 - Posted: 21 Jul 2016, 10:17:55 UTC
Last modified: 21 Jul 2016, 10:21:09 UTC

One possible solution is to add a start up delay to your cc_config.xml file:

<start_delay>nseconds</start_delay>


I had to do this on one of my crunchers some time ago for much the same reason as you are suffering just now - I think I used a 120 second delay.
The delay gives the drivers time to get going properly before BOINC starts to do its system probing to see what hardware is available.

edit:
Under Windoze 7 the default location of cc_config is c:\ProgramData\BOINC (by default this folder is hidden)
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1803896 · Report as offensive
Profile AllenIN
Volunteer tester
Avatar

Send message
Joined: 5 Dec 00
Posts: 292
Credit: 58,297,005
RAC: 311
United States
Message 1803973 - Posted: 21 Jul 2016, 20:26:30 UTC - in response to Message 1803872.  

Does anyone have any thoughts on this?

The only thing that comes to mind would be to re-download the new BOINC version, and make sure you've got the right one (32 or 64bit).

http://boinc.berkeley.edu/download_all.php



EDIT- the only way to upgrade from a 32 to 64bit OS is a clean installation.



EDIT- Problem Event Name: BEX64 gives a few hits, and several of them relate to AV programmes and 3rd party programmes that monitor the system & interfere with the startup of the installer.


Hi Grant. I noticed that too, but disabled the AV program during installation and it makes me wonder why the old version 7.0.46 (I think) will work but not the newer ones.

The installation was a clean install to 64 bit Win7, but it was to the same disk drive that the older Vista 32 bit was on. I assume that Win7 automatically reformatted the drive on installation. I'm sure the new d/l of Boinc is 64 bit, but I will d/l it again and try to reinstall per your suggestion. Thanks!

Allen
ID: 1803973 · Report as offensive
Profile AllenIN
Volunteer tester
Avatar

Send message
Joined: 5 Dec 00
Posts: 292
Credit: 58,297,005
RAC: 311
United States
Message 1803975 - Posted: 21 Jul 2016, 20:30:00 UTC - in response to Message 1803877.  

The most useful link I've been able to find concerning "Problem Event Name:BEX64" issues.
What does event BEX64 mean?

There are some references that BEX stands for "Buffer Overflow Exception" and is somehow related to Data Execution Prevention.
...

Indicates a buffer overflow (/GS) or DEP exception (BEX64 indicates a buffer overflow (/GS) or DEP exception on 64-bit versions of Windows)

I translate that to a couple of programmes interfering with each other, and in this case the BOINC installer comes off second best.


Found another site, and there the issue relates to a programme having issues with extremely long file names on some folders. Remove the folder with the extremely long file name & no more BEX64 errors.

Very odd and interesting. Should I go hunting.....grin Perhaps I should!


Fixing BEX64 error nvcplui.exe

BEX64 NVcplui.exe and nvgames.dll error in manage 3d settings
In process monitor, it showed that the nvcplui.exe was for some reason interacting with these long named folders/directories. Many programs are not designed to recognize or handle long names like the above example and usually will crash. Sure enough that was the problem. I moved all my folders and personal stuff off the desktop and to a different partition (in this case D drive). I then relaunched the application and the manage 3d settings worked perfectly. To test if this was the problem, I put back the items I had moved off the desktop and launched the application again and sure enough it crashed at the manage3d settings.

ID: 1803975 · Report as offensive
The_Matrix
Volunteer tester

Send message
Joined: 17 Nov 03
Posts: 414
Credit: 5,827,850
RAC: 0
Germany
Message 1803976 - Posted: 21 Jul 2016, 20:31:24 UTC
Last modified: 21 Jul 2016, 20:32:02 UTC

I am always using a videocut software , guess what, i want to install it on W7 64-bit, but the system refuses.

I had to download the software new, then it installs. But before it always worked.

-,- gremlins....
ID: 1803976 · Report as offensive
Profile AllenIN
Volunteer tester
Avatar

Send message
Joined: 5 Dec 00
Posts: 292
Credit: 58,297,005
RAC: 311
United States
Message 1803978 - Posted: 21 Jul 2016, 20:32:49 UTC - in response to Message 1803896.  

One possible solution is to add a start up delay to your cc_config.xml file:

<start_delay>nseconds</start_delay>


I had to do this on one of my crunchers some time ago for much the same reason as you are suffering just now - I think I used a 120 second delay.
The delay gives the drivers time to get going properly before BOINC starts to do its system probing to see what hardware is available.

edit:
Under Windoze 7 the default location of cc_config is c:\ProgramData\BOINC (by default this folder is hidden)


Some things are just so darn finicky..guess that's another one I'll have to try and since it's the simplest, I guess I'll try it first.

Thanks!
ID: 1803978 · Report as offensive
Profile AllenIN
Volunteer tester
Avatar

Send message
Joined: 5 Dec 00
Posts: 292
Credit: 58,297,005
RAC: 311
United States
Message 1803980 - Posted: 21 Jul 2016, 20:36:46 UTC - in response to Message 1803896.  

One possible solution is to add a start up delay to your cc_config.xml file:

<start_delay>nseconds</start_delay>


I had to do this on one of my crunchers some time ago for much the same reason as you are suffering just now - I think I used a 120 second delay.
The delay gives the drivers time to get going properly before BOINC starts to do its system probing to see what hardware is available.

edit:
Under Windoze 7 the default location of cc_config is c:\ProgramData\BOINC (by default this folder is hidden)


Rob,

That didn't go so well. My c:\ProgramData\BOINC directory doesn't even have a cc_config.xml file in it. Do I need to make one?

Allen
ID: 1803980 · Report as offensive
Profile AllenIN
Volunteer tester
Avatar

Send message
Joined: 5 Dec 00
Posts: 292
Credit: 58,297,005
RAC: 311
United States
Message 1804319 - Posted: 22 Jul 2016, 23:54:18 UTC

Just thought that I would get back to you all with my dismal results after checking out all of the suggestions.

Unfortunately nothing worked and I am back to running the older version of Boinc.
At least I am able to run.

Perhaps sometime in the future I will come across some more clues and finally solve this unusual problem.

Thanks to all for giving it a shot!

Allen
ID: 1804319 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13720
Credit: 208,696,464
RAC: 304
Australia
Message 1804327 - Posted: 23 Jul 2016, 0:08:15 UTC - in response to Message 1804319.  

Perhaps sometime in the future I will come across some more clues and finally solve this unusual problem.

Process Monitor might be the best option.

Fire it up, run the BOINC installer, then check to see what was happening just prior to the BEX64 error.
Grant
Darwin NT
ID: 1804327 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1804476 - Posted: 23 Jul 2016, 15:46:24 UTC

You could check stderrdae.txt in BOINC's data directory if the client had a chance to log the error there.

Did you try 7.6.33?
ID: 1804476 · Report as offensive
Profile AllenIN
Volunteer tester
Avatar

Send message
Joined: 5 Dec 00
Posts: 292
Credit: 58,297,005
RAC: 311
United States
Message 1805656 - Posted: 29 Jul 2016, 20:08:14 UTC - in response to Message 1804476.  

You could check stderrdae.txt in BOINC's data directory if the client had a chance to log the error there.

Did you try 7.6.33?


I didn't even know there was a 7.6.33.

When I try it again, I will check the err file.

Thanks!
ID: 1805656 · Report as offensive
Profile AllenIN
Volunteer tester
Avatar

Send message
Joined: 5 Dec 00
Posts: 292
Credit: 58,297,005
RAC: 311
United States
Message 1805659 - Posted: 29 Jul 2016, 20:13:32 UTC - in response to Message 1804327.  

Perhaps sometime in the future I will come across some more clues and finally solve this unusual problem.

Process Monitor might be the best option.

Fire it up, run the BOINC installer, then check to see what was happening just prior to the BEX64 error.


Definitely a good idea. Will try it the next time I go hunting...grin

Thanks!
ID: 1805659 · Report as offensive
Previous · 1 · 2

Message boards : Number crunching : Boinc won't run on new install......HELP!


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.