Home

SQL Server 2016 crashes

%3CLINGO-SUB%20id%3D%22lingo-sub-1096502%22%20slang%3D%22en-US%22%3ESQL%20Server%202016%20crashes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096502%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20facing%20really%20weird%20issue%20with%20MS%20SQL%202016%20crashes.%20Every%20so%20often%20there%20is%20a%20crash%20dump%20generated%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESqlDumpExceptionHandler%3A%20Process%20105%20generated%20fatal%20exception%20c0000005%20EXCEPTION_ACCESS_VIOLATION.%20SQL%20Server%20is%3CBR%20%2F%3Eterminating%20this%20process.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20information%20is%20very%20vague%20so%20you%20cannot%20really%20determine%20what%20is%20the%20cause%20of%20it.%20I%20was%20playing%20with%20the%20dump%20file%20a%20bit%20An%20I%20got%20into%20the%20module%20that%20is%20causing%20the%20crash%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%3CSPAN%3Entdll!NtWaitForSingleObject%2B0x14%3A%0A00007ffb%60d5255ac4%20c3%20%20%20%20%20%20%20%20%20%20%20%20%20%20ret%3C%2FSPAN%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BSQL%20is%20working%20the%20cluster%20with%204%20nodes.%20Two%20nodes%20are%20in%20one%20site%20and%20two%20other%20nodes%20are%20in%20the%20second%20site.%20Network%20is%20working%20fine.%20There%20are%20no%20error%20logs%20inside%20the%20system%20event%20viewer%20or%20Failover%20Cluster%20operational%20logs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20noticed%20that%20we%20are%20running%20on%20older%20version%20of%20ODBC%20drivers%20which%20is%2017.3.1.1%20and%20the%20newest%20one%20is%2017.4.2.1.%20Do%20you%20think%20this%20might%20be%20related%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ERegards%2C%3C%2FP%3E%3CP%3EWojciech%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1096502%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Edump%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ememory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESQL%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESQL%20Server%202016%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

Hey Guys,

 

I am facing really weird issue with MS SQL 2016 crashes. Every so often there is a crash dump generated:

 

SqlDumpExceptionHandler: Process 105 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.

 

This information is very vague so you cannot really determine what is the cause of it. I was playing with the dump file a bit An I got into the module that is causing the crash:

 

ntdll!NtWaitForSingleObject+0x14:
00007ffb`d5255ac4 c3              ret

 

 SQL is working the cluster with 4 nodes. Two nodes are in one site and two other nodes are in the second site. Network is working fine. There are no error logs inside the system event viewer or Failover Cluster operational logs.

 

I have noticed that we are running on older version of ODBC drivers which is 17.3.1.1 and the newest one is 17.4.2.1. Do you think this might be related?


Regards,

Wojciech

Related Conversations
Sequencing based on the Value
rolo1007 in Access on
3 Replies
Room calendar multiple booking
ThomasVde in Exchange on
3 Replies
Combo box does not retain selected values
monica_123 in Access on
10 Replies