asked on
SqlDumpExceptionHandler: Process 41 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
PLEASE
view attachment
The files . mdmp are being saved in the Log folder of Disk C where SQL Server C: \ Program Files \ Microsoft SQL Server \ MSSQL13.POSEIDON \ MSSQL \ Log is installed, the .mdmp files are equal to the dump file I think, when you I right click on a dump file and see its properties, its extension is .mdmp
On the C disk the mdf and ldf files of the databases are not being saved, on the C disk there are only the installation folders and the 223 GB weight of the log referred to the Log of the installation folder C: \ Program Files \ Microsoft SQL Server \ MSSQL13.POSEIDON \ MSSQL \ Log and it's just so heavy because every day a lot of Dump files are being generated
On the other hand, we do not have visible problems with the bd server, everything works fine, it does not fall or anything, that's why I wanted to know why so many dump files are being generated daily or how could I identify what is happening to solve it? that eliminates the dump files and frees a little space, in a few days it is full again.
view attachment
The files . mdmp are being saved in the Log folder of Disk C where SQL Server C: \ Program Files \ Microsoft SQL Server \ MSSQL13.POSEIDON \ MSSQL \ Log is installed, the .mdmp files are equal to the dump file I think, when you I right click on a dump file and see its properties, its extension is .mdmp
On the C disk the mdf and ldf files of the databases are not being saved, on the C disk there are only the installation folders and the 223 GB weight of the log referred to the Log of the installation folder C: \ Program Files \ Microsoft SQL Server \ MSSQL13.POSEIDON \ MSSQL \ Log and it's just so heavy because every day a lot of Dump files are being generated
On the other hand, we do not have visible problems with the bd server, everything works fine, it does not fall or anything, that's why I wanted to know why so many dump files are being generated daily or how could I identify what is happening to solve it? that eliminates the dump files and frees a little space, in a few days it is full again.
Microsoft SQL Server 2008Microsoft SQL ServerMicrosoft SQL Server 2005
Last Comment
Vitor Montalvão
ASKER
Can you also attach the file C:\Program Files\Microsoft SQL Server\MSSQL13.POSEIDON\MS
ASKER
What is the difference between the ERRORLOG and the SQLDump10000.txt, how are they generated? They seem to have similar information.
It weighs almost 1 GB the file, is it normal?
log_cibertec.txt
It weighs almost 1 GB the file, is it normal?
log_cibertec.txt
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
then what should I do?
If you have Microsoft's support then contact them. You should also provide them the error log and dump files so they can perform their troubleshooting. Usually they have the necessary tools to analyze the dump file.
mdmp is a mini-dump file, meaning that's a dump file with less information than usual but should be enough to use for troubleshooting.
Can you attach the last SQL Server error log?