It's worked out a couple of times... "How can the process have failed when the logs indicate success?" "Everybody lies." "Oh, so maybe the log is written at some point before the process actually finishes?" "Treat with steroids."
It's never hardware... except that one time that it was. [1]
[1] http://www.bit-tech.net/news/hardware/2012/03/06/coder-finds...
Years ago when I was doing tech support a fellow on Long Island would call up and start explaining his problem--at a rate of speech that made me get out of breath listening. Usually, about 3 minutes into the call he'd arrive at the answer that had been occurring to me, thank me, and hang up.
Just writing out what I'm trying to do in a hypothetical email to someone who has no knowledge of the problem usually unties the knots in my brain.
At least take the time to sit down and write up a detailed explanation of the problem first. Do your due diligence before consuming the time of another developer.
The theory is definitely sound, but simply saying "phrase your question in an email to me, making sure to be detailed" should suffice. Talking to stuffed animals is probably unnecessary!