Are you up to Boot Camp 3.2 now? or left at 3.0? Yes, AppleMNT.sys and AppleMNT.sys are buggy and known for BSODs.
Also, HFS filenames with special characters are not supported.
I use paragon and disabled Apple HFS read only by only method I know, to rename those two files. There is no "on/off" for HFS driver and service.
There are many more driver errors that need to be tended to. I made my own thread about it(http://discussions.apple.com/thread.jspa?threadID=2771438&tstart=0) and I'm tired of getting BSODs especially when I need windows for school. Apple needs to remedy these issues ASAP.
I was getting the BSOD when rebooting into Boot Camp 3.1 after attempting to update Windows 7 64-bit security patches in Windows Update. I found a solution that was posted by an IT Consultant. The problem is with the Apple system drivers for mounting HFS volumes. These files are AppleHFS.sys and AppleMNT.sys. Apple needs to fix these drivers to resolve the BSOD issues. In the meantime, here is what you can do to fix the problem:
1) Boot into Windows Safe Mode (at black screen before startup continue to press F2, then press F8 for safe mode)
2) Navigate to c:\windows\system32\drivers\
3) Rename AppleHFS.sys to AppleHFS.sys.BACKUP
4) Rename AppleMNT.sys to AppleMNT.sys.BACKUP
5) Reboot into normal Windows mode
You may notice after rebooting that Windows will no longer mount your HFS OS X volumes because these HFS system drivers are nopw disabled. One solution is to install MacDrive which does a better job than Apple's driver at mounting HFS volumes.
I had similar issues with Windows 7 64-bit on my Mac Pro. I got a BSOD when windows update was creating a restore point. The BSOD was caused by AppleHFS.sys. I was able to repeat this with 2 separate Windows 7 installs. Since this was a fairly fresh install I decided to re-install Windows 7. I was curious because I have not had any issues with my MacBook Pro. One big difference between the two is that my MacPro has a software RAID 1 HFS+ volume in addition to the boot volume. My MacBook Pro only has the single Mac volume.
What I did was to install Windows 7, then I went into disk management and took the two drives that comprised my Mac RAID volume offline. Note this only effects the Windows environment. The RAID still comes up fine in OS X. Then I proceeded to install and update BootCamp. I then ran Windows update with no issue. I haven't had a BSOD since.
Just after making this fix, I found a patch in Apple Support to upgrade BootCamp 3.1 to BootCamp 3.2. I put the Apple system files AppleHFS.sys and AppleMNT.sys back online and installed BootCamp 3.2. It's been a couple of months and I've had many Windows security patches and updates applied and not one BSOD since BootCamp 3.2 was applied. Also, I can access my Windows files when in OS X and my OS X files when in BootCamp. If you haven't already updated BootCamp 3.1, I strongly suggest you do so.