A Very Annoying X Problem

I've bitten again by a very intermittent X problem. Sometimes my X run smoothly for a month (with many hibernates in between), but these last couple of days, it stroked twice! I can't find any informative messages in logs. Not in any /var/log/X*, /var/log/messages, /var/log/syslog, ~/.xsession-errors. This .xsession-errors is ultimately can't be used for anything! It doesn't have timestamps on each event; no standard delimiter between events; what can you hope to salvage from this garbage?

$ tail -50 .xsession-errors
at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.runSelect(TCPConnectionManager.java:535)
at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.mainLoop(TCPConnectionManager.java:212)
at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.access$900(TCPConnectionManager.java:45)
at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager$5.runSupport(TCPConnectionManager.java:201)
at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:71)
Peringatan pengatur jendela: Error IO yang fatal berkode 104 (Connection reset by peer) pada tampilan ':0.0'
nm-applet: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
gnome-panel: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
The application 'update-notifier' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'nautilus' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'bluetooth-applet' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'kerneloops-applet' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'gnome-screensaver' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'gnome-settings-daemon' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
opera: Fatal IO error: client killed
pidgin: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
The application 'SWT' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
X IO Error
The application 'gedit' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'gecko' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'gnome-session' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
The application 'gnome-terminal' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
liferea: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
Exit from Azureus complete
[1211343465,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
(gnome-panel:4361): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed

(gnome-panel:4361): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed

FYI this is a Debian Sid box.

So, how would you debug this problem? Run a debug version of X server and collecting huge amount of garbage without any time reference? Throw away this box and buy a better one? Use Windows XP instead? Get a plastic surgery? Please, pretty please, help me!