Comment 4 for bug 1850258

Another instruction which appears to have issues with memory operands and breakpoint on the instruction is vpmuludq. This time it didn't crash but I was looking at completely incorrect multiplication results compared to incoming values to the instruction. To me this indicates like vpmuludq read the memory operand from wrong address which happened to be a mapped address.