Driver BSOD on Startup after Boot Camp 3.0 Upgrade.

Hello all you support board types. I have a little bit of a problem these days.
Yesterday I went and installed the Boot Camp 3.0 Drivers from my shiny new Snow Leopard Disc. The install went off without a hitch and I hit restart to complete the install.
And then I hit a nice big blue screen of death.
Here is the info from the blue screen:
Driver in Question: NV4_DISP (sounds like graphics card driver to me) thrown into an infinite loop.
*STOP: 0x000000EA (0x8A46E428, 0X8A91A1B8, 0XF78C3CBC, 0X0000000)
NV4_DISP
It will not start up with multiple restarts. It will start in safe mode. You cannot reinstall the Boot Camp drivers while in safe mode (a feature, it seems, of safe mode, natch).
Any ideas?
Thanks.

Your assupmtion is right....its a problem with the nvidia display driver.
Try booting in safemode and deinstalling the driver. This should at least make u able to boot normally. Then try to install one of those modded-drivers. I've been using those for a long time without problems

Similar Messages

Screen flickers after boot camp 2.1 upgrade

I have been running boot camp 2.0 and WinXP for a few weeks on my iMac 24" 3.06 Ghz 4 Gb running 10.5.5. I had installed the nvidia 177.98 drivers and they improved gaming performance and work great.
I installed the boot camp 2.1 upgrade and the video drivers changed back to the boot camp 2.1 drivers. I re-installed the nvidia 177.98 drivers.
I now have two issues:
1. the monitor is listed as generic plug and play. Is there a driver for the iMac 24" display?
2. My room is dark so I use F1 to reduce the screen brightness. The whole screen flickers or flashes continuously. IF i have the brightness up near make the flickers or flashing stops. Anyone sen this or have any thoughts?
If i can't stop the flickering and flashing, I will eventually delete the WinXP system and re-create it and stick with boot camp 2.0.
..Bob

Before you re-do everything consider other options.
This is the procedure for uninstalling and installing drivers. A program called driver sweeper is required. To uninstall your old drivers you must boot into safe mode, uninstall your old drivers, use driver sweeper to eliminate any remaining fragments of your driver and then install new driver.
http://www.guru3d.com/category/driversweeper/
http://forums.guru3d.com/forumdisplay.php?f=29
Maybe you need to do 2.1 first? or use later drivers?
nVIDIA ForceWare X 179.13 for Windows XP/2K 32bit
http://www.laptopvideo2go.com/drivers/xp/179.13
In the future, you might want to use something to regularly backup, but for now, WinClone can take a full snapshot image for restore, and runs in OS X. DataBackupPC from Prosoft Engineering (Data Rescue II folks) or similar backup / cloning software (Acronis doesn't support GPT and EFI, so no Mac support).

Gray screen during startup after boot camp installation

I cannot either Mac and Windows t start on Mac Mini after I updated with Windows7 on Bootcamp.

Hi there Sudarshan21,
I would recommend taking a look at the troubleshooting steps found in the article below.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/ts2570
-Griff W.

"Your bootable USB drive could not be created" "Boot Camp only supports 64-bit Windows installation on this platform. Please use an ISO file for 64-bit Windows installation."

I try to install windows7 system on my macbook air, which version is 10.8.5. When I open the bootcamp, it let me to choose a windows ISO image, which I've already downloaded from this website: http://www.w7forums.com/threads/official-windows-7-sp1-iso-image-downloads.12325 /, it also asked me to select a USB drive, which is kingston that has 8GB. Then when I clicked "continue", it said that "Your bootable USB drive could not be created" "Boot Camp only supports 64-bit Windows installation on this platform. Please use an ISO file for 64-bit Windows installation." But actually the ISO image I downloaded is 64-bit windows7. I don't know why this would happen. Could someone help me please!!

Thanks for your feedbakc Kiranjj!
I identified the reason to be that the W8 installation file didn't download completely from a Mac OS-device. I downloaded from another Win-device and the moved the installation file with a USB-stick and then everything worked diectly! But thanks anyway.

HT1899 How do i boot to mac after boot camp

How do i boot back to mac after boot camp? I was in the middle of installing windows 7 when i received an error message saying the partition needs to be in a diff format ( NFTS ). I tried restarting my mac but now its saying "no bootable device - insert boot disk"

Welcome to the Apple Support Communities
You have to format the volume using NTFS in Windows installer. After you've installed Windows, press X key while your computer is starting to start in Mac OS X

HT5446 If I buy a mac mini with a fusion drive and add windows using boot camp, can I make the SSD function be dedicated to the windows partition?

If I buy a mac mini with a fusion drive and add windows using boot camp, can I make the SSD function be dedicated to the windows partition?

Additional information from Linc's post. Basically, only one additional partition can be added to a Fusion Drive and it resides on the HDD.
Do computers that come with a Fusion Drive support Boot Camp?
Yes. Use the Boot Camp Assistant to create a Windows partition and install Boot Camp. The Windows partition will exist on the hard disk drive, not the Flash drive, and is not part of Fusion Drive Logical Volume Group. 3TB Fusion Drive configurations need to update to OS X Mountain Lion v10.8.3 or later to install Windows 8. See iMac (27-inch, Late 2012): Boot Camp alert with 3T hard drive for more information.

Cannot install Boot Camp 3.2 upgrade for Windows 7 64 bit

I recently installed Windows 7 64 bit on my macbook. I also installed Boot Camp 3.0.1 after Windows 7 installation, however, WiFi did not work. Therefore, I needed to upgrade to the latest Boot Camp 3.2. However, when I tried to install Boot Camp 3.2 upgrade for Windows 7 74 bit, I got an error message saying that I needed Boot Camp 3.1 installed first. I CANNOT find Boot Camp 3.1 upgrade for Windows 7 64 bit on Apple website at all. Can someone please help me on this? Is there a way to get the complete Boot Camp 3.2 package that can simply be installed on version 3.0.1??

here is the link to bootcamp 3.1 for windows 7 64 bit http://support.apple.com/kb/DL1336 .. and no there is no package that can be applied to the windows side to go from 3.0.1 to 3.2

Hard drive missing space after boot camp got stocked on "Creating Partition"

Hi guys, last night I was trying to install windows 7 in my computer for some gaming, the process with boot camp went well until it said "Creating Partition" there it got stocked for a good 2 hours, because of this I did a bit of research on what could happen if I would force quit it, I read that it might happen that if I restart the partition would be there or just nothing would have change but in my case none of those happened, my hard drive is keeping that space in blank without letting me use it, before trying boot camp I had 240 GB of free space and now after restart it I have 90 gb of free space, yes I tried to make the partition of 150 GB, so what should I do to repair this?, I verified the permissions on Disk Utility and I just got one weird message:
Warnin SUID file "Library/CoreS" has been modified and will not be repaired
But when I try to verify/repair I get this:
or this:

Reboot to your recovery partition and run disk utility from there, you can not repair the disk you are booted from.

External USB Hard Drive Can't Be Safely Removed After Boot Camp 3.1 Install

I just wanted to report that I've done multiple installs of Windows 7 Ultimate 64-bit on my MacBook 4,1 and although I've had no problem using the cmd workaround ( http://www.zath.co.uk/how-to-install-windows-7-on-apple-mac-boot-camp/ ) to install the 64-bit Boot Camp drivers that come with the Mac OS X 10.6 Snow Leopard retail DVD, I have found that by installing the Boot Camp 3.1 drivers on the same system, under no circumstance can I click the the "Safely Remove Hardware" icon in the system tray and not receive a message saying that ... "The device 'Generic Volume' cannot be safely ejected..." and that some program or service must be using it. However, a restart doesn't solve the problem any more than logging out does.
I read somewhere that part of the fix that Boot Camp 3.1 was intended to provide was to allow safe ejecting of the Macintosh HFS+ partition. Well, my external hard drive has three partitions: one NTFS, another NTFS, and a third HFS+ for Time Machine backups. I suspect, since I haven't seen anyone else reporting this issue, that it may simply be that the Boot Camp 3.1 drivers don't take into account the possibility of an HFS+ partition on external USB devices. Anyway, a System Restore to before Boot Camp 3.1 drivers were installed completely remedies the issue.
At this point, I'm not having any trackpad issues or anything else of note with respect to the original Boot Camp 3.0 drivers that came with the Snow Leopard retail disc, so I'm fine keeping those drivers installed and allowing Windows Update to update the Intel and Marvell drivers as it recommends. I just find it slightly amusing that the Boot Camp 3.0 drivers, which supposedly did not support Windows 7 (let alone the 64-bit version) work better than the 3.1 drivers which do supposedly support Windows 7. And the funny thing (or is it?) is that you have to install the original Boot Camp drivers with the cmd workaround before you're even able to update to the Boot Camp 3.1 drivers. Hilarious stuff there.
Proprietary gamesmanship is a big reason some of us prefer the Linux "share the ownership +for free+" model of computing. Just saying...
Anyone have any proper solutions (as in, other than "don't install the updates then!")?
bkadoctaj

I have a pair of external usb drives, one formatted for NTFS and the other for HFS+ connected through an external 7 port hub. I am running Windows 7 (64 bit) with bootcamp 3.1 on a late 2009 Mac BookPro. I share the same "safely remove hardware" issues you described. I always assumed it was because my external drives were connected through my external USB hub because of a similar issue I had running Vista (64 bit), but now I can confirm directly connecting the external USB HFS+ drive also yields the same "safely remove hardware" problem. Unfortunately for me, if I regress to the Bootcamp 3.0 drivers, my audio drivers, at times, fails to load. I would need to regress to Windows Vista (64 bit), the last environment where my iSight camera, internal speakers and all other hardware performed correctly. I would gladly, at this point, live with the "safely remove hardware" issue in exchange for a working iSight camera, the one and only hardware device lost to me in the move to Windows 7.

OS X disappeared from "Option" key startup menu after Boot Camp

I ran Boot Camp Assistant until the part where I enter the XP CD. (I entered the version before service pack 1 by accident.)
I'm not sure if it's related, but I can no longer boot to Mac OS X. It just hangs on the gray screen (no logo) if there's no CD, or hangs on the black blinking cursor if there is a CD.
Windows shows up as a bootup option, but I never got the chance to install it.
What do I do?

Press and Hold the OPTION key during startup and see if you get the menu to load OSx. If you do then click on OSx and boot into Leopard. Run boot camp assistant again and remove the Windows partition to restore the HD back into its original state.
Axel F.

BSOD w/Vista 32bit after Boot Camp 2.1 update - bluetooth related?

Ok, so 2.1 has officially hosed my Boot Camp installation now - I was really hoping for access to more than 2GB of RAM on my Mac Pro but instead I'm blessed with BSOD every 20 seconds - thanks! This seems to be somewhat random but I figured out that I can actually cause it pretty easily by opening Internet Explorer 7 and trying to type into the Live Search bar - I'm using an Apple bluetooth (aluminum) keyboard and it almost seems to be related - my password doesnt show up when I type it in at Vista log in either and its really funky when it does work.
I installed my Boot camp drivers from the Mac Pro (2008) disc that came with my MP - didn't have any troubles with those - all I really wanted was to use another GB or 2 of RAM..... instead I get constant lockups.

You need the 64-bit version of Vista for one thing to use more than 1.9GB RAM.
Most of the problems people have with SP1 update have been pre-existing 'dirty file system'
To backup or clone Vista, I would use WinClone from OS X, or use Vista Businss/Ultimate before hand to backup files and system and make sure you have a good restore point before applying updates. Taht is one thing I would like to see Apple do, which MS updates often will.
http://windowsvistablog.com/blogs/windowsvista/archive/2006/12/05/windows-recove ry-environment.aspx
http://www.twocanoes.com/winclone/
What to do when Windows crashes:
http://www.informationweek.com/news/windows/showArticle.jhtml?articleID=20000032 9

MacBook Pro 13" Late 2011 Experiencing Significant Slow Down After Boot Camp Installation

     Okay, so today, after installing Windows 7 on my MacBook Pro via Bootcamp Assistant, I experienced significant performance slow down (fans going at full blast, applications opening after extended periods of time, keystrokes not being registered) when I returned to my OS X partition/second hard drive. I have dual hard drives, one of them being a Samsung 256 GB SSD with OS X Mavericks and the other being my original 500 GB HDD, divided into a 250 GB OS X Mavericks partition and a 250 GB Windows partition. I have the SSD set as my startup disk and I have it located in the main HDD bay. I moved the old HDD into a caddy and placed it where the optical drive normally should be.
      After multiple failed attempts to install Windows via USB and Bootcamp Assistant, I decided to reinstall my optical drive and use a Windows installation disk. This attempt proved successful, and I was able to install Windows 7 onto the 250 GB partition I had created for it on the 500 GB HDD. After completing basic setup of Windows, I removed the optical disk drive and reinstalled the SSD and the HDD into their original spots (SSD in the main HDD bay, HDD in the caddy where the optical drive normally is).
     After completing this tedious process, I booted my Mac back up using the SSD. However, I noticed something was wrong when the login screen, apps, and nearly everything else on my desktop had slowed to crawl. I decided to check my Activity Monitor to see what the problem might be. Activity Monitor told me that the task "kernel_task" was taking up anywhere from 200-600% of my CPU, which explained the slowdown in performance. I looked around to see if there were others with the same problem as me, and I found that Spotlight Indexing might be an issue, with a potential remedy being move my Bootcamp Partition into the Privacy section of Spotlight under System Preferences. After doing that, I experienced no increase in performance and everything was still going very slowly.
     The next step I took was to see if booting into Safe Mode would help the issue. After booting into Safe Mode on my SSD, I noticed that things were back to their normal speeds, with applications opening at the speed they should be and keystrokes being registered instantaneously. However, the fans were still going and had not shut off once booting into Safe Mode. In addition, I checked Activity Monitor and the "kernel_task" in question was no longer taking up massive amounts of the CPU.
     At this point, I don't know what to do and I need help in restoring my Mac to original speeds. I may end up deleting my Boot Camp partition as a last measure if all else fails, seeing as I installed Windows in the first place for running a few programs and games that I can live without. However, I'd prefer to not have things come to that and fix things before deleting the Boot Camp Partition. I've heard that if everything runs normally in Safe Mode, then the issue is third-party software. Is this true?
     Any help would be greatly appreciated as I am writing this from the MacBook in question in Safe Mode because it's essentially useless in normal SSD operation.

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
Don't be put off merely by the seeming complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the behest of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
Here's a summary of what you need to do, if you choose to proceed:
Copy a line of text in this window to the Clipboard.
Paste into the window of another application.
Wait for the test to run. It usually takes a few minutes.
Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports ' \*AutoCad \*dropbox \*GoogleDr\* vidinst\* ' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 1000 MB com.apple.AirPortBaseStationAgent 464843899 );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[26]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n-\t%s\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}') printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */ /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { if(n<200) print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}') print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR!=2{next}'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' 's/^.{52}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { print "'${p[41]}'";if(n<200) print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$|'${p[41]}'/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/ { n++;print;} END { if(n<1000) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/ { next;} /(etc|Preferences|Launch[AD].+)\// { sub(".(/private)?","");n++;print;} END { print "'${p[41]}'.plist\t'${p[42]}'";if(n<500) print "Launch";} ' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.([bw]|plu)/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| |\n","\\|\\|kMDItem'${p[35]}'=");sub("^...."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]" "$1;b=b$1;} END { if(b) print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n [N/A]";"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' /^ +[NP].+ =/h;/^( +D.+[{]|[}])/{ g;s/.+= //p;};' 's/0/Off/p' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / / { print "'"${p[28]}"'";exit;};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/$L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9;} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil 'PlistBuddy 2>&1 -c "Print' whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil sudo\ lsof test );c2=(com.apple.loginwindow\ LoginHook '" /L*/P*/loginw*' '" L*/P*/*loginit*' 'L*/Ca*/com.ap*.Saf*/E*/* -depth 1 -name In*t -exec '"${c1[14]}"' :CFBundleDisplayName" {} \;' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' :${p[35]}\" :Label\" '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status " -F '\$Time \$Message' -k Sender kernel -k Message Req 'bad |Beac|caug|dead[^bl]|FAIL|fail|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA$|pagin|proc: t|Roamed|rror|ssert|Thrott|tim(ed? ?|ing )o|WARN' -k Message Rne 'Goog|ksadm|SMC:' -o -k Sender fseventsd -k Message Req 'SL' " '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/r*/com.apple.*.{BS,Bas,Es,J,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cgh] ! -name *ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Ca*/*/Ex,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,{[lp],sy}*.conf,pam.d/*,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}*t /S*/L*/Lau*/*t .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers\ "${p[N5]}" -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / '-R -l1 -n1 -o mem -stats command,uid,mem' -i4TCP:0-1023 com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' '-app Safari WebKitDNSPrefetchingEnabled' );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n ' syscall::'${p[33+j]}':return { @out[execname,uid]=sum(arg0) } tick-10sec { trunc(@out,1);exit(0);} '";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls Prefetching );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear >&-;date '+Start time: %T %D%n';};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do [[ "$i" ]]&&eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};';done;A7(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ [[ "$v" ]]&&echo "$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "$s"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D23 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 44 54 45;D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D13 24 24 32 31;D13 25 37 32 33;A2 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D13 14 1 48 42;D12 34 43 53 44;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;B1&&D23 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 20 42 32 41;D13 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 4 3 32 5;D12 26 48 49 49;B3 4 22 57;A1 26 46 56;B7 22;B3 0 0 58;C3 47;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Launch the built-in Terminal application in any of the following ways:
Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
8. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start Time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

After Boot Camp partition, iMac no longer boots

Hi, I have a 20" iMac Core Duo (the first Intel Mac off the line) running Snow Leopard 10.6.4. I ran the Boot Camp Assistant to partition my hard drive, and it successfully created the "BOOTCAMP" drive. When it asked for my installation CD, I tried loading a Windows installation partition through a USB hard drive, but the assistant would not recognize it as an install disk. So, I closed out of the assistant early, leaving the Boot Camp partition in place. Eventually, I rebooted my machine in an attempt to boot directly from the USB drive and resume installation.
However, I found the machine will not boot at all. It powers on normally, makes the startup sound, but after a few seconds I'm left with just a flashing folder and question mark icon. Holding down Option-key at startup does nothing. Trying to boot from my Snow Leopard disc by holding down C or D during startup does nothing. Holding down Command-S does nothing. Holding down Shift-key does nothing. Resetting the PRAM does nothing.
What can I do? Is there some way I can access the on-board EFI to make sure the correct startup disk is selected? Why am I unable to boot from my CD drive?
Thanks for your help, everyone.

On OSX go to System Preferences the Startup Volume and reset your Windows 7 partition to be the default.
On the next reboot it should automatically boot into Windows.
A PRAM-reset http://support.apple.com/kb/HT1895 can be the cause of this behavior.
Stefan

Apple Store Refuses to Diagnose Hardware Issue after Boot Camp Installed

I previously reported an issue in the Boot Camp Beta forum, but figured I share this with other MBP users as well. After loading the updated firmware, running boot camp to partion my drive, I installed Windows XP Professional. During the install, the screen would go dark, and come back at irregular intervals, as if there was a video sync problem of something. I managed to get XP installed, and booted it and loaded the updated drives from the Boot Camp driver CD which I had earlier created. Subsequent attempt to use the XP installation result in a constantly blank screen, with only occational glitches, as if there is some activity coming out of the GPU, but it's not working correctly.
This is what led me to take my machine to my local (15 miles away) Apple Retail Store (Washington Sqaure, Tigard, Oregon), and attempt to show the problem to a "genius". HOWEVER... As soon as I mentioned "Boot Camp" and XP, they went into the whole "public beta, blah, blah, blah", "not supported", etc. I tried to explain that I was not reporting a SOFTWARE issue with Boot Camp, but rather a HARDWARE ISSUE which is exposed on my machine only after using BOOT CAMP to partition the hard drive, and then installing Windows XP. All I get was "Well, it works fine in OSX, and Boot Camp is Public Beta, so there's nothing we're going to do". Obviously, I'm livid. And, will pursuing any and all avenues to bring this problem to Apple Management attention. First it was Mark Pienpakdee the "genius" who tried to help me, and then I was further rebuked by Mark Macsurak, Assistant Manager. So, I'm left with broken hardware which won't work correctly running Windows, and no recourse until Boot Camp isn't "Public Beta". What a load of crap. I was so mad, I didn't even bother buying the extra AC adapter I was planning on picking up. ARGHHHHHHHHHHH!!!!!!!!!!!!!!!
I was absolutly shocked that the "genius" didn't react with anything like "wow, what an interesting problem, let's see if we can diagnose it". He didn't even want to see me boot XP to show the problem, only wanted to see that OSX was working normally and send me on my way.
If you have had similar problem at the Washington Square store in Oregon, be sure to let them know by sending e-mail to [email protected], I know I will...
Eric

If you are going to send an e-mail you should send it to [email protected] However, nobody from Apple is going to send you a response. The Software is Beta which means it is not ready for Prime Time (Also that means that the drivers are beta too). Plus they say before you decide to install any of this in their write ups that they do not and will not provide any support for BootCamp and/or Windows. So they are right not to do anything if the computer works like it is supposed to under OS 10.4.6. Now they might take a look at somethings when OS 10.5 comes out if it has BootCamp in it. They may have something similiar in it, or it might be a perfected BootCamp. However, I doubt that they will ever provide any support for Windows. There has been some talk that Microsoft is looking into supporting Windows on the MAC. However, as far as I have heard no decision on that has come out as of yet.

Windows 7 - Blue screen of death after Boot Camp install

Hello! I have done some searches with no answers, so...
After installing Windows 7 from scratch I then install Boot Camp 3.0 which then leads to the Windows blue screen of death upon reboot. I then have to recover Windows to the previous state prior to installing Boot Camp.
Help!?

Most likely, Apple HFS read-only, which is AppleHFS.sys and AppleMNT.sys - rename those and see.
You might want to run chkdsk after all this to make sure there are no errors with the drive and file system.
Windows Explorer will not accept HFS+ filenames with special characters and will "green bar" and hang when it does, too.
The faulty HFS driver is a valid concern.
Rename AppleHFS.sys and AppleMNT.sys
By doing the following you will disable HFS mount / read mode on windows XP, Vista, 7.
Navigate to c:/windows/system32/drivers/AppleMNT.sys, rename the AppleMNT.sys file to something like AppleMNT_keep.sys or something of your likings.
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
After renaming both myself because they are no longer "*.sys" or something? they are gone. In my case AppleHFS prevented Windows Backup from running to end and was causing error "some files skipped" and while some might find reading convenient, I prefer Windows not have even read-only access.
You can probably do better with MacDrive, or probably Paragon's HFS driver, to read AND write if needed, to HFS from Windows.

Driver BSOD on Startup after Boot Camp 3.0 Upgrade.

Similar Messages

Maybe you are looking for