This is what Visual Studio 2015 debugging gives

Visual C++ 2015 debugging gives this info. I hope it helps?

Forgot to mention, it was EXCEPTION_ACCESS_VIOLATION.

OK. I can confirm this. Attaching suncrash.txt (the -d export) and also crash log crash.crash.txt

I managed to get it to crash, I think at that time Sun sample = 55. But its rarely happens (as in hard me to re-create it), as if it was random.

You must increase Sun Light's sample ratio (by this way realtime render time increase). and when not finish Viewport Render, then press F12 and render. 3-4 times after Blender crash, not say anything, not show message box, not create debug log, only crash and close...

I can't recreate the crash. Win 7 + GTX 750. I notice the first time I press F12, twice the renderer windows says "Not Responding" but after a while it continues rendering. I repeat rotate the viewport (causing it re-render) and presses F12.

Hi, is this problem still an issue 2.78c ?

This is indeed not a bug, the pass ID is not inherited by objects in the group. Overriding the ID is not always the desired behavior, it depends. The new collections / overrides planned in 2.8 are intended to let you control this kind of thing.

Thanks for the report, but this has absolutely nothing to do with linking - thing here is that pass ID of group instantiations is not used for group’s objects…

Hi Mario,

Rotate several times Vieport Realtime Render panel and F12, and exit. Repeat 3-4 times, and after crash, also if Viewport Render operation not finish and press F12.

I send a scene file, if you want. Bu this issue happens all scenes...

Unless this happens with the default scene, we need a .blend file to reproduce this problem.

Blender don't create text file after crash. I use debug mode, my file is saved, and no text file created on file directory or Temp directory. Only create "blend" file on Temp directory.

Was crash log generated? Please upload if it does. Thanks.
https://docs.blender.org/manual/en/dev/troubleshooting/crash.html

This file is configured to use Filmic color management. Without that you would get an immediate mapping of the color ramp to the ones in the final render, however with Filmic there is contrast adjustment that causes the differences you see. For these types of toon renders disabling Filmic may work better.

Please attach a .blend file that demonstrates the issue.

but I like BI because it is fast and not focused on realism, which is exactly what I need for my visualiser.
Will Eevee be able to deliver the same speed?

I stumbled across the fix : USER PREFS > SYSTEM > OPENGL CLIP ALPHA change from default 0.04 to 0.5

Wow… indeed…
Will close the report as known issue then, tbh it’s very unlikely it ever gets fixed now, since we plan to remove Blender Internal from Blender2.8 (to be replaced by real-time OpenGL Eevee). Thanks anyway!

This is an old issue, see e.g. T18056: Quad directly infront of the camera gives artifacts.

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

Uuuh… weird, looks like a triangulation issue. Not sure what happens here, in viewport rendering shows no issue, and your scene does not use insane scaling or nearly-coplanar faces, so…

the werid below-ground color

sun is not available maybe but in luxrender(spectral) it is

Thanks for the suggestion, but this tracker is not for feature requests, see here for other options:
https://wiki.blender.org/index.php/Dev:Doc/Contact#Requesting_Features

Reduce your tile size in the render settings, should fix the issue.

There was no crash reports at that time for id 4101, but this is what was found during the error "illegal address" :

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvlddmkm" /> 
<EventID Qualifiers="49322">13</EventID> 
<Level>2</Level> 
<Task>0</Task> 
<Keywords>0x80000000000000</Keywords> 
<TimeCreated SystemTime="2017-06-19T14:33:07.194255300Z" /> 
<EventRecordID>14416943</EventRecordID> 
<Channel>System</Channel> 
<Computer>Computer_i7</Computer> 
<Security /> 
</System>

• <EventData> <Data>\Device\UVMLiteProcess4</Data> <Data>Graphics Exception: ESR 0x524e48=0x1000e 0x524e50=0x4 0x524e44=0x13eff2 0x524e4c=0x7f</Data> <Binary>0000000002003000000000000D00AAC0000000000000000000000000000000000000000000000000</Binary> </EventData> </Event>

Can you check your windows event log for any reports of event ID 4101 around the time that blender crashes?

Here's the blender.log, I assume there's only the last part of the action (quit)...

Thanks, now we know issue is still in current code.

Ok, latest version 2.78 downloaded - results :

• Blender default scene
• Cyclic rendering
• GPU mode

--> render -> CUDA error : illegal address in cuCtxSynchronize(), line 1371 (render stops)

In T51696#440786, @Bastien Montagne (mont29) wrote:

@Tapani Korhonen (Tapu) Please always try the latest build from our buildbot.

Ok, this is the version what I'm using at the moment. It has been released in january 2017, I installed this version in april - it's the official version.