Rather than a misuse of the API, this appears to have been a driver-related issue on AMD's end, which is not present in driver version 31.0.21923.11000.