Blue Screen at Start up after changed HD Preferences-Need to back up files!

So here’s what happened,
A few days ago I mistakenly took my HD Drive and changed the permissions on it. Since then, when I start up I first see the apple logo (with chime) followed by a blue screen with a flashing wheel (loading). I have called tech support over the phone and I was told that I should use my mac OS X CD to erase and install to just wipe everything out. Which is fine with me, however, I do not have a back up and would like to be able to keep my files.
I was then told that I would be able to “migrate” my files to a working macbook, then to go ahead and erase the system and put them back in. The problem is that I tried doing the whole migration process but it didn’t work because I could not login to my mac to initiate the process. I also then tried to look at my files from the network, but that is also blocked and does not show up on the other macbook’s available networks.
My question is, what can I do to extract my files from my macbook so I can add them in after I’ve reinstalled my system? Help!

"A1. If the disk in question is your Mac OS X startup disk and your computer stops starting up at the blue screen, restart with the Command and S keys held down, and enter the following commands:
mount -uw /
chown root /
chmod 1775 /
exit
I tried putting in the commands but was not able to exit properly.
After the chmod 1775 /
it asked if I wanted to see a list...
Did nothing for me. Any other suggestions?

Similar Messages

Why can't I access my own wifi? why do I get a blue screen on start up or after watching a netflix movie, and why is it getting so hot?

My mac has been showing a blue screen on start up and before shut down, especially after netflix. Is it silverlight? Why can't I get on my own wifi? It defaults to a linkys public network, I try to access the secure network, type my password, enter, and I get connection timeout.

I was re-decorating my blogger .. then I got the 'Bad Request Error 400' .. I re-formatted my computer, reloaded all .. I can now access my Blogger sites .. Don't know what the problem is/was, but I solved it by reloading my computer to Out-of-Box condition, and all is perfect now .. I have an alert set up for this Error 400 .. Masses of people are having problems daily ..
http://littlemisscinderellasquotes.blogspot.com/

Blue Screen on Domain controllers after Updates

After patching our Domain controllers (virtual on ESXi 5.5 U2) recently we started getting Blue screens and reboots. Other changes in our environment around this time include enabling vshield drivers and scanning with Trend Micro. I have removed patches
from April but cannot remove Patch KB3020370 - there is no uninstall button. The error still persists, I have removed the Vshield driver and am waiting to see if the issue reoccurs. Can anyone assist in interpreting the details below? Also is it possible to
remove the patch KB3020370? This only appeart to affect Domain Controllers, regular servers appear unaffected.
Thanks
Below is the BugCheck event.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000406f8, 0xfffff800018c0e14). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042915-21762-01.
And output from the debug tool.
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\MiniDump\042815-21762-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Error: Attempts to access 'c:\windows\i386' failed: 0x2 - The system cannot find the file specified.
************* Symbol Path validation summary **************
Response Time (ms) Location
Error c:\windows\i386
************* 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: c:\windows\i386
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`0185e000 PsLoadedModuleList = 0xfffff800`01aa3890
Debug session time: Tue Apr 28 13:20:34.290 2015 (UTC + 1:00)
System Uptime: 0 days 0:27:28.954
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 406f8, fffff800018d4e14}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
kd> !analyze -v
* Bugcheck Analysis *
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff800018d4e14
Debugging Details:
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT_SERVER
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from fffff800018cffe9 to fffff800018d0a40
STACK_TEXT:
fffff800`01620d28 fffff800`018cffe9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff800`01620d30 fffff800`018ce4b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`01620e70 fffff800`018d4e14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0276e000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`018ce4b2 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5507a73c
IMAGE_VERSION: 6.1.7601.18798
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7f_8_nt!kidoublefaultabort+b2
FAILURE_ID_HASH: {0367acc4-9bb4-ab69-5701-46a2011718e9}
Followup: MachineOwner

Hi,
Dump file displays：
BugCheck 7F, {8, 80050031, 406f8, fffff800018d4e14} and Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ).
Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack
overflows.
You may reference the link below for detailed resolution about this problem:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff559244(v=vs.85).aspx
Besides, you may try to restore the server to the state before installing these Windows Update.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Blue screen at start up,safe mode only, resolved ,what next?

I got the old stuck on blue screen at start up ,
would only boot in safe mode , after two afternoons of RAM test , repairing disk permissions , hrdware tests , zapping PRam and the likes to no avail , I finally resolved the problem thanks to a tip from this forum:
bad video card drivers ( ATIRadeon 8500 ) , after removing them from the extension folder , it boots up! ( I tried to reset the pram , it won't work though , one chime only then nothing).
so I'm wondering what's next , can i reinstall the video card drivers only ?
is it the card itself ? (everything looks normal) or should I go for an archive and install ?
any input would be great,
Thanks,
JB

Hi-
Jean Baptiste mentioned that he removed extensions for the drivers.
Removing a conflicting driver is fine as long as the driver specific for the card installed remains.
In this case, I think it may have been a corrupt driver, rather than a conflicting driver.
Radeon drivers in OS X have a good track record of compatibility, and such driver conflict is not a historically common occurrence.
Hard drive maintenance with Disk Warrior is the best way to correct corrupt files, unless bad RAM is corrupting the files.....
In your case, it shouldn't hurt anything to remove the Radeon 8500 drivers.
Could it be the driver extensions that are preventing a proper boot. The monitor displays perfectly in safe mode so I don't understand why it would be the video card.
Booting to Safe mode unloads drivers. Only very basic core graphics rendering drivers are loaded.
No Quartz/Quartz Extreme, no Core Image, no 3D acceleration, etc.
This doesn't tax a graphics card.
Failure to boot, or failure of graphics when drivers are loaded are due to one of two things- corrupt drivers or failing components on the graphics card.
A reinstall of the OS can rule out the first.
Installing a different graphics card is the only way to rule out the second.
Before buying a new card, I would try a fresh OS.
Installing a new OS on a separate drive, and booting to that is an easy way to test.

Hi, Hi, Hi I have the old MacBook Pro. Upgraded to Mountain Lion which completely wrecked the system. So downgraded to Snow Leopard. The updated the combo update. Now stuck on blue screen at start-up. Need help. Greatly appreciated. Thank you.

Hi,
I have the old MacBook Pro. Upgraded to Mountain Lion which completely wrecked the system. So downgraded to Snow Leopard.
Then updated the combo update. Now stuck on blue screen at start-up.
Need help. Greatly appreciated. Thank you.

Downgrade Lion/Mountain Lion to Snow Leopard
1. Boot from your Snow Leopard Installer Disc. After the installer
      loads select your language and click on the Continue
      button. When the menu bar appears select Disk Utility from the
      Utilities menu.
2. After DU loads select your hard drive (this is the entry with the
      mfgr.'s ID and size) from the left side list. Note the SMART status
      of the drive in DU's status area. If it does not say "Verified" then
      the drive is failing or has failed and will need replacing. SMART
      info will not be reported on external drives. Otherwise, click on
      the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions
      from the drop down menu to one. Set the format type to Mac OS
      Extended (Journaled.) Click on the Options button, set the
      partition scheme to GUID then click on the OK button. Click on
      the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Install Snow Leopard.
This will erase the whole drive so be sure to backup your files if you don't have a backup already. If you have performed a TM backup using Lion be aware that you cannot restore from that backup in Snow Leopard (see below.) I suggest you make a separate backup using Carbon Copy Cloner.
If you have Snow Leopard Time Machine backups, do a full system restore per #14 in Time Machine - Frequently Asked Questions. If you have subsequent backups from Lion, you can restore newer items selectively, via the "Star Wars" display, per #15 there, but be careful; some Snow Leopard apps may not work with the Lion files.

Blue Screen on start up with dual monitors

I have a macpro running Mac OS X 10.5.6 (9G55) when 2 monitors are hooked up to it the computer the machine Blue Screens on start up. This also occurs when the computer wakes up from a deep sleep. Currently the only work around is to just use one monitor. Ive read the posting here and on macosrumors.com, but there does not seem to be a solution, however most post are from last summer. Was this fixed at some point? Is there a solution? I also tried boot from another drive (from another macpro) with both monitors hooked up and the problem continues.
Ive also read the KB article and removed ApplicationEnchancer.bundle, but the problem continues.
http://support.apple.com/kb/TS1545?viewlocale=en_US
Any help would be much appreciated.
Thanks,
Scott

Scott,
Ok here are the next things on my list, and I will start with what I think is the most valuable to the just plain fun and simple you and I would be shocked if it fixed it. I only skimmed your other post, if you feel that something I recommend is a repeat you can ignore it and I will not take any offense. Sorry If my post is a little loopy I've been up for way to long.
1) Safe Boot your mac. To do so hold shift whilst your Mac boots. Please note it will take longer to load.
Starting up into Safe Mode does several things:
1. It forces a directory check of the startup volume.
2. It loads only required kernel extensions (some of the items in /System/Library/Extensions).
3. In Mac OS X 10.3.9 or earlier, Safe Mode runs only Apple-installed startup items (such items may be installed either in /Library/StartupItems or in /System/Library/StartupItems; these are different than user-selected account login items).
4. It disables all fonts other than those in /System/Library/Fonts (Mac OS X 10.4 or later).
5. It moves to the Trash all font caches normally stored in /Library/Caches/com.apple.ATS/(uid)/ , where (uid) is a user ID number such as 501 (Mac OS X 10.4 or later).
6. It disables all startup items and login items (Mac OS X 10.4 or later).
7. Mac OS X 10.5.6 or later: A Safe Boot deletes the dynamic loader shared cache at (/var/db/dyld/). A cache with issues may cause a blue screen on startup, particularly after a Software Update. Restarting normally recreates this cache.
http://support.apple.com/kb/HT1564
2) Try reseting the Pram.
Resetting PRAM and NVRAM
1. Shut down the computer.
2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
3. Turn on the computer.
4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
6. Release the keys.
http://support.apple.com/kb/HT1379
3) Reset the startup Disk. Open System Preferences -> Startup Disk -> Select Mac OS X.
I'll leave you with that, please come back with your results.
Weston

Help Blue screen on start up

Hey Guys,
I could use a little help on this one.
Symptoms:
I am only getting a blue screen on start up.
This happened after I downloaded an FLV player.
I think it was called "whimpy flv player."
Might be a coincidence (not sure).
I can start up in safe mode only and can get online hardwired, but the option for wireless is gone.
Any help would be appreciated.
Poncho

First try resetting your PRAM
Then try booting from your install disc and verifying/repairing your hard drive.
Disk Utility
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.

What would cause a prolonged blue screen during start up?

I have an iMac desktop. Recently I've had trouble with a prolonged blue screen during start up (approx. 10 mins) before it finally takes me to the login screen. Any ideas why this is happening?
Jeff P.

Hi Jeff,
Open console in Applications>Utilities, check the system log for the date/time of the last problem Startup for clues.

On start up sometimes I get a blue screen and start up hang there

On start up I sometimes get a blue screen and it hangs there the only way to get out of this is to turn the iMac off at the back then when you turn it back on the desk top appears without going through the startup screens. Even had the blue screen when starting in safe mode.

Then run Apple Hardware Test in Extended Mode, it's possible you have a hardware issue. If you still can't locate the issue the next step is taking the machine in for a professional diagnosis at your local Apple Store or AASP.

Can't get past the blue screen with "starting Mac OS X"

I am having problems with starting my iMac. It gets to the blue screen with "starting Mac OS X" but won't go beyond that point. I was able to get the disc drive open with the help of other posts, holding down the mouse while turning on the computer, but the drive won't stay closed with the install disc in it. I have even tried holding down the "c" key while restarting the computer and it wouldn't work. Any help would be greatly appreciated. So much info that I could really use. Also, please keep in mind that I am not too computer savy. Simple language please.
Thanks

If the steps I provided in my earlier post are not helping, then I see your options at this point as follows:
1. Run the Apple Hardware Test (AHT) that came the affected computer. See my "Apple Hardware Test" FAQ for comprehensive advice on using the AHT in troubleshooting.
2. Performing an Archive and Install. For important tips on this, see my "General advice on performing an Archive and Install" FAQ. Perform the steps therein in the specified order.
3. Take the computer in for service. If there is an Apple Retail Store in your area, I'd recommend taking it there. You may wish to call ahead to make an appointment at the Genius Bar.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

How to get past blue screen at start up on MacPro?

I have a blue screen at start up and the MacPro won't boot up.
Before I attempt to hold down keys at start, pls let me know which one to hold down.

See if there is assistance here:
https://discussions.apple.com/docs/DOC-5282
Ciao.

Blue screen: HP Pavilion dv6 after Windows update on Aug 1.

Last year or so, I had this blue screen issue with my dv6 laptop and was solved by uninstalling KB2670838.And things have been very peaceful since then, but the blue screen re-occured recently after windows update last week.The updates were suggested by HP Support agent installed in and was for getting ready for Windows 10 installation.But my pc gets blue in every 3 min now, so I un-installed all updated job occured last week as temporal solution. Though I wish to be ready for Windows 10 installation, I need to have operable PC for my work.(This is Win7 sp1, home eddition) It would be great if anyone could assist me on this. Thank you, Piko.

I have this problem. It happens without any warning.
I don't know the reason. Please help me.

Blue screen on start up. Safe mode not working?

Blue screen on start up. Safe mode not working, any suggestions?

Thank you, I had forgotten about target mode. I was able to back up all of my files. I also copied some additional 50 GB of files of the disk as a stress test and the hard drive worked fine and quick (and because it was quicker than retrieving the same files from a network drive to my desktop).
I was hoping to also unpack the Applejack files on my desktop and put them back so I could run them in single user mode without running /etc/rc. However I haven't been able to get my Linux desktop to mount the iBook in Read-Write instead of Read-Only yet (I don't have access to another Mac at the moment).

Stuck at Blue Screen on start up

My MacBook Pro gets stuck on the blue screen at start up. Have tried all the obvious fixes but no joy.
I put my mac in target mode and connected to another MacBook Pro
Then selected my HDD as the start up disc, rebooted, and this worked fine, i was able to run my HDD and all software fine.
I conclude this shows i have a hardware problem on my mac.
Can anyone please give me a clue as to what it might be? or is it time for a visit to the apple store (and a remortgage on the house)?
Many thanks Phil.

I know you already mentioned that you "Tried all the obvious fixes" but this is the first thing that came to mind when I read your problem.
Hold down the power button until your Macintosh shuts off.
Then hold down the power button until the white light on the front of your Macintosh starts flashing rapidly.
Then release the button and see if your device boots up normally.
I had this very same problem happen to me a few weeks ago and I was able to solve it by doing those few steps.
Hope this helps!
-Benjamin

I have an Imac. On startup I get the blue screen. An apple Tech told me I need a new hard drive? Is he right?

My Imac has the dreaded blue screen on start up. To avoid this, I unplug the machine each night which solves the problem. I have contacted an Apple service rep who says I need to replace the hard drive. Nothing I have read indicates this. I have not added new hardware, not changed anything. Could it be my hard drive is bad?
Thanks

You could try a few things (if you haven't already) before giving up on the HD. You could try a Safe Boot:
Restart holding down the shift key until you see the grey progress bar. When the Mac has finished booting, restart as normal from the Apple menu.
Boot from your install disk and verify/repair the disk using Disk Utility (let us know if you're unsure how to do this).
Try an SMC reset and a PRAM reset:
SMC Reset
Shut down the computer.
Unplug the computer's power cord and disconnect attached devices.
Wait fifteen seconds.
Attach the computer's power cord.
Wait five seconds, then press the power button to turn on the computer.
Reset PRAM
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P and R.
You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
Try these things one at a time, and test the machine after each step.

Blue Screen at Start up after changed HD Preferences-Need to back up files!

Similar Messages

Maybe you are looking for