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

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.

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.

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.

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

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

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.

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.

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.

MJH:

Regarding the "display driver constantly crashing" issue, it's important that you look into the problem here:
http://www.gpugrid.net/forum_thread.php?id=3491
... in order to ensure that other users do not suffer the same fate.

My workaround for it was to log into Windows, and while the display driver was crashing repeatedly, desperately try to get to the BOINC menu to select "Disable GPU". Once that was disabled, I aborted the offending/stuck GPUGrid.net tasks.

Note: This has nothing to do with the "Access violation" errors (which are a completely different issue, and which will show up in the stderr.txt log when the work units are uploaded). As such, I will try not to post again within this thread, about the "display driver constantly crashing" issue.

Thanks for listening,
Jacob

MJH:

Regarding the "display driver constantly crashing" issue, it's important that you look into the problem here:
http://www.gpugrid.net/forum_thread.php?id=3491
... in order to ensure that other users do not suffer the same fate.

My workaround for it was to log into Windows, and while the display driver was crashing repeatedly, desperately try to get to the BOINC menu to select "Disable GPU". Once that was disabled, I aborted the offending/stuck GPUGrid.net tasks.

Note: This has nothing to do with the "Access violation" errors (which are a completely different issue, and which will show up in the stderr.txt log when the work units are uploaded). As such, I will try not to post again within this thread, about the "display driver constantly crashing" issue.

Thanks for listening,
Jacob

Another option is, within the cc_config.xml file, within the <options> block, you can set a <start_delay>.
Details here: http://boinc.berkeley.edu/wiki/Client_configuration

So, for instance, you could do the following to have BOINC delay running until 30 seconds after it normally would:

I think Richard Haselgrove had a more elegant way of preventing blue screen crashes after recovery/reboot by editing some xml file to fool BOINC into thinking the project was suspended before attempting to start BOINC up, but I don't remember the details.

Operator

My workround has been to restart Windows in safe mode (which prevents BOINC loading), and edit client_state.xml to add the line

<suspended_via_gui/>

to the <result> block for the suspect task.

As the name suggests, that's the same as clicking 'suspend' for the task while BOINC is running, and gets control of the machine back so you can investigate on the next normal restart. By convention, the line goes just under <plan_class> in client_state, but I think anywhere at the first indent level will do.

Robert, you might want to try the following,
Go to the location of the Boinc Manager (default is C:\Program Files\BOINC), alternate click on the application, select Properties, click the Compatibility Tab and set the Privilege Level to Run the program as an administrator. Then click 'Change setings fro all users' and set the privilege level to Run as administrator. Click OK, Apply, OK and restart the system.

I ran a couple of WUs over the weekend on my GTX 460 after updating to driver 331.40 and had no problems.

However, I did not notice this problem to begin with.

http://www.gpugrid.net/workunit.php?wuid=4840060
http://www.gpugrid.net/workunit.php?wuid=4838699

____________

Strangely enough I did a project reset and my access violations went away. Didn't do anything else. Go figure.

With driver 326.80 my 660 ran for 10 days continuously without any error or fatal cuda driver and thus a downclock of the GPU clock.

Then 6 days ago I needed to reboot the system for a Windows update and thought I can afterwards install latest driver 331.40.
I did a clean install and reboot again. Now it has already three times a fatal cuda driver error and a downclock, which only can be resolved by booting.

Have more people seen this fatal cuda driver (in stderr) with this beta driver on another card then 780 or Titan?
____________
Greetings from TJ

With driver 326.80 my 660 ran for 10 days continuously without any error or fatal cuda driver and thus a downclock of the GPU clock.

Then 6 days ago I needed to reboot the system for a Windows update and thought I can afterwards install latest driver 331.40.
I did a clean install and reboot again. Now it has already three times a fatal cuda driver error and a downclock, which only can be resolved by booting.

Have more people seen this fatal cuda driver (in stderr) with this beta driver on another card then 780 or Titan?