Hi relic,
try BOINC version 5.10.45 (http://boinc.berkeley.edu/download_all.php). The latest version might still have problems.

cheers

Hi relic[H],
This is a new problem to me. Without any prior examples to guide me, I start off with asking what security programs are running on thee systems?

Lawrence

Added: We have recently had a member who traced his random errors to a bank of memory, even though it ran Prime 95 and memory tests without problems.

Hi Lawrence, thanks for trying to help. :)

I've tried the BOINC client on several Vista systems. So far it is only freezing the two x64 systems.

The AV is AVG on one and Symantec Client Security (Enterprise) on the other. (Unfortunately disabling AV for testing is not an acceptable option.)

Most of the Vista security features are disabled and the Vista firewall is turned off. (We're behind a tight corporate firewall)

As two dissimilar hardware configurations have an identical problem that only occurs when running the BOINC software I am going to discount the possibility that it is a hardware problem unless the 8800GT Video cards are a possible issue.

8800GTs are also installed in the non-freezing 32-bit systems, but obviously they are using a 32-bit driver rather than 64-bit drivers used in the two Vista x64 systems.

All four systems are running the latest NVidia CUDA drivers if that helps.

The systems will sometimes run for a few minutes, occasionally for an hour or two then freeze without any warning or symptoms. The keyboard locks mid-word, the mouse freezes and Everest Ultimate (hardware monitoring software) stops updating. Nothing in the event logs...the system just locks.

Prior to the lockup the systems are running at reasonable temps and the CPU loads are close to those set in the BOINC manager. Available RAM is plentiful and the Voltages are nominal. It's easy to see how the system was doing right at lockup since Everest freezes when the screen does. ;)

Any ideas? I don't have enough experience with BOINC to even have a clue.

Regards,
relic

What I was saying was Boinc does work fine with 64bit systems in response to your 'Is this the wrong project or is there a workaround for x64 systems' quote.

There is no need for a 'workaround' as it does work fine, but obviously there is something specific with the setup of your systems that is not allowing it to, rather than with the Boinc client itself working with a 64bit OS.

Unfortunately diagnosing exactly what it is not easy, and as has already been suggested it is often a case of just disabling things one by one until you reach the issue. Obviously in your case doing that in itself causes problems due to being in a corporate setup where certain tests cannot be done for security reasons.

Hi relic[H],

This stopped me from thinking about graphics, but Didactylos is right. BOINC 6 is trying to add minimal CUDA support, which means there may be buggy code interacting with your CUDA drivers. BOINC 5 does not have any CUDA interfaces.

Lawrence