BUG REPORT

Although I don't know if it is caused by the new WUs... This bug makes my system BSOD every time I shut down BOINC Manager. The message says something is wrong with:

nvlddmkm.sys

and then restarts. I had no problems with this and previous nvidia driver (310.70) and thought a fresh 314.07 drivers install would be able to make it go away. It didn't.

My system is WIN7pro/x64, only use GPUGrid and here is an excerpt from stderr.out:

Stderr output

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
El sistema no puede encontrar la ruta especificada. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
MDIO: cannot open file "restart.coor"
SWAN : FATAL : Cuda driver error 999 in file 'swanlibnv2.cpp' in line 1574.
Assertion failed: a, file swanlibnv2.cpp, line 59

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

</stderr_txt>
]]>

the message translates to: "System can't find specified path". The error presents itself only when shuting down BOINC but has no problem when crunching the WU's.

Also, when the error presents itself, I have to manually unable starting BOINC at startup (when on safe mode), otherwise, the BSOD will appear every restart when BOINC restarts...


??????????

Just got this (like Jorge):

<core_client_version>7.0.52</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified.
 (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
MDIO: cannot open file "restart.coor"
SWAN : FATAL : Cuda driver error 999 in file 'swanlibnv2.cpp' in line 1574.
Assertion failed: a, file swanlibnv2.cpp, line 59

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

</stderr_txt>

Never saw this with v6.17. Also, it was a NOELIA WU, haven't seen it with TONI.

Only new WUs will have reduced upload sizes. The old ones will be the same.
We need to tell the code to output in a different format.
Soon all will be using the compressed format.

A new NOELIA task has as large as 164MB upload file.
It's time to tell the code to output in that different (compressed) format.

While running my first 6.18 long run task my laptop locked up and I had to do a hard reboot. After the system was back up this WU had terminated with an error. The details are below. However, I have run two 6.18 WUs successfully since then. It appears one other host also terminated with an error on this WU.

The NOELIA WUs seem to be averaging about 80% utilization GTX 680M and the run times are over 18 hours. I don't know much effect having to share CPU time is having on these numbers.

Error Details:

i7-3740QM 16GB - Win7 Pro x64 - GTX 680m (Alienware 9.18.13.717)
GPU: dedicated to GPUGRID - CPU: SETI, Poem, Milkyway, WUProp, FreeHAL

------------------------------------------------------------------------

Work Unit: 4209987 (041px21x2-NOELIA_041p-0-2-RND9096_0)

Stderr output

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
MDIO: cannot open file "restart.coor"
SWAN : FATAL : Cuda driver error 999 in file 'swanlibnv2.cpp' in line 1574.
Assertion failed: a, file swanlibnv2.cpp, line 59

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

</stderr_txt>
]]>

I thought Noelia asked us to report bugs in the other thread she started a couple days ago?

BUG REPORT

Although I don't know if it is caused by the new WUs... This bug makes my system BSOD every time I shut down BOINC Manager. The message says something is wrong with:

nvlddmkm.sys

and then restarts. I had no problems with this and previous nvidia driver (310.70) and thought a fresh 314.07 drivers install would be able to make it go away. It didn't.

My system is WIN7pro/x64, only use GPUGrid and here is an excerpt from stderr.out:

Stderr output

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
El sistema no puede encontrar la ruta especificada. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
MDIO: cannot open file "restart.coor"
SWAN : FATAL : Cuda driver error 999 in file 'swanlibnv2.cpp' in line 1574.
Assertion failed: a, file swanlibnv2.cpp, line 59

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

</stderr_txt>
]]>

the message translates to: "System can't find specified path". The error presents itself only when shuting down BOINC but has no problem when crunching the WU's.

I got the same error. The WU was running normally, when I rebooted the computer. After reboot the WU crashed.

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

Application 6.18 is turning into a nightmare, too many errors. Let go back to 6.17, and send 6.18 back to beta.

After the new drivers where installed (which didn't solve the problem) I reinitiated GPUGrid and uninstalled/reinstalled BOINC. Hope this will fix the problem.

6.18 apps do have a problem (70% sure about that ;) )

here's how to reproduce the windows crashes (BSOD's) (I do not know if all these steps are necessary, but they are enough for me, system has to have at least 3 useable -not physical, but "logical"- GPU's):

step 1: make a config file to use some GPU's and disable others so that at least 2 of them are available to GPUGrid.
step 2: download some 6.18 long units (at least are 3 necessary)
step 3: while crunching, suspend and then restart your workunits in the BOINC tab "tasks" so that your gpu's cycle amongst all of them.
step 3: keep doing this until BSOD

WARNING (if I am correct) your system WILL crash. Save all data first. When your system first crashes, it will keep doing so after every restart if you have set BOINC to open at logon. To rescue your system you have to logon in safe mode, start BOINC and disable it (e.g. by setting it to suspend GPU computation when system is in use).

I have succesfully run a few workunits after new drivers and BOINC where reinstalled. Ocassionally, the system screen would black out, but would never crash if I havn't got to play with the steps above first.

BOINC is not the problem, as I had a working system with 7.0.28 regardless of the steps I described for you above (and with 6.17 apps). using win7 x64 edition and a combination of 1 gtx690 (2 gpus) and a gt640 for this tests.

windows crashes (BSOD's) (I do not know if all these steps are necessary, but they are enough for me, system has to have at least 3 useable -not physical, but "logical"- GPU's):

Not sure if this applies but just saw this warning:

"Microsoft pushes another botched automatic update":

"If you had Windows set for automatic updates last Tuesday, Feb 26, and you run 64-bit Windows 7, you may have been hit by the latest bad patch. KB 2670838 -- known officially as a "Platform Update for Windows 7 x64-Edition" -- appears to be the source of a blue screen problem, where Internet Explorer 9, in particular, stops working and throws a "PAGE_FAULT_IN_NONPAGED_AREA" error identifying the video driver (the reports I've seen cite igdpmd64.sys) as the source of the BSOD."

http://www.infoworld.com/t/microsoft-windows/microsoft-pushes-another-botched-automatic-update-213802?source=IFWNLE_nlt_blogs_2013-03-04

Edit: Personally I avoid IE like the plague.

windows crashes (BSOD's) (I do not know if all these steps are necessary, but they are enough for me, system has to have at least 3 useable -not physical, but "logical"- GPU's):

Not sure if this applies but just saw this warning:

"Microsoft pushes another botched automatic update":

"If you had Windows set for automatic updates last Tuesday, Feb 26, and you run 64-bit Windows 7, you may have been hit by the latest bad patch. KB 2670838 -- known officially as a "Platform Update for Windows 7 x64-Edition" -- appears to be the source of a blue screen problem, where Internet Explorer 9, in particular, stops working and throws a "PAGE_FAULT_IN_NONPAGED_AREA" error identifying the video driver (the reports I've seen cite igdpmd64.sys) as the source of the BSOD."

http://www.infoworld.com/t/microsoft-windows/microsoft-pushes-another-botched-automatic-update-213802?source=IFWNLE_nlt_blogs_2013-03-04

Edit: Personally I avoid IE like the plague.

Looking at my Windows 7/64 computer, Microsoft Update is telling me "No important updates available": that update is listed as available, but optional.

My automatic settings for important updates are set to "Download updates, but let me choose whether to install them" - KB2670838 wasn't even listed until I went looking for it.

windows crashes (BSOD's) (I do not know if all these steps are necessary, but they are enough for me, system has to have at least 3 useable -not physical, but "logical"- GPU's):

Not sure if this applies but just saw this warning:

"Microsoft pushes another botched automatic update":

"If you had Windows set for automatic updates last Tuesday, Feb 26, and you run 64-bit Windows 7, you may have been hit by the latest bad patch. KB 2670838 -- known officially as a "Platform Update for Windows 7 x64-Edition" -- appears to be the source of a blue screen problem, where Internet Explorer 9, in particular, stops working and throws a "PAGE_FAULT_IN_NONPAGED_AREA" error identifying the video driver (the reports I've seen cite igdpmd64.sys) as the source of the BSOD."

http://www.infoworld.com/t/microsoft-windows/microsoft-pushes-another-botched-automatic-update-213802?source=IFWNLE_nlt_blogs_2013-03-04

Edit: Personally I avoid IE like the plague.

Looking at my Windows 7/64 computer, Microsoft Update is telling me "No important updates available": that update is listed as available, but optional.

My automatic settings for important updates are set to "Download updates, but let me choose whether to install them" - KB2670838 wasn't even listed until I went looking for it.

I think I ran into it a couple hours ago. I accidentally clicked Windows media Center on one of my remote machines and it crashed the NVidia driver. Never saw that before (WMC probably starts up a lot of IE code), and yes the new "Platform Update for Windows 7" was installed. It took a cold reboot to get things back working again.

windows crashes (BSOD's) (I do not know if all these steps are necessary, but they are enough for me, system has to have at least 3 useable -not physical, but "logical"- GPU's):

Not sure if this applies but just saw this warning:

"Microsoft pushes another botched automatic update":

"If you had Windows set for automatic updates last Tuesday, Feb 26, and you run 64-bit Windows 7, you may have been hit by the latest bad patch. KB 2670838 -- known officially as a "Platform Update for Windows 7 x64-Edition" -- appears to be the source of a blue screen problem, where Internet Explorer 9, in particular, stops working and throws a "PAGE_FAULT_IN_NONPAGED_AREA" error identifying the video driver (the reports I've seen cite igdpmd64.sys) as the source of the BSOD."

http://www.infoworld.com/t/microsoft-windows/microsoft-pushes-another-botched-automatic-update-213802?source=IFWNLE_nlt_blogs_2013-03-04

Edit: Personally I avoid IE like the plague.

I do have that update installed. I'll get into it and see if this has been buggin my system. (I also dont use IE)

I just had a segfault on a new Noelia. I had a very similar segfault on a short NATHAN earlier, so I don't think it's Noelia's fault.

From the article, "its status was changed from Important to Optional on Thursday".
Having automatic updates enabled is a bad setting for crunching, unless you want your computer to update in the middle of the night and then sit idle until you wake up and log on.

From the article, "its status was changed from Important to Optional on Thursday".
Having automatic updates enabled is a bad setting for crunching, unless you want your computer to update in the middle of the night and then sit idle until you wake up and log on.

In my case I have windows update set to "Check for updates but let me choose whether to download and install them". I saw the "important" update ready to DL and install so I did on several machines. Turned out to be a bad idea...

My rig has recently been able to crunch some data, although more than one variable was changed after the BSOD's:

1) There are reports of new tasks and that they have been modified to temporarily deal with "a" problem: here, here and here.

2) I have only crunched Nathan tasks but apparently the troublesome ones where Noelias'.

3) Since the last BSOD, I have uninstalled a windows update as was first noted here.

My rig is working fine, but 3 variables have changed since my ast BSOD, therefore I could not determine which one variable (or combination of them) was affecting on the system crashes.