@Marodeur

- can you upgrade to 178.24, which is the latest one?
- 6.42 .. do you mean 6.45? It's been weeks since we switched from 6.45 to 6.48

@Jay

Are you referring to Marodeurs recent posts or something else? Because his problem seems actually very different than your's. He's having crashes upon WU startup, which can be avoided by restarting BOINC before each WU. You are talking about not getting work and screen flicker which, with all due respect, seem like some strange linux issues.

MrS

---

Scanning for our furry friends since Jan 2002

Sorry ETA the similarity is having to babysit Boinc.

This comp is just BOINC farm. There is no ANY other software, just drivers and BOINC.

Win XP x64
178.24
6.3.19
6.48
As always!

2GB RAM + 280GTX(1GB)

It`s crunching 24/7. No any changes in last week. ANY. Everything was fine until yesterday evening.

Today, right before I waked up:

<core_client_version>6.3.19</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 280"
# Clock rate: 1296000 kilohertz
Cuda error in file '..\cuda/cutil.h' in line 298 : out of memory.
Memory usage: host: bytes device: bytes
Assertion failed: 0, file ..\cuda/cutil.h, line 298

OR

<core_client_version>6.3.19</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
Cuda error in file 'deviceQuery.cu' in line 59 : out of memory.

</stderr_txt>
]]>


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>
]]>



Last 15 tasks... !!! :/.

http://www.gpugrid.net/results.php?hostid=15721

And now my daily quota is ofc 4 :/. Dunno why, haven`t changed ANYTHING in comp (hardware or software). I could understand if I`ll do something with that, but this comp was crunching correct hole night... And I`ll repeat: it`s just an BOINC farm. Then pls don`t write about SLi, different drivers or anything like that... This comp was crunching correct last weeks.

Why it happened? Any1 knows?

---

I guess if anyone can say anything helpful regarding your problem it would be GDF. The problem appeared with 6.48-WUs, so it's not related to the new application. Edit: oh.. did you reboot?

Unrelated: I've seen your other host uses 6.3.19 and occasionally gets this error that BOINC quit (likely on a file transfer). I don't have this error any more since I swtiched to 6.3.21. Give it a try, it seems very well-behaved.

MrS

---

Scanning for our furry friends since Jan 2002

this appears to be a problem with win64 here are the latest fails with 6.3.21 and app 6.52

<core_client_version>6.3.21</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
Cuda error in file 'deviceQuery.cu' in line 59 : out of memory.

</stderr_txt>
]]>

<core_client_version>6.3.21</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# Using CUDA device 3
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 3
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Using CUDA device 3
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
Cuda error in file '..\cuda/cutil.h' in line 298 : out of memory.
Memory usage: host: bytes device: bytes
Assertion failed: 0, file ..\cuda/cutil.h, line 298

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>
]]>

<core_client_version>6.3.21</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# Using CUDA device 1
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 1
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Using CUDA device 1
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
Cuda error in file '..\cuda/cutil.h' in line 298 : out of memory.
Memory usage: host: bytes device: bytes
Assertion failed: 0, file ..\cuda/cutil.h, line 298

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>
]]>

<core_client_version>6.3.21</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# Using CUDA device 2
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 2
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Using CUDA device 2
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
Cuda error in file '..\cuda/cutil.h' in line 298 : out of memory.
Memory usage: host: bytes device: bytes
Assertion failed: 0, file ..\cuda/cutil.h, line 298

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>
]]>

<core_client_version>6.3.21</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 0
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 1: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 2: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Device 3: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
# Number of multiprocessors: 14
# Number of cores: 112
# Using CUDA device 0
Cuda error in file 'deviceQuery.cu' in line 59 : out of memory.

</stderr_txt>
]]>

I guess if anyone can say anything helpful regarding your problem it would be GDF. The problem appeared with 6.48-WUs, so it's not related to the new application. Edit: oh.. did you reboot?

Unrelated: I've seen your other host uses 6.3.19 and occasionally gets this error that BOINC quit (likely on a file transfer). I don't have this error any more since I swtiched to 6.3.21. Give it a try, it seems very well-behaved.

MrS

I`ll switch to 6.3.21 ASAP. Unfortunatelly some of my comps are unavailable for me now (and soon). And I`m without WU`s :(.

Anyway thx :)


But, it seems to be (4 me) a problem with app. Tell me guys, not enough memory? Which memory - 2GB RAM not used for anything else (just Milkyway)? Or 1GB RAM on 280GTX? Impossible...

---

But, it seems to be (4 me) a problem with app. Tell me guys, not enough memory? Which memory - 2GB RAM not used for anything else (just Milkyway)? Or 1GB RAM on 280GTX? Impossible...

I agree, it can not be that someone is actually using that memory for something else. But I wouldn't say "problem with app". The thing is, GPU-Grid asks the driver for memory, usually get allocated some space and is fine.. but if the driver decides for some reason that this amount of space is not available, then you get this "out of mem" error. I'd say the error lies somewhere in the range of app / driver / windows. Which, unfortunately, is a very large range..

MrS

---

Scanning for our furry friends since Jan 2002

@Marodeur

- can you upgrade to 178.24, which is the latest one?
- 6.42 .. do you mean 6.45? It's been weeks since we switched from 6.45 to 6.48

Hi,

yes, it was 6.45 :)

I have upgraded the drivers for my card to 178.24.

I got 2 WUs in the morning. One of them is running at the moment. Hope to see, that the 2nd WU starts without the memory error.

btw. the combo 6.3.19 and 6.45 runs for more than a month without an error on my box...

One other thing I see is that the total calculation time has changed from about 38000 per WU to 48000. Is that a slowdown by the application or more calculations?

And one last thing - THANKS for the help!! :)

It's a slowdown because of CPU <1 on Windows. The speed of my GTX 260 on Vista 64 also went down from 33 ms/step to 47 ms/step only because of CPU <1...
Speed on Linux 64 is the same like before.
I already reported that in an email to GDF 4 days ago, but got no reply... :?

---

pixelicious.at - my little photoblog

It seems to me that my problem is fixed now :)

Two new workunits were started without an intervention from me.
The last driver update to 178.24 was the winner.

Great help, thx again!

That's good to hear! we should really keep in mind that 178.08 is a *Doh* for GPU-Grid.

Regarding the speed difference: actually you only have a few WUs with ~40ks, whereas most others took about 48ks (+/- a lot). If you run 3+1 instead of 4+1 it might be worth it, if you'd get consistent 40ks afterwards.

MrS

---

Scanning for our furry friends since Jan 2002

It's a slowdown because of CPU <1 on Windows. The speed of my GTX 260 on Vista 64 also went down from 33 ms/step to 47 ms/step only because of CPU <1...
Speed on Linux 64 is the same like before.
I already reported that in an email to GDF 4 days ago, but got no reply... :?

I've reported my Windows XP slowdown also.

I'm not sure if it is a NVIDIA problem or a Windows problem.

GDF's reply, something to this effect, not exact words,
will be traveling November 15th to the US for the supercomputing conference trade show in Texas. He will take these issues up with the NVIDIA people in person when he is there.

We just have to wait and see what the outcome is.

I have been rebooting my machine daily, to try to avoid this problem. It seemed to help for a while. It didn't happen for a couple of weeks anyway. Then last night, it happened again. It's with 6.3.19. Now I have to wait 24 hours until I can get more tasks to crunch.

And again, this time with 6.3.21. And another day of crunching lost.

---

Reno, NV
Team: SETI.USA

Me too....another day lost crunching toast, er...another day lost toasting crunchy bagels, hmmmm...


WinXP Pro64
6.3.21
177.84
Is there a solution on the horizon??

---

Consciousness: That annoying time between naps......

Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it.

And again, this time with 6.3.21. And another day of crunching lost.

Same here. Unfortunately. Is there a way to monitor mem. usage on GFX cards - something like process explorer - as I suspect a major memory leak?

BR,

---

Is there a way to monitor mem. usage on GFX cards - something like process explorer - as I suspect a major memory leak?

Search for Rivatuner at the end of this thread.

MrS

---

Scanning for our furry friends since Jan 2002

So, nvidia said that they are aware of a leaking problem, but could never reproduce the problem.
Can anyone affected by this issue specify:

OS: (WIN XP, Vista, Linux,etc)
Bit: 32 or 64
Driver: Nvidia driver version
or any other information useful to them to debug it


thanks.

GDF

I never got an "out of memory" error and Riva Tuner does not show an increase of used GPU memory in my case.

However, I do have a memory leak which was not there a few months ago. The only major change was going from ATI to nVidia, so I suspect a connection.
After 1 - 2 weeks my system "lost" about 1 GB of my 2 GB and I reach the point where it starts to hurt, so I have to reboot. Closing all apps (which I could find) didn't help. Also it is not related to gaming, as I first suspected. This time I was away from the Pc for a few days and it happened nevertheless. Is there a way to spot which app is responsible for this? Maybe some trick using Process Explorer?

I hope I'm not hijacking the thread, as any suggestions for further diagnostic given to me might also help the people with GPU errors.

MrS

---

Scanning for our furry friends since Jan 2002

So, nvidia said that they are aware of a leaking problem, but could never reproduce the problem.
Can anyone affected by this issue specify:

OS: (WIN XP, Vista, Linux,etc)
Bit: 32 or 64
Driver: Nvidia driver version
or any other information useful to them to debug it

Yes. It's here only present on XP 64 bit with BOINC 64 bit. Every WU needs approximately 70 MB of the video memory. This problem is still present since the beginning of the use of his system for PrimeGrid/GPUGrid. I've never seen this problem on my XP 32 bit or Vista 64 bit PCs. When I forget to reboot my XP 64 bit PC every 2 daysw, they crash every WU from the third day on, when I have not further 70,2 MB free for the start of a new WU.

I have this problem with any CUDA enabled driver on my GTX260 card and before on the 8800GT card, which I had replaced.

---

So, nvidia said that they are aware of a leaking problem, but could never reproduce the problem.
Can anyone affected by this issue specify:

OS: (WIN XP, Vista, Linux,etc)
Bit: 32 or 64
Driver: Nvidia driver version
or any other information useful to them to debug it

Yes. It's here only present on XP 64 bit with BOINC 64 bit. Every WU needs approximately 70 MB of the video memory. This problem is still present since the beginning of the use of his system for PrimeGrid/GPUGrid. I've never seen this problem on my XP 32 bit or Vista 64 bit PCs. When I forget to reboot my XP 64 bit PC every 2 daysw, they crash every WU from the third day on, when I have not further 70,2 MB free for the start of a new WU.

I have this problem with any CUDA enabled driver on my GTX260 card and before on the 8800GT card, which I had replaced.

I agree. It seems to be an XP 64 bit running 64 bit Boinc issue...

WinXP Pro64 SP2
6.3.21
177.84
eVGA 8800GT

---

Consciousness: That annoying time between naps......

Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it.