Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

milbournosphere

macrumors 6502a
Original poster
Mar 3, 2009
857
1
San Diego, CA
So I recently got one of those new fangled SSD drives. The install went well, both on OS X and installing bootcamp. However, once I updated the boot camp tools for Win 7 (Pro, 64 bit), I'm getting nothing but BSODs upon bootup into Windows. Is there a way to roll back the boot camp utilities to an earlier version using safe mode, or am I going to have to wipe the boot camp partition and start over? A scarier question: could it be a problem with installing boot camp on an SSD? Thanks for any help.
 
Go back to a previous system restore point before you installed the updated drivers.

Also, are you sure it was the boot camp drivers? Did you install any software with the SSD like SSD optimizer tools or anything like that? They might have installed an AHCI driver which could definitely cause BSOD.
 
No, I have yet to install any SSD tools. The plan was to update Windows and the Boot Camp drivers before attempting anything else.

The reason that I'm fingering the Boot Camp drivers as the issue is that things were running well after updating Windows, after installing the (older) Boot Camp drivers from my OS disk, and before updating the Boot Camp drivers to v3.2 via Apple's Software Update utility.

I will look and see if a snapshot was taken before installing the updated Boot Camp drivers; thanks for the tip regarding an AHCI driver.
 
I run boot camp on a Mac Pro 4,1 (win7 64 bit) and a MacBook Pro 3,1 (win7 32 bit) using SSDs to boot without any issues from any boot camp updates/drivers. You might want to try again to see if it repeats.
 
I run boot camp on a Mac Pro 4,1 (win7 64 bit) and a MacBook Pro 3,1 (win7 32 bit) using SSDs to boot without any issues from any boot camp updates/drivers. You might want to try again to see if it repeats.
I've restarted several times now and the issue has yet to go away. I'd write the BSOD error down, but it flashes too quickly. This is on a Mac Pro 5,1 running Win 7 Pro 64 bit. I've installed boot camp on a regular HD before in this mac and had no issues. When I get home this evening, I will try reverting to a snapshot and see if that helps.
 
I also use an SSD with bootcamp, as do many others.

Hopefully the system restore will do the trick and you can just wait for boot camp 3.3 or whatever is next.
 
I restored back to the system restore that was created before Boot Camp Services was installed. I played around with the system for a good while, and had no problems. So, I installed the Boot Camp drivers from my Mac Pro install disk. On the first boot, it barely lasted 5 minutes before BSODing.

Here's the info from Windows' little 'oh noes, there was a bad shutdown' window:

Code:
Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7600.2.0.0.256.48
  Locale ID:	1033

Additional information about the problem:
  BCCode:	34
  BCP1:	0000000000000107
  BCP2:	FFFFFFFFC0000420
  BCP3:	0000000000000000
  BCP4:	0000000000000000
  OS Version:	6_1_7600
  Service Pack:	0_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\052611-7566-01.dmp
  C:\Users\ryan\AppData\Local\Temp\WER-9048-0.sysdata.xml

My guess is that it's a driver causing an issue somewhere. I searched but could only find one other person having this issue, and it was with an eSATA card. I'm going to restore back to that earlier snapshot again and attempt to download the debug tools to see about looking at the dmp file to try to get a more specific reason as to why the OS is bluescreening.
 
Did you install the Windows 7 service pack 1?

The above says "Service Pack: 0_0". Maybe that's normal for Service Pack 1, I wouldn't know, but it makes me think you haven't installed it yet.
 
Did you install the Windows 7 service pack 1?

The above says "Service Pack: 0_0". Maybe that's normal for Service Pack 1, I wouldn't know, but it makes me think you haven't installed it yet.
You are correct, I have not installed the service pack. I wouldn't think that this would cause problems though.

I did a fresh install last night, and installed only the basic drivers from the Mac Pro install disk. With only video, audio and the intel chipset drivers, things seem to be going well. I'm starting to think that it might be an issue with Windows not liking the two striped HFS raid arrays that I have in my pro. Does anybody know which driver package contains the HFS drivers so I can be sure not to install them?
 
The plan was to update Windows

I would have stuck with the plan and tried the service pack before starting all over. But too late for that.

I suppose you could just disable the HFS drives in device manager so that Windows does not try to interact with your RAID.

I would still do SP1 anyway, unless there's some important reason you don't want to update Windows.
 
No, SP1 was the first thing to do after installing the drivers. I attempted to restore the OS to a working state before wiping the drive. Not even the restore utility was working for me (restore attempt failed, and it all went down hill from there). Wiping and starting over just seemed easiest. I used the time while windows was copying files to go down to the gym anyways. :)

At this point, I'll probably install the Boot Camp tools, boot into safe mode, and delete these two files from c:\windows\system32\drivers\:
  • AppleHFS.sys
  • AppleMNT.sys
After looking around, these drivers seem to be the ones causing headaches for some people. They seem to be quite buggy and prone to causing BSODs. Anybody have experience with MacDrive as a replacement for HFS functionality? It's not crucial, but it would be nice to be able to access some files stored on one of my raid arrays.
 
I used MacDrive for a couple of years. I had to do a disk repair in OS X about every three months or so. AFAIK I never lost a file, but still it scared the crap out of me. I gave up and keep my common drives in NTFS now.

I wish Apple would write a really solid read/write HFS driver for Windows.
 
No, SP1 was the first thing to do after installing the drivers. I attempted to restore the OS to a working state before wiping the drive. Not even the restore utility was working for me (restore attempt failed, and it all went down hill from there). Wiping and starting over just seemed easiest. I used the time while windows was copying files to go down to the gym anyways. :)

At this point, I'll probably install the Boot Camp tools, boot into safe mode, and delete these two files from c:\windows\system32\drivers\:
  • AppleHFS.sys
  • AppleMNT.sys
After looking around, these drivers seem to be the ones causing headaches for some people. They seem to be quite buggy and prone to causing BSODs. Anybody have experience with MacDrive as a replacement for HFS functionality? It's not crucial, but it would be nice to be able to access some files stored on one of my raid arrays.

yes apple hfs driver gives issues.

macdrive works really good.
 
I did a fresh installation of Windows 7 on my Boot Camp drive and ran into the same problems as the OP, happening at the same step in the process: right after installing the Boot Camp 3.2 drivers. Some googling led me to the same two files

AppleHFS.sys
AppleMNT.sys


I didn't delete them. I think I relabeled them instead. But the result was the same: no BSOD afterwards. I'll have to look into MacDrive.
 
Deleting\renaming worked for me. I installed SP1, installed\updated the Boot Camp tools, then immediately renamed those two files. I've yet to have a single BSOD.
 
I have a MP 4,1 FWIW.

I run MacDrive without issue and bootcamp tools updates have worked fine with either the original Win7 (x64) or with SP1. (I've not needed to rename the files)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.