I've had crashes on heavy scenes while navigating, creating materials, and also on empty scenes... sometimes even starting Cinema4D with OpenGL enabled and idling my computer on an empty scene for a while would freeze up Cinema 4D when I came back, so I don't think it's related to any specific use.
I've had to forcequit every single time, with no bugreport present when firing it back up. A couple of times (1 or 2 out of 100) I've gotten a warning, stating that the driver has crashed, but that could be related to some other issue, at this point I just don't know.
I just gave up calling the IT guys after about 2 months of constantly nagging them. Once, the IT guy actually sent the workstation back to HP and HP even replaced the motherboard (wtf's that got to do with anything?!?), but I'm doubtful, that they actually replaced anything at all.
I do not know it the issue is resolved in R17 or R18.
It's interesting that Cinema doesn't crash on you if you're using Physical or Standard, I almost strictly use Physical and it's crashing all the time with OpenGL.
I just did a quick test with Alpha from the Corona site.
With OpenGL enabled
Switched renderer to Corona, made a cube, made a corona material, made a light, while moving the light - It froze up.
Another try, froze up when creating the material.
With OpenGL disabled
Same procedure, working fine without interactive.
Same procedure, I enabled Corona interactive, and Corona_Release.dll crashed, bugreport and everything, as expected.
Certified drivers don't work for me, maybe it'll work for GilmourMotionDesign.
----
If anyone had the same problem with R16.051 or 16.050 and got it working on R17 or R18, please let me know also, maybe I can convince the powers that be for an upgrade.