The problem seems to be wine and bumblebee independent: I have tried several version of wine (ranging from 1.3.30 (and earlier) to 1.5.1), and also different version of bumblebee and the nvidia driver (from around 275.* to now 295.20).

With wine 1.3.37 (set on Win7) and 295.20 I have for the first time got the crash to take so long that I get some error messages. The crash acts a little different then:

* Computer locks for 5-10 seconds
* Realease for 1-3 seconds
* Flips image upside-down and mirrored (do not affect the apperence of the desktop, which also runs on the nvidia card).
* locks permanently (sometimes I get a few second window here to kill relevant processes, but not often.)

Good luck getting it resolved man. I know tons of people on these boards having this issue (I get it too but usually only when switching X sessions) and nvidia has pretty much ignored all reports of this issue and never replies to the threads =(

I have almost the same issue, only with me, Xorg will restart, leaving screen corruption in the top left corner. This issue only happens when I use the latest driver (295.33). Rolling back to 290.10 and my system is rock solid again.

edit, I don't use wine, it isn't installed. I sometimes get a hard crash but only on rare occasions. It is either Chrome or vlc, both are hardware accelerated.

Does anyone know how or where to look up these codes? This seems to be "13". I guess nvidia would have some code for thinks like 'overheating', 'unreadable memory', 'unwritable memory' and so on. That would at least say something if this is a software fault or because of hardware.

Starting to wonder if maybe my one 6990 that did not burn out in three months should go back in this box. IMHO, with all things considered, the AMD drivers are maybe a bit better than Nvidia's, but still nothing to write home about. Time to make a donation to the Nouveau project maybe....

I concur, 295.33 has been the most stable and incident-free driver yet.
295.40 is very finicky, throwing all sorts of XIDs with my usual use-pattern
(firefox + mplayer, kde).

I do not agree. The .20 have an avrage of maybe ~1-1.5 hours to crash (#13 and #39 errors), and .33 and .40 ~10 minutes (only #13). But that might be since .33 and .40 are 'unstable' in gentoo, maybe they'll be better once stabalized (or newer stable version comes out).

The crash then progress a bit further:
* The screen flips upside-down and mirrors, stays for a few seconds (10-20)
* The screen flips back (10-20 sec.)
* The screen flips upside-down-morror and back ~30 times in a row
* The application crash.