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

Similar Messages

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 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

MSI X99S MPOWER won't boot (Debug 00) after installing Transcend 256 M.2 SSD

Hey all, as the subject suggests I bought a new MSI X99S Mpower mobo. I put together a new system with it without any problems using my old SSD. I received a new M.2 SSD (Transcend 256 GB) once I installed it the system would no longer boot. I removed the M.2 SSD and the unit will now still not boot. I power on and the LED just displays 00.

what bios version you are using?
can you list the exact M.2 SSD (Transcend 256 GB) mode/part number?

Early 2008 MacBook Pro won't boot after Lion 10.7.1 update

My 2.4 GHz 4GB RAM Early 2008 MacBook Pro wont boot after downloaded the Lion 10.7.1 upate. Upon restarting the screen went dead and now the system does not boot, as if the bootloader has been wiped out. Screen appears dead but was known to be working before hand. The hard drive spins up but doesn't sound like it is searching for data.
Can anyone help me?

Okay, I tried everything I can think of last night. I removed every startup process and every tool or programm that goes deeper into the system (GlimmerBlocker, LittleSnitch, Parallels). Cleaned Up every Cache I could find and refreshed every necessary Cache or Database possible. Took me a couple of hours. But still no luck - the machine doesn't boot, just in safe mode. Right now I copy all my personal stuff to a new external harddrive because TimeMachine doesn't work, after this I will do a clean install of Lion.
It's not hardware related, it's the 10.7.1 update that doesn't work properly. By the way, the only errors remaining are:
WindowServer - kCGErrorFailure
ManagedClient - kCGErrorFailure: CGSPackageGetWorkspaceType: couldn't get workspace type
SecurityAgent - kCGErrorFailure: CGSPackageGetWorkspaceType: couldn't get workspace type
and a lot of:
com.Apple.SecurityAgent.00000000-0000-0000-0000-0000000186A7: CoreAnimation: rendering error 506
that's also the last one I get before the system hangs…

MOVED: MSI X99S MPOWER won't boot (Debug 00) after installing Transcend 256 M.2 SSD

This topic has been moved to MSI Intel boards.
https://forum-en.msi.com/index.php?topic=254774.0

what bios version you are using?
can you list the exact M.2 SSD (Transcend 256 GB) mode/part number?

MacBook won't boot after OS 10.5.5 update

I updated OS to 10.5.5. Now the computer will not boot. Get grey screen with spinning wheel. Tried Utility disk repair, hard disk had no problems but could not repair permissions -- spinning ball was continuous.
Used DVD 10.5 and tried an archive and install but that did not work. Message received was 4 minutes left to completion, but the completion never came. The ball was spinning all night and still did not complete the installation.
Would appreciate advice as to how to resolve this.
gripko

I tried an archive and install again and this time it worked. However, I now find I can't use Bluetooth to send files between my MacBook and iMAC. My MacBook OS after the archive and install is 10.5.1. I've gone through the pairing process and the two computers are paired and connected. However, when I try to send a file from my iMAC to my MacBook I get a message saying that "the device does not have the necessary services".
What does that mean?
gripko

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]

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.

IMac G4 won't boot after install of iTunes latest update

I just updated my iTunes software via download. I have the iMac configured to ID when new updates are available. After download I selected the "restart" option. Computer shut off and upon power up will not proceed past blue start up screen with the progress bar and "starting MAC OSX...." text. I have tried power down/power up. It has been at least an hour and still on blue screen. I have never had a problem in 5 years. Any ideas?

Hi Dean, and a warm welcome to the forums!
Unbeknownst to you, you had problems on your HD before the update.
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot.
The usual reason why updates fail or mess things up, is if Permissions are not fixed before & after every update, with a reboot... you may get a partial update when the installer finds it doesn't have Permissions to change one obscure little part of the OS, leaving you with a mix of OS versions.
Some people get away without Repairing Permissions for years, some for only days.
If Permissions are wrong before applying an update, you could get mixed OS versions, if Directory is the slightest messed up, who knows!
If many Permission are repaired, or any Directory errors are found, you may need to re-apply some the latest/biggest updates again, or even do an A&I if you have enough free disk space.
An Archive & Install, which gives you a new OS, but can preserve all your files, pics, music, settings, etc...
http://docs.info.apple.com/article.html?artnum=107120

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]

Won't boot after using windows Bios flash utility

I used the windows bios flash utility i found on the toshiba website for this sat a135-s2386, all looked good until reboot, now just a white screen.

Attitude is not going to get you far.
Let's try a proper system reset, and see if this helps bring the unit back. Power off your system, unplug everything including the AC, remove the battery, press and hold down the power on button for 30 seconds, replace battery and AC, power on, if you see the Toshiba logo press the 'F2' key to enter BIOS Setup, in setup press 'F9' to load setup defaults, press 'F10' to save and exit, then try to boot into Windows.
Please let us know what happens. Good luck.
Mike

Won't boot after resizing Windows partition

So I'm dual-booting Windows 7 with OSX using Boot Camp. The Windows partition had very little space left so I decided to go ahead and resize it. I first used Disk Utility inside OSX to shrink the size of the OSX partition. Worked like a beauty.
I then went into Windows and resized the Windows partition using Paragon's Partition Manager....big mistake.
I would gander a guess that in order to resize, the Paragon software has to reboot and boot into a partition it created. Which is all fine and good except I don't think (version 2010 of Partition Manager) the Mac bootup hardware likes this. Unfortunately, this seemed to have nuked my bootup of anything, including OSX.
Is there a way to recover/repair this without having to do wipe everything and reinstall?

Welcome to Apple Discussions,
You can boot to the Mac OS Install disk that came with the computer and run Disk Utility from from the disk to attempt to repair the Mac OS partition of the logical drive. If it can repair it then you may be able to boot.
Live partitioning is like doing open heart surgery on yourself. Its not a simple process. Doing it with a utility that isn't necessarily made for handling an HFS+ partition table (Like what the Mac OS uses) is tricker still.
Give Disk Utility a try. There are other directory repair programs out there (Drive Genius, Disk Warrior, etc.) that can do deeper levels of repair.
Were it my drive, I would probably just erase it and restore from backup (assuming you have all your data backed up and are confident that the backup is good). You don't want to keep working with a potentially damaged partition table. But thats just me.
Hope that helps.

Mac Pro early 2009 won't boot after running 1.8.2 update

It even does not get into recovery mode. A grey screen with dots appear.

Hold down the Option key at Startup. This invokes the Startup Manager, whose code is all in ROM. It will then draw an Icon for each potentially bootable drive.
If there are defects on the screen during this process, you probably have a Hardware problem.

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.

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

Similar Messages

Maybe you are looking for