http://www.pasteall.org/pic/82780

sorry.. pasted same screenshot twice

What Driver do you have long time no talk

Am testing like mad...

Started with factory defaults and 'Supported' Mode.
Maybe it is due to 'experimental' I had/have in several scenes.
I'm checking this out also..
Trying different OpenGL settings also..
Would be great to know what 'normal' settings would be for a setup like mine..

I'm also considering that maybe it's an OS problem.
At the moment, I can't reproduce the screen corruption after a reboot and preventing screen saver to come up..
(Apple forums blame all kinds of strange behaviour due to 'wake after sleep'.. I do not have sleep or hybernation activated, only monitor sleep, but testing also)

It takes a lot of testing so please bare with me.

Did some further testing today.

Seems that OSX Yosemite is very 'unstable' regarding GPU usage.. and more prone to corruption of the screen.
On Mavericks I have not been able to reproduce them again today although one of the screenshots sent earlier was made while on this OS (the blender window corruption)
So I really don't know if Yosemite has problems or they only arise because this OS asks more of the GPU..

I'm not sure if you can investigate if Blender will/could run into issues when Yosemite is more mainstream..
We'll have to wait until more users (are FORCED to) update...

If there's a developer who wants to test something on my hardware, feel free to ask!

Regards,
Roel

This is your filed here

A few days ago, NVidia updated their CUDA drivers once again in a short amount of time..
It's now at 6.5.45 (10.2.1 310.41.15f01)

Last couple of hours my Blender is stable on GPU.. if it's due to that particular driver I don't know but I'll keep my fingers crossed.

BTW. It seems that some of my scenes have 'experimental mode' on. Could this be also a reason for screen corruption?
I will keep on testing..

Thanks
Roel

Bummer,

The screen corruption has returned..

http://www.pasteall.org/pic/83287

If I only could rule out hardware problems.. but I don't know how..
on a Mac there is not much I can test.. I would like to test each and every byte of graphics memory.. but I haven't got the tools..

Notes:

• This instance it corrupted the Blender window only, the rest of the OS kept stable.. (this is new behaviour)
• These things show up like crazy in console..

04/02/15 09:35:44,690 WindowServer[127]: Surface testing disallowed updates for 10 sequential attempts...
04/02/15 09:35:45,013 WindowServer[127]: Surface test allowed updates after 77 attempts

Does apple allow you to boot from a bootable source e.g. thumb drive

if so could you make a linux bootable

so you can try on a different os on the same computer

I'm familiar with linux/booting from thumbdrives etc..

On a mac it's a different story but not impossible ;)
My best guess now is that I'll have more trouble getting a stable linux distro on mac hardware than getting Blender on it to test corruption.. but it's worth a try!

What I've done now is again went back to Mavericks (for a couple of days) and keep on doing what I've been doing..
I first want to rule out that miserable thing they call Yosemite..

Thanks

Hi

This is definitely a bug in Yosemite or Nvidia Drivers/CUDA or both as I have the same issues on Yosemite 10.10.2, CUDA Driver Version: 6.5.45, GPU Driver Version: 10.2.1 310.41.15f01 (all latest versions)

Regards,
Rafal

Rafal,

You can't imagine how happy I am to hear that!
Not because we both have issues, but to rule out my hardware!

I'm back on Mavericks (not the greatest OS either..)

Thanks again for sharing that info.. means a lot..

What I don't know however is how this 'bug report' should be treated now..
If Apple has changed the 'rules' regarding screen invalidation, refreshes or whatnot, maybe the issue will never disappear.
Maybe the blender code still needs some 'adjustments'?

Regards!
Roel

Hi Roel,

I think I have found the root cause - OS X Default Graphics Driver.

I have just installed these Web Drivers from Nvidia: http://www.nvidia.com/download/driverResults.aspx/81365/en-us
and all the issues with screen corruption disappeared... for half an hour I haven't seen any screen artifacts while using GPU preview/rendering in Cycles.

Unfortunately for you, they are only for Mac Pro, so you probably won't be able to install them on iMac.

Br,
Rafal

@jens verwiebe (jensverwiebe) should know (or should be able to find out) if this is a issue on Blender's side or Mac OS'

Unfortunately i have no NVidia gpu in my MAcPro atm., still hesitant to get an GTX 970 due 'am
a LuxRender user and AMD is much better with these.

I really dunno whats up with these drivers nowadays. Also the issue could be the cuda sdk used itself ?
I used the cuda_6.5.25_mac_64.pkg for 2.73a. We should lookup if there are newer ones thats perhaps
fix issues. What users could check if older Blender rises same problems which would point to buggy sdk.

Jens

I have verified few Blender releases back. All suffered from the screen artifacts a lot, even the versions which I remember that they were working properly.
For me new Nvidia Web Drivers solved this problem completely.

Would you please reconsider keeping this open for a bit?
Finally there is a thread investigating the issue's..

Compiling Blender with a possible updated SDK could also be a fantastic strategy..

Cuda drivers for the user get updates frequently. I've had similar good results, but issues kept returning..

Driver bugs are nothing we can solve, so I don't see a reason to re-open. You can still add comments/more findings here if you like though. Thanks.

Anyone find a solution yet?

This driver update seems to have fixed issue as it is not happening anymore crossing fingers.

https://developer.nvidia.com/cuda-downloads

I'm at 7.0.36 at the moment, but I still have the issues..
It seems that when approaching max gpu memory usage, the screen corruption starts..

My case, an iMac with 780m, has no other video card, so all memory has to be divided between cuda, dual screens and whatnot (forgive me if I'm not savvy enough to explain that better)
Maybe that's why the screen corruption also has an effect on 'finder' windows and also complete system crashes..

Roel

I am and was at 7.0.36 also however when I found that link it download and installed some tools and samples the cuda driver version didn't change yet it quit having the issue. After that install

I will check this right away..

By the way..
http://www.pasteall.org/pic/show.php?id=89314

It shows out of memory at 2Gb? while my card is 4Gb?
Or is that statement complete nonsense?

Make sure your max prefences is as high as your memory. It seemed to have updated my cuda driver installer or something hopefully this continues to work I've been rendering all morning since update still running fine.

please explain 'max preferences'..

after I've installed the pkg, the cuda preferences panel shows the 7.0.29 and the message that an update is available..
now it says
cuda driver: 7.0.29
gpu driver: 10.4.2 310.41.35f01)

you said the info still shows 7.0.36 after that 29 install?

It first took it back to .29 then yes required to update again to .036 in system settings cuda update.

On .29 I got screen corruption without much trouble... after an update back to .36 (and reboot)
I gave it a large scene to chew on.. and almost immediate corruption:

http://www.pasteall.org/pic/show.php?id=89317

so my problems are still there..

btw.. would you please explain the max memory allocation? I'm not aware of any setting to do just that

Go in to preferences and increase max memory based on your system. I have 32 gb ram plus the 4gb card i'm sure this helps my situation. Animation I'm rendering is not a huge scene either, but I'm not having issue since the reinstall of driver. Not sure if it will happen again when I do a scene with more vertices sounds like yours is much bigger if its saying out of memory.

Hate to be a drag.. but I really haven't got a clue what you're saying with increase max memory based on your system..
Blender has no options like that, that I'm aware of.. only Undo Buffers and VSE preload memory allocation..
Neither of the two have something to do with CUDA memory allocation to my knowledge..

btw.. I have 16Gb Ram and 4Gb 780m... that does not explain why cuda gives an out of memory error at 2Gb
But maybe some other apps (OSX itself maybe?) reserves 2 for itself? I wouldn't know.. disconnecting my 2nd screen doesn't change anything..

I think the corruption occurs when using memory to the limits.. maybe allocation overlap issues? but who am I to suggest that...
When I was coding back in the days, we'd allocate on the fly, and never cleaned up after ourselves ;-)

In preferences under editing it has memory limit I have this increased over the default which may not help in rendering but increases available memory for editing at least. I wish I could use my system memory and cuda together?

Looks like a spoke to soon its already happening again