Wasn't SQL 2012 SP1 CU4 supposed to be the build that had the fix?

In my experience you usually have to be able to tell Microsoft that all BIOS/FIRMWARE/DRIVER/VMWARE/WIN/SQL/ETC patches have been applied. That done? firmware/drivers have been most common cause of memory flushes in my past...