SQL 2005 SP3 Error 17310 Severity 20 EXCEPTION_ACCESS_VIOLATION

[DatabasePrincess]

Hello all!

When I run T-SQL to drop and re-create a specific stored procedure on a development server, I get a stack dump every time and it disconnects my session from the server.

Server Info:
SQL Server 2005 SP3 (9.0.4035)
Windows Server 2003 Standard SP2
2 GB RAM

The procedure contains a union between two select statements which are built from a view. I found out that the dump occurred because I had misspelled a column in both select statements and in the order by clause. First I commented out the order by clause. I did not get the dump. That's when I noticed the misspelling from the syntax error it generated. Once I fixed the misspelling, I put the order by clause back in and it worked.

My big question is why did it cause a stack dump in the first place? Everything I've Google'd or bing'd points to a bug but they are all prior to SP3. Is this another bug? Could it be the server ran low on memory? Any ideas are greatly appreciated!

SQL Error Log:

Potential image corruption/hotpatch detected. This may be a sign of a hardware problem or caused by presence of CLR/jitted images on the stack. Check SQLDUMPER_ERRORLOG.log for details.
Error: 17310, Severity: 20, State: 1.

Here's some of the dump info:

=====================================================================             
       BugCheck Dump
=====================================================================             
This file is generated by Microsoft SQL Server 
version 9.00.4035.00
upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request.        
                    
Computer type is AT/AT COMPATIBLE. 
Bios Version is HP     - 2
Current time is 16:02:05 02/02/10. 
4 Intel x86 level 15, 3200 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
      
Memory
MemoryLoad = 95%
Total Physical = 2047 MB
Available Physical = 88 MB
Total Page File = 5993 MB 
Available Page File = 3584 MB 
Total Virtual = 2047 MB 
Available Virtual = 241 MB 
***Stack Dump being sent to F:\MSSQL.1\MSSQL\LOG\SQLDump0008.txt  
SqlDumpExceptionHandler: Process 93 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is 
terminating this process. 
* ******************************************************************************* 
*                   
* BEGIN STACK DUMP: 
*   02/02/10 16:02:05 spid 93      
*                   
*   Exception Address = 01B20F13 Module(sqlservr+00B20F13)        
*   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION       
*   Access Violation occurred reading address 00000000            
* Input Buffer 510 bytes -
*                create procedure

Here's info from the sqldumper_errorlog.log file:

02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 2000
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x02A3F808
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated with file F:\MSSQL.1\MSSQL\LOG\SQLDump0008.txt
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
02/02/10 16:02:06, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
02/02/10 16:02:08, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, ValidateModule: Potential image problem at 0x77E64841: read 0xE9 instead of 0x8B (module C:\WINDOWS\system32\kernel32.dll)
02/02/10 16:02:08, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
02/02/10 16:02:08, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: F:\MSSQL.1\MSSQL\LOG\SQLDump0008.mdmp
02/02/10 16:02:08, ACTION,              sqlservr.exe, Watson Invoke: No

 

[Jamfool]

You best bet is to contact microsoft with the error details so that they can check it and guide you as to the best resolution.

As you have said you are on sp3, and the latest code version is 9.00.4273 so it may already have been addressed. But again I stress it would be best to check with MS before applying any patches.

Below are the details for the latest updates links:

Cumulative Update 7 for SQL Server 2005 Service Pack 3

http://support.microsoft.com/kb/976951/

Some bugs that mention access violations:

371796 977247 (

http://support.microsoft.com/kb/977247/

)
FIX: An access violation occurs when you run a query on a table that has a partitioned nonclustered index in SQL Server 2005

376699 977842 (

http://support.microsoft.com/kb/977842/

)
FIX: An access violation occurs when you run the SET FMTONLY statement to set the value of the FMTONLY option to ON and the Microsoft SQL Server 2005 server is under memory pressure

 

[DatabasePrincess]

Thanks