I normally recommend configuring the system to generate a full memory
dump. But at the very least, it should be generating a small memory dump
(file name MEMORY.DMP) when the stop occurs. The MEMORY.DMP file can then
be loaded into a debugger (like windbg.exe), from which the error can be
viewed. If you use windbg.exe, "!analyze -v" will show the module that
triggered the failure.

See http://www.microsoft.com/whdc/devtools/debugging/default.mspx as a
starting point for the Windows debugging tools.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 09/05/2007
12:25:30 PM:

> TSM server 5.4.1.0, running on Windows 2003 server standard (w/ SP2).
>
> Hardware is DL380G5.
>
> Backup client is installed, and is version 5.4.1.0 as well.
>
> While backing up two large NetApp filer shares, server will get Stop
> Error and reboot. Problem is 100% repeatable.
>
> So far, we've upgraded the NIC drivers, but the problem has not gone
> away.
>
> Any tips on tracking down which piece of code is causing the "Stop
> Error"?