http://bugs.winehq.org/show_bug.cgi?id=20448
--- Comment #3 from Henri Verbeet hverbeet@gmail.com 2009-10-23 19:33:28 --- That situation can only happen when your graphics driver setup is broken. The window system provided framebuffer can never be invalid, and 0 is not a valid return code for glCheckFramebufferStatus().
I'd be ok with printing an ERR instead of crashing, but I doubt it'll make the application work correctly. I think there's already a bug filed against Mesa for this.