Just an addendum to my last post, I enabled drwatson as my default debugger by doing a 'drwtsn32 -i' from the Run command. I wonder why HP tech, in the three times I spoke to them about this issue, never asked me about drwatson ??? Well, 'nuff said on that I guess. Anyway, hopefully when it happens the next time there'll be an error log. If in the meantime anyone has any suggestions based on what I wrote, I welcome them. I'm curious, would bad memory slots be a possibility? I asked that question to two of the tech reps, and they both said that if I had bad slots, I would get a beep when I tried to turn boot up the computer, and nothing would happen. A third one said it might be a possibility that I would still be able to boot up with a bad slot. Anyway, just asking, since these geniuses at HP didn't even ask about DrWatson.