Stack dumps like this one are often due to bugs in SQL Server. The way to get them resolved is to open a support case with Microsoft. But since you are on a very old an unsupported version that route is not really open to you. Maybe you should consider upgrading to a more modern version - chances are that bug that causes the stack dump has been fixed.
Stack dumps can also be due to external components that runs in SQL Server's memory space. This can be:
- Extended stored procedures.
- OLE objects invoked from sp_OAxxxxx-
- Unsafe CLR modules.
- Linked servers using third-party drivers that runs with "Allow in-process".
If such components has bugs they can scribble SQL Server's own memory which leads to random crashes.
Another possible source for such dumps are hardware errors, particularly faulty memory sticks.