If you have been unfortunate enough to have been afflicted by the problem of repeated crashing with 'access violation' errors, please upgrade the Nvidia driver to 331.40 to rejoin us in the happy land of mostly-crash-free crunching.

MJH

Doesn't work on my GTX 460 still have access violations. :-(

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

Uh, that's bad.. so far I'Ve only read about GK110 GPUs being affected. And everyone of them who upgraded got it fixed (or at least noone reported the opposite).

MrS

---

Scanning for our furry friends since Jan 2002

Uh, that's bad.. so far I'Ve only read about GK110 GPUs being affected. And everyone of them who upgraded got it fixed (or at least noone reported the opposite).

MrS

Yes, would be interested to hear if anyone with a GTX460 is getting access violations.

The problem is I can't see nVidia concerning themselves with any new driver bugs for the 4 series cards

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

If it would be a problem with the card you should rather get "simulation has become instable" messages than access violations.

MrS

---

Scanning for our furry friends since Jan 2002

I received this error on a GTX460 on the below work unit. Did it a 7 times before erroring out the WU. This was my fault though as I was trying to push the card a little faster on the OC now that cooler temps are here.

http://www.gpugrid.net/result.php?resultid=7346741

# The simulation has become unstable. Terminating to avoid lock-up (1)
# Attempting restart (step 2147000)
# GPU [GeForce GTX 460] Platform [Windows] Rev [3203] VERSION [55]

WinXP32bit, 326.80 beta drivers

Other than that, I have two of these cards running error free for almost a couple months 24/7.

Is this the same problem as in this thread - http://www.gpugrid.net/forum_thread.php?id=3491#33391 - "Number crunching : Abrupt computer restart - Tasks stuck - Kernel not found"

I've a GTX 460 and I have updated to this driver. I will be running this weekend. I will post whether or not I receive the error.

---

Is this the same problem as in this thread - http://www.gpugrid.net/forum_thread.php?id=3491#33391 - "Number crunching : Abrupt computer restart - Tasks stuck - Kernel not found"

I've a GTX 460 and I have updated to this driver. I will be running this weekend. I will post whether or not I receive the error.

No, not the same problem.

I received this error on a GTX460 on the below work unit. Did it a 7 times before erroring out the WU. This was my fault though as I was trying to push the card a little faster on the OC now that cooler temps are here.

http://www.gpugrid.net/result.php?resultid=7346741

# The simulation has become unstable. Terminating to avoid lock-up (1)
# Attempting restart (step 2147000)
# GPU [GeForce GTX 460] Platform [Windows] Rev [3203] VERSION [55]

WinXP32bit, 326.80 beta drivers

Other than that, I have two of these cards running error free for almost a couple months 24/7.

WOW, that's a big OverClock, you have your GPU clock set @ 920 from a stock of 675, you almost certainly will get problems at that speed.. I have my GPU set @ 750 giving a device clock of 1500 which runs fine and is not responsible for Access Violations.

Is this the same problem as in this thread - http://www.gpugrid.net/forum_thread.php?id=3491#33391 - "Number crunching : Abrupt computer restart - Tasks stuck - Kernel not found"

I've a GTX 460 and I have updated to this driver. I will be running this weekend. I will post whether or not I receive the error.

As Jacob said, it's not the same problem. I would be grateful to hear of your experiences.

The two cards have been at 880 OC with 1850 memory for a month. One in one machine sitting at 70C and the other sitting at 69C. House is cooling off with the fall season. The temps were 68 and 66 now. Bumped the 68C one from 880 to 900/1900 and no issues (back to 70C). Bumped the other one to 920/1900 to 69C. After the error, dropped it back down to 880/1850. These are the stock air coolers from the Gigabyte factory OC at 760. Had these cards for a couple years and never OC'ed them. Did not realize how much overhead they had with the stock cooler. :) Got lucky.

The two cards have been at 880 OC with 1850 memory for a month. One in one machine sitting at 70C and the other sitting at 69C. House is cooling off with the fall season. The temps were 68 and 66 now. Bumped the 68C one from 880 to 900/1900 and no issues (back to 70C). Bumped the other one to 920/1900 to 69C. After the error, dropped it back down to 880/1850. These are the stock air coolers from the Gigabyte factory OC at 760. Had these cards for a couple years and never OC'ed them. Did not realize how much overhead they had with the stock cooler. :) Got lucky.

Have you had them working on GPUGrid at that speed recently?

The apps have been updated a couple of times along with Cuda version and they are a lot more efficient now than a couple of years ago. I had my 460 running at 850 but now have had to drop back to 750 because it would be unstable on GPUGrid

EDIT

I see now you have them running with later cards. Has a 460 ever done a WU on its own?

I see now you have them running with later cards. Has a 460 ever done a WU on its own?

Yes. Many. Typically 65,000 to 80,000s (18-22h) for Nathan, Santi, Noelia. Have the Boinc Buffers at 0.1 and 0.2 so GPUGRID does not download a new WU until around 1-3 hours before a unit finishes. Nearly all of the WU's for these cards will have the <24h turn around for {Reported - Sent}.

If you have been unfortunate enough to have been afflicted by the problem of repeated crashing with 'access violation' errors, please upgrade the Nvidia driver to 331.40 to rejoin us in the happy land of mostly-crash-free crunching.

MJH

Is that driver version suitable for my 64-bit Windows Vista computer, which is giving a chain of crashes too fast to see whether an access violation is involved or not? The chain ends with the operating system giving a blue screen, and almost immediately starting a reboot.

The chain starts without BOINC running, shortly after I log on.

If you have been unfortunate enough to have been afflicted by the problem of repeated crashing with 'access violation' errors, please upgrade the Nvidia driver to 331.40 to rejoin us in the happy land of mostly-crash-free crunching.

MJH

Is that driver version suitable for my 64-bit Windows Vista computer, which is giving a chain of crashes too fast to see whether an access violation is involved or not? The chain ends with the operating system giving a blue screen, and almost immediately starting a reboot.

The chain starts without BOINC running, shortly after I log on.

This sounds a lot like the problem that I referenced earlier in this thread, but it may not be. What you might try is to boot into "safe mode." Run BOINC in safe mode - GPU Grid tasks will not run since the NVidia driver is not loaded. Select the task, and suspend it in BOINC, then reboot and let Vista start normally. If the computer does not crash when it gets into Vista, then to me, it is much more likely to be the problem I reference earlier in the thread.

---

If you have been unfortunate enough to have been afflicted by the problem of repeated crashing with 'access violation' errors, please upgrade the Nvidia driver to 331.40 to rejoin us in the happy land of mostly-crash-free crunching.

MJH

Is that driver version suitable for my 64-bit Windows Vista computer, which is giving a chain of crashes too fast to see whether an access violation is involved or not? The chain ends with the operating system giving a blue screen, and almost immediately starting a reboot.

The chain starts without BOINC running, shortly after I log on.

This sounds a lot like the problem that I referenced earlier in this thread, but it may not be. What you might try is to boot into "safe mode." Run BOINC in safe mode - GPU Grid tasks will not run since the NVidia driver is not loaded. Select the task, and suspend it in BOINC, then reboot and let Vista start normally. If the computer does not crash when it gets into Vista, then to me, it is much more likely to be the problem I reference earlier in the thread.

Safe mode starts normally, but I have not found how to start BOINC there.

An additional account starts normally, but trying to start BOINC there gives only an error message saying I must do something under the administrator account before running BOINC there. Only the administrator account shows the problem, and the administrator account won't run long enough I can make that change for the other account.

Once the problem starts, the Nvidia driver crashes a few times at about once a second before Windows Vista crashes.

Safe mode starts normally, but I have not found how to start BOINC there.

An additional account starts normally, but trying to start BOINC there gives only an error message saying I must do something under the administrator account before running BOINC there. Only the administrator account shows the problem, and the administrator account won't run long enough I can make that change for the other account.

Once the problem starts, the Nvidia driver crashes a few times at about once a second before Windows Vista crashes.

It currently looks like I need to find a way to use a non-administrator account to edit the list of tasks that are automatically started when logging in to the administrator account. Editing the list of gadgets started then looks like a good first try.

Did you make sure port number 31416 is allowed for Boinc in your firewall?
Is Boinc installed for All Users?

You might want to install CCleaner, open it, go to Tools, Startup, and disable anything and everything that you don't NEED to start with Windows.

You can also use CCleaner to prevent Boinc from autostarting (useful when changing drivers when a restart is required), and then manually start it, from the start menu.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

It currently looks like I need to find a way to use a non-administrator account to edit the list of tasks that are automatically started when logging in to the administrator account. Editing the list of gadgets started then looks like a good first try.

You can't edit the list of the startup tasks as a non-administrator user, but you can run any application as a different user (having administrator privileges) while you are logged in as a non-administrator user.
I suggest you to use the built in msconfig.exe tool to do that:
1. click the start button, then type msconfig.exe in the search field, press enter.
2. you should give the user name and password of your administrator account.
3. In the 'system configuration utility' select the 'startup' tab, and look for boincmgr and boinctray on the list, and uncheck both.
4. Press 'OK' (twice), and restart your computer to apply changes.

It currently looks like I need to find a way to use a non-administrator account to edit the list of tasks that are automatically started when logging in to the administrator account. Editing the list of gadgets started then looks like a good first try.

You can't edit the list of the startup tasks as a non-administrator user, but you can run any application as a different user (having administrator privileges) while you are logged in as a non-administrator user.
I suggest you to use the built in msconfig.exe tool to do that:
1. click the start button, then type msconfig.exe in the search field, press enter.
2. you should give the user name and password of your administrator account.
3. In the 'system configuration utility' select the 'startup' tab, and look for boincmgr and boinctray on the list, and uncheck both.
4. Press 'OK' (twice), and restart your computer to apply changes.

I did that. Trying to run BOINC under the non-administrator account still gives the same error message:

BOINC Manager - Connection Error

You are currently not authorized to manage the client.
Please contact your administrator to add you to the 'boinc_users' local
user group.


Logging in to the administrator account now works, but without automatic startup of BOINC.

Trying to add the other account to the local user group only gives messages saying that Windows Vista Home Premium does not support that operation.

Manually starting BOINCMGR under the administrator account now works and starts BOINC. The BOINC log file gave many error messages about missing files, before the download of new workunits started.