Regarding the suggestion about Watson, that certainly is a possibility, but my experience is that Watson doesn't trigger on it's own out of the blue. Something really bad has to happen, usually with something to do with the Win32 API or worse for it to come into the picture. Also you might be able to get some more insight into what's going on by looking over Windows event logs around the time of the failure for clues.
Alinator
I concede that Alinator is right on the Dr. Watson issue concerning my suggestion. (The main box I use is pretty minimalistic and streamlined without what I consider bloat (most normal startup programs, etc., etc.)
Here is an article that correlates with Alinator's advice on looking over the event logs.
I wouldn't even know where to start on that. I have done a registry scan, reset the seti project too and stopped crunching seti beta. So far things have been quiet and Dr Watson has been minding his own business. Fingers crossed.
RE: RE: Regarding the
)
I wouldn't even know where to start on that. I have done a registry scan, reset the seti project too and stopped crunching seti beta. So far things have been quiet and Dr Watson has been minding his own business. Fingers crossed.
Physics is for gurls!