Mac OS won't boot after 2007-009 1.1 update

Hi all
Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
Any help would be really appreciated.
Thanks

I have been booting up for...2.45 hours now
Good grief!
Here are a few hints about what you should have done:
There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692

Similar Messages

  • Mac Mini won't boot after 10.6.6 / Airport update

    I just reinstalled 10.6.3 on a unibody Mac Mini, updated to 10.6.6 - and it booted fine. I ran another software update, and it suggested two more updates - which I believe was an Airport Utility update and a Java update. Now the Mac Mini fails to boot, stopping at the Apple logo.
    The last lines of verbose startup goes like this:
    Airport: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Aut result for: (MAC address) succeded
    AirPort: Link Up on en1
    AirPort: RSN handshake complete on en1
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?
    Suggestions?
    H

    I experienced a similar problem today after a recent upgrade to 10.6.6. I ran Tech Tool Pro 5 on the machine, which reported everything as just dandy after about 6 hours of testing, but it still wouldn't boot. Next, I tried booting in Verbose mode, which revealed that my iMac was hanging on:
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?
    I used Safe Single User mode (turn on power, then immediately press and hold Shift-Command-S until text starts appearing) to boot to a command line. Single User mode provides instructions on how to mount the file system read/write. I executed the `fsck` command as instructed, and after a few minutes it reported that it had made changes to the file system. At that point, I skipped the `mount` command and went directly to `exit` to continue the boot process, which completed. I turned AirPort back on (I had it turned off), then rebooted normally without any trouble.

  • Mac Mini won't boot after applying 2009-001 Security Update

    I'm stuck at the gray startup screen with the Apple logo and the "gear wheel" progress indicator. Still stuck there after 60 minutes of "letting it brood."
    How to I fix this?

    The easiest way to solve the problem is to restore the drive from the backup you made just before installing any update or software on your computer, then do the installation again following the suggestions at the end of this post. Failing that...
    First, try the routine repair disk and repair permissions with Disk Utility on your installer disc. Boot from the installer disk, select language if applicable, choose utilities, run Disk Utility and verify (and repair if necessary) the drive. You can verify a drive from DU on your main drive while booted but I have found this can result in incorrect reporting of errors. To repair your drive you have to run it from a drive other than the boot drive anyway.
    Next, boot from your drive in [Safe Mode|http://docs.info.apple.com/article.html?artnum=107393] and repair permissions. You can repair permissions while booted from the installer disc but this uses the permissions configuration on the installer disc which may be out of date if you have run any updates on your computer. Booting your computer to Safe Mode restricts the number of things running on your computer while permissions are being run and done a bit of spring cleaning at the same time.
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    From BDaqua (couldn't have said it better):
    "Try Disk Utility
    1. Insert the Mac OS X Install disc that came with your computer (Edit: Do not use this disc if it is not the same general version as what you have currently on your computer, e.g. use a Tiger disc for a Tiger drive, not a Panther disc), 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.
    Then Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes."
    If you don't have an installer disc available you can try effecting repairs using [fsk in Single User Mode|http://docs.info.apple.com/article.html?artnum=106214].
    [Post by japamac about using fsk|http://discussions.apple.com/thread.jspa?threadID=1649143&tstart=0]
    If the above don't work, two things seemed to be solutions for Security Update 2008-008 problems.
    One is Archive and Install which will replace the corrupted system but then requires you reapply all your updates. Select the keep settings and preferences when doing A&I. Make sure you select that option when doing A&I if you want settings and preferences kept. Some third party applications may need reinstalling if they have special components.
    [Mac OS X: About the Archive and Install feature|http://support.apple.com/kb/HT1710?viewlocale=en_US]
    [X-Lab Archive and install|http://www.thexlab.com/faqs/archiveinstall.html]
    [Kappy's A&I instructions|http://discussions.apple.com/thread.jspa?threadID=1823034&tstart=0 ]
    [How to get files from a previous home directory after Archive and Install|http://docs.info.apple.com/article.html?artnum=107297]
    The other is to try to re-install the security update on the main drive while booted from a secondary drive or in Single User Mode. This could be from another Mac computer while your first one is in Target Disk Mode, perhaps a bootable backup drive, or possibly from your installer disc. Here's references for those methods:
    http://discussions.apple.com/message.jspa?messageID=8728797#8728797
    http://discussions.apple.com/message.jspa?messageID=8733921#8733921
    http://discussions.apple.com/thread.jspa?messageID=8634535#8634535
    Updating
    There's been recent discussions as to what steps are truly necessary in doing a minimal problem update.
    I think #1 to which all agree is to make sure you have a backup of your computer in case you do need to back out of it again.
    Some like to boot from their installer discs or an external backup and verify (and if necessary repair) their internal drives as well as drive permissions. This is done with Disk Utility. You can verify a drive while booted from the same drive but sometimes this produces spurious errors. Repairing a drive (if necessary) has to be done while booted from another disk. Permissions repair can, and is probably best, done when booted from your internal drive.
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    You can also go to the step of booting into safe mode to do the install.
    [Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
    [What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
    [Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
    I like to download the update onto my computer and install it from there rather than let Software Update do it. I know a few people who had problems with doing the update via software updater found a manual install to work.
    Repair permissions again afterward.
    It also helps to only install one update at a time and to run the computer for a while to make sure it is behaving well.
    Almost all of the above steps (except backup) have been questioned as to necessity because probably many people have done successful updates without doing them. I say they can't hurt, they can very likely do good (especially if your computer isn't regularly maintained), so why not do them to be safe.
    [BDaqua's comments on updating problems|http://discussions.apple.com/message.jspa?messageID=8948595#8948595]

  • Another Mac Mini won't boot after applying 2009-001 Security Update

    I installed 2009-001 Security Update last night. Now it is stuck at the Apple Logo and Progress Indicator screen. I booted to Single User mode, and ran "/sbin/fsck -fy", it reported no problems. I also booted in verbose mode, which results in:
    /System/Library/CoreServices/Loginwindow.app/Contents/MacOS/loginwindow: Login Window Appliation Started
    It shows this message, waits 5 seconds (or so) shows it again, waits 35 seconds (or so), and repeats this loop ad infinitum.
    I am not able to boot into Safe Mode, still gets stuck at Apple Logo and Progress Indicator screen.
    I do not have immediate access to my installation media - they are in another state.
    Much of this information is already in another thread, but, that one was started by someone else who did resolve there problems, and the thread is marked answered - so I am started a new thread:
    http://discussions.apple.com/thread.jspa?threadID=1904960&tstart=0
    Thanks,
    Chris

    No, because it isn't clear what really caused the problem. There's lots of different bits of computer code on your computer from many different programmers and companies and all those people have to interact with their coding. Then too, maybe there was a power flicker at some stage and a file wasn't closed properly and couldn't be replaced by the update so not all the files were replaced. Also, you are one out of maybe a couple of dozen who have posted about this problem, vs. how many million Mac users who haven't had a problem and haven't posted here to say, "No problem!"
    Here's my boilerplate post on updating:
    Updating
    There's been recent discussions as to what steps are truly necessary in doing a minimal problem update.
    I think #1 to which all agree is to make sure you have a backup of your computer in case you do need to back out of it again. This is the easiest way to resolve any problems an update may produce.
    Some like to boot from their installer discs or an external backup and verify (and if necessary repair) their internal drives as well as drive permissions. This is done with Disk Utility. You can verify a drive while booted from the same drive but sometimes this produces spurious errors. Repairing a drive (if necessary) has to be done while booted from another disk. Permissions repair can, and is probably best, done when booted from your internal drive.
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    You can also go to the step of booting into safe mode to do the install.
    [Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
    [What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
    [Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
    I like to download the update onto my computer and install it from there rather than let Software Update do it. I know a few people who had problems with doing the update via software updater found a manual install to work.
    Repair permissions again afterward.
    It also helps to only install one update at a time and to run the computer for a while to make sure it is behaving well.
    Almost all of the above steps (except backup) have been questioned as to necessity because probably many people have done successful updates without doing them. I say they can't hurt, they can very likely do good (especially if your computer isn't regularly maintained), so why not do them to be safe.
    [BDaqua's comments on updating problems|http://discussions.apple.com/message.jspa?messageID=8948595#8948595]

  • Mac Mini won't boot after update

    I have a Mac Mini that won't boot after the most recent software update. Since the Mini has only a bluetooth keyboard and mouse, a number of the usual options (hold down shift, etc.) won't work. I've tried a reset, also no luck. At the moment, I can't locate my Tiger install CD either.
    When holding the power button on during boot, I get a series of flashes from the status light on the front (a set of very rapid flashes, followed by a slower set, followed by a slow set) but no startup chime, or fan, or video. My display and power source are both known-good (work fine with my Powerbook)
    Any suggestions, other than buying a hardwired keyboard/mouse?

    Welcome to Apple Discussions!
    The 'newer version of OS X" error occurs because the installer on the DVD you have booted to has by default been set to update the version of MacOS on the hard drive, which of course it can't do because the version of MacOS it is installing is newer. The only way to install in this situation is to select a different option. However, that isn't what you want to do at this point, because as it says, you'll loose your data if you do an 'erase and install'.
    Instead, you should see menus at the top of the screen when it's booted to that install disk. Click the Utilities menu, select Disk Utility, and then click the top entry for the internal hard drive on the left. Once done, click on the 'Repair Disk' button (not Repair Permissions). This will test the drive to make sure it's OK. If it reports errors, and then reports 'error or exit' with the drive not repaired, you will either need a 3rd party application such as Alsoft's Disk Warrior, or to perform an erase and install (which of course you don't want to do at this point because your data is not backed up).
    If the Repair Disk process completes with no errors, next select Repair Permissions, and let that process complete, then reboot the system as normal to see if you can now access the drive.

  • My MacAir 1st gen. won't boot after latest OS X Lion update.

    My MacAir 1st gen. won't boot after latest OS X Lion update. tried safe boot(didn't work) tried disk repair, said it was successful, but my mac won't start up. Just get white screen.  Also been having trouble with it overheating. Fan seems to work. But when it get too hot whole interface slows down.

    Yikes, I hope you have AppleCare on it still, I think it needs to be taken in, but as a last ditch effort...
    Have you done a PRAM reset, CMD+Option+p+r...
    http://support.apple.com/kb/HT1379
    In fact, do 3 in a row, takes a bit of time.

  • Mac mini won't boot after RAM upgrade.

    Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
    Things I've tried so far:
    1. Resetting the PRAM, no luck.
    2. Holding option at start-up, shows no icon.
    3. Holding shift, no luck.
    4. Holding X, nothing.
    How do I get it to accept a CD if it won't boot?

    Welcome to Apple Discussions!
    You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
    If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
    It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

  • My Mac Pro won't boot after installing the latest update

    Im running the latest OSX on my mac and recenty did a small updated that i believe contain a few security thing and bug fixs but when restarting the machine after the update it would not boot again after the apple logo has appeard apple script is displayed on the screen contain what i think is boot script failing to run. I have been able to boot the system in safe mode. does anyone have and solution for this as i realy don't want to reinstall the OS
    Thanks

    The most common cause for "Won't boot after software Update" is Directory Damage that existed before the Update, but was made worse by adding files during the Update.
    The most common cure for that Directory Damage problem is to boot in Safe Mode, which takes five minutes to repair the disk, then comes up demanding your username and password, even if you normally auto-login.
    Rarely, third-party add-ons are made obsolete by an update. In this case, booting in Safe Mode (with few Apple extensions and NO third-party extensions loaded) works fine, even if normal mode does not work.
    Have you tried normal mode again after your Safe Boot?

  • Mac Mini won't boot after failed XP installation

    Recently upgrade HD to 320GB 7200 rpm and 3GB ram. Running 10.5.8 fine.
    I tried to install Windows XP through Boot Camp, but wasn't successful, I terminated the installation. Then Mac Mini won't boot up. When powered on, you heard the chime, then grey screen showed and stayed. Tried starting with "C" (boot from CD), "OPT" (boot option), "T" (target), and reset PRAM. None of them worked.
    What should I try next?
    Thanks
    Message was edited by: Yijian Cao

    If you install XP on Bootcamp, your startup disc will be changed to XP Windows partitioned you did. To restore your startup disc back to Mac OS, make sure your Mac is turned off. 1. Plug the power back and press the power button ON. When you hear the power On sound, press and hold the ALT key on your keyboard until you see the hardrives. 2. Select the HD that says MAc OS, then your mac will boot back to Mac OS.
    Let me know if you have more problems, maybe I can help.
    Abel

  • Mac Pro won't boot after forced shutdown

    Hi all, hopefully someone will be able to help with this.
    This is a Mac Pro (don't have the exact spec right now, but will have later, I think it's a dual), which is used to run ProTools. It has no internet or network connections.
    It's running OS X 10.5.8 and has been for quite a while with no problems. Nothing new has been installed recently (hardware or software).
    The other night it was playing back a ProTools session and recording a mix of the result when it started behaving strangely. When ProTools is recording, it creates a waveform display of the recording as it goes, and this suddenly started being corrupted by what appeared to be bits of a photograph or video image. The owner tried to hit "Stop", but nothing would work. Mouse still moved, but no button response, keyboard shortcuts ineffective, and Force Quit did nothing, so in the end he had to kill it by holding down the power button.
    Since then it won't boot normally, though it will boot into Safe Mode with no problem.
    On a "normal" startup, it powers up, goes through the grey screen/Apple logo/spinning thing stage on the left monitor, then that one goes blue, then both monitors go blue for a few seconds and finally both screens go black, with a mouse pointer in the top left of the left screen. You can move the mouse all over both screens (though if you wait a few seconds it leaves a copy of the pointer in the top left), but that's as far as it gets. Disk activity continues for a while (maybe a minute or so) after the screens go to black, and the spinning rainbow thing comes and goes, but it then seems to give up.
    Here's what I've tried so far:
    Boot into Safe Mode - no problem
    Verify disk using Disk Utility - no problem
    Repair permissions - loads of screwed up stuff, all with "permission should be ?-----" . Repair didn't work. Finally fixed these by running the 10.5.8 combo updater twice (known issue with this updater), then repairing again. Permissions now come up clean.
    Cleared all caches etc. using Cocktail - slight improvement. Before this it was sticking on the one blue screen stage.
    Got rid of a few corrupt preference files using Cocktail (all last modified years ago) - no difference.
    Reset PRAM and MBC - no difference
    Tried booting with everything disconnected except one screen, keyboard and mouse - no difference.
    I'm going over later to see if reseating cards/removing memory etc. will make any difference, and to see if it will fire up fom it's original 10.4.? CD.
    Beyond that, I'm kind of out of ideas, so I figured I'd see if anyone else had any!
    Below is (what I think!) is the relevant bit of the log file, showing a failed boot, forced power off and reboot intoSafe Mode.
    Any clues to corrupt files etc. in there?
    Brian
    Jan 17 19:19:07 *****-****-computer com.apple.SystemStarter[16]: kextload: extension /System/Library/Extensions/DigiIO.kext appears to be loadable
    Jan 17 19:19:07 *****-****-computer com.apple.SystemStarter[16]: kextload: loading extension /System/Library/Extensions/DigiIO.kext
    Jan 17 19:19:07 *****-****-computer com.apple.SystemStarter[16]: kextload: extension /System/Library/Extensions/DigiIO.kext is already loaded
    Jan 17 19:19:07 *****-****-computer com.apple.SystemStarter[16]: kextload: extension /System/Library/Extensions/DigiDal.kext appears to be loadable
    Jan 17 19:19:07 *****-****-computer com.apple.SystemStarter[16]: kextload: loading extension /System/Library/Extensions/DigiDal.kext
    Jan 17 19:19:07 *****-****-computer com.apple.SystemStarter[16]: kextload: extension /System/Library/Extensions/DigiDal.kext is already loaded
    Jan 17 19:19:30 localhost kernel[0]: npvhash=4095
    Jan 17 19:19:28 localhost com.apple.launchctl.System[2]: BootCacheControl: could not open /var/db/BootCache.playlist: No such file or directory
    Jan 17 19:19:28 localhost com.apple.launchctl.System[2]: BootCacheControl: could not unlink playlist /var/db/BootCache.playlist: Unknown error: -1
    Jan 17 19:19:29 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
    Jan 17 19:19:29 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
    Jan 17 19:19:29 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
    Jan 17 19:19:29 localhost com.apple.launchd[1] (org.x.privileged_startx): Unknown key for boolean: EnableTransactions
    Jan 17 19:19:30 localhost kextd[10]: 439 cached, 0 uncached personalities to catalog
    Jan 17 19:19:30 localhost kernel[0]: hi mem tramps at 0xffe00000
    Jan 17 19:19:30 localhost kernel[0]: PAE enabled
    Jan 17 19:19:30 localhost kernel[0]: 64 bit mode enabled
    Jan 17 19:19:30 localhost kernel[0]: Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
    Jan 17 19:19:30 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Jan 17 19:19:30 localhost kernel[0]: vm_page_bootstrap: 714269 free pages and 72163 wired pages
    Jan 17 19:19:30 localhost kernel[0]: mig_table_max_displ = 79
    Jan 17 19:19:30 localhost kernel[0]: Error: Couldn't read XML property list for multikext archive entry 115.
    Jan 17 19:19:30 localhost kernel[0]: XML parse error: OSUnserializeXML: syntax error near line 1
    Jan 17 19:19:30 localhost kernel[0]: .
    Jan 17 19:19:30 localhost kernel[0]: Extension "com.apple.driver.AppleACPIPlatform" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:19:30 localhost kernel[0]: Extension "com.apple.driver.AppleIntelCPUPowerManagement" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=2 LocalApicId=6 Enabled
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=3 LocalApicId=7 Enabled
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=4 LocalApicId=0 Disabled
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=5 LocalApicId=0 Disabled
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=6 LocalApicId=0 Disabled
    Jan 17 19:19:30 localhost kernel[0]: AppleACPICPU: ProcessorApicId=7 LocalApicId=0 Disabled
    Jan 17 19:19:30 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
    Jan 17 19:19:30 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
    Jan 17 19:19:30 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
    Jan 17 19:19:30 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
    Jan 17 19:19:30 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
    Jan 17 19:19:30 localhost kernel[0]: calling mpo_policy_init for mb
    Jan 17 19:19:30 localhost kernel[0]: Seatbelt MACF policy initialized
    Jan 17 19:19:30 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
    Jan 17 19:19:30 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Jan 17 19:19:31 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Jan 17 19:19:31 localhost kernel[0]: MAC Framework successfully initialized
    Jan 17 19:19:31 localhost kernel[0]: using 15728 buffer headers and 4096 cluster IO buffer headers
    Jan 17 19:19:31 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
    Jan 17 19:19:31 localhost kernel[0]: Extension "com.apple.driver.AppleACPIPlatform" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:19:31 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
    Jan 17 19:19:31 localhost kernel[0]: Extension "com.apple.driver.AppleACPIPlatform" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:19:31 localhost kernel[0]: Extension "com.apple.driver.AppleACPIPlatform" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.AppleIntelCPUPowerManagement: Enabling legacy HPET check
    Jan 17 19:19:31 localhost kernel[0]: mbinit: done
    Jan 17 19:19:31 localhost kernel[0]: Security auditing service present
    Jan 17 19:19:31 localhost kernel[0]: BSM auditing present
    Jan 17 19:19:31 localhost kernel[0]: rooting via boot-uuid from /chosen: A3A529FC-62F4-3CBC-91C6-E6C6DC1F954B
    Jan 17 19:19:31 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Jan 17 19:19:31 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 0019e3fffe92f662; max speed s800.
    Jan 17 19:19:31 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0 @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/ST3250820AS P Media/IOGUIDPartitionScheme/Customer@2
    Jan 17 19:19:31 localhost kernel[0]: BSD root: disk0s2, major 14, minor 5
    Jan 17 19:19:31 localhost kernel[0]: Jettisoning kernel linker.
    Jan 17 19:19:31 localhost kernel[0]: Resetting IOCatalogue.
    Jan 17 19:19:31 localhost kernel[0]: PXS1: family specific matching fails
    Jan 17 19:19:31 localhost kernel[0]: Matching service count = 2
    Jan 17 19:19:31 localhost kernel[0]: Matching service count = 3
    Jan 17 19:19:31: --- last message repeated 4 times ---
    Jan 17 19:19:31 localhost kernel[0]: Matching service count = 4
    Jan 17 19:19:31 localhost kernel[0]: MacPro1,1: stalling for module
    Jan 17 19:19:31 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
    Jan 17 19:19:32 localhost kernel[0]: Matching service count = 1
    Jan 17 19:19:32 localhost kernel[0]: AppleTyMCEDriver::probe(MacPro1,1)
    Jan 17 19:19:32 localhost kernel[0]: AppleTyMCEDriver::probe fails
    Jan 17 19:19:32 localhost kernel[0]: Previous Shutdown Cause: 3
    Jan 17 19:19:33 localhost kernel[0]: Probing MOTU Driver
    Jan 17 19:19:33 localhost kernel[0]: IOKit version is "Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386"
    Jan 17 19:19:33 localhost kernel[0]: uhcim Not using bug fix
    Jan 17 19:19:33 localhost kernel[0]: GetDevInfoForSubclass interfacesubclass 0 forUHCI 0
    Jan 17 19:19:34 localhost kernel[0]: NVDANV40HAL loaded and registered.
    Jan 17 19:19:34 localhost kernel[0]: PXS1: family specific matching fails
    Jan 17 19:19:34: --- last message repeated 3 times ---
    Jan 17 19:19:34 localhost kernel[0]: Matching service count = 0
    Jan 17 19:19:35 localhost bootlog[65]: BOOT_TIME: 1326824366 0
    Jan 17 19:19:36 localhost rpc.statd[47]: statd.notify - no notifications needed
    Jan 17 19:19:37 localhost fseventsd[56]: bumping event counter to: 0x28c7 (current 0x0) from log file '0000000000000665'
    Jan 17 19:19:39 localhost DirectoryService[61]: Launched version 5.7 (v514.25)
    Jan 17 19:19:42 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[52]: Login Window Application Started -- Threaded auth
    Jan 17 19:19:44 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:09:62:9c
    Jan 17 19:19:44 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:09:62:9d
    Jan 17 19:19:45 localhost com.paceap.pacesupport[68]: kextload: /System/Library/Extensions/PACESupportFamily.kext/Contents/PlugIns/PACESupportL eopard.kext loaded successfully
    Jan 17 19:19:49 localhost kernel[0]: Ethernet [Intel8254X]: Link down on en0 called by enableHardware() -- 
    Jan 17 19:19:49 localhost mDNSResponder mDNSResponder-176.3 (Jun 17 2009 18:57:49)[51]: starting
    Jan 17 19:19:50 localhost /usr/sbin/ocspd[94]: starting
    Jan 17 19:19:52 localhost kextd[10]: writing kernel link data to /var/run/mach.sym
    Jan 17 19:19:54 localhost kernel[0]: Ethernet [Intel8254X]: Link down on en1 called by enableHardware() -- 
    Jan 17 19:19:54 *****-****-computer configd[63]: setting hostname to "*****-****-computer.local"
    Jan 17 19:19:56 *****-****-computer org.ntp.ntpd[42]: Error : nodename nor servname provided, or not known
    Jan 17 19:19:56 *****-****-computer ntpdate[106]: can't find host time.euro.apple.com
    Jan 17 19:19:56 *****-****-computer ntpdate[106]: no servers can be used, exiting
    Jan 17 19:19:56 *****-****-computer com.apple.SystemStarter[45]: PACESupport - launchd already started us
    Jan 17 19:19:56 *****-****-computer com.apple.SystemStarter[45]: kextload: extension /System/Library/Extensions/DigiIO.kext appears to be loadable
    Jan 17 19:19:56 *****-****-computer com.apple.SystemStarter[45]: kextload: loading extension /System/Library/Extensions/DigiIO.kext
    Jan 17 19:19:56 *****-****-computer com.apple.SystemStarter[45]: kextload: extension /System/Library/Extensions/DigiIO.kext is already loaded
    Jan 17 19:19:57 *****-****-computer com.apple.SystemStarter[45]: kextload: extension /System/Library/Extensions/DigiDal.kext appears to be loadable
    Jan 17 19:19:57 *****-****-computer com.apple.SystemStarter[45]: kextload: loading extension /System/Library/Extensions/DigiDal.kext
    Jan 17 19:19:57 *****-****-computer com.apple.SystemStarter[45]: kextload: extension /System/Library/Extensions/DigiDal.kext is already loaded
    Jan 17 19:19:59 *****-****-computer kernel[0]: NVDA(OpenGL): Channel exception!  status = 0xffff info32 = 0x2 = Fifo: SW Method Error
    Jan 17 19:19:59 *****-****-computer kernel[0]: 0000000b
    Jan 17 19:19:59 *****-****-computer kernel[0]: NVDA(OpenGL): Channel exception!  status = 0xffff info32 = 0x2 = Fifo: SW Method Error
    Jan 17 19:19:59 *****-****-computer kernel[0]: 0000000b
    Jan 17 19:19:59 *****-****-computer kernel[0]: NVDA(OpenGL): Channel exception!  status = 0xffff info32 = 0x2 = Fifo: SW Method Error
    Jan 17 19:19:59 *****-****-computer kernel[0]: 0000000b
    Jan 17 19:20:01 *****-****-computer kernel[0]: NVDA(OpenGL): Channel exception!  status = 0xffff info32 = 0x2 = Fifo: SW Method Error
    Jan 17 19:20:01 *****-****-computer kernel[0]: 0000000b
    Jan 17 19:20:01 *****-****-computer kernel[0]: NVDA(OpenGL): Channel exception!  status = 0xffff info32 = 0x2 = Fifo: SW Method Error
    Jan 17 19:20:01 *****-****-computer kernel[0]: 0000000b
    Jan 17 19:20:01 *****-****-computer kernel[0]: NVDA(OpenGL): Channel exception!  status = 0xffff info32 = 0x2 = Fifo: SW Method Error
    Jan 17 19:20:01 *****-****-computer kernel[0]: 0000000b
    Jan 17 19:20:01 *****-****-computer kernel[0]: NVDA(OpenGL): Channel exception!  status = 0xffff info32 = 0x2 = Fifo: SW Method Error
    Jan 17 19:20:01 *****-****-computer kernel[0]: 0000000b
    Jan 17 19:20:09 *****-****-computer loginwindow[52]: Login Window Started Security Agent
    Jan 17 19:20:15 *****-****-computer com.apple.launchd[1] ([0x0-0x5005].com.dantz.RetroRunSL[123]): Stray process with PGID equal to this dead job: PID 125 PPID 1 RetroRunSL
    Jan 17 19:23:49 *****-****-computer com.apple.firmwaresyncd[57]: kextload: /System/Library/Extensions/msdosfs.kext loaded successfully
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** /dev/rdisk1s2
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Root file system
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking Journaled HFS Plus volume.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking Extents Overflow file.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking Catalog file.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking multi-linked files.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking Catalog hierarchy.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking Extended Attributes file.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking volume bitmap.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** Checking volume information.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ** The volume Macintosh HD appears to be OK.
    Jan 17 19:28:18 localhost com.apple.launchctl.System[2]: ***** FILE SYSTEM WAS MODIFIED *****
    Jan 17 19:28:20 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
    Jan 17 19:28:20 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
    Jan 17 19:28:20 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
    Jan 17 19:28:20 localhost com.apple.launchd[1] (org.x.privileged_startx): Unknown key for boolean: EnableTransactions
    Jan 17 19:28:21 localhost kernel[0]: npvhash=4095
    Jan 17 19:28:20 localhost kextd[9]: safe boot detected
    Jan 17 19:28:21 localhost kernel[0]: hi mem tramps at 0xffe00000
    Jan 17 19:28:20 localhost kextd[9]: safe boot; invalidating extensions caches
    Jan 17 19:28:21 localhost kernel[0]: PAE enabled
    Jan 17 19:28:21 localhost kernel[0]: 64 bit mode enabled
    Jan 17 19:28:21 localhost kernel[0]: Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
    Jan 17 19:28:21 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Jan 17 19:28:21 localhost kernel[0]: vm_page_bootstrap: 508650 free pages and 277782 wired pages
    Jan 17 19:28:21 localhost kernel[0]: mig_table_max_displ = 79
    Jan 17 19:28:21 localhost kernel[0]: Extension "com.apple.driver.AppleACPIPlatform" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:28:21 localhost kernel[0]: Extension "com.apple.driver.AppleIntelCPUPowerManagement" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=2 LocalApicId=6 Enabled
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=3 LocalApicId=7 Enabled
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=4 LocalApicId=0 Disabled
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=5 LocalApicId=0 Disabled
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=6 LocalApicId=0 Disabled
    Jan 17 19:28:21 localhost kernel[0]: AppleACPICPU: ProcessorApicId=7 LocalApicId=0 Disabled
    Jan 17 19:28:21 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
    Jan 17 19:28:21 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
    Jan 17 19:28:21 localhost kernel[0]: calling mpo_policy_init for mb
    Jan 17 19:28:21 localhost kernel[0]: Seatbelt MACF policy initialized
    Jan 17 19:28:21 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
    Jan 17 19:28:21 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
    Jan 17 19:28:21 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
    Jan 17 19:28:21 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
    Jan 17 19:28:21 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Jan 17 19:28:21 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Jan 17 19:28:21 localhost kernel[0]: MAC Framework successfully initialized
    Jan 17 19:28:21 localhost kernel[0]: using 15728 buffer headers and 4096 cluster IO buffer headers
    Jan 17 19:28:21 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
    Jan 17 19:28:21 localhost kernel[0]: Extension "com.apple.driver.AppleACPIPlatform" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:28:21 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
    Jan 17 19:28:21 localhost kernel[0]: Extension "com.apple.driver.AppleACPIPlatform" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
    Jan 17 19:28:21: --- last message repeated 1 time ---
    Jan 17 19:28:21 localhost kernel[0]: AppleIntelCPUPowerManagement: Enabling legacy HPET check
    Jan 17 19:28:21 localhost kernel[0]: mbinit: done
    Jan 17 19:28:21 localhost kernel[0]: Security auditing service present
    Jan 17 19:28:21 localhost kernel[0]: BSM auditing present
    Jan 17 19:28:21 localhost kernel[0]: rooting via boot-uuid from /chosen: A3A529FC-62F4-3CBC-91C6-E6C6DC1F954B
    Jan 17 19:28:21 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Jan 17 19:28:21 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 0019e3fffe92f662; max speed s800.
    Jan 17 19:28:21 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0 @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/ST3250820AS P Media/IOGUIDPartitionScheme/Customer@2
    Jan 17 19:28:21 localhost kernel[0]: BSD root: disk1s2, major 14, minor 5
    Jan 17 19:28:21 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 23181312 to: 122368 (joffset 0x746000)
    Jan 17 19:28:21 localhost kernel[0]: jnl: unknown-dev: journal replay done.
    Jan 17 19:28:21 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
    Jan 17 19:28:21 localhost kernel[0]: HFS: Removed 4 orphaned unlinked files or directories 
    Jan 17 19:28:21 localhost kernel[0]: Jettisoning kernel linker.
    Jan 17 19:28:26 localhost bootlog[36]: BOOT_TIME: 1326824767 0
    Jan 17 19:28:26 localhost fseventsd[27]: event logs in /.fseventsd out of sync with volume.  destroying old logs. (330 139 558)
    Jan 17 19:28:27 localhost rpc.statd[18]: statd.notify - no notifications needed
    Jan 17 19:28:27 localhost fseventsd[27]: log dir: /.fseventsd getting new uuid: 07B57D5F-5A7E-483F-8FBE-40E8DF7E6E23
    Jan 17 19:28:32 localhost DirectoryService[32]: Launched version 5.7 (v514.25)
    Jan 17 19:28:32 localhost DirectoryService[32]: Improper shutdown detected
    Jan 17 19:28:38 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:09:62:9c
    Jan 17 19:28:38 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:09:62:9d
    Jan 17 19:28:43 localhost kernel[0]: Resetting IOCatalogue.
    Jan 17 19:28:43 localhost kextd[9]: 0 cached, 291 uncached personalities to catalog
    Jan 17 19:28:44 localhost kernel[0]: PXS1: family specific matching fails
    Jan 17 19:28:44 localhost kernel[0]: Matching service count = 2
    Jan 17 19:28:45 localhost kernel[0]: Previous Shutdown Cause: 3
    Jan 17 19:28:45 localhost mDNSResponder mDNSResponder-176.3 (Jun 17 2009 18:57:49)[22]: starting
    Jan 17 19:28:46 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[23]: Login Window Application Started -- Threaded auth
    Jan 17 19:28:50 localhost kernel[0]: NVDANV40HAL loaded and registered.
    Jan 17 19:28:50 localhost kernel[0]: PXS1: family specific matching fails
    Jan 17 19:28:50 localhost kernel[0]: Ethernet [Intel8254X]: Link down on en0 called by enableHardware() -- 
    Jan 17 19:28:52 localhost kernel[0]: PXS1: family specific matching fails
    Jan 17 19:28:52 localhost kernel[0]: Matching service count = 0
    Jan 17 19:28:54 localhost kernel[0]: Ethernet [Intel8254X]: Link down on en1 called by enableHardware() -- 
    Jan 17 19:28:54 *****-****-computer configd[34]: setting hostname to "*****-****-computer.local"
    Jan 17 19:28:56 *****-****-computer org.ntp.ntpd[13]: Error : nodename nor servname provided, or not known
    Jan 17 19:28:56 *****-****-computer ntpdate[68]: can't find host time.euro.apple.com
    Jan 17 19:28:56 *****-****-computer ntpdate[68]: no servers can be used, exiting
    Jan 17 19:28:56 *****-****-computer com.apple.ATSServer[67]: FODBCheck: New annex file created
    Jan 17 19:28:57 *****-****-computer /usr/sbin/ocspd[73]: starting
    Jan 17 19:29:01 *****-****-computer kextd[9]: writing kernel link data to /var/run/mach.sym
    Jan 17 19:29:04 *****-****-computer loginwindow[23]: Login Window Started Security Agent
    Jan 17 19:29:05 *****-****-computer fseventsd[27]: event logs in /Volumes/DATA DRIVE/.fseventsd out of sync with volume. destroying old logs. (63 0 598)
    Jan 17 19:29:05 *****-****-computer fseventsd[27]: log dir: /Volumes/DATA DRIVE/.fseventsd getting new uuid: 0E7FBB62-F55F-413D-970B-FB402543BF2D
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: PACESupport - launchd already started us
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: extension /System/Library/Extensions/DigiIO.kext appears to be loadable
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: loading extension /System/Library/Extensions/DigiIO.kext
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: /System/Library/Extensions/DigiIO.kext loaded successfully
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: sending personalities to kernel:
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:     from extension /System/Library/Extensions/IOStorageFamily.kext:
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOFDiskPartitionScheme
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOMediaBSDClient
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOGUIDPartitionScheme
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOAppleLabelScheme
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOBlockStorageDriver
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOApplePartitionScheme
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:     from extension /System/Library/Extensions/IOPCIFamily.kext:
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOPCI2PCIBridge-Name
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOPCI2PCIBridge-i386
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOPCI2PCIBridge-PCI
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:     from extension /System/Library/Extensions/DigiIO.kext:
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload:         DigiIO
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: sending 10 personalities to the kernel
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: matching started for /System/Library/Extensions/DigiIO.kext
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: extension /System/Library/Extensions/DigiDal.kext appears to be loadable
    Jan 17 19:29:06 *****-****-computer com.apple.SystemStarter[16]: kextload: loading extension /System/Library/Extensions/DigiDal.kext
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload: /System/Library/Extensions/DigiDal.kext loaded successfully
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload: sending personalities to kernel:
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:     from extension /System/Library/Extensions/IOPCIFamily.kext:
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOPCI2PCIBridge-Name
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOPCI2PCIBridge-i386
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         IOPCI2PCIBridge-PCI
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:     from extension /System/Library/Extensions/DigiDal.kext:
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinIIIPLXDevice
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinRev2Farm
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinFarm
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinEngine
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinPCIBridgeDeviceHiNTHB2
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinPCIBridgeDeviceDEC21154
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinIIFarm
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinPCIBridgeDevicePericom8154
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         DigidesignGeneral
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinIIIFarm
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinRev2Engine
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinIIEngine
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinPCIBridgeDevicePLXPCIExpress
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         MotorolaPresto
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinIIPLXDevice
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinPCIBridgeDeviceDEC21154BE
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinPCIBridgeDeviceHiNTHB4
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload:         GershwinIIIEngine
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload: sending 21 personalities to the kernel
    Jan 17 19:29:07 *****-****-computer com.apple.SystemStarter[16]: kextload: matching started for /System/Library/Extensions/DigiDal.kext
    Jan 17 19:29:11 *****-****-computer com.apple.launchd[1] ([0x0-0x4004].com.dantz.RetroRunSL[83]): Stray process with PGID equal to this dead job: PID 95 PPID 1 RetroRunSL
    Jan 17 19:29:37 *****-****-computer com.apple.dyld[10]: update_dyld_shared_cache[10] regenerated cache for arch=i386
    Jan 17 19:31:09 *****-****-computer authorizationhost[82]: MechanismInvoke 0x1d2de70 retainCount 2
    Jan 17 19:31:09 *****-****-computer SecurityAgent[92]: MechanismInvoke 0x5b31950 retainCount 1
    Jan 17 19:31:09 *****-****-computer SecurityAgent[92]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
    Jan 17 19:31:10 *****-****-computer SecurityAgent[92]: MechanismDestroy 0x5b31950 retainCount 1
    Jan 17 19:31:10 *****-****-computer authorizationhost[82]: MechanismDestroy 0x1d2de70 retainCount 2
    Jan 17 19:31:10 *****-****-computer loginwindow[23]: Login Window - Returned from Security Agent
    Jan 17 19:31:10 *****-****-computer loginwindow[23]: USER_PROCESS: 23 console
    Jan 17 19:31:10 *****-****-computer com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[79]): Exited: Terminated
    Jan 17 19:31:10 *****-****-computer com.apple.launchctl.Aqua[110]: launchctl: Please convert the following to launchd: /etc/mach_init_per_user.d/RemoteUI.plist
    Jan 17 19:31:10 *****-****-computer com.apple.launchd[108] (org.x.startx): Unknown key for boolean: EnableTransactions
    Jan 17 19:31:10 *****-****-computer /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer[118]: (-3230) Cannot use ATS Persistent Store - switching to old FODB cache code
    Jan 17 19:31:13 *****-****-computer /System/Library/CoreServices/coreservicesd[43]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(***** ***'s Public Folder) returned -14135
    Jan 17 19:31:18 *****-****-computer /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 22]: CPSGetProcessInfo(): This call is deprecated and should not be called anymore.
    Jan 17 19:31:18 *****-****-computer /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 22]: CPSPBGetProcessInfo(): This call is deprecated and should not be called anymore.
    Jan 17 19:32:21 *****-****-computer Cocktail[129]: Cocktail 4.7 launched.
    Jan 17 19:32:24 *****-****-computer com.apple.FolderActions.enabled[141]: launchctl: Error unloading: com.apple.FolderActions.folders
    Jan 17 19:32:32 *****-****-computer authexec[146]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer Cocktail[129]: ***** *** authenticated.
    Jan 17 19:32:32 *****-****-computer authexec[149]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[151]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[153]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[155]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[157]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[159]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[161]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[163]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[165]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[167]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[169]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[171]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[173]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[175]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[177]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:32 *****-****-computer authexec[179]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:38 *****-****-computer defaults[184]: \nThe domain/default pair of (com.apple.spotlight, DictionaryLookupEnabled) does not exist
    Jan 17 19:32:38 *****-****-computer defaults[185]: \nThe domain/default pair of (com.apple.spotlight, CalculationEnabled) does not exist
    Jan 17 19:32:38 *****-****-computer defaults[186]: \nThe domain/default pair of (com.apple.systempreferences, TMShowUnsupportedNetworkVolumes) does not exist
    Jan 17 19:32:38 *****-****-computer authexec[188]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:38 *****-****-computer authexec[190]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:38 *****-****-computer defaults[190]: \nThe domain/default pair of (/System/Library/LaunchDaemons/com.apple.backupd-attach, Disabled) does not exist
    Jan 17 19:32:38 *****-****-computer defaults[191]: \nThe domain/default pair of (com.apple.TimeMachine, DoNotOfferNewDisksForBackup) does not exist
    Jan 17 19:32:38 *****-****-computer defaults[192]: \nThe domain/default pair of (com.apple.finder, _FXShowBackgroundAnimation) does not exist
    Jan 17 19:32:38 *****-****-computer authexec[194]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:39 *****-****-computer authexec[204]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:39 *****-****-computer defaults[204]: \nThe domain/default pair of (com.apple.loginwindow, StartupDelay) does not exist
    Jan 17 19:32:39 *****-****-computer authexec[206]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:39 *****-****-computer defaults[206]: \nThe domain/default pair of (com.apple.loginwindow, Kiosk) does not exist
    Jan 17 19:32:42 *****-****-computer defaults[207]: \nThe domain/default pair of (com.apple.desktopservices, DSDontWriteNetworkStores) does not exist
    Jan 17 19:32:47 *****-****-computer authexec[213]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:32:48 *****-****-computer authexec[215]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:44:05 *****-****-computer Cocktail[129]: System log (/private/var/log/system.log) has been saved to /Users/********/Library/Logs/System LOg 2.log.
    Jan 17 19:44:45 *****-****-computer fseventsd[27]: log dir: /Volumes/NO NAME/.fseventsd getting new uuid: 2DADE658-7648-47A4-A16F-8B77B56B575C
    Jan 17 19:46:33 *****-****-computer Cocktail[246]: Cocktail 4.7 launched.
    Jan 17 19:46:34 *****-****-computer [0x0-0x1b01b].com.apple.systemevents[254]: com.apple.FolderActions.enabled: Already loaded
    Jan 17 19:46:36 *****-****-computer authexec[257]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:36 *****-****-computer Cocktail[246]: ***** *** authenticated.
    Jan 17 19:46:36 *****-****-computer authexec[260]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:36 *****-****-computer authexec[262]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:36 *****-****-computer authexec[264]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:36 *****-****-computer authexec[266]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:36 *****-****-computer authexec[268]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:36 *****-****-computer authexec[270]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:36 *****-****-computer authexec[272]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[274]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[276]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[278]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[280]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[282]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[284]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[286]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[288]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:37 *****-****-computer authexec[290]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:39 *****-****-computer defaults[292]: \nThe domain/default pair of (com.apple.desktopservices, DSDontWriteNetworkStores) does not exist
    Jan 17 19:46:44 *****-****-computer authexec[298]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
    Jan 17 19:46:44 *****-****-computer authexec[300]: executing /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid

    Hi,
    Yes, I did resolve it - it was the graphics card. Changed that, updated OS X and it was done.
    I can't now remember exactly which card I used, and I'm away at the moment so I can't get to the infomation, but I do remember that it was a full length card with a large heatsink, and was a bit of a pig to squeeze into the chassis!
    Had to buy an adaptor for the second monitor connection, but that didn't cause any hassle. I got the card and cable from the local Apple Store.
    It also theoretically needed a later version of OS X than was already there, but since it allowed me to boot off the CD, that didn't matter (and it worked with the old one anyway, as it turned out).
    Oh, and also of course, although it's a bog standard PC card, you have to pay way over the odds for it because it has to have different PROMS for a Mac. (Thank you Apple.)  Just part of the price we all have to pay for using Macs.
    I seem to remember that there was a certain amount of dancing involved in upgrading the OS afterwards (might have had to do one step twice), but nothing that unusual.
    Hope this helps,
    All the best,
    Brian

  • Mac mini won't boot after latest update Maverick

    My Mac mini running Maverick after an automatic update won't boot. " no bootable device -- insert boot disk and press any key"
    What option do I have here?

    Reinstall Mountain Lion or Mavericks
    OS X Mavericks- Reinstall OS X
    OS X Mountain Lion- Reinstall OS X
         Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is
                    three times faster than wireless.

  • Early 2008 Mac Pro won't boot after installing 2nd DVD drive

    All,
    I purchased a Pioneer DVR-117D from Mac Sales and after installing it in my new refurbished 2008 Mac Pro it won't boot. My MP will boot if I remove the drive. According to the Mac Sales website this drive should work fine in my MP. Any ideas as to why this is happening. I literally just got my MP today and installed the drive. Is it the drive or the Mac Pro. Thank you all.

    The drive was set to master, I switched it to CS before I left for work but haven't tried reinstalling it. I will try when I get back and let you know if it worked. Thank you again.

  • Mac G5 won't boot after updating

    I am having issues with a PPC Mac G5 not booting after trying to install updates. The computer is my sons PPC G5. It had not been updated in a while so I selected the "software update" which appeared to progress succefully. I believe that the s/w level was a version 10.5.x. It never came back from the reboot. I'm more familiar with the older Macs (v 7/8/9) so I'm having to dig a bit here. I tried to start in safe mode and even in single user mode but no help.
    The symptoms are that the computer plays the startup chime and then eventually shows an icon of a folder with the opposing faces in it. THat goes away leaving a grey screen and the fan goes to high setting. No change from there.
    I have also started it in the mode to see which disks are available and the HD icon appears but has a circle with an X in it at the lower side of the icon. It almost seams like the OS got corrupted.
    Here's my real problem. Since it was my sons computer and came with the OS pre-loaded, I do not have the original software or a boot disk or other bootable tools. Any thoughts would be appreciated. Undo button or restore feature?
    Thanks in advance for the knowledge and help.

    An install disc would really help. Besides eBay & such, You have to call Apple & ask for a Product Specialist to get it, if they still have it.
    Other than that, your best bet is DiskWarrior, you need the CD though.
    http://www.alsoft.com/DiskWarrior/
    But others that may work…
    Drive Genius 2…
    http://www.prosofteng.com/products/drive_genius.php
    TechTool Pro 4…
    http://www.micromat.com/index.php?option=com_content&task=view&id=31&Itemid=83
    BTW, you might enjoy this DiskWarrior review/recommendation...
    http://discussions.apple.com/thread.jspa?messageID=9645801&#9645801

  • Screen Dims at start up after 2007-009 1.1 Update

    My macbook pro has started booting up in the lowest brightness setting after the 2007-009 1.1 security update... Anybody else having a similar problem?? Any methods of fixing it??

    That is OFTEN caused by a Windows DLL change that renders your graphics adapter driver out of date
    •What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    •What is your exact graphics adapter driver version?
    •Have you gone to the vendor web site to check for a newer driver?
    •For Windows, do NOT rely on Windows Update to have current driver information
    •-you need to go direct to the vendor web site and check updates for yourself
    •ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    •nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
    ALSO
    Dual video problems - Do you have dual graphics adapters?
    Go to the Windows Control Panel and select Hardware and Sound and then select Device Manager... In Device manager you click the + sign to the left of Display Adapters... and see if 2 are listed
    IF YES, read below
    -http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
    -http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
    -link to why http://forums.adobe.com/message/4685328
    -http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2

  • MSI X99S XPOWER won't boot after a Windows 8.1 Update

    Hi all, two days ago I was using my PC as normally and Windows needed to restart because of an update from Windows Update. It restarted and won't be able to boot again. I get a 04 debug code (Power on South Bridge Initialization) and I've tried clearing CMOS, without SSD/HDD... and there is no way.
    I'm reading something about an Intel drivers update that can modify the firmware, do you know anything about it?
    Board: MSI X99S XPOWER
    Bios: Version 1.4
    VGA:   MATRIX GTX 780Ti
    PSU:   Enermax Platimax 850W
    Intel Core i7 5820K
    MEM: G.Skill 32GB in 4 sticks (8 GB each) @2400 MHz XMP
    HDD: OCZ Vertex 450 256GB
    COOLER: Akasa Venom Vodoo
    OC: 4 GHz 1.15v
    OS: Windows 8.1 x64
    Thanks

    Windows is not corrupted, I've tried that SSD on another computer without problems and in my computer without HDD/SSD and won't boot anyway.
    If I'm able to boot with the secondary BIOS, I'll recover the first one by the following steps:
    Quote
    BIOS recovery with AFUDOS command
    When BIOS updating fails or causes the computer non-bootable, you can recover the
    failed BIOS by the steps below.
    Preparation:
    1. Prepare a bootable USB flash drive.
    2. Download the latest BIOS file from the MSI official website at www.msi.com, and
    then decompress the file.
    3. Copy the AFUDE238.exe and the BIOS file to the bootable USB flash drive
    BIOS recovery steps:
    1. Power off the computer.
    2. Set the Multi-BIOS switch to the functional BIOS ROM.
    3. Insert the bootable USB flash drive you have made to the USB port.
    4. Boot the computer into the bootable USB flash drive.
    5. Set the Multi-BIOS switch to the failed BIOS ROM.
    6. Execute the below command to flash the BIOS:
    For example: AFUDE238 EXXXXIMS.XXX
    7. Restart the computer after the BIOS flashing is complete.
    Important
    Do not use the Multi-BIOS switch when system is booting up.
    But I have a doubt with the "Important" note because I need to change from safe BIOS to failed BIOS with the PC booted, right? So I'll use the Multi-BIOS switch with the system up...
    Thanks a lot

Maybe you are looking for

  • Using dbms_lob in trigger 10gR2

    Hello, I'm trying to read from a clob using dbms_lob in my trigger and assigning the value to a variable. My trigger is compiling fine, but it doesn't seem to be working. I'm using 10gR2. Am I misunderstanding how to read from/assign to a variable in

  • To Do Lists not included in iCal??!!

    Am I missing something or are To Do lists not included in the iPhone version of iCal? If that is true why is this so? I will be including this on another list of things I don't understand about the software implementation in iPhone (no way to back up

  • Photosmart 8050 and 'Out of Paper' Error

    I own a Photosmart 8050 photo printer.  I have had it for a little while now and i only print on it every so often when I need to print pictures or other color documents.  I use my laser jet printer for printing most of my documents.  I've had no pro

  • Garage Band shuts down unexpectedly

    Whenever I try and open it, it tells me the application GarageBand quit unexpectedly. Anyone encounter the same problem?

  • Lenovo Z570 Mother Board

    Hi my laptop was not turning on and was told to replace the motherboard. Where can I get OEM part of my laptop in India? My laptop specifications are  Intel i3 2310 2.10Ghz 4 GB RAM 750 GB Hard Drive Please advice at the earliest.