FIX: Heavy Stress on Tempdb with Multi-CPU Computer May Cause AVs or Level 600 Error

SYMPTOMS

You may receive "max connection" errors, access violations (AVs) and/or 600- level errors if you are using a multi-processor computer and tempdb is under heavy stress (creating or dropping tables, using SELECT INTO statements, and so on).

In the case of "max connection" errors, the server goes into a spin loop and stops responding. The following is an example of an error message you may receive:

The following are some example AVs (taken from Debugsr.exe 6.50.262):

97/07/12 03:06:10.07 spid11   ***BEGIN STACK TRACE***
97/07/12 03:06:10.18 spid11   0x005DD5BC in debugsr.EXE, getobject() +
0x01EC
97/07/12 03:06:10.34 spid11   0x005A6A34 in debugsr.EXE, droptempo() +
0x0636
97/07/12 03:06:10.40 spid11   0x0051C4A3 in debugsr.EXE, tmp_alldrop() +
0x014A
97/07/12 03:06:10.47 spid11   0x00511281 in debugsr.EXE, s_free() + 0x005A
97/07/12 03:06:10.47 spid11   0x0051118A in debugsr.EXE, s_pop() + 0x00B9
97/07/12 03:06:10.50 spid11   0x0055D492 in debugsr.EXE, execproc() +
0x11EB
97/07/12 03:06:10.55 spid11   0x00559751 in debugsr.EXE, s_execute() +
0x0E81
97/07/12 03:06:10.62 spid11   0x0050E5EC in debugsr.EXE, sequencer() +
0x035C
97/07/12 03:06:10.67 spid11   0x004156C1 in debugsr.EXE, language_exec() +
0x06DD
97/07/12 03:06:10.74 spid11   0x00250FED in opends60.dll
97/07/12 03:06:10.74 spid11   0x0025055B in opends60.dll
97/07/12 03:06:10.74 spid11   0x002414D1 in opends60.dll
97/07/12 03:06:10.74 spid11   0x00241384 in opends60.dll
97/07/12 03:06:10.74 spid11   0x10219D84 in MSVCRT40.dll
97/07/12 03:06:10.74 spid11   0x77F04F2C in KERNEL32.dll
97/07/12 03:06:10.75 spid11   ***END STACK TRACE***
97/07/12 03:06:11.16 kernel   The current contents of process'''' input
buffer are ''''exec p1''''.
				

Limited testing has shown this problem only occurs in an extremely narrow scope where both a high performance server and heavy volume activity are involved.