Windows 7 Freezes at Restart After Installing Boot Camp Drivers

Hi,
I have a MacBook Pro and am having troubles installing 32-Bit Windows 7. All seems to be functional until I install the Boot Camp drivers included on the Install Disk. I have tried using the Boot Camp 3.1 update, but the same problem occurs. After the computer freezes on the install page, I can no longer access Windows (even in Safe Mode) and am forced to restart the entire process (that is, repartition the hard drive and reinstall Windows).
If I don't install the Boot Camp drivers, Windows seems to be functional, so I'm pretty sure it's something in the Boot Camp package causing the trouble.
Is anyone else having this problem? Any ideas or workarounds?

I finally got it to work. You need to go to the NVidia website and install their drivers. I think the Apple supplied ones are out of date and are causing Windows to hang. Install Boot Camp from the supplied DVD, install the update that Apple supplies through the newly installed Boot Camp, and then go to the NVidia website to manually download the drivers. I used the GeForce 300M series installer. Make sure you do all of this before letting Windows restart.
I had a few issues with it hanging a few times, but once I was able to get into Windows it seems to be working. All of the other Apple supplied drivers seem to work.

Similar Messages

  • 2010 Mac Pro Boot Camp - Refuses to boot Windows after installing Boot Camp drivers

    Hey all,
    I have a quad 3.2Ghz 2010 Mac Pro with a Radeon 5870 and 8 GB RAM.
    I have 2 10000RPM WD Raptor drives, the first drive is my Lion boot drive. The 4th bay contains the second Raptor which has Windows 7 Ultimate 64 bit installed. Bay 2 has Time Machine, bay 3 has a Windows backup drive.
    I had first installed Windows and the Boot Camp drivers a few months ago and everything was humming along smoothly. Monday I tried to boot into Windows and it crashed immediately after the black Booting Windows screen started to change to the login window. This happened repeatedly. Nothing changed on the system that I am aware of. Whenever I tried to boot windows again, it booted into the repair mode. That did not seem to work because after running the repair it would still not boot.
    So I did what is usually required of Windows, and that was to reinstall. I reformatted the hard drive, ran Boot Camp assistant, and started the install.
    Everything was peachy so far, so I tried to reinstall the Boot Camp drivers (4.0). Did a reboot. Same problem. Doh!
    So I did ANOTHER reinstall, and everything was fine. But this time I tried to install the Boot Camp drivers off the os install disc that came with my Mac (3.1). Still no go!
    So finally I did my third reinstall and after that I did not install Boot Camp drivers. However, I did load up the CD and individually installed drivers for the Apple Mouse, Apple Keyboard, Cinema Display, etc. No problems whatsoever. Everything is actually still humming along fine.
    So it looks like running the full Boot Camp install for some reason no longer works. Which means I am missing the Apple Boot Camp control panel, but that's not really a big deal. Althought it's quite annoying to not have the functionality of the special Mac keyboard keys like volume control, etc.
    Has anyone run into this? I thought it might be a hardware problem but my Mac OS X OS exhibits no problems whatsoever.
    Thanks!

    Thank you to The hatter.
    I have a Mac Pro mid 2010 with a SSD and several internal hard disks. For some time I was trying to install Windows 7 on a fresh boot camp volume on a new WD 7200rpm 1TB hard disk. It was taking hours to install, and then I had a series of failures to reboot that proved permanent. The Window Repair utility would come up and took forever to repair the volume - but failed to actually do so, requiring completion reinstallation of the bootcamp volume. This occurred three times, between 1 day and 2 months after installation. I had already moved the Windows drive in to drive slot 1 of the Mac Pro.
    Eventually I gave up and installed boot camp on a secondary partition of the SSD. This worked fine, however is limited in capacity. So yesterday I thought I would try to install Windows on the hard disk again. The Windows installer took many hours to do its thing, and eventually a message came up that the installation had failed.
    I took your tip about possible hard disk failure, and ran Techtool Pro surface scan. It turns out that there are lots of bad blocks being reported. According to Micromat's documentation, the bad blocks being reported are those that may be in critical areas of the disk that cannot be mapped out. They recommend low level reinitialisation (with zeros) to map out the bad blocks, if possible. I am now running Apple's Disk Utility to do this, and fingers crossed that this reinitialisation succeeds, or I will have to replace the drive.

  • BSOD on restart after installing Boot Camp 4 Support Software

    My install of Windows 7 Ultimate on a separate Boot Camp works until I try to install the Apple Boot Camp 4 Support Software. After I do so the system gives me BSOD on restart. I've tried the following suggestions from other threads:
    - Renaming/removing AppleHSF.sys and AppleMNT.sys
    - Removing BootCamp.exe from msconfig.exe
    I've attached the error dumps associated with the BSOD, as well as a screen shot of the BSOD screen (see link below).
    Windbg suggests that wininit.exe is likely causing the problem.
    Any help would be greatly appreciated.
    https://www.dropbox.com/s/f5do4y38y0be3s6/ErrorFiles.zip?dl=0

    I do not know exsactly what your issue could be. My advice would be to try and F8 Windows into safe mode and try to run a Disc check on the Windows partition to see if their are errors that might be fixed. If you have the Windows DVD you can boot into that and run repair apps from that. You may just have a corupt boot config and its causing the BSOD. I have a 2011 Macbook and have similar problem with freeze ups on Windows 7. Mostly after it has to reboot after a update? All I can think of after looking at my Windows Events viewer was that a problem with a driver was most likely the cause. I unfortunately have Mountain Lion and have to use BootCamp 4. Personally I have never had a issue with BootCamp until 4.0 and Mountain Lion. In fact when I upgraded to Mountain Lion I did so without the BootCamp partition and then I added BootCamp back in after Mountain Lion upgrade. When I fist tried to install Windows 7 BootCamp never did start the Windows install corectly. All it did was boot back into OS X. That should have been my first hint that things would not go well

  • Windows 8 crashes and with the error "kernel_security_check_failure" after installing Boot Camp drivers.

    Hi!
    I've got a new 27" iMac (late 2013), and I was going to install Windows 8.1 (64-bit) to be able to play a few games.
    Everything went smoothly (installed normally via Boot Camp Assistant), and after the Windows setup, the Boot Camp drivers needed to be installed. After this, the computer rebooted, but crashed at a blue screen with the error called "kernel_security_check_failure".
    It rebooted a few times on its own, but after a few times, I got some options, and I chose to "refresh" the Windows 8 install, meaning it would reset the install while keeping my files (even though I didn't have any, as I never got to use it). This took some time, but it worked, and it booted into W8.
    The Boot Camp drivers had been removed though, so I had to reinstall them. After they had reinstalled, the computer rebooted and the same blue screen with the same error hit me.
    Something tells me that some of the BC drivers are messing things up. I can't find any information on this elsewhere.
    Would it be possible to install only selected drivers, to eventually find out which driver is causing the problem?
    All help is greatly appreciated!

    I finally gave up, reloaded everything, this time, using WIn 8.1 Pro, not Enterprise.  After I did the updates, patches, Norton 360, shut computer down and connected the external drives, and booted up...and got the BSOD.  This time, I went to Microsoft and downloaded the Windows Debugger, and think I may have found the problem...NORTON! 
    Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
    Am conrtacting them, but, here's the Debugger output:
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Dump\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
    Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
    System Uptime: 0 days 0:03:09.864
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
    *** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
    Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
    Followup: MachineOwner
    6: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    Debugging Details:
    TRAP_FRAME:  ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
    rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
    r8=0000000000005aa0  r9=00000000000007ff r10=ffffd00066cc8000
    r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    nt! ?? ::FNODOBFM::`string'+0x682b:
    fffff802`0f9e8cdb cd29            int     29h
    Resetting default scope
    EXCEPTION_RECORD:  ffffd0002852d338 -- (.exr 0xffffd0002852d338)
    ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    BUGCHECK_STR:  0x139
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    EXCEPTION_PARAMETER1:  0000000000000003
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff8020f9ddae9 to fffff8020f9d1fa0
    STACK_TEXT: 
    ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
    ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
    ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
    ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
    ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
    ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
    ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
    ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
    ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
    ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
    ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
    ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
    ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
    ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
    ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
    ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
    ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
    ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
    ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
    ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
    ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
    ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
    ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
    ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
    ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    SYMDS64+71be6
    fffff800`1d7a0be6 33d2            xor     edx,edx
    SYMBOL_STACK_INDEX:  5
    SYMBOL_NAME:  SYMDS64+71be6
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: SYMDS64
    IMAGE_NAME:  SYMDS64.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  51f84c44
    FAILURE_BUCKET_ID:  0x139_3_SYMDS64+71be6
    BUCKET_ID:  0x139_3_SYMDS64+71be6
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x139_3_symds64+71be6
    FAILURE_ID_HASH:  {bf9be68b-5f04-08d4-3152-3d420dc362f6}
    Followup: MachineOwner

  • Mid-2010 Mac Mini -  black screen after installing boot camp drivers

    I successfully installed Windows XP Service Pack 2 on my new Mac Mini. The display worked without issue in XP at this point.
    After doing this, I proceeded to install the boot camp drivers. They installed and automatically rebooted the machine.
    After reboot, Windows XP no longer has a functioning display. The display is a black screen and eventually the monitor shuts off.
    Things I've tried:
    - Reset PRAM
    - Reset SMC
    - Tried both Mini DisplayPort and HDMI connections to connect to the HDMI port on the monitor
    - Booting into Safe Mode. Holding down F8 successfully brought up the Safe Mode options, but again the display was blank after choosing the Safe Mode option and attempting to load Windows.
    Message was edited by: mullingitover

    Update: Other stuff I've now tried--
    - Swapping out RAM modules. I've tried it with the stock 2GB sticks in place, also with a single 4GB stick. Same result.
    Other interesting/troubling problems:
    - Unable to boot into Safe Mode with command line. The text-only interface with safe mode options that is reached by pressing F8 during windows startup is displayed. However, no matter which option I choose, the result is a dead display.
    - Unable to boot with Windows XP install CD (?!). After choosing the CD at the boot selection screen, the display blanks and never wakes up.

  • Bluetooth Keyboard/Mouse/Trackpad won't automatically connect after installing Boot Camp

    Hey guys!
    Another peculiar thing happened to me today with my 3-week-old maxed-out 2012 iMac (other than it kernel panicking when I powered it down the other day...did I mention this was 3 weeks old?).
    After installing Boot Camp which I will never do again, my iMac (on the OS X side) no longer recognizes my stock Apple Wireless Keyboard, Magic Trackpad, or Magic Mouse automatically, until I press a button on the keyboard and wait 5 seconds, click the trackpad and wait 5 seconds, or click the mouse and wait 5 seconds.
    (The Windows 8 Boot Camp side pairs with the devices immediately after Windows boots, which leads me to believe that the bluetooth devices are defaulting to look for Windows.)
    One of my huge fears I had when considering purchasing an iMac is that the Bluetooth devices wouldn't immediately connect. Being a power-user with former Mac notebooks and working understandably fast having owned a web development company for 8 years now and not having to worry about Bluetooth device pairing, I'd like to think this fear is substantiated. But after first use (before installing Windows 8 with Boot Camp Assistant) it functioned normally and the iMac would automatically discover my peripherals and connect them by the time time computer turned on. I also had no trouble holding the Option key on boot to select a boot device....
    Now, ever since I set up Windows 8 on the Boot Camp partition and paired the keyboard/mouse/trackpad to Windows, the Mac side completely ignores the keyboard/mouse/trackpad until I click a button on each.
    I'm trying to keep it together but this is raging me out.
    I went into Windows, immediately unpaired the 3 peripherals from windows and now use a wired keyboard/mouse with Windows (yay, desk space!), deleted the items entirely from the bluetooth panel, then booted to Mac and did the same thing. I then re-paired the devices to the OS X side andddd...no go! Still doesn't find them automatically. I am extremely upset by this and can't seem to fix it.
    To summarize, my two issues are:
    A. The iMac in OS X does not automatically recognize my bluetooth peripherals until I click a button on each and wait a couple seconds for them to pair.
    B. I cannot hold Option to select a boot device (or choose Windows/Mac for example) because the computer doesn't recognize the keyboard until OS X boots and I press a key.
    Please...for the love of god...someone help me, and stop me from formatting my entire computer over this issue.

    I don't have a logitech mouse, but is it possible that the mouse is going to sleep during the reboot, and is thus unavailable when the OS is looking for it?

  • Unable to install Boot Camp Drivers for Windows

    Mac Pro (2) 3.2 Xeon quads
    Mac OS 10.5.2
    Boot Camp side - Windows XP pro x64 w/SP2
    Step 3 listed in the instructions for setting up Boot Camp is to Install the Boot Camp drivers for Windows. At this point Windows recognizes my Mac Install disk 1. I get the following message: "the installer encountered errors before Boot Camp could be configured. To retry these operations at a later time, please run the installer again." I am not sure if I needed to do something to install the Service Pack 2? My firmware is at MP31.006C.B02 and 1.25f4. When I checked for the latest firmware, it returned a message that it was not necessary.
    Maybe the XP pro x64 is not compatible?
    Barry in St. Louis

    I did install windows xp sp2 32 bit on my macbook pro 2.2 GB and I'm getting the same ...
    When trying to install boot camp drivers, a message came up saying:
    Boot Camp requires that your computer is running Windows XP Service Pack 2 or Windows Vista.
    The only option it gave me was to click the "OK" button. When I clicked OK , another message came up saying:
    Boot Camp Installer completed. The install encountered errors before Boot Camp could be configured. To retry these operations at a later time, please run the installer again. Click "finish" to exit installer. I am running a brand new full retail version of windows xp service pack 2. Applecare will not help blaming Microsoft and of course Microsoft is blaming Apple. What a bunch of useless crap!! Can anyone help??

  • Can't install boot camp drivers on my windown vista

    Hello
    First:-
    I would like to say thanks to all of the members how helped me with allot of issues.
    Second:-
    I'm having a problem while installing boot camp drivers on my vista with using the Leopard disc, it always stop installing and gives me a message about sufficient privilege then i have to choose between these choices (Abort-retry-ignore)
    please guys how i can solve this problem??

    Well i did the same thing but i lost so many functions, such as:-
    1_ Volume controller on my keyboard is not working.
    2_ I cant switch to my macintosh unless if i restart and insert the leopard disc to open the startup disc and let me choose the way i want my computer to reboot.
    3_ isight is not working.
    4_ Bluetooth is not working.
    and so many stuff.
    i hope that there is another way like giving it the permission or something like that?
    please guys is there a way to solve this issue?

  • How to create extra partitions for windows 7 after installing boot camp

    hello
    i am pretty new at imac so bare with me and i really need help.
    IMAC
    OS X version  10.9.5  ( i think its os X mavericks ??)
    iMac 21. inch  , Late 2013
    iMac model identifier  iMac 14,1
    i installed boot camp windows 7  and it works perfectly, after i tried to create two partition using disk utility  for windows 7 (ms-dos) format because i really want to separate my files on other partition instead of everything on Boot Camp drive.  after i restart choosing windows OS i cannot go back to windows 7.
    i hold option on the keyboard but does not show window 7 so i went back to Apple ox s , found my boot camp hd on the desktop with files in it.  checked boot camp assistance showing 
    " The startup disk must be formatted as a single Mac OS Extended (Journaled) volume or already partitioned by Boot Camp Assistant for installing Windows. "
    i read alot of article about but i don't seem to understand much about
    i understand alot of people created these kind of topics
    please if someone can help me solve this problem again
    i only want an apple os ,  boot camp for windows 7  and 2 extra partitions for storage  ,  my hard drive is 1TB
    thank you

    Last login: Mon Feb 16 16:11:46 on console
    YLFs-iMac:~ ylf$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            999.3 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s4
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     FDisk_partition_scheme                        *8.0 GB     disk1
       1:                 DOS_FAT_32 WININSTALL              8.0 GB     disk1s1
    YLFs-iMac:~ ylf$ diskutil cs list
    No CoreStorage logical volume groups found
    YLFs-iMac:~ ylf$ sudo gpt -vv -r show /dev/disk0
    Password:
    gpt show: /dev/disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
    gpt show: /dev/disk0: PMBR at sector 0
    gpt show: /dev/disk0: Pri GPT at sector 1
    gpt show: /dev/disk0: Sec GPT at sector 1953525167
           start        size  index  contents
               0           1         PMBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  1951845952      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      1952255592     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      1953525128           7        
      1953525135          32         Sec GPT table
      1953525167           1         Sec GPT header
    YLFs-iMac:~ ylf$
    Also i do not have boot camp installed yet because like i said, it messed up my boot camp after i created the partition thats why i removed boot camp, right now i only have APPLE OS

  • Blue screen of death after installing Boot Camp on Windows 7

    Hello and thanks for the help!
    Brnad new user to Boot Camp here. After a new install of Windows 7, I install Boot Camp but then when rebooting Windows I get the blue screen of death. When letting Windows attempt a repair, it fails and I am forced to Recover Windows 7 to a state before I installed Boot Camp.
    Help!?

    Solution for this problem is simple. You have to apply Mac Book Air SMC Update 1.7 which you can do from Mac OS X with Software Update or you can download required update manually from Apple support site. If you don't use BootCamp and have installed Windows without it, you will have to boot Mac OS X from external drive just to apply required update. After you applied SMC update, you can boot to Windows and apply BootCamp update 3.2 and 3.3.
    There is a known problem with Mac Book Air EFI Update 2.3, which you won't be able to apply and it will show in Software Update every time you check for updates. There is no solution for it yet.
    You get BSOD if you have BootCamp 3.1 and Windows 7 SP1 installed and you have commited Windows update which will break applemtp.sys as your SMC firmware is too old. It applies to Windows 7 32 bit and 64 bit versions in BootCamp or native install.

  • Black screen after installing Boot camp Win7 on iMac 27 late 2009

    I've run out of ideas as to how to fix this problem. I have a late 2009 iMac quad i5, Mountain Lion, 12GB RAM, 1TB HD (recently exchanged under extended warranty).
    I stopped counting how many times I have tried to get this up and running but I followed a whole bunch of 'how to's' on the net, including the official Appple guide, but I always end up with a black screen. I insytalled it from scratch using both, Apple drivers on CD and SD card and I can confirn that they installed correctly during my last try. That time I first installed Win Vista, then upgraded to Win 7. I took out the install DVD after first restart and left the SD card in its slot (correctly named, as suggested by Apple). the installation finished, the screen went dark for about 5 min, then the computer rebooted, the screen went dark again for another few min and after that the vomputer restarted again but this time all stayed dark and nothing happened for the better part of an hour.
    I also restarted from the Win install disk and tried to remove the ATI drivers using command lines, as suggested in one post.
    I need to run Win in Bootcamp because some application I use are very demanding so I need Win to run natively. In an earlier attempt I managed to boot Win7 from the Bootcamp partition in Parallels and I installed the Apple Drivers in that environment but it still resulted in a black screen. I also tried to remove the ATI drivers from Drivers directory manually in MacOS mode but the System wouldn't let me edit the Syustem folder at all, not even in Root user mode.
    I understand that I'm not the only one with problem and I feel for you, but please refrain from "me too" posts becuase it doesn't really solve my problem. Thank you.

    I presume that you've followed the instructions for sideloading the iMac Windows drivers into your install via USB stick? (wasn't aware the EFI recognized the SD slot as storage on boot. Now i know)
    I always found more success in just slipstreaming the drivers and install.xml file onto a custom Win7 DVD rather than the USB approach when trying with my Late 2009 27" iMac. The Win7 installer needs that enclosed .xml file in the driver package to tell it where to find the drivers so that they be loaded when the Win7 image extracts itself.
    If you're using mountain lion, then you should be receiving the proper Win7 driver set. If you wanted to create a custom image, then you can use an ISO file, the driver package and disk utility to make something you can use. Either that or you learn what edits your install.xml file needs to point the installer properly and check it manually.
    I don't know what links you have so i'll just include everything:
    Installing boot camp on a Late 2009 iMac:
    http://support.apple.com/kb/TS3173
    Direct link to Late 2009 iMac-specific Windows drivers.
    http://support.apple.com/kb/DL995
    I'd try a USB stick and the iMac-specific driver set. It should steer your insolent windows installer correctly.
    Hope this helps.

  • BSOD after installing Boot Camp 5 drivers on my MacBook Pro (13" mid 2012, non-retina)

    Basically what the post says. I go through the normal rounds of creating a bootable flash drive (i've tried ISO files from 7, 8, and 8.1 -- all 64 bit versions), downloading the drivers either off the website, or through the Boot Camp Assistant, then I finally partition my disk equally and go through the normal install process with the version of windows. Everytime windows installs correctly and starts up just fine, but as soon as I install the bootcamp drivers (or any drivers at all, say the graphic drivers from intel's website) all **** breaks loose. Near the end of the bootcamp driver install on windows 7 it blue screens and shuts the computer down. In windows 8 and 8.1 it installs without a hitch then when I go to restart it the machine boots into the windows partition, shows the windows 8 logo with the loading circle thing under it for several minutes then I get presented with the new Windows 8 blue screen of death with the (sorry there was a problem loading your system ) on it. Then it shuts down, restarts and does it all over again. Someitmes it will try and "repair" the system on windows 8 start up but that never does anything.
    I've tried what seems to be everything with this situation and still I get the same results. Even reinstalled OS X. I've searched the internet for hours upon hours for an answer and I've gotten nowhere. Any help would be greatly appreciated!
    here are my exact system specs if anyone needs to know anything more than what I've posted in the title: http://store.apple.com/us/product/FD101/refurbished-macbook-pro-25ghz-dual-core- intel-i5
    Thank you to anyone in advance.

    Well, at least my Windows won't boot after renaming them to *.sys.old.
    But anyway, these two drivers aren't the cause, instead it's actually BootCamp.exe and/or the trackpad or keyboard drivers.
    This guy had the exact same problem and the 'solution' was to disable BootCamp.exe.
    https://discussions.apple.com/message/10301692#10301692
    I finally managed to install all Boot Camp updates but still nothing has changed; as soon as I launch BootCamp.exe or change settings for the trackpad the system crashes.
    It seems I have two options now: Use Windows without "Tap to click", "Secondary Tap" and modified keyboard settings, or find suitable trackpad/keyboard drivers.
    Speaking of which, is there any chance to get Boot Camp drivers for Win 7? Maybe this would solve my problem since I only have Vista/x64 drivers which I used for Win 7.
    Thanks!

  • BSoD after installing Boot Camp 3.0 into Win 7 Pro x64

    I installed Windows 7 Professional x64 into the partition created by the Boot Camp Assistent (3.0.4), the whole windows setup worked just fine and finished as usual. Then, after the final reboot to finish the windows setup I installed the Boot Camp software and drivers from my 10.6 DVD. The setup finished and promted me to restart the system - no problems so far. But just as Windows rebooted and was about to show the desktop, it crashed with with a BSoD providing no precise imfomation as to which driver could have caused it.
    I have re-installed Windows and Boot Camp about ten times now, and no matter what I tried, the result always remained the same.
    I booted in Safe Mode and tried to update to Boot Camp 3.1 and 3.2, but near the end of the setup it shows that Keyagent and MacHAL could not be installed (Setup said the Updates were installed successfully though).
    When I rebooted Windows normally it was still the same - BSoD just when the desktop was about to be shown.
    I have absolutely no idea what causes this. The BSoD only shows a hex-code, but I wasn't able to write it down since it disappears too quick and I don't know how to 'pause' using the integrated keyboard.
    • Computer is a MBP mid '09 running 10.6.8 with all updates
    • Boot Camp version is 3.0
    • Provided drivers on the Snow Leopard DVD are for XP and Vista/Vista x64 only, but since the setup completes without any error message I assume those Vista drivers are OK
    • Windows - as stated above - is a 7 Professional x64
    So, does anyone have an idea what might be the problem and/or how to solve this issue?
    If any possibly useful information missing please ask and I'll add them.
    Thanks in advance

    Well, at least my Windows won't boot after renaming them to *.sys.old.
    But anyway, these two drivers aren't the cause, instead it's actually BootCamp.exe and/or the trackpad or keyboard drivers.
    This guy had the exact same problem and the 'solution' was to disable BootCamp.exe.
    https://discussions.apple.com/message/10301692#10301692
    I finally managed to install all Boot Camp updates but still nothing has changed; as soon as I launch BootCamp.exe or change settings for the trackpad the system crashes.
    It seems I have two options now: Use Windows without "Tap to click", "Secondary Tap" and modified keyboard settings, or find suitable trackpad/keyboard drivers.
    Speaking of which, is there any chance to get Boot Camp drivers for Win 7? Maybe this would solve my problem since I only have Vista/x64 drivers which I used for Win 7.
    Thanks!

  • BSOD after installing Boot Camp, AMD Radeon 6630M driver issue

    I have reinstalled Windows using Boot Camp twice now and get a blue screen right after installing the Boot Camp drivers and restarting.
    I am installing Windows 7 Ultimate 64-bit on my Mac mini 2011 edition. I created an install disk in Lion and used the option to copy the Boot Camp drivers into the disk.
    I have narrowed the problem down to Apple's driver for the AMD Radeon 6630M graphics which my Mac mini has. The driver will install without errors but then the blue screen appears on next startup. If I use safe mode to uninstall the AMD driver, the blue screen goes away, but the display resolution is very low.
    I checked for driver updates from AMD, but there are none for the 6630M.
    Anyone else having this issue?

    Hi,
    I have installed Windows using Boot Camp and I also get the blue screen of death right after installing the Boot Camp drivers and restarting.
    I am installing Windows 7 Ultimate 64-bit on a i7 Mac mini 2011 edition. I created the USB install thumb within Lion's Boot Camp, and got downloaded the latest Bootcamp drivers (bootcamp 4.0). I connect the mac mini to a 24" iiyama screen with a HDMI cable. I don't have a DVI cable anymore unless i would have checked that point too.
    I have also narrowed the problem down to Apple's driver for the AMD Radeon 6630M graphics which my Mac mini also has. The driver will install without errors but then the blue screen appears on next startup. If I use safe mode to uninstall the AMD driver or renaming the atikmdag.sys file (the main cause of the crash), the blue screen goes away, but the display can't get the effects such as Aero interface.
    AMD provides official drivers that don't recognize its own 6630m graphic card with Apple, then doesn't install any up-to-date driver... Only Apple's AtiGraphics setup program will install the drivers...but it makes Windows 7 crash at each boot.
    Thanks for your technical skills or info to come over this issue (or releasing a bootcamp update ?)

  • Installed Boot Camp drivers for Windows 7, now black screen!

    I have a question--I have a late 2009 iMac with the ATI card, followed Apple's procedure for avoiding the black screen while installing Windows 7 on the partitioned HD, and found I could not update to Boot Camp 3.1 without already having Boot Camp 3.0 from the 10.6 install disc. I inserted the disc, had to perform a workaround because it said I couldn't run 64-bit, and installed the drivers (I assume?) from Boot Camp on the 10.6 disc. When my iMac restarted the screen soon goes black. I guessed I was at the login screen, typed in my name and password, and could hear it logging into Windows--my sound works, Magic Mouse works (no scrolling), etc but no screen after booting up in Windows. Did the Boot Camp drivers from the install disc over-write something that was working? How do I fix this so I can proceed to install the 3.1 and 3.2 Boot Camp updates? Just the ATI* trick? Please help!!!

    I'm sorry to take up your time guys - as I wrote earlier I'm not that technical and new to all of this - I was promised that I could do everything the mac way in the windows environment if I bought Parallels Desktop 7 - I only did this as my company is installing af new CRM system that is only supported in Windows - now I have installed everything and find out that the MAC keyboard shortcuts and layout is not working at all in i.e. Outlook etc. and I've totally forgotten how the Windows shortcuts etc. is working - Parallels asked me to go to Apple for help and here I am
    You write that "if you believe it's correct do it" - but I don't believe anything else than what I'm told - I'm not going to install anything if I don't know how to do and whether it's correct - I wont have the nerve to do that.
    If at least could get a list or someting on how to use my Magic Trackpad in the windows environment I would be happy - then I would just have to switch between how to use it on both sides.
    Hope you understand and sorry again for taking up your valuable time

Maybe you are looking for