That byte sequence you specified (7D 06 33 C0 50 50 EB) was a component of a different string I had experimented with, but I found that it showed up in XBE files that really had no new media check at all. The media check only seems to be active when the bytes that precede your string in the 20-byte string I had selected are present. Perhaps these bytes are a part of a larger failure/jump-to-byte routine that lapses the string you had selected.
Although the entire 20-byte string may not be necessary for the media check, it was just a search string I specified to ensure the change was made to the proper location in the file. Your string may be more central to the media check itself, but it tends to trigger changes to the file even when none are necessary, which I generally don't consider a good idea. Conversely, the aforementioned 20-byte string only triggers any changes made to the file when the media check is present.