Does Boot Camp use Hybrid MBR, and if so is there a way to avoid it?

Question

The title pretty much says it all, folks.  I don't know how to tell if it does or not, except that certain Windows applications will not perform everything they should because they say I'm running on a dynamic disk.
So... when I use the automated utility to set up boot camp, does it partition my drive to be a hybrid MBR, and if so is there another way to do it?  I am one of those people who will avoid hybrid MBR like the plague, and I know that Windows 7 will boot from a GPT disk.  I also know that the bootcamp assistant isn't necessarily needed for dual booting (it's just nice and easy!).
Thoughts?

Answer 1

EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 is a Windows or Linux data partition.
48465300-0000-11AA-AA11-00306543ECAC is an HFS+ partition.
C12A7328-F81F-11D2-BA4B-00A0C93EC93B is the EFI boot partition.
My first thought was also that it must've been Windows' fault, but could anything from a different system really cause OSX to corrupt itself almost EVERY time it boots (as in... without even touching the Win7 partition)?
Software-partitioned disks depend entirely on correct implementations and the full cooperation among the operating systems.  Any corruption-level mistake in any operating system, in a privileged application within any of the operating systems, or within the EFI console, can mean the disk is toast.
To get the whole disk erased, you have to select and erase the whole disk, and not any of the partitions.  This isn't necessarily obvious in Disk Utility, particularly given that tool doesn't show "hidden" partitions.  (You can't see the EFI partition, for instance.)
There are all sorts of odd games software can play with disks, including (depending on the particular disks) hiding ranges of sectors, or "repurposing" gaps among the partitions, or "repurposing" otherwise unspecified parts within the MBR.
That Tuxera NTFS is certainly a reasonable potential suspect.  That's a privileged application that's writing directly into the disk structures, and those can corrupt the context of another operating system sharing the disk.  (Microsoft Windows had one of these with their "harmless signature" offer for some years; a sequence that effectively corrupted other operating systems on other disks in the server.)  In this case, the particular NTFS tool deliberately accesses other partitions, so that intentionally breaks through to the other partitions, which makes it a candidate for corruptions.
Ensure you're on a current version of that tool, as a start, and see if the vendor has any reports of issues.