Advanced search

Message boards : News : Update to 331.40 to fix access violations on Windows

Author Message
Profile MJH
Project administrator
Project developer
Project scientist
Send message
Joined: 12 Nov 07
Posts: 696
Credit: 27,266,655
RAC: 0
Level
Val
Scientific publications
watwat
Message 33430 - Posted: 8 Oct 2013 | 23:00:23 UTC

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

Betting Slip
Send message
Joined: 5 Jan 09
Posts: 588
Credit: 2,036,066,275
RAC: 1,520,724
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33435 - Posted: 9 Oct 2013 | 9:50:25 UTC - in response to Message 33430.

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


____________

ExtraTerrestrial Apes
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 17 Aug 08
Posts: 2670
Credit: 750,715,174
RAC: 487,288
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33442 - Posted: 9 Oct 2013 | 20:32:00 UTC - in response to Message 33435.

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

Betting Slip
Send message
Joined: 5 Jan 09
Posts: 588
Credit: 2,036,066,275
RAC: 1,520,724
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33444 - Posted: 10 Oct 2013 | 9:42:48 UTC - in response to Message 33442.

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


____________

ExtraTerrestrial Apes
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 17 Aug 08
Posts: 2670
Credit: 750,715,174
RAC: 487,288
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33447 - Posted: 10 Oct 2013 | 19:04:26 UTC

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

Jeremy Zimmerman
Send message
Joined: 13 Apr 13
Posts: 61
Credit: 726,605,417
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwat
Message 33448 - Posted: 10 Oct 2013 | 22:44:24 UTC - in response to Message 33447.

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.

Wiyosaya
Send message
Joined: 22 Nov 09
Posts: 111
Credit: 171,819,453
RAC: 528,356
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33449 - Posted: 11 Oct 2013 | 0:36:27 UTC

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.
____________

Jacob Klein
Send message
Joined: 11 Oct 08
Posts: 1067
Credit: 1,145,477,339
RAC: 1,117,306
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33450 - Posted: 11 Oct 2013 | 0:53:19 UTC - in response to Message 33449.

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.

Betting Slip
Send message
Joined: 5 Jan 09
Posts: 588
Credit: 2,036,066,275
RAC: 1,520,724
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33453 - Posted: 11 Oct 2013 | 9:02:19 UTC - in response to Message 33448.
Last modified: 11 Oct 2013 | 9:13:58 UTC

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.

Betting Slip
Send message
Joined: 5 Jan 09
Posts: 588
Credit: 2,036,066,275
RAC: 1,520,724
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33454 - Posted: 11 Oct 2013 | 9:06:48 UTC - in response to Message 33449.

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.

Jeremy Zimmerman
Send message
Joined: 13 Apr 13
Posts: 61
Credit: 726,605,417
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwat
Message 33458 - Posted: 11 Oct 2013 | 10:39:17 UTC - in response to Message 33453.

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.

Betting Slip
Send message
Joined: 5 Jan 09
Posts: 588
Credit: 2,036,066,275
RAC: 1,520,724
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33459 - Posted: 11 Oct 2013 | 10:54:39 UTC - in response to Message 33458.
Last modified: 11 Oct 2013 | 11:11:11 UTC

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?

Jeremy Zimmerman
Send message
Joined: 13 Apr 13
Posts: 61
Credit: 726,605,417
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwat
Message 33460 - Posted: 11 Oct 2013 | 12:46:59 UTC - in response to Message 33459.

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}.

Profile robertmiles
Send message
Joined: 16 Apr 09
Posts: 402
Credit: 169,015,396
RAC: 339,121
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33465 - Posted: 12 Oct 2013 | 0:35:12 UTC - in response to Message 33430.
Last modified: 12 Oct 2013 | 0:36:20 UTC

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.

Wiyosaya
Send message
Joined: 22 Nov 09
Posts: 111
Credit: 171,819,453
RAC: 528,356
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33466 - Posted: 12 Oct 2013 | 1:16:00 UTC - in response to Message 33465.

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.
____________

Profile robertmiles
Send message
Joined: 16 Apr 09
Posts: 402
Credit: 169,015,396
RAC: 339,121
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33467 - Posted: 12 Oct 2013 | 4:22:40 UTC - in response to Message 33466.
Last modified: 12 Oct 2013 | 4:30:35 UTC

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.

Profile robertmiles
Send message
Joined: 16 Apr 09
Posts: 402
Credit: 169,015,396
RAC: 339,121
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33468 - Posted: 12 Oct 2013 | 5:51:19 UTC - in response to Message 33467.

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.

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 322,566
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33469 - Posted: 12 Oct 2013 | 9:18:18 UTC - in response to Message 33468.

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

Profile Retvari Zoltan
Avatar
Send message
Joined: 20 Jan 09
Posts: 1844
Credit: 10,620,014,794
RAC: 9,851,592
Level
Trp
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33470 - Posted: 12 Oct 2013 | 10:19:17 UTC - in response to Message 33468.

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.

Profile robertmiles
Send message
Joined: 16 Apr 09
Posts: 402
Credit: 169,015,396
RAC: 339,121
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33471 - Posted: 12 Oct 2013 | 15:06:46 UTC - in response to Message 33470.

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.

Jacob Klein
Send message
Joined: 11 Oct 08
Posts: 1067
Credit: 1,145,477,339
RAC: 1,117,306
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33472 - Posted: 12 Oct 2013 | 15:25:18 UTC - in response to Message 33471.
Last modified: 12 Oct 2013 | 15:26:00 UTC

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

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 322,566
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33474 - Posted: 12 Oct 2013 | 19:59:35 UTC - in response to Message 33471.
Last modified: 12 Oct 2013 | 20:03:18 UTC

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.
____________
FAQ's

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

Operator
Send message
Joined: 15 May 11
Posts: 108
Credit: 297,176,099
RAC: 0
Level
Asn
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33476 - Posted: 12 Oct 2013 | 21:46:30 UTC - in response to Message 33472.
Last modified: 12 Oct 2013 | 21:48:25 UTC

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


Many people have had this issue and had to figure out how to catch BOINC before the crashes start again.

I have BOINC set to not start automatically because of all the TDRs I've had recently.

So I get the system back up and running after the TDR, click the BOINC shortcut and poise my mouse pointer over the GPUGrid project line so I can hit the 'Suspend' button before it all crashes again. I've gotten pretty good at it.

That way I can switch to the tasks panel and abort whatever was running because they will all be corrupted and completely worthless as a result of the TDR that happened (on whichever GPU crashed at the time).

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
____________

Jacob Klein
Send message
Joined: 11 Oct 08
Posts: 1067
Credit: 1,145,477,339
RAC: 1,117,306
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33477 - Posted: 12 Oct 2013 | 21:50:15 UTC - in response to Message 33476.
Last modified: 12 Oct 2013 | 21:51:21 UTC

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:

<cc_config>
<options>
<start_delay>30</start_delay>
</options>
</cc_config>

Richard Haselgrove
Send message
Joined: 11 Jul 09
Posts: 788
Credit: 1,420,906,745
RAC: 1,418,697
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33478 - Posted: 12 Oct 2013 | 22:11:31 UTC - in response to Message 33476.

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

Quoting from message 33277:

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.

Profile robertmiles
Send message
Joined: 16 Apr 09
Posts: 402
Credit: 169,015,396
RAC: 339,121
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33491 - Posted: 14 Oct 2013 | 5:32:15 UTC - in response to Message 33474.
Last modified: 14 Oct 2013 | 5:39:39 UTC

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.


Doesn't seem necessary now - BOINC is now running properly under the administrator account.

A workunit you may want to assign an Error result to:

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

That's the one that was in progress when the crashes started, and was lost from that computer' BOINC database during the recovery. In other words, now a phantom workunit.

It may or may not be significant that after the recovery, the BOINC version in use was 7.0.56. Now upgraded to 7.0.64, though.

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 322,566
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33494 - Posted: 14 Oct 2013 | 9:26:13 UTC - in response to Message 33491.
Last modified: 14 Oct 2013 | 9:26:33 UTC

The phantom WU will clear from your list in around 2weeks.

Sounds like your system recovered to a time when a previous version of BOINC was installed. I expect your system associated the crash with Boinc and went to a previous version.
____________
FAQ's

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

Wiyosaya
Send message
Joined: 22 Nov 09
Posts: 111
Credit: 171,819,453
RAC: 528,356
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33500 - Posted: 14 Oct 2013 | 18:47:39 UTC

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

____________

Betting Slip
Send message
Joined: 5 Jan 09
Posts: 588
Credit: 2,036,066,275
RAC: 1,520,724
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33508 - Posted: 15 Oct 2013 | 15:27:00 UTC - in response to Message 33500.

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

TJ
Send message
Joined: 26 Jun 09
Posts: 815
Credit: 1,469,215,105
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33552 - Posted: 19 Oct 2013 | 15:07:13 UTC

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

Richard Haselgrove
Send message
Joined: 11 Jul 09
Posts: 788
Credit: 1,420,906,745
RAC: 1,418,697
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 33554 - Posted: 19 Oct 2013 | 16:47:33 UTC - in response to Message 33552.

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?

The discussion thread with some examples is in Number crunching.

Post to thread

Message boards : News : Update to 331.40 to fix access violations on Windows