Hi! Thanks for attaching the files. We've confirmed that we already have it in our database and it's quite uncommon.
Our programmers are currently investigating it and there's a chance that the issue is on the side of Intel in which case it will be patched alongside a system update. If it turns out to be on our side, the fix will likely be deployed in a future major patch.
Apologies for the inconvenience!