I looked into it, but I can't reproduce it with the 2.80 release from the 30th. I tried my damdest, I even looked up the dimension of the final shot and number of edges etc but nope...
If I run into it again, I will post the blend file to this report.

I experienced this too. It was when using a simple deform and I CTRL-Z back because I didn't like the result and blender just crashed. I can see if I can reproduce it and post a scene file.
It was very predictable in that combination. So I'll get into it now, see if I can reproduce it.

You called the cops???... Oh Balls!! That’s what the guy in the boot would say (if he still was alive ;) )

Obviously there’s no animation, and thus no change in the frames. But I rendered 12 of the same frames without crash.
So there’s a definite link with Animation Nodes or animation.

After rendering about 20 frames of the animation_pillars.blend it started crashing again. And each time it now crashes again after about 5 frames.
Franmes where it crashed were: 50, 60, 65

The random crashes after rendering frames seems to be solved in 2.80.42 release.
Well done!

I made a change to the blend file, where in the Animation Nodes I have added a function that changes the material based on a Z value. Since that moment it crashes structurually when pressing F12 or CTRL-F12.
I don't know whether this could be related but at least it's easy to reproduce this one.

My workaround is to start NVIDIA control panel. Add the blender.exe executable that causes the error and add it to the Manage 3D Settings list.
Since I have 2 GTX680 GPUs in SLI, I found that setting GPU 1 of 2 solves the issue.

I am experiencing this too. I'd been working on project all evening. Blender then crashed after that as soon as I open the project I get that exact same error.
I also upgraded the NVIDIA drivers just in case. But OpenGL 3.3 is pretty old so I already had the idea that this wouldn't solve the issue.