As some will no doubt already be aware, there is an elusive bug in conjunction with nVidia graphics cards that causes a crash to desktop. This bug has been difficult to track down, as for some reason it seems to only show up in somewhat large PvP scenarios, and neither I nor anyone else seems to have been able to come up with any method for reproducing it in a controlled manner. The fact that the crash happens in the driver also makes it difficult to collect ancillary information. Because of all this, this bug has remained elusive for well over a year at this point, despite it being quite critical.
Some time ago, someone (I only heard of it indirectly, so I actually don't know who) managed to figure out a way to make the driver crash in a seemingly identical manner. It should be well noted that crashing in the same manner doesn't necessarily mean that it crashes for the same root cause, but nevertheless it's the best (or only, really) lead that I've got so far. Specifically, the crash happens when issuing an OpenGL draw command that takes data from a zero-sized Vertex Buffer or Index Buffer. Since a while back, therefore, I've made the client emit warnings whenever it attempts to create such a buffer object, however the only mechanic I've been able to find that has done that has been the falling leaves in autumn (and it also avoids the actual crash by not actually attempting to draw any vertices), and that's clearly not the cause of the issue, since crashes haven't only happened during autumn.
Therefore, I'd appreciate it if you all could check your warning logs, especially any of you who have experienced a crash-to-desktop lately (but regardless, really; it's not like it's guaranteed to cause a crash). These critical warnings are saved in your user home directory (which, on Windows, is usually C:\Users\<your-username>\), and is called haven-errors.log. If you have a file of that name in your home directory, please convey its contents to me in one way or another, by posting it directly in this thread if it's small enough, using the forum Attachment function if it's larger than that, or in some other manner of your choosing.
Of course, I don't know how many custom clients have actually merged this warning functionality, and it would be unfortunate if a useful warning had been lost, but let's hope someone has logged a clue. It would be quite great if this bug could finally be fixed!