Oh, come on. That looks like a database error, and has nothing to do with Windows.
Is interesting that it coincided with MSBlast, though. Perhaps the machine on the *other end* was taken out?
Guess y'never know. Unless/until someone spills the beans on RISKS, anyway.
Now, I remember the time I saw a BSOD at the train station. That was funny. 
PS - Don't most ATM's still use OS/2?
As far as I can tell, there was a mass exodus off OS/2 for ATMs around the Y2k time. Probably not for any planned reason, but between IBM's EOLing, Y2k concerns, and the relative ease of reimaging what are, after all, just embedded PCs, a lot of things started turning up Windows during that time. It was a bit eerie to watch it disappear from recently-erected POS systems (the sort with the giant truecolor LCDs that you might see at any recently-renovated supermarket, that leave the titlebar and widgets visible for easy identifcation by peons like me)... I can only imagine whoever wrote the cash-register software probably EOLed the OS/2 version when IBM declared it dead, licensed, and supported for only another decade. Though as far as I can remember, those were usually seen with Warp 3 widgets, not 4 or later, so it wasn't like they were keeping current anyway.
Now, what the good ol' monochrome/textmode ATMs run is anyone's guess. (Or rather, there seems to be enough variation in those that I've never heard a conclusive 'answer.') Sure haven't seen *those* crash much, though I did fear for my card a few weeks back when one was slow to respond...
