I encountered this very strange behaviour of D3DImage, which is only reproducible on XP. The following bug? doesn't seem to occur on any other OS.
The D3DImage has a correct backbuffer set up. I checked the bytes of the backbuffer, and they are updated. (Also updates are visible on other OS.) Still the following code doesn't appear to update the front buffer, without any warning whatsoever.
View Complete Post