I think it worth a try to set HMBAllocationPolicy to 2.
And I need to mention that probably it is not WD’s problem. The problem maybe at Microsoft side. It may be because Windows cannot handle 200MB HMB. Maybe, Windows treats it as 256MB, and it causes memory exploit. That is also possible.
200MB is a weird number in binary world. I don’t know why WD picks that number.
