First up, Phil has it right. Get backups of *ALL* the databases on the server and test restore them. It doesn't have to be to a "server," they could have someone set up SQL2005 on their desktop machine and restore there. Make sure the backups are good!

Boiling it down, in order of importance, I'd:

1. Set up backups of all the databases

2. Test those backups on another system (server, desktop, someone's spare laptop from home, doesn't matter)

3. Investigate the cause of the BSODs (could be a fixable hardware issue)

The other thing is, as they're on SQL2005, they're either going to have to scrounge up a SQL2005 Developer Edition, violate licensing and install their existing copy on that 2nd PC, or if someone has an MSDN Subscription they might be able to get a copy from there.

But the point they need to keep in mind is not "fix the server," it's PROTECT THE DATA. And that means making sure not only that it's being backed up, but that it can be restored and used.