a lot of SQL Server dump files generated almost on the same time in C disk whic

Question

The version is Microsoft SQL Server 2017 - 14.0.3460.9. The issue happened on midnight, The application using SQL server didn't perform any Query ,Insert, Update ,Delete operation. We see a lot of error almost at the same time on Windows 10 event log.

The error is " lockMonitorThread: Process 5 generated an access violation. SQL Server is terminating this process."

In addition, a lot of SQL Server dump files generated in C disk, each dump is about 10M , total 36g dump files, caused the C disk full and other application could not run normally.

From the following dump, it should be a db deadlock resulted in a lot of dump files generated. Since the issue happened on SQL server level , Could you help to investigate this issue ?

Answer 1

Hi @Xianjun Zhan,

For this case, I really would suggest you to reach MS to open a ticket at

https://support.serviceshub.microsoft.com/supportforbusiness/create

With more professional background and remote desktop or other troubleshooting tool, they could be able to resolve this issue.

Regards，

Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

From the following dump, it should be a db deadlock resulted in a lot of dump files generated

Deadlocks never causes SQL Server to generate dump files; never.

Mainstream support for SQL Server 2017 ended Oct 11, 2022: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017

14.0.3460.9

Patch level is fine, but better install latest security updates as well, see

https://sqlserverbuilds.blogspot.com

Could you help to investigate this issue ?

Only MS Support can analyse dump file, but again: SQL Server 2017 = out-of-support.

Consider to upgrade to a supported version.

Answer 3

In addition to the other posts: Dumps like this are typically due to bugs in SQL Server, and the way to resolve it is to open a support case. But since you have a version that is out of mainstream support, that is not an option.

Restart the machine and hope that it does not happen again.