This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 72%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBH%3C/text%3E%3C/svg%3E)
We have recently upgraded our servers to SQL Server 2022, and are currently hosting three Microsoft SQL servers running version 16.0.4015.1. We have enabled the query store on all of our databases, with between 5 to 9 databases hosted per server. Since the upgrade, we have noticed errors in the SQL Server logs occurring every 15 minutes exactly: "SqlDumpExceptionHandler: Process 10 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process." We have also observed the "qds" value in the stack dump with the following module property: "spid8s,Unknown,<frame id="00" address="0x7FFA49CC85BA" pdb="qds.pdb" age="2" guid="58E8B5EB-D36D-4ACC-B68D-3A997239CFD0" module="qds" rva="0x685BA" />" To resolve this issue, we have disabled the query store for all of our databases, which has eliminated any further errors. We would appreciate any insight on whether this is a known bug and how to address it. Thank you for your assistance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 2%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESX%3C/text%3E%3C/svg%3E)
We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.
Best regards,
Seeya
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 24%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
We are experiencing exactly that and we had to disable Query Store in all databases. Please let us know if you make any progress with this.
Again: please open a support case. I am sure that Microsoft would like to fix this issue, but to be able to that, they need a case to work with.
By the way, Dani and Hendrik- Are these servers in an AG? With readable secondaries? And you enabled Query Store for the readable secondaries?
We don't use AG. By the way: the problem happened again today at 1 of our 3 servers. The problem disappeared after purging the query data store.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 22%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJF%3C/text%3E%3C/svg%3E)
We having this same issue on one of our QA servers. It's a SQL 2019 instance that we in-place upgraded to 2022. We're going to create a support ticket today. Hopefully they can find the root cause and get this fixed.
That certainly sounds like a bug. I would recommend that you open a case with Microsoft to have this resolved. The only other recommendation I can give is to enable Query Store for one database at a time, to see if it is a specific database that is causing the crashes.
Hi @Erland Sommarskog , Thank you for your answer. This worked for us. We also 'purged query data' before enabling the query store again. As suggested, I also created a bug-report: https://feedback.azure.com/d365community/idea/27e971e1-1dd5-ed11-a81c-000d3a7a9cdb
Just bear in mind that it is very unlikely that your item will lead to any fix. At best it serves to indicate to Microsoft that there is an issue out there, and if they get many of these reports, they may start digging. But they really need a way to repro the issue to be able to fix it. If the issues come back, don't hesitate to open a support case.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 79%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Thanks for your question. During my research, I stumbled upon a document that contains error details similar to those related to SqlDumpExceptionHandler and EXCEPTION_ACCESS_VIOLATION. "Access violations and memory dump files when you use XEvent session with sqlos.wait_info event in SQL Server" Although I am uncertain whether this is relevant to your current situation, could you kindly take a look at it, please? https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/backup-restore/access-violations-memory-dump-files Thank you!
Thank you @RahulRandive
I don't think this applies to us, since we are not using sqlos.wait_info Events
I agree that this is a bug issue. You can post this on the feedback page. Someone from the product team will see it.
https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0
Best regards,
Seeya
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
I don't think there is much point with logging this on the feedback site, because I can't see how Hendrik would be able to give enough details to repro the problem. Just saying "Query store crashes, and I need to turn it off" is not of any use for Microsoft. That's why I think a support case is the way to go. Since with a support case, MS can slap on a bunch of troubleshooting tools and get a lot of information from Hendrik's server.
Thank you for the feedback page url. I have created a bug report: https://feedback.azure.com/d365community/idea/27e971e1-1dd5-ed11-a81c-000d3a7a9cdb
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 38%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFS%3C/text%3E%3C/svg%3E)
If you hit an issue similar to this, ensure you upgrade to CU12.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 86%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELJ%3C/text%3E%3C/svg%3E)
We had this issue with CU11 or 10, upgraded to CU12 and the system just went to 100% CPU usage again, 3 days after re-enabling the QS. CU12 does NOT fix the issue. MS so far has no clue either.
Have you opened a support case?