Same on my Titan - stopped at mark 15.

Thanks guys. 711 has even more debug.

This is an awful way to tackle the problem, but I can't reproduce it in-house, and I'm damned if I can make Visual Studio emit a binary that does something useful on segfault like drop a core file.

And yes, the GPU+version debug will be staying. If you want something else there too, now is the time to ask for it!

MJH

Sweet news that the GPU printout is staying - hopefully you print it each time the task is restarted too, as I have 3 total GPUs in my system. Things that might prove useful:
- The RAM that the GPU has (seems very useful to have)
- The full array of GPUs
- CPU information

For 7.11, I again got 2 tasks (1 for each of my GPUGrid GPUs).
They both:
- did print "MARK 15"
- did print "MARK 15.1"
- got as far as printing "di MARK 13" before erroring.

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

Thanks,
Jacob

Same on the Titan - di mark 13:

http://www.gpugrid.net/result.php?resultid=7198904
http://www.gpugrid.net/result.php?resultid=7198901
http://www.gpugrid.net/result.php?resultid=7198899

All have same result, but the 3rd one is a GIANNI test, not an MJHARVEY??

712. Almost at the bottom turtle now.

M

For v7.12, for me, they got as far as:
CPi MRK 8

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

And yes, the GPU+version debug will be staying. If you want something else there too, now is the time to ask for it!

It would be nice to have:
- the manufacturer (vendor) ID
- the type of the GPU
- the number of the GPU
- the memory size of the GPU
- the clock rate of the GPU
in the stderr output file.

Something like in this post.

yup - CPI MRK 8

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

713 now

7.13 appears to start (and make progress) on each of my 2 GPUs (GTX 660 Ti, GTX 460). It does not crash immediately.
So... I guess I'll let it run, and try to remember to report back when it's done.
Note: GPU Usage is around 15%-25% while processing the task, quite low.

PS: I'd also love to see the DRIVER VERSION printed in the stderr.txt. Could prove quite useful in tracking down specific versions causing problems (which has happened in the past!)

Thanks,
Jacob

Better kill that - it will make way too much debug.
714 now.

MJH

You weren't kidding - 5 minutes created 140MB debug :)
Hope everyone that got 7.13 knows to abort them!

For me, 7.14 is running/progressing at an appropriate GPU Usage, without any immediate crash.

One 7.13 finished ok in about 7 minutes on my Titan.
http://www.gpugrid.net/result.php?resultid=7199039

The another 7.13 crashed at sRKA 7

http://www.gpugrid.net/result.php?resultid=7199046[/url]

One 7.13 finished ok in about 12 minutes on my gtx 680
http://www.gpugrid.net/result.php?resultid=7199074

---

Three 7.14's completed ok.
http://www.gpugrid.net/result.php?resultid=7199117
http://www.gpugrid.net/result.php?resultid=7199119
http://www.gpugrid.net/result.php?resultid=7199122

My 7.14 task finished successfully too, but I don't know what GPU was used - that debug info has now disappeared :)

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

I would like to see, at a minimum, each time the task is started/restarted:
- GPU Name, Vendor, and Memory size
- Driver Version
... hopefully you can also include other identifying information too, as others have suggested, and as that other thread seems to show that you once actually did print/include!

the webpage only show the last few lines of the debug.

One 7.14 finished ok in about 1 minute. GPU utilization ~ 72%
http://www.gpugrid.net/result.php?resultid=7199239

---

One short 7.14 finished fine.
One long 7.14 and 7.15 is running...