Mac mini restarts on its own after shut-down.
The Mac mini will restart by itself about 10 minutes after shut down. I turned off all the restart options in energy saver. Funning 10.4.8 with the latest firmware instalation.
Any suggestions how to stop this?
I have had this problem for a looooong time and I think I finally resolved it. Last weekend I was trying a demo of MacPilot 3 and found Elgato's EyeTV had two items in the Power > Events list. Apparently when you set EyeTV to start up the computer for it's schedule it restarts the computer randomly rather in a reasonable amount of time before the recording begins. Since there were two files, I think 1 was left over from previous EyeTV version and was starting up the computer even though I told EyeTV not to start the computer at a later date. Deleting both files seems to be the solution.
Similar Messages
-
Why does my new Mac Mini restart on its own?
Why does my new Mac Mini restart on its own?
At diffrent times of the day or time.
Thanks.The warranty entitles you to complimentary phone support for the first 90 days of ownership.
If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies. -
after downloading ios 8 on my i pad air 16 GB, my i pad keeps on restarting on its own after some time? any idea how can it be rectified?
Please tell me that it has NEVER been jailbroke. If it has not been jailbroke, here are some standard repair procedures:
First, try a system reset. It cures many ills and it's quick, easy and harmless...
Hold down the on/off switch and the Home button simultaneously until you see the Apple logo. Ignore the "Slide to power off" text if it appears. You will not lose any apps, data, music, movies, settings, etc.
If the Reset doesn't work, try a Restore. Note that it's nowhere near as quick as a Reset. It could take well over an hour! Connect via cable to the computer that you use for sync. From iTunes, select the iPad/iPod and then select the Summary tab. Follow the on-screen directions for Restore and be sure to say "yes" to the backup. You will be warned that all data (apps, music, movies, etc.) will be erased but, as the Restore finishes, you will be asked if you wish the contents of the backup to be copied to the iPad/iPod. Again, say "yes."
At the end of the basic Restore, you will be asked if you wish to sync the iPad/iPod. As before, say "yes." Note that that sync selection will disappear and the Restore will end if you do not respond within a reasonable time. If that happens, only the apps that are part of the IOS will appear on your device. Corrective action is simple - choose manual "Sync" from the bottom right of iTunes.
If you're unable to do the Restore (or it doesn't help), go into Recovery Mode per the instructions here. You WILL lose all of your data (game scores, etc,) but, for the most part, you can redownload apps and music without being charged again. Also, read this. -
Imac keeps restarting on its own after installing update X?
Imac keeps restarting on its own after installing update X?
What do you mean "update X"? What update are you referring to?
-
My Mac Mini won't fully shut down. How do I fix this?
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful. -
Power Mac G4 MDD - Has difficulty booting after shut down
I have a Power Mac G4 MDD (1.25Ghz) that is having issues when it is shut down. The power button on the front of the machine does not start the computer every time. Sometimes it works, sometimes I need to wait a while before it will work. When the button is pressed, it does not light up or anything.
I have noticed that if I sleep the computer it always seems to wakeup when the front button is pressed. But if I shut down the G4, is does not always bootup.
I have also performed multiple restarts when performing software updates, and they always seemed to work fine.
I have changed the Saft battery inside - it was at about .4v
I have performed a CUDA/PMU reset using the button on the motherboard, and followed the Apple procedure. (disconnect power, and accesories, press reset button, wait 10 seconds, reconnect, restart) It did not restart right away, had to wait 20 minutes or so.
The G4 has a new installation of Tiger, with all of the updates.
I have not checked the PSU, but plan on doing that soon. Just seems odd that it only has issues when the machine was shutdown. Seems to start after it sits for a while, but last night I was switching monitors, and shut it down, switched monitors, and it would not re-boot.
Any ideas?With the "sometimes" nature of the problem, it could be the front panel board, a much cheaper replacement than a PSU. An Apple tech told me that one way to test the front panel board was to find one of the first Apple USB keyboards for the original iMac. The early ones have a power button like the old ADB boards that overrides the internal board/button. He said that, should the Mac start reliably from the old keyboard, then there is trouble with the front panel board. The Apple model number for the USB board with power button is M2452.
Very helpful forum member japamac has a test procedure for the MDD PSU on his site here:
http://jcsenterprises.com/Japamacs_Page/Blog/D275729F-09DA-4FBB-96B3-BEEEB2C0461 9.html
You'll need a multimeter to check the voltage levels. -
Power Mac G4 won't start up after shut down
I have a Power Mac G4 (dual 1 GHz with 2 GB of RAM) running OS X 10.4.11. It has the mirror drive doors and was once referred to as the “wind tunnel”.
The problem is that it will not start up after it has been shut down unless I first push the reset button. I have tried replacing the battery and resetting the p-ram. When I try to start it without first pushing the reset button nothing happens. The light for the start button doesn’t even come on. But if I disconnect the power, open it up and push the reset button it will start up and run perfectly.
Thank you for any suggestions that you might have.Thanks BDAqua, it does sound like a bad capacitor. The PSU is one that I put in a few years back when Apple was giving them out so as to reduce the fan noise. I kept the old one until last week when I sent it off to be recycled. I suppose it would be a tough job to find the bad capacitor and I doubt that I would have the skill to replace it even if I could find it. It's not like I really need this power mac since I have a Mac Pro 1,1 but I do occasionally want to run something in OS 9 and I do love this machine for what ever reason. There was remarkably little dust inside but I went over it with a can of dust remover.
Don -
External USB 2.0 hard drive reconnects on its own after power-down
I have an external USB 2.0 hard drive which I'm trying to power off (after unmounting all partitions, of course) using:
$ udisksctl power-off --block-device /dev/sdb
When I do this, the drive spins back up after a few seconds. Only when I issue the same command again does the drive stay powered off.
I'm running:
linux 3.13.7-1
udisks2 2.1.3-1
This is what I see in the journal log when I:
- Plug in the drive's USB cable
- Issue the power-off command
- After the drive spins up again, issue the command again
Mar 29 19:51:01 miki-desktop kernel: usb 1-5: new high-speed USB device number 10 using ehci-pci
Mar 29 19:51:01 miki-desktop kernel: usb-storage 1-5:1.0: USB Mass Storage device detected
Mar 29 19:51:01 miki-desktop kernel: usb-storage 1-5:1.0: Quirks match for vid 1058 pid 0704: 8000
Mar 29 19:51:01 miki-desktop kernel: scsi12 : usb-storage 1-5:1.0
Mar 29 19:51:01 miki-desktop mtp-probe[21301]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:04.1/usb1/1-5"
Mar 29 19:51:01 miki-desktop mtp-probe[21301]: bus: 1, device: 10 was not an MTP device
Mar 29 19:51:02 miki-desktop kernel: scsi 12:0:0:0: Direct-Access WD 5000BMV External 1.75 PQ: 0 ANSI: 4
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Write Protect is off
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Mode Sense: 23 00 00 00
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:02 miki-desktop kernel: sdb: sdb1 sdb2
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Attached SCSI disk
Mar 29 19:51:47 miki-desktop udisksd[21107]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
Mar 29 19:51:47 miki-desktop udisksd[21107]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:04.1/usb1/1-5/remove
Mar 29 19:51:47 miki-desktop kernel: usb 1-5: USB disconnect, device number 10
Mar 29 19:51:47 miki-desktop kernel: usb 2-5: new full-speed USB device number 9 using ohci-pci
Mar 29 19:51:48 miki-desktop kernel: usb 2-5: not running at top speed; connect to a high speed hub
Mar 29 19:51:48 miki-desktop kernel: usb-storage 2-5:1.0: USB Mass Storage device detected
Mar 29 19:51:48 miki-desktop kernel: usb-storage 2-5:1.0: Quirks match for vid 1058 pid 0704: 8000
Mar 29 19:51:48 miki-desktop kernel: scsi13 : usb-storage 2-5:1.0
Mar 29 19:51:48 miki-desktop mtp-probe[21555]: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:04.0/usb2/2-5"
Mar 29 19:51:48 miki-desktop mtp-probe[21555]: bus: 2, device: 9 was not an MTP device
Mar 29 19:51:49 miki-desktop kernel: scsi 13:0:0:0: Direct-Access WD 5000BMV External 1.75 PQ: 0 ANSI: 4
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Write Protect is off
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Mode Sense: 23 00 00 00
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:52 miki-desktop kernel: sdb: sdb1 sdb2
Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] Attached SCSI disk
Mar 29 19:52:20 miki-desktop udisksd[21107]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
Mar 29 19:52:20 miki-desktop udisksd[21107]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:04.0/usb2/2-5/remove
Mar 29 19:52:20 miki-desktop kernel: usb 2-5: USB disconnect, device number 9
What is interesting is that on first connect, the drive is using ehci-pci driver, then after the first try powering it off, the drive appears to reconnect using the ohci-pci driver. Not just that, it appears to 'jump' from one USB bus to another. How is this even possible?
$ lspci
00:00.0 Host bridge: NVIDIA Corporation MCP73 Host Bridge (rev a2)
00:00.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a2)
00:01.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.2 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.3 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.4 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.5 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:01.6 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:02.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
00:03.0 ISA bridge: NVIDIA Corporation MCP73 LPC Bridge (rev a2)
00:03.1 SMBus: NVIDIA Corporation MCP73 SMBus (rev a1)
00:03.2 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1)
00:03.3 Co-processor: NVIDIA Corporation MCP73 Co-processor (rev a2)
00:03.4 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1)
00:04.0 USB controller: NVIDIA Corporation GeForce 7100/nForce 630i USB (rev a1)
00:04.1 USB controller: NVIDIA Corporation MCP73 [nForce 630i] USB 2.0 Controller (EHCI) (rev a1)
00:0a.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0b.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0c.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
00:0e.0 IDE interface: NVIDIA Corporation MCP73 IDE (rev a2)
00:0f.0 Ethernet controller: NVIDIA Corporation MCP73 Ethernet (rev a2)
01:06.0 Multimedia audio controller: C-Media Electronics Inc CMI8738/CMI8768 PCI Audio (rev 10)
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4550]
02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV710/730 HDMI Audio [Radeon HD 4000 series]
$ lsusb
Bus 001 Device 009: ID 1058:0704 Western Digital Technologies, Inc. Passport External HDD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 007: ID 15ca:0101 Textech International Ltd. MIDI Interface cable
Bus 002 Device 003: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 002 Device 002: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Before the first power-off attempt:
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M
|__ Port 5: Dev 9, If 0, Class=Mass Storage, Driver=usb-storage, 480M
After the first power-off attempt:
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 5: Dev 10, If 0, Class=Mass Storage, Driver=usb-storage, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M
Does anyone know how to fix this problem? Is it a device quirk, a driver bug or something?
Last edited by ackalker (2014-03-29 19:21:04)Just to be sure, I rebooted my system, shut down lightdm from another VT, made sure that really nothing is using the drive, no partitions are mounted, no services that could try to use the drive (except udisks2.service, could this one be the problem? But how am I supposed to use the udisksctl command when the service isn't running?).
Tried the same command again. same result: I needed to run it twice in a row for it to 'take'.
What I find even more fascinating: how can a USB device jump from one USB bus to another like that? I've honestly never seen anything like this before :-)
Last edited by ackalker (2014-03-29 19:35:29) -
I need help because I want to fix it by myself
Have you blown the dust out lately?
Get Temperature Monitor to see if it's heat related...
http://www.macupdate.com/info.php/id/12381/temperature-monitor
iStat Menus...
http://bjango.com/mac/istatmenus/
And/or iStat Pro...
http://www.islayer.com/apps/istatpro/ -
Mac Mini restarts automatically after shutdown
This has been happening for a few months. (I have to run older Macs for Rosetta.) After the reboot, when I hit shutdown, it shuts down.
I looked at other forums and no one has an answer. The Mini otherwise runs fine. It's most annoying as I want to shut down and leave the office but have to wait for the reboot and then shut down a second time. Any ideas?Try unplugging all USB and Firewire accessories (except for your mouse) from the Mac Mini and see if it will shut down properly.
If it does, plug one back in at a time and see which one is interfering with the shutdown!
What apps do you continue to run that need Rosetta? -
HP 2140 Mini reboots on its own...
Hello everybody, I need your help.
My HP2140 Mini reboots on its own after being shut down. This only happens when it's on AC-Power, not when on battery power only. It's due to a software glitch and not due to a faulty power supply.
I had this problem once before and was able to get ahold of a software fix that stopped it from doing it. That software fix came directly from HP and was emailed to all HP2140 Mini owners.
Since I had to reinstall the Operating System again, that software fix is now gone and I don't have the email anymore.
Can anyone help?An alternative is SANE, here is a link, its also FREE. The first link shows the scanners supported. The second is the program link.
http://www.sane-project.org/sane-mfgs.html#SCANNERS
http://www.ellert.se/twain-sane/ -
Troubles with the sleeper: how can I avoid it restarting on its own?
When on sleeper, my MacPro early 2008 restarts on its own after a while.
Until very recently, it worked perfectly well.Thanks for your help.
I wonder if the the troubles I have with the sleeper and with the start button are not linked with an issue on the main disk. Apparently, I need to repair my main drive:
- the number of volume files is not valid
- the numner of volume directories is not valid.
2013-12-15 11:02:20 +0100: Utilitaire de disque a commencé.
2013-12-15 11:04:13 +0100: Vérification du volume « 1 Main HD »
2013-12-15 11:04:13 +0100: Démarrage de l’outil de vérification :
2013-12-15 11:04:15 +0100: Vérification en direct en cours.
2013-12-15 11:05:18 +0100: Vérification du volume HFS Plus journalisé.
2013-12-15 11:05:18 +0100: Vérification du fichier de blocs en excès.
2013-12-15 11:05:18 +0100: Vérification du fichier de catalogue.
2013-12-15 11:05:18 +0100: Vérification des fichiers à liens multiples.
2013-12-15 11:05:18 +0100: Vérification de la hiérarchie du catalogue.
2013-12-15 11:05:18 +0100: Vérification du fichier des attributs étendus.
2013-12-15 11:05:18 +0100: Vérification bitmap du volume.
2013-12-15 11:05:18 +0100: Vérification des informations du volume.
2013-12-15 11:05:18 +0100: Nombre de fichiers de volume non valide
2013-12-15 11:05:19 +0100: (normalement 617151 au lieu de 617152)
2013-12-15 11:05:19 +0100: Nombre de répertoires de volume non valide
2013-12-15 11:05:19 +0100: (normalement 173934 au lieu de 173933)
2013-12-15 11:05:19 +0100: Le volume 1 Main HD s’avère corrompu et doit être réparé.
2013-12-15 11:05:19 +0100: Erreur : Le disque nécessite un réparation. Démarrez votre ordinateur depuis un autre disque (tel que votre disque d’installation Mac OS X), puis ouvrez Utilitaire de disque pour réparer ce disque.2013-12-15 11:05:19 +0100:
2013-12-15 11:05:19 +0100: Utilitaire de disque a cessé de vérifier « 1 Main HD »: Le disque nécessite un réparation. Démarrez votre ordinateur depuis un autre disque (tel que votre disque d’installation Mac OS X), puis ouvrez Utilitaire de disque pour réparer ce disque.
2013-12-15 11:05:19 +0100: -
Mac Pro 4,1 kernel panic - restarts on its own
I have a Mac Pro 4,1 that will not finish the start up process It kernel panics at the end of the process. It will then do a restart on its own and kernel panics again.
What's the best way to figure out what's wrong with it? HDs? Processor ? Or the RAM? I have not changed anything for a long time.
ThanksPlease read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including Wi-Fi on certain iMacs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test. -
Ipad mini constantly restart by its own
The screen suddenly displays some black strip then shut down and restart, happens often with some tap and sometimes on its own. The issue starts to constantly happen ever since one time when the device shut down by out of battery. Any help to resolve this issue? This happens about 10 times a day and really gets me frustrated.
Hi Kokynu,
Welcome to the Apple Support Communities!
I understand that your iPad mini is sporadically restarting on its own and know how frustrating situations like this can be. To troubleshoot, I would recommend reading over and working through the information in the attached article.
If your iOS device restarts, displays the Apple logo, or powers off while you're using it - Apple Support
Best regards,
Joe -
My mac has been restarting on its own since i installed Yosemite 10.10.1
I installed Yosemite 10.10.1 last month. Since then, My macbook has been restarting on its own. Furthermore overtime I am getting an error message that my JAVA runtime needs to be updated . Although I have Installed JAVA again and again I am constantly getting the error.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.
Maybe you are looking for
-
XBOX 360, MacBook Pro, PC and Airport Express don't all connect
Just got the new XBOX360 with built in wi-fi for Christmas! Also have a MacBook Pro and a PC connected wirelessly to my Airport Express. Prior to the XBOX 360 the ApE worked flawlessly with the MbP and PC. Now, depending on the day, either the PC or
-
I'm trying to build a simple app which has multiple views. When the user clicks on the worksetItem I want to change the view, and display an other table in the shell. But I dont know how can I define another view, and add it to the shell.
-
How Far Does Lid open Macbook Retina 15
Hi there Well my 3 year old son decided to jump on my 15" retina Pro and I think that he may have broken the stops that limit how far you screen can open I could be paranoid but can anyone confirm if this is the case ? My screen goes so far back I j
-
Photosmart D7260 won't print Word 97 docs
I was referred to the printer diagnostics program by an HP support email. The diagnostics cured another problem with HP Solution Centre but now I cannot print my Word 97 docs. Test page, PDFs, Excel, emails all print normally. Printer is connected to
-
The I4S is frequently hanging when a call is received after updating the Sw to version 8
After updating the Phone Software to version 8 the Instrument I4S hangs frequently when a call is received. You can see who is calling but the touch screen does not respond and only way is to switch off and on.