Article ID: 972936 - Last Review: August 28, 2010 - Revision: 3.1 FIX: Error message when you run a query in SQL Server 2008 or in SQL Server 2005: "SqlDumpExceptionHandler: Process <spid> generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process."
Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. On This PageSYMPTOMSIn Microsoft SQL Server 2008 or in Microsoft SQL Server 2005, you query the sys.dm_os_waiting_tasks dynamic management view, an access violation occurs, and SQL Server crashes. Note Generally, the sys.dm_os_waiting_tasks view may be queried by an extra data collection utility, such as PSSDIAG. When this problem occurs, a mini-dump file is generated in the SQL Server log folder. Additionally, error messages that resemble the following are logged in the SQL Server error log file: Date Time SPID Using 'dbghelp.dll' version '4.0.5' Date Time SPID ***Stack Dump being sent to <Log file Path> Date Time SPID SqlDumpExceptionHandler: Process <spid> generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. Date Time SPID * ******************************************************************************* Date Time SPID * Date Time SPID * BEGIN STACK DUMP: Date Time SPID * Date Time SPID Date Time SPID * Date Time SPID * Date Time SPID * Exception Address = 0000000113DFDB00 Module(UNKNOWN+0000000000000000) Date Time SPID * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION Date Time SPID * Access Violation occurred writing address 0000000113DFDB00 Date Time SPID * Input Buffer 37 bytes - Date Time SPID * 16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00 Date Time SPID * ?? & J1 01 00 00 00 ff ff 0c 00 02 00 00 00 26 04 04 4a 31 04 Date Time SPID * 00 Date Time SPID * Date Time SPID * Date Time SPID * MODULE BASE END SIZE Date Time SPID * sqlservr 0000000001000000 0000000007AE3FFF 06ae4000 Date Time SPID * ntdll 0000000077B30000 0000000077CCFFFF 001a0000 Date Time SPID * kernel32 0000000076E10000 0000000076FFFFFF 001f0000 . . Date Time SPID * StFIR: 0000000000000000: Date Time SPID * StFDR: 0000000000000000: Date Time SPID * ******************************************************************************* Date Time SPID * ------------------------------------------------------------------------------- Date Time SPID 0000000113DFDB00 Module(UNKNOWN+0000000000000000) Date Time SPID 0000000002F74640 Module(sqlservr+0000000001F74640) Date Time SPID Stack Signature for the dump is 0x0000000164592CC6 Date Time SPID External dump process return code 0x20000001. External dump process returned no errors. Date Time SPID Error: 17311, Severity: 16, State: 1. Date Time SPID SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart). Date Time SPID SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. Date Time Logon Error: 17188, Severity: 16, State: 1. Date Time Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: <IP Address>]
RESOLUTIONSQL Server 2008The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:973602
(http://support.microsoft.com/kb/973602/LN/
)
Cumulative update package 4 for SQL Server 2008 Service Pack 1 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:970365
(http://support.microsoft.com/kb/970365/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2005The fix for this issue was first released in Cumulative Update 9 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:980176
(http://support.microsoft.com/kb/980176/LN/
)
Cumulative update package 9 for SQL Server 2005 Service Pack 3 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:960598
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCES
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates | Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
