April 18, 2006 at 2:57 pm
Hi,
Our SQL Server (SQL2K/SP4 on Windows Server 2003 R2 x64 cluster) restarted with error messages saying "SQL Server is aborting. Fatal exception c0000005 caught". The following is part of SQL Server Error Log,
--------
SqlDumpExceptionHandler: Process 6684 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 04/18/06 14:55:41 spid 0
*
* Exception Address = 7D620DD0 (RtlUnicodeToMultiByteSize + 00000139 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 0000003C
*
* MODULE BASE END SIZE
________
Does anyone out there have any idea what caused this problem? Any helps would be greatly appreciated.
Thanks.
April 19, 2006 at 9:23 am
there's a couple of knowledge base article that might help: one has to do with raising the # of locks, and the other is due to a denial of service attack:
Lowell
April 19, 2006 at 9:41 am
I read that article before posting this thread. It is my understanding that there are differenct causes for "c0000005 EXCEPTION_ACCESS_VIOLATION" which is indicated by "Exception Address" such as
"Exception Address = 0082EAEC (LockManager::AllocateLockOwnerBlocks + 00000047 Line 0+00000000)" in the artical you cited.
However, the problem I ran across was "Exception Address = 7D620DD0 (RtlUnicodeToMultiByteSize + 00000139 Line 0+00000000)". I believe it has someting to do with RtlUnicodeToMultiByteSize but have no idea what is that.
Thank you for your reply.
April 19, 2006 at 2:13 pm
Best bet for access violations is to send the minidump to Microsoft PSS.
Cheers,
* Noel
November 27, 2006 at 1:12 pm
Hi,
have you solved your problem with this error? I had the same error and have no idea how to solve it...
Can you help me?
November 27, 2006 at 9:22 pm
Yes, the problem was fixed by Microsoft. It took them about a month to figure out what the problem was and they sent me a hot fix. Probably you'd better to contact Microsoft for this issue.
Good luck
November 30, 2006 at 11:09 am
The log in event viewer was:
SqlDumpExceptionHandler: Process 1156 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 11/24/06 05:01:00 spid -7112
*
* Exception Address = 7D620DD0 (RtlUnicodeToMultiByteSize + 00000139 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000048
* TDS Input Buffer 81163403 bytes -
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBAFFF 008bb000
* ntdll 7D600000 7D6EFFFF 000f0000
* kernel32 7D4C0000 7D5EFFFF 00130000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 7DA20000 7DAFFFFF 000e0000
* MSVCP71 7C3A0000 7C41AFFF 0007b000
* MSVCR71 7C340000 7C395FFF 00056000
* opends60 41060000 41065FFF 00006000
* SHELL32 7C8D0000 7D0D2FFF 00803000
* GDI32 7D800000 7D88FFFF 00090000
* USER32 7D930000 7D9FFFFF 000d0000
* msvcrt 77BA0000 77BF9FFF 0005a000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* sqlsort 42AE0000 42B6FFFF 00090000
* ums 41070000 4107DFFF 0000e000
* comctl32 7DBD0000 7DCD2FFF 00103000
* sqlevn70 41080000 4108AFFF 0000b000
* CLUSAPI 74DE0000 74DF1FFF 00012000
* ole32 77670000 777A3FFF 00134000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* RESUTILS 74EF0000 74F02FFF 00013000
* USERENV 76920000 769E3FFF 000c4000
* NETAPI32 04080000 040D7FFF 00058000
* AUTHZ 040E0000 040F3FFF 00014000
* COMRES 044D0000 04595FFF 000c6000
* XOLEHLP 046A0000 046A5FFF 00006000
* MSDTCPRX 04770000 047E7FFF 00078000
* msvcp60 047F0000 04854FFF 00065000
* MTXCLU 04860000 04878FFF 00019000
* VERSION 04880000 04887FFF 00008000
* WSOCK32 04890000 04898FFF 00009000
* WS2_32 048A0000 048B6FFF 00017000
* WS2HELP 048C0000 048C7FFF 00008000
* NTMARTA 010C0000 010E1FFF 00022000
* SAMLIB 010F0000 010FEFFF 0000f000
* WLDAP32 01100000 0112DFFF 0002e000
* SSNETLIB 01140000 01155FFF 00016000
* security 01170000 01173FFF 00004000
* SECUR32 05280000 052CFFFF 00050000
* msapsspc 052D0000 052E3FFF 00014000
* MSVCRT40 05EF0000 05F00FFF 00011000
* msnsspc 05F20000 05F6FFFF 00050000
* mswsock 05F80000 05FFFFFF 00080000
* hnetcfg 06000000 06058FFF 00059000
* wshtcpip 060A0000 060A7FFF 00008000
* SSmsLPCn 06170000 06177FFF 00008000
* SSnmPN70 06180000 06186FFF 00007000
* ntdsapi 06250000 06264FFF 00015000
* DNSAPI 06280000 062A8FFF 00029000
* winrnr 062F0000 062F6FFF 00007000
* rasadhlp 06310000 06314FFF 00005000
* Kerberos 06330000 06387FFF 00058000
* cryptdll 06390000 0639BFFF 0000c000
* MSASN1 063A0000 063B1FFF 00012000
* rsaenh 06910000 0693EFFF 0002f000
* PSAPI 06970000 0697AFFF 0000b000
* msv1_0 06AF0000 06B16FFF 00027000
* iphlpapi 06B20000 06B39FFF 0001a000
* xpsp2res 10000000 102C4FFF 002c5000
* sqloledb 05950000 059D0FFF 00081000
* MSDART 059E0000 059F9FFF 0001a000
* MSDATL3 05A00000 05A14FFF 00015000
* oledb32 05DA0000 05E18FFF 00079000
* OLEDB32R 05E20000 05E30FFF 00011000
* xpstar 07150000 0719CFFF 0004d000
* SQLRESLD 05EC0000 05ECBFFF 0000c000
* SQLSVC 05ED0000 05EEAFFF 0001b000
* ODBC32 071A0000 071DCFFF 0003d000
* COMCTL32 071E0000 07276FFF 00097000
* comdlg32 07280000 072C9FFF 0004a000
* odbcbcp 07060000 07065FFF 00006000
* W95SCM 072D0000 072DCFFF 0000d000
* SQLUNIRL 072E0000 0730CFFF 0002d000
* WINSPOOL 07310000 07336FFF 00027000
* SHFOLDER 07340000 07348FFF 00009000
* odbcint 07520000 07536FFF 00017000
* NDDEAPI 07650000 07656FFF 00007000
* SQLSVC 07660000 07665FFF 00006000
* xpstar 07670000 07678FFF 00009000
* SQLFTQRY 07680000 076A5FFF 00026000
* srchadm 07960000 07995FFF 00036000
* mssws 079A0000 079A7FFF 00008000
* SXS 07E20000 07EDBFFF 000bc000
* athprxy 07EF0000 07EF7FFF 00008000
* xpsqlbot 07F00000 07F05FFF 00006000
* ACTIVEDS 06980000 069B2FFF 00033000
* adsldpc 069C0000 069E6FFF 00027000
* credui 069F0000 06A1DFFF 0002e000
* ATL 04F70000 04F81FFF 00012000
* adsldp 06A60000 06A8DFFF 0002e000
* dbghelp 08C50000 08D4FFFF 00100000
*
* Edi: 0023BE38: 00030002 000800F5 0022E438 0022E450 00000000 00000000
* Esi: 0023BE48: 00000000 00000000 00000044 C731054C 11D1AC80 C000F38D
* Eax: 0023BE50: 00000044 C731054C 11D1AC80 C000F38D 4FEFB64F 00000000
* Ebx: 001D0000: 000000C8 00000132 EEFFEEFF 00000002 00000000 0000FE00
* Ecx: 00000000:
* Edx: 00000044:
* Eip: 7D620DD0: 89044A3B 850F1455 00002948 850FC83B 00002940 EDE85356
* Ebp: 07D1FDF8: 07D1FEE0 7D620EA5 001D0000 C731054C 07D1FEC0 00000000
* SegCs: 00000023:
* EFlags: 00010246: 00630065 0043003D 005C003A 00490057 0044004E 0057004F
* Esp: 07D1FDEC: 001D0000 0023BE38 00000000 07D1FEE0 7D620EA5 001D0000
* SegSs: 0000002B:
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
* 7D620DD0 Module(ntdll+00020DD0) (RtlUnicodeToMultiByteSize+00000139)
* 7D620EA5 Module(ntdll+00020EA5) (RtlUnicodeToMultiByteSize+0000020E)
* 7D636994 Module(ntdll+00036994) (RtlDowncaseUnicodeString+0000011A)
* 7D62B977 Module(ntdll+0002B977) (LdrShutdownThread+00000129)
* 7D4E0A7F Module(kernel32+00020A7F) (ExitThread+0000002F)
* 7D4E072F Module(kernel32+0002072F) (FlsSetValue+0000013C)
* -------------------------------------------------------------------------------
SQL Server is aborting. Fatal exception c0000005 caught.
Stack Signature for the dump is 0xE322EAF7
Could you please tell me if this log error represents exactally the error that has occurrend in your server...
Thanks,
December 5, 2006 at 7:44 am
Exactly the same as our error.
December 5, 2006 at 10:46 am
Thanks,
December 15, 2006 at 7:44 am
Would you happen to have a KB, SRX, or file name associated with this fix? We have the same issue. Thanks!
December 15, 2006 at 8:01 am
Here is the SRX
SRX060501603817
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy