Error 132 in combination with hardware virtualization

So for the last few days I had random crashes caused by error 132 (cannot read memory).
I though this had to do with the new release, but thinking a bit further I also remembered I just had enabled hardware virtualization in my BIOS to allow docker to run on my machine.
So I turned that off again and I have had no crashes since.
Is this a know issue, and if so will this be fixed? Because I do not like to go changing my BIOS settings every time I want to play vs develop.

Kind regards!

Thanks for posting this! I didn’t have it enabled, but more posts to get focus on this error message is great.
Another post here if you want to check for updates if Blizz ever finds it under the sea of Kazzak / Draenor posts.