Not booting after update (10.6.4)

I updated my MacBook the other day and after rebooting, it gets to the gray screen with the apple logo and the spinning disk. It then just sits there.
I have tried booting to safemode, resetting the smc and nvram, I've run Disk Utility from CD and repaired the disk and permissions. None of that has made a difference. I am able to get to single user mode and I've run fsck from there, but still no luck.
I'd rather not go the reinstall route is there anything else that I can do to fix this?
When I boot in verbose mode these are the messages I get just before it freezes:
systemShutdown false
Warning - kext com.apple.iokit.CHUDProf has immediate dependencies on both com.apple.kernel* and com.apple.kpi.* components; use only one style
NVADANV50HAL loaded and registered.
Previous Shutdown Cause: 3
**Truncated... apparently normal AirPort stuff**
failed to inflate in one pass: -3
/SourceCache/AppleFSCompression/AppleFSCompression-24.3/Common/commonUtils.c:233 : decompressChunk: error
decmpfs.c:1149:decmpfspageincompressed:err -1
AirPort: Link Down on en1. reason 1 (Unspecified).
NTFS driver 3.2 [Flags: R/W].
NTFS volume name BOOTCAMP, version 3.1.
After that it just sits there.
Any suggestions?

Reinstalling the OS and then updating it should take less than an hour.

Similar Messages

Macbook Will Not Boot After Updating Leopard

I just reinstalled Leopard after having some trouble with my partition tables, and everything ran smoothly and worked fine. After the install I let software update update everything including the 10.5.5 update. It prompted me to reboot, and when I did it got to the grey Apple screen and the thing spun for about 30 seconds before it restarted and did it again. This happened a few times and then I booted from a Leopard disk to look at disk permissions and they seem to be fine. Anyone have any idea why this is happening or how I would fix it?
Thanks in advance, hope to get this sorted out quickly, I thought I had finally gotten my computer working fine again when I reinstalled Leopard. :P

At start up, press 'C' to boot directly from a CD/DVD. Or, you can press 'Option' and you should get a list of bootable selections (CD/DVD, external hardrives) that you can boot from - assuming you have something that IS bootable.
I recently had a problem and ended up reinstalling my OS (via TimeMachine). I also confirmed that you can boot from your original OSX install disk. As part of this process I also discovered I could NOT boot directly FROM the AppleCare provided TechTools Deluxe disk. Supposedly you can boot INTO that disk via a restart but that seems kind of silly to me.
However, if you have signed up for AppleCare and go to the Apple Support web site, you can download TechTools Deluxe and it can be made bootable by burning the .dmg file via Apple Disk Utilities. I don't understand Apple logic of not making the provided AppleCare TechTools Deluxe disk bootable.

My iMac does not boot after update!!!

I have just update my iMac (Intel) with Apple Software update. I have not updated for quite a while and obvious there were a bunch of stuff to update on my mac. However, when the computer requests a restart, my computer simply does not restart at all. I have tried to make it restart from the apple icon, and it still stay on. So I turn it off manually and the problem kicks in. My computer start with the grey apple icon screen and the little progress indicator, but it does not boot into OS X!!! It remains in a blue screen with the mouse pointer.
I restarted it again unplugging everying and nothing changed. Then I tried Disk Repair and it does not help neither. Then I tried to hold the power button while turning it on till I get the loud beep noise and flashy light. The problem stay the same. I do not want to erase my disk...
Someone Helps!
Intel iMac 20" Dual Core / MacBook Pro 15" Mac OS X (10.4.6)

Interesting. Have you installed any third-party RAM? Is there any possibility that your RAM became loose? Make sure your existing RAM is seated properly.
Have you performed a SMC reset?
Resetting the SMC can resolve some computer issues such as not starting up:
From the Apple menu, choose Shut Down (or if the computer is not responding, hold the power button until it turns off).
Unplug all cables from the computer, including the power cord and any display cables.
Wait at least 15 seconds.
Plug the power cord back in, making sure the power button is not being pressed at the time. Then reconnect your keyboard and mouse to the computer.
Press the power button on the back to start up your computer.
Are you able to boot in SAFE mode? If so, you can trouble shoot from there.
Be sure the computer is shut down.
Press the power button.
Immediately after you hear the startup tone, press and hold the Shift key.
Tip: The Shift key should be held as soon as possible after the startup tone but not before.
Release the Shift key when you see the gray Apple and progress indicator (looks like a spinning gear).

Will not boot after updates

I have a macbook air. It is running Lion. After updates it will not boot. It starts installing updates and just stops all together. Any help would be very welcome.

Hey bfa67,
Thanks for the question. To isolate the issue, what happens when you start up in Safe Mode?:
OS X: What is Safe Boot, Safe Mode?
http://support.apple.com/kb/HT1564
Thanks,
Matt M.

[SOLVED] Kernel will not boot after update to 3.1.5

Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
Last edited by bolshevik (2011-12-16 14:31:19)

bolshevik wrote:
Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
If you foolishly interrupted the initramfs creation after a kernel upgrade and didn't regenerate it manually, you earned this.
You'll need to find a live CD so you can chroot to your install and rerun mkinitcpio.

Server will not boot after update !! Help needed fast !!

I have a new (Aug 2005) XServe G5, running 4.3.
Active Directory integrated, stores home folders (AFP), manages preferences and 5 print queues for 55 Mac OS X.4.3 clients and 200 users.
It downloaded the 4.4 update, unchecked the OS 4.4 update (I think was my first mistake), restarted. Now, at boot up, about the moment the apple would appear (maybe it appears for a split second) all I get is the ugly not sign.
-- Am able to boot to external firewire drive
-- Drive shows as boot option
-- Disk repair reported no problems to fix
-- Can not find any log entries after last shut down. No service ever starts for any entries to be made.
-- Applied the 4.4 update successfully while booted from external fw drive, no effect. Startup disk reports system to be OS X Server 4.4 and lists as a boot option.
-- Drive behaves same when transferred to my G5 tower: big not sign.
What other steps can I do to troubleshoot this boot problem? If I don't get this server up this weekend, I'll get roasted by an angry mob.
Any suggestions are welcomed and greatly appreciated.

Eeh...
Always clone the existing system prior to updating it. Do so when the server is not in use, shut off services where possible (you want it to be as quiescent as possible).
Mike Bombich (at Apple) describes how you can do this via the command-line, which I prefer for this purpose (you can stagger the process):
http://www.bombich.com/mactips/image.html
Now then:
Have you booted from the install CD and used Disk Utility to run Repair Permissions ? That should be your first step.
It may change nothing, but can you boot into Safe mode ? Hold down the Shift key at powerup and keep holding it until you see: "Safe boot"
If you CAN get it booted in that state, then run the 10.4.4 COMBO updater
you need to run the combo updater at this point. After doing so, use Disk Utility to run repair permissions on the boot drive itself, and then reboot.
Otherwise, start it in Target Disk Mode as you did before, connect it to a unit running 10.4.4, and run the /combo/ 10.4.4 Server updator (NOT client, of course) onto the server's mounted hard drive.
I'm not sure you can do this while running 10.4.x client. You may need to do a quick install of 10.4 server (say onto a Firewire drive), boot your spare Mac from it, and -then- mount the server via Firewire target mode, and apply the 10.4.4 server combo updater.
Good luck !

[SOLVED] Not booting after update to grub, syslinux

I did a system update trying to fix some package dependencies for a mongodb issue. I saw that there were changes to grub, so I stopped, and was good. I checked the home page, I checked the forums. The only thing I found was a thread saying that it should be fine. So I ran the update. syslinux also updated.
After it completed, I diff'd the pacnew files, made all the appropriate changes (I thought) and rebooted.
:: Triggering uevents...
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device 'dev/sda3' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda3',
I was then dumped into the recovery shell, which was completely useless since it doesn't seem to be loading the USB drivers and so my keyboard won't work. I think I've got a PS2 keyboard in storage, I'll try to grab it tomorrow. (With my luck, I purged it last time I was cleaning.) I downloaded a fresh image and got a bootable USB going, but I'm at a loss as to what to do next.
I'd wipe and restore the damn thing so I could get back to work, but there's a couple ssh keys that would be a pain to replace. (Yeah, I know, I should have backed them up some place. I didn't.)
Help?
Last edited by jbhelfrich (2013-07-31 19:49:08)

I have two partitions on SDA. Partition 1 has the core file system and partition 2 has the contents of the /home directory. I mounted them and chroot into them.
I found http://sourceforge.net/projects/bootinfoscript/, and downloaded that and ran it. It shows that sda1 has syslinux as the boot sector type, but that "the 2 ADV sectors are not the same (corrupt)."
Can I pacman -R grub safely at this point, to at least remove one source of confusion?
Looking at the syslinux.cfg file to see if I can figure out what I missed.
EDIT: OK, the syslinux.cfg has "APPEND root=/dev/sda3 rw" for both arch and archfallback. I assume I can change those to either sda1 or the UUIDs listed in etc/fstab and be good to go?
And yes, I see the trend on wiki articles. Sadly there's not a wiki entry for "hey, what's that linux admin command that I've forgotten will totally save me?" to point me in the right direction.
Last edited by jbhelfrich (2013-07-31 18:24:53)

Arch not booting after update due to udev problems

Hi,
since an update yesterday one of my systems won't boot anymore.
I tried several solutions mentioned in the forum with no success:
1) went back to an older kernel
2) uninstalled and reinstalled mkinitcpio, delete and got a new mkinitcpio.conf
and ran mkinitcpio -p kernel26 on the kernel
I had a sort of success by disabling autoloading in rc.conf. Instead of just crashing
as with autoload enabled it went through to the boot prompt. But I couldn't test any further because I had only usb-keyboard available and that didn't work due to some a missing module I guess . I'll try to get my hands on a PS2 keyboard and look how far I can get later.
I think the key to the problem might be that I use JFS for both root and home partition (ext2 for boot). From the error messages before the crash it looks like the computer can't reach the root-device. I tried to add jfs to the modules section of mkinitcpio.conf and ran mkinitcpio -p kernel26 again but no change.
Maybe someone can give me a hint how to get the system up again and fixing the udev problems. This setup did work for the last couple of months so maybe there was some recent change in this regard I overlooked.
I'm using testing repos and thats what might happen at bleeding edge, no complaining . Nevertheless I would be very interested to understand whats happening and how do get the system up again.
Thanks and best regards

Hi,
thanks for your answer.
I had merged the pacnew-files already. I read through the udev-readme and did the suggested changes (for example in modprobe.conf) but still not able to boot.
If I boot failsafe I can actually read an error message on the screen instead of blanking out:
md: raid10 personality registered for level 10
:: Running Hook [filesystems]
:: Loading root filesystem module...
Attempting to create root device '/dev/sda3'
/bin/mknod "dev/root" b 8 3
/init: 1: cannot open /dev/root: No such device or address
and after some more lines
kinit: Unable to mount root fs on device dev(8,3)
kinit: init not found
Kernel panic - not syncing: Atempted to kill init
/dev/sda3 is the correct root-device but I have no raid. I have two hdd's (one IDE, one SATA) and one DVD-RAM on IDE as slave, nothing more, nothing less.
If I boot via install-cd I can mount /dev/sda3. Sometimes I have to run fsck first because mount complains about bad superblock but after fsck I can mount without problem although it didn't report any error. I'm confused.
Any ideas?

Macbook Pro not booting after update. ''Disk Utility can't repair disk''. Help needed!

I have recently updated my macbook pro as I had some pending software updates. I left it to do the job over night and the next day I noticed it was not letting me sign in to my account session as usual.
I restarted the computer and ever since then when I boot it, it just shows the apple grey screen with a bar that loads to about a 3rd and then it turns off again. I have contacted apple but they were unable to help me with this.
So far I have tried to:
1. Re-install OS X 10.8 - but it says the disk is locked or OS X cannot be installed on Recovery HD.
2. Verify and Repair the disk and I errors but it cannot fix them. Some are:
               'invalid leaf count''
               ''missing thread record''
               ''incorrect number of file hard links''
               ''overlapped extent allocation''
          and it finally says ''the volume Macintosh HD cannot be repaired'' Error: ''Disk Utility can't repair this disk.. disk, and restore your backed up files.
I would like to know a way to back up my files so that i can completely restore the disk without any data loss as I havent backed up for a while!
If anyone has any solution to this issue it would be much appreciated!

I just ran the Disk Utility, and cannot very disk. It gives me an error message;
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
and when I run the repair, this is the message:
The volume GERRARD could not be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
1 volume could not be repaired because of an error
Repair attempted on 1 volume
1 volume could not be repaired
Prior to running Disk Utility, I have already tried DiskWarrior, and could not repair my disk. Anyway I can fix this problem??? Formatting the disk would be my last option (though I am unsure if it will fix the problem). Any advise would be greatly appreciated. Meanwhile, I will continue to back up my file, and delete unused data and try to run it again.
Thank you all very much for any input.
Cheers,
Matt

Macbook (Black) Will Not Boot After Update (grey screen of non-booting)

I bought my first MacBook less than one month ago.
Last night at 9pm the apple update software said there was an update and I should restart. It has not been able to boot since.
Now, when the computer turns on it shows a grey screen with a dark grey apple logo for a few minutes, then turns off again.
I am completely lost, any help would be greatly appreciated.
Thank you for your time.
Chris Albon

Sorry to hear about your troubles Chris.
Was this a System/Security update you installed or just for an application? Personally, I never install anything system related without first running a 3rd party Disk Utility like DiskWarrior. It's important to ensure that there are no latent issues before doing so. That being said, if you don't have access to DW, try booting up from your OSX installation DVD (insert the disk and hold down the 'C' key on startup) and choose Disk Utility's disk repair option from the file menu once it's loaded. Post back once you've tried this.

IMac, 2010, will not boot after update

After downloading Yosemite, my 2010, 27" iMac will not reboot. It appeared to install ok but it stayed white screen, no text for more than an hour after it automatically rebooted. Idaes?

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

HP Pavilion 500 (desktop) will not boot after updating driver's.

Working on my mothers CPU but I cant seem to get past this screen now
This was after I had downloaded and installed drivers from this site. I cant seem to figure out why it is not going in to windows xp. Any ideas? It also was giving me a fan error which was easy to fix but cant seem to figure this out.

wow no one can help I guess everyone is duped as I am. DaRN HP

Not Booting after recent Security Patch/Java update

My wife has experienced what many have experienced with the recent update.
MacBook not booting after update (i.e. - "I have no name!")
I have tried everything posted on this topic since 2/13/09, but without any success. Does anyone have the fix for this yet?
Things I have tried:
* I can boot in safe mode (holding "Shift" while restarting)
* I cannot boot from an install disk(s) (holding C while restarting) - I have both a black one from purchase, and two gray ones with purchase from MiniMac
* Booting with verbose - gets stuck at same place as everyone else
Operating in safe mode:
* I can run DU and "repair" drive
* I can see and access the CD/DVD
* I cannot see drive in target drive mode (doesn't ever connect the 2 systems)
* I downloaded the update files from apple and reinstalled them individually (via USB ext Drive) with a reboot in between
* I attempted to update & archive, but I cannot run install CD from any systems disks (see above)
Has anyone figured out how to fix this yet?

Same problem than the other guy who is not mentioning the update in the title.
Powerbook 1.67.
System log said "No user defined computer name" and "using blah blah name" or so.
Mac Os X report (for apple) says:
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000003900FF1C PC=0x00000000008FC020
Latest crash info for cpu 0:
Exception state (sv=0x4299D280)
PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
0x000233F8 0x000ABEAC 0xFF9BA29B
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon9700(4.1.8)@0x8d8000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
Proceeding back via exception chain:
Exception state (sv=0x4299D280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x43D0D000)
PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x4299D280)
PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
0x000233F8 0x000ABEAC 0xFF9BA29B
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon9700(4.1.8)@0x8d8000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
Exception state (sv=0x43D0D000)
PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC

My Laptop B490 not booting after bios update

My laptop not booting after updating bios i used windows 8 OS.
I downloaded Bios from following link.
Bios Download Link
After updating bios, system restarted automaticaly, after that only power led is glowing, screen stays blank.
Help me solve it.
Solved!
Go to Solution.

hi sathish291
Welcome to the Forums.
Can you try the following:
1. Power down the machine, remove the AC adapter and battery.
2. Hold the power button for 30secs and reconnect the AC adapter only then turn the computer ON.
If the machine still doesn't power up normally and boot into WIndows then it's likely that something went wrong (could be a bad BIOS flash or an internal component might have gone defective during or after the BIOS update). In this case, you may need to contact lenovo on how to go about getting the unit serviced.
Support phone list
Regards
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

HELP ME! Nokia 5230 does not work after update

My nokia
5230 will not boot after update. I've also tried everything and red green camera button intedruken but nothing worked. Can someone help me I am so on vacation.
Sorry for my English I am Dutch

Have a look at this complete guide.. If nothing works, then the ONLY solution is to visit Nokia Care...

Not booting after update (10.6.4)

Similar Messages

Maybe you are looking for