Boot Camp 3.0 AppleHFS.sys Windows blue screen crash

I'm having this same problem, right after installing the drivers from the Snow Leopard CD. It hasn't lived long enough for me to run the updater.

My current setup involves several HFS+ volumes, one with case-sensitivity and no journaling, and one is a software RAID 0. I'm going to try a few tricks to see if something works.

Another problem I have is that the Nvidia drivers seem to have been blown away by the Snow Leopard driver install, so my max resolution is 1600x1200 on my 30 in. screen.

Well, I think I may have killed this bug.

I logged into XP and went directly to the Control Panel via the Start menu, avoiding any access to My Computer. I selected "Add/Remove Programs", and noticed that the NVidia driver package didn't say anything beyond its name and that there were multiple instances (with different version numbers) of all the "Windows Driver Package" items.

I uninstalled all the Windows Driver Package items, the NVidia driver, the RealTek audio driver, and the Boot Camp Services package over two (intentional, not blue-screen) reboots. I noticed that the HFS volumes mounted if the Boot Camp Services package was installed.

After the last reboot, I dropped in the Snow Leopard install CD and it auto-loaded the Boot Camp installer. This is different from what it did the first time I tried to install: that time, it popped up a window asking if I wanted to install either the Boot Camp drivers or MacBook Air optical drive sharing software.

One install and reboot later, and my NVidia card is happily running at 2560x1600 again, there's only one set of Windows Driver Package entries, and things seem okay.

My Windows guru friend always told me to uninstall the NVidia drivers and reboot before installing new NVidia drivers. Guess that should be the case for the Boot Camp drivers as well. I'm surprised Apple's installer doesn't uninstall the old drivers.

I started having the BSOD problem after letting vista update to SP2 (64 bit). AppleHFS.sys was the issue (narrowed down with windows driver verifier). I tried un/reinstalling the driver package but it did not help.
Solution: I've manually removed AppleHFS.sys from my windows system and everything is fine again.
The BSOD error was PFN LISTCORRUPT which means that the apple driver was writing garbage all over windows' high level memory area. I am not going to be using this again until Apple releases a fix.

Disable HFS service. Maybe look into MacDrive8 if you really need access to your Mac volume and files.

We had one single update to Boot Camp 2, even though newer Macs had later versions of drivers and such, those were never posted (you could buy later retail Mac OS and get latest 😟

I bought a macpro a few months ago and I installed vista sp2 with bootcamp 2.1 and it is working fine. I bought another macpro last week, same hardware but with last version of leopard and bootcamp 3.0. This one keeps shutting down like 3 to 4 times a day. I use it as a render slave so it is often idle and even though it keeps on crashing. I tried to contact apple support on the phone but I was tired of waiting after one hour crapy radio on their phone waiting system!

Has anyone tried to disable hfs? does it work? And me too I would like to know how to do that.

I just found this:

<---------------This is for bootcamp 3.0 users------------------------>

By doing the following you will disable HFS mount / read mode on windows XP, Vista, 7.

Navigate to c:/windows/systems32/drivers/AppleMNT.sys, rename the AppleMNT.sys file to something like AppleMNT_keep.sys or something of your likings.

Reboot your machine and notice that your Mac volume is no longer mounted.

Message was edited by: Node927

I ran into the same problem described her.
I followed the suggestions her and so far, no BSOD. I keep my fingers crossed.
Thanks for the info, i was about ready to reinstall my Windows from scratch. You saved me a bundle of time.
However, there are lingering video issue with a CAD program. This is an ATI RadeonX1600.
The window background in my CAD program is unstable. Normally a pale light blue, it turns, after changing from Window to full screen or vice versa, to a striped black and white background. It appears reversible and I can get it back to normal.
Has anybody seen this before?
These started also after upgrading to Snow Leopard and BootCamp 3. This is a true disaster.

Great find, would have been easier and more obvious if name they chose had HFS instead of the MNT.

And I have to ask, is there an "AppleMNT" services that is related to this driver normally? maybe see if that can be changed from automatic or delayed or manual to disable/off?

Saw this on MacRumors -

The faulty HFS driver is a valid concern.
It seems to happen on many systems.
You find it in Windows/system32/drivers/ AppleHFS.sys
Renaming to AppleHFS_disabled.sys will avoid the blue screens until you have found another solution or Apple updates Bootcamp 3.0.

If the system crashes before you can edit the name you can do it in OS X as well if you install NTFS drivers. Paragon has a test driver that will do temporarily.

I just was able to rename AppleHFS.sys using the Safe Mode with Command Prompt as attempting to rename in Windows Vista Ultimate 64-bit produced the error.

I am now successfully installing Flight Sim X...fingers crossed...

Thanks for an incredible forum.

On my Mac Pro I saw both AppleHFS and AppleMNT. If you rename just the HFS driver, the drive (my internal TimeMachine Backup) still mounted but when I double clicked it, the drive couldn't be read and windows said it needed to be formated. After disabling the MNT driver, the drive no longer shows up. For the time being I will leave both disabled as I really don't have a need to view my TM backup drive and my OSX is software RAID 0 and is not visible.

Thanks for the work around guys! I was tried of random BSOD from the HFS driver. Sometimes I couldn't login before the BSOD would happen.

I was having massive problems with Windows Vista running in Boot Camp crashing whenever I "walked away" from my machine for a while. I tried disabling the AppleHFS driver and the problems stopped, but of course I can't access my HFS partition from within Windows.

I kept looking around and ran across another reference which implied the problem could also be cured by turning off the power down disk drives after "x" minutes. I turned the AppleHFS driver back on and disabled the turning off the the hard disk to save power. I recently made this change, but I've yet to have a BSOD reboot and can still access my HFS volume from within Windows.

To turn off the hard drive power down option in Windows Vista go into control panels >> power options >> change plan settings >> change advanced power settings >> Hard Disk >> Turn off Hard Disk >> never.

I had to rename c:/windows/systems32/drivers/AppleMNT.sys to get my quad-core i5 iMac to boot Windows XP in Parallels. With the regular name, I get the Blue Screen of Death (BSOD) every time I boot (when Windows logo appears). When it is renamed, I can boot fine.

Booting directly in Windows works with the original name for this file.

What do I lose in Parallels by having this file renamed?

I ran Vista x64 SP2 but switched to Windows 7 RC once that reached mid-beta builds.

I had to force Boot Camp, even 3.0, to install drivers.