FIX: "SqlDumpExceptionHandler: Process <spid> generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION." error when you run a query in SQL Server 2012, in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2005

Article ID: 972936 - View products that this article applies to.
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.
Expand all | Collapse all

On This Page

Symptoms

In Microsoft SQL Server 2012, Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2 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>]
You may also experience the following problems:
  • A query that is run against sys.dm_os_wait_stats encounters an access violation. The request could be from another program like Activity Monitor or from the data collection job that is used by Management Data Warehouse.
  • Other queries that are run against sys.dm_os_wait_stats may appear to wait indefinitely on the DEADLOCK_ENUM_MUTEX wait type.
Back to the top | Give Feedback

Resolution

Cumulative update information

Cumulative update 6 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2728897
(http://support.microsoft.com/kb/2728897/ )
Cumulative update package 6 for SQL Server 2012
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 2012 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:
2692828
(http://support.microsoft.com/kb/2692828 / )
The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative Update 5 for SQL Server 2008 R2 SP2

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:
2797460
(http://support.microsoft.com/kb/2797460/ )
Cumulative update package 5 for SQL Server 2008 R2 Service Pack 2
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 R2 SP 2 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:
2730301
(http://support.microsoft.com/kb/2730301/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Cumulative Update 2 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947
(http://support.microsoft.com/kb/2790947/ )
Cumulative update package 2 for SQL Server 2012 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 2012 SP1 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:
2772858
(http://support.microsoft.com/kb/2772858/ )
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative update package 10 for SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2783135
(http://support.microsoft.com/kb/2783135/ )
Cumulative update package 10 for SQL Server 2008 R2 SP1
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 R2 SP1 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:
2567616
(http://support.microsoft.com/kb/2567616/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008

The 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 2005

The 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.
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

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
Back to the top | Give Feedback

Properties

Article ID: 972936 - Last Review: February 18, 2013 - Revision: 6.0
Applies to
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2005 Service Pack 3
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
  • SQL Server 2012 Enterprise Core
  • Microsoft SQL Server 2012 Web
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Developer
Keywords: 
kbsurveynew kbexpertiseadvanced kbqfe kbfix KB972936
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top