Essentially, its the intersection of Murphy's Law and PEBKAC.
E.g., I'm currently helping someone build some s/w on Windows. He's a Linux hacker, and quickly gets frustrated by the Windows "everything has to be a GUI" imposition.
Now, when I personally built this particular package, I had no problems. But I've been hacking Windows for years, and know how to install/setup Visual Studio by rote.
So when my protoge encountered difficulties, I was at a loss. Until I learned he had all manner of crapware on his laptop. And 2 versions of Visual Studio. And the wrong version of the software to be built. And was missing one of the prereqs.
And so, after scrubbing his system, I walk him through the build process. But I can tell he's frustrated, and he has other responsibilities, so he's also a bit distracted.
Then I get his latest email listing the errors issuing forth from the build process. I know he's probably fuming at this point, and probably suspects I'm a part of this diabolic conspiracy to thwart his progress.
Then I point out that he's fatfingered an extra quote in the initial command line, which subsequently causes Perl and the generated makefile to do various bizarre, non-Windows things.
After correcting his mistake, he's now progressing nicely. But I'm certain the experience has further prejudiced him against Windows, and probably Perl, despite the fact that neither suspect is particularly culpable for his frustration.
So is there a word for it ? Perhaps the opposite of "serendipity" ? Roughly defined, its the act of making a personal error which you blame on the machine due to having previously experienced numerous machine induced errors.
If there isn't a word for it, there certainly should be. And there should be at least one expletive embedded in it.