The updated exceptq report helps a lot. I'm going to chalk this trap up to bad luck. Here's what I suspect is
happening. We are trying to execute
vmovdqa ymm7, [rbx+40h]
and exceptq tells us that
EBX : read/exec memory at 0001:00148930 in CRYPTO11
which confirms that ebx+40 is not properly aligned. It also tells us that ebx is probably pointing at constant data stored in the code segment - possibly OPENSSL_ia32cap_P. A copy of poly1305-x86.s would make this easier
to figure this out.
IAC, whatever the data is, it's now in an unaligned location in 1.1.1w.
To avoid this, we would need to figure out how to ensure the data is aligned and change to code to use vmovdqu rather than vmovdqa.