Shuts down COLD

I am stunned. The Apple help crew was terrific over the past month of problems installing Leopard in my iMac, the most alarming of which was its increasingly frequent habit of just shutting down cold. Turns out that the problem was known to Apple, which issued a recall about a year and a half ago for models which included mine. If you weren’t looking for the notice, you wouldn’t have found it,. The Mac service center now tells me that the recall expired 5 months ago, and it will cost me $6-700 to get it fixed. A call to Apple’s “customer service” got me a stout NO. The supervisor was downright rude, all but said “tough”. Apple knew about but didn’t notify owners -- the “customer service” supervisor said Apple couldn’t possibly be expected to e-mail everybody about it (say what?). They didn’t offer even to meet me halfway, reduce the cost of the replacement parts. Nothing. Tough luck. I’ve always had such good experience with Apple, their products, their customer service, their options for help for non-geek-speak people like my husband and I. Has something fundamental changed at Apple?

I am sorry to hear your story - did you call Apple Customer Relations at 800-767-2775?
In fact, Apple did not issue a "recall", they simply extended the warranty for models that had a known defect. Unfortunately, these warranty extensions cannot be open-ended, a line has to be drawn somewhere. Apparently, the extension ended three years after the date the computer was purchased. In some cases, where the machine broke down very close after the end date of the extension, it was honored and repairs were made for free. You, unfortunately, are well outside the parameters, so you are out of luck.
I don't think anything fundamental has changed at Apple. It is, however, a business, and as such, has to pay attention to the bottom line as well as to satisfying customers. It's a fine line to tread, and Apple generally does a good job of balancing one against the other.
I'm sorry you are unhappy with Apple, calling the number I gave you above might produce some positive results.
Let me know how things turn out,

Similar Messages

IPhone 5s shuts down after being in the cold for a while

I have an iPhone 5s. I go outside jogging at noon and listen to the radio on the phone app. Since it is cold outside, it has happened several times that after about 20 minutes I come back into the building and take out and check my phone it shuts down by itself. If I try to restart, it will tell me the battery is low and need recharge. I will have to wait for a couple of minutes before I could restart. First couple of times, the battery was low, close to 10%. Today it happened again. When I restarted eventually, it showed over 60% battery life left. Has anyone else had similar issues? The warrenty just expired. What is my option?

sideline2 wrote:
I have an iPhone 5s. I go outside jogging at noon and listen to the radio on the phone app. Since it is cold outside, it has happened several times that after about 20 minutes I come back into the building and take out and check my phone it shuts down by itself. If I try to restart, it will tell me the battery is low and need recharge. I will have to wait for a couple of minutes before I could restart. First couple of times, the battery was low, close to 10%. Today it happened again. When I restarted eventually, it showed over 60% battery life left. Has anyone else had similar issues? The warrenty just expired. What is my option?
Don't let it get so cold...
Set up a Genius appt and see what they say.
-> https://www.apple.com/retail/geniusbar/

IPhone4 shuts down when mildly cold?

Just wondering if anyone else has encountered anything similar, and if someone might know whats going on...
Aside from the consistently poor signal and practically unusable 3G speed in everyday use, I'm having a problem with my iPhone 4 completely shutting itself off when it is in my backpack whilst I am riding my mountain bike.
It's not particularly cold in there (UK summer), but that is when the phone is at it's coldest throughout my weekly useage. The phone is in a case and it in no way taking any abuse. Once I get home I have to wait 10 minutes for the thing to warm up again and then perform a two button reset, obviously making taking the phone out in the first place completely pointless.
I really hope that it is a fault my partcular unit, as I'd expect the iP4 would be able to perform this most basic of functions that my 3 year old bashed up Nokia had no trouble at all with.
Any suggestions very much appreciated.

I have an IPhone4 and mine does the same thing. When only slightly cold it shuts completely down. I don't buy Apple's little "32 degrees" garbage either becaause that would mean that if I lived in a place like New York where everyone is constantly walking from block to block I couldn't walk around the city in the middle of winter and talk on my phone..........so I just paid hundreds of dollars for a phone that I can only use say half the year when it's warm out?
Also, I did a little test, I have an older IPhone 3G and I put my 3G and my 4 side by side in my car. With the engine shut off, I left them both in their for about 15 minutes (I live in Northern Michigan, and I did this this morning). I went back out to my car and sure enough the IPhone 4 was shut down yet the 3G was working fine. Now, Apple either wants me to be without my phone while they repair/replace it or allow them to charge/authorize my credit card $500.00 for an advance replacement until they get my current defective phone back. Of course a third option is to drive to my local Apple store (3 hours drive one way) to have them replace it.
It's time to switch to a phone I can use all year around, that works in any weather....... A Droid based phone from Verizon!!!!

IPhone 4s Shuts Down In Cold

I have a iphone 4s and in the winter it shuts down in the cold. If it is im outer coat pocket it shuts down all the timewhen its not even that cold out. When its in my inside pocket it dont shut down as much unless it is very cold like -20 or so. Does anybody else have the same problem? And my iPhone can be upgraded in febuary and i was wondering dows it still do this with the 5s?
Thanks, Josh

Here are the iPhone 5S technical specs:
http://support.apple.com/kb/SP685
I believe the operating temperature for the iPhone 4S is the same as that shown for the 5S: 32 to 95°F (0 to 35°C).

My iphone shuts down in cold weather.

My Iphone shuts down when is around 0 C, which is very common in Sweden.
I can not use it outdoors to take pictures of my children etc. Should it really be this way? Many of my friends have the same problems and are really annoyed.
Is it specified only for California ?

You may find it difficult getting a smartphone that can operate well in sub-zero temperatures.
Read:
http://www.techhive.com/article/249134/sub_zero_weather_can_your_smartphone_stan d_the_cold_.html
http://www.technobuffalo.com/2013/02/18/iphone-samsung-galaxy-s-iii-maximum-temp eratures/
Old style "dumb" phones fair much better as they have less tech in them, and basic lcd screens.

Battery life issue, phone shuts down

HI I have an iphone 4S running 6.1.1 and with 10.6GB avail space running 3G on the Fido network. Had the phone for less than a year and it was sent to me as a refurbished
My phone shuts down before it gets to 0%. Sometimes it lets me get to 0% and does a normal shut down, but in some cases it will suddenly just shut down and claim it has no battery life left, then when plug in loads up right away, exactly with all the same apps open and with a good chuck of battery.
Today for example
- Was at 70% when went out on a bike ride
- 2 hours later and after some tethering and listening to music it shuts down all of a sudden while looking at a tweet
- Try to turn back on, says its out of battery
- Get home and plug in, starts up at 17% right back at the same tweet

I have the same issue with the same 4S. I thought it was a bug with the camera because it would happen while I was in the middle of taking a picture. The phone would shut down and after attempting to restart it prompted no battery life. But once I plugged the phone in it would start up and show the proper battery % left on the phone.
Another forum on here stated a probelm is with the cold weather which was cauing the battery to lower in tempature, falsly causing a depleted percentage which forced a shutdown. They said all they had to do was let the phone warm up and it would reboot back up just fine.
I thought it odd but most of my issues were when I was outside. That is until just last night when I was in my kitchen taking a picture of something on the counter and it again shut down. I had to plug in the charger, boot it back up and once back up I went right back to the kitchen and tried again and it happened again. So I plugged it in again rebooted and then unplugged the phone and let it sit about 10 minutes on the counter and then tried again and it worked. I am not sure the cold had anytyhing to do with it this time because I had been home a couple of hours already and my home is 70 degrees. It is frustraing. I find myself caring a backup battery to plug in the phone if and when this happens when I am away. Not a good solution.

Intermittent Shut Down Syndrome Redux 2

The old redux thread was locked, probably because it became too large. This is an updated redux to replace the old one.
MacBook Intermittent Shut Down
Redux 2 (Updated Oct 13, 2006)
Guy Kuo
Do a google search for "macbook random shutdown" and you will find many people with similar problems reporting on various forums. Most frequently, the MacBook operates normally for several weeks or months, but mysteriously begins intermittently shutting off suddenly. The shutdowns are not accompanied by kernel panics, but instead the machine simply goes black and the machine is off. Initially, the cause of this problem was not known and early repairs of the main logic board and heat sink did not incorporate the changes made after the cause of the problem was discovered. Numerous attempts at user, ad hoc, solutions have been posted, but the only definitive and permanent solution requires repair by Apple.
The problem as difficult to characterize because its symptoms mimic more common causes of system failure (bad RAM, improperly seated RAM, improperly seated hard drive, bad software install, bad battery, bad AC adapter, corrupted PRAM, corrupted NVRAM) which ALL must be ruled out before making the sudden shutdown diagnosis. The problem's intermittent nature means it may not be possible to reproduce on demand.
At present, this problem is being addressed by Apple and affects at least serial number range 4H617-4H635. MacBooks produced after that date should have an updated heat sink assembly which does not have that problem. The problem seems to have two root causes.
1. Two heat sensor wires in contact with the heat sink can melt and once that occurs, intermittent shorting of the wires causes the machine to sense an emergent temperature problem and the system performs an immediate power down.
2. Also, as described in a MacTalk Australia posting ..... 2 small connectors that bake under the enclosed heat on the Macbook (the Mac book Pro has more space and 2 fans) these connects then loose contact with their pins.... Once contact is lost, the machine does an emergency power down
The common thread is that heat in the original heat sink and thermal sensor design eventually may cause the problem to occur. Once contact or insulation problems begin, the machine can begin suddenly shutting down while cold or hot. Until sufficient heat is built up, the MacBook operates without any issues. It is possible for an early MacBook to operate normally for months before heat causes the problem to occur. Indeed it is possible a machine may never exhibit this problem despite having this weakness in its components. None the less, the early MacBooks have a heat sink and thermal sensor wiring harness that is inherently prone to deterioration. Because the risk of deterioration increases over time, it is reasonable to expect more early MacBooks to develop intermittent shutdown problems as time passes.
There are some early reports that even a heat sink assembly replacement repair does not always solve the issue. In such cases, a logic board replacement may also be necessary, but at this point, heat sink assembly replacement should solve the identified problem unless the MLB was also somehow damaged.
The current count of affected MacBooks has not been disclosed, but well over 1,000 machines have been reported on-line independent of Apple. The actual number of early MacBooks which will eventually be affected may be significantly larger even if one discounts the tendency of the web to amplify negative news.
Because heat is the root cause of the problem, two camps have appeared regarding how to deal with this issue. This author believes that the MacBooks should be allowed to warm to full operating temperature by running some high CPU usage tasks (with normal circulation around the case) for several hours and then seeing over the next few days if the problem occurs. The rationale is reveal any tendency for the problem while the MacBook is within warranty and before any critical usage. The other camp believes that the MacBook should only be used lightly and never allowed to get warm enough to induces the problem. The reader is left to choose their own course.
Only a fraction of shutdowns are due to this particular fault. A large number of other reasons must be ruled out before a MacBook owner should become convinced their machine is one which suffers this problem. Bad RAM, poorly seated RAM, improperly installed hard drive, corrupted OS, corrupted plists, bad batteries, bad chargers, corrupted PMU, and corrupted NVRAM all need to be ruled out first. During your call to Apple care you may be asked to perform checks to rule out the above list. Once a diagnosis of intermittent shut down is made, repair can take days to weeks depending on availability of parts and whether additional components beyond the heat sink assembly needs to be repaired. Once repaired, the MacBook is less likely to redevelop the problem, but as of this date, long term usage of several months has not had time to happen.
It is the hope of this writer that Apple will continue to assist its customers with this hardware "defect." So many first time Apple owners could be lost forever if this is not addressed openly and aggressively.

Are you sure RSD is the problem? Then, first, be sure you have downloaded all the updates. The smc update (late October) stopped RSD for many people. If you're updated, then you may need a new heatsink. That's what stopped it for me. I had it replaced at an authorized repair center while I waited - only took a couple of hours. You are still under warranty, so repair will be free if RSD is indeed the problem. You can look on these apple pages for the nearest Apple Store or authorized repair center.
In the meantime, I found it very helpful to hold down the on button for 5 seconds when I restarted the macbook. That kept the processor speed down to 1.0 gH, and for some reason, for me and for some other users, RSD never happened while in that mode.
Let us know how it goes!

MBP 13 Retina shuts down at 8% without warning

Hi
I have a MacBook Pro Retina 13'', Late 2012, with OS X 10.9.2 (13C64). It keeps shutting down at 8% on battery power. On charge, it is ok. I don't get any low battery warning before shutting down. Obiously I lose everything every time. I have reset the SMC, Pram/nvram. I have also run Apple Hardware Test, and checked the battery status:
Battery Information:
Model Information:
Serial Number:          C013302007VF957AM
Manufacturer:          DP
Device Name:          bq20z451
Pack Lot Code:          0
PCB Lot Code:          0
Firmware Version:          511
Hardware Revision:          000a
Cell Revision:          1155
Charge Information:
Charge Remaining (mAh):          4843
Fully Charged:          No
Charging:          Yes
Full Charge Capacity (mAh):          6410
Health Information:
Cycle Count:          154
Condition:          Normal
Battery Installed:          Yes
Amperage (mA):          2667
Voltage (mV):          12065
It was working properly before. I am not sure, but I believe, it started doing that after I had reset the SMC. I had done it (and pram/nvram) because it was a bit slow. I have also realised, the battery is loose inside. If i gently shake the machine, it rattles, when the machine is cold. If it is hot, doesnt do that.
Do I should get a low battery warning under 20% anyway? I beleive so.

Hi, thanks for your answer. I will take it to Genius Bar one day (it is 1000 km away from us), but in the meantime, I would like to investigate the "no warning at low power" issue. The battery does the same rattling nearly from the first minute. I took it to NextByte (premium reseller) where I bought it, but they are useless, their service is crap.
My main question is at the moment, why I don't get any low power warning? usually I don't let it go down under 30%, but it obviously can happen sometimes. As I am a graphic designer, it is not the best thing to lose 3-4 hours work.

To shut down or not

my macpro with 4 hard drives and connected to a 23" cinema display.
i use my computer twice a day, once in the morning for about 2 hours then when I get home from work for another 2 hours. should i leave my computer on? put it to sleep?
just looking for the best option... less wear and tear on my hardware.

4151
Hello again Jeff,
So this shutting down vs. sleep question is clearly not very problematic after all.
- (shutdown) Cold boots are certainly the most demanding task for the whole computer in general
vs.
- (sleep) Idling and gently resting, but for such a long time per 24 hour
won't make any significant difference in the long run.
Now, about this so-called nightly maintenance:
This issue sounds off-topic, but it is not, as the question arises each time along with the shutdown vs. sleep vs. awake question.
Mike B,
You are very late with your KB articles information. It's been over one year now that the new periodic behaviour is known and indeed put back to its benign character, not important issue at all.
You are (were) also wrong about how the periodic tasks used to work, if you think (thought) only one or two times a week was equivalent to catching every night.
You wrote:
"All this does is scare those who are not very computer literate into thinking Macs are too complex when they are the opposite in many ways."
- Indeed Mike, Macs just work, and you don't have to mention the nightly periodic tasks anymore in a "sleep vs. shutdown" thread.
This issue was worth mentioning many years ago when it was a pure Unix issue, far before Mac OS X was completed and enhanced with new versions,
and also
far before this new era of huge hard drives capacities that make the periodic tasks such a non-issue even more.
"a couple of times a week just to make sure the maintenance is caught"
- it wouldn't work that way (I mean in Panther and before, when this question was already overkill but still worth the look):
There are three different maintenance tasks, occuring at three different times and doing three different things.
The "daily" is set to run at 3:15 every morning.
The "weekly" is set to run at 4:30 in the morning on Saturdays. (3:15 since Tiger)
The "monthly" is set to run at 5:30 in the morning on the first day of each month.
If you want all three to run, it's not by leaving your Mac on once or twice a week at random times...
"you should read this [KB article #107388]"
- this article is still useful with Jaguar and with old G3 or small-capacity Macs that run Jaguar or Panther.
It's never been updated, even the latest update date is a lie. See the software it mentions (CronMaster, weRclean): long gone, unavailable even by searching Version Tracker oldies.
"(About OSX 10.4.2 Update) [KB article #301722]"
(here is the text you are referring to:
"This update ensures that periodic background maintenance tasks run as scheduled in launchd.conf.")
- "as scheduled in launchd.conf", yes, since before Tiger (10.4) the periodic tasks were taken care of by cron, not launchd.
What this 10.4.2 update brings, is the fix to one of the two bugs launchd new handling was suffering since 10.4.0.
In 10.4.0 and in 10.4.1 already, launchd does the maintenance, not cron anymore, except that because of a bug there is no chance for the tasks to be automated at all, unless you reboot your Mac every day.
So this is the 10.4.2 fix: not having to reboot every day anymore.
The new launchd handling is meant to precisely not need anymore our Macs to stay awake at night like before:
Maintenance tasks are meant to now run delayed if sleeping at night.
No need to worry anymore, except,
-- there is still one other bug: Tasks will run, sleep or not sleep, right, BUT will be cancelled sometimes if Mac is shutdown AND sleeps a lot during the week.
These details just so you know.
Please run the ls -al /var/log/*.out Terminal command day after day if you are interested and would like to verify my info. Keep track of your sleep times, and do the maths.
Much better, much Mac-friendly, simple and easy way:
- Just don't worry about these periodic maintenance tasks, and run them manually once or twice a month.
Installing Anacron or Macaroni too is overkill. Just use your OnyX or Cocktail or TinkerTool System or your favorite small utility.
Jeff,
in a word, about the nightly automatic maintenance:
It is not at all such an important thing that would have to be mentioned here.
The kind of maintenance it does, anyway, is about taking care of log files and some system database. It has not much to do with Mac OS X performance itself
(all that is taken care of automatically, and all Mac OS X needs is a lot of free HD space and RAM)
--> Sleep settings in Energy Saver,
--> Shut down if Mac left untouched for more than 24 hours.
Enjoy your Mac!
Axl

IMac unexpectedly shutting down

My iMac has begun to shut down unexpectedly, repeatedly. I've been struggling with this issue for two days now and so can describe the typical pattern of odd behavior. I use my computer in the office of my private English school. For several hours in the day I teach in the classroom next to my office and simply leave the computer on so I can pick up research and materials design where I left off. A couple of evenings ago I returned to my desk to find the Mac shut down. Odd, but not scary -- yet. I entered the Twilight Zone when I tried starting it up. It went something like this:
1st try- Partial startup, screen lights up, no chime, shutdown.
2nd try- Complete startup, no user apps launched, shutdown after less than a minute.
3rd try- Complete startup, begin cautiously checking for damage and causes, shutdown after several minutes.
4th try- Begins as 3rd try (above), checked Console log, attempted to set up diagnostics programs to determine cause, shutdown in about 20 minutes or so.
This basic pattern (1~4, above) has occurred three times so far. In addition, there have been other (less regular or perhaps more widely spaced timing?) instances. Also, I successfully booted from an external firewire drive dedicated to TechTools as an "edrive" and running Mac OS Tiger same as my Mac. To my horror, shutdown occurred after about 10 minutes booted in the external edrive! It was very late so I left it shut down and went to bed (for a very poor night's sleep!). Early the next morning, in my second attempt booted in the external edrive, I got a diagnostics utility launched (DiskWarrior) which found no directory damage on the internal drive! I decided to try another one (TechTools) and the Mac shutdown again while testing was going on!
At this point I had lessons I started the Mac and let it sleep while and put the whole mess aside till evening. I pondered everything I thought might be wrong. The Mac was still up and sleeping several hours later. Yet, when I tried to use it, it started the pattern of shutting down described above. I disconnected all peripherals and freed up ports, and tried agin.
Temperature is usually under control as I have designed an effective constant airflow system for my office that incorporates fans which keep air moving, so no dead air can collect in the space behind the Mac. In addition, I reposition my desk according to the season; now it is by a north window with no direct sunlight and which I keep cracked open to the cold winter air which bathes the back of the computer constantly. One cool Mac. Of course, if internal components, such as the sensor responsible for monitoring heat, are defective, this will not matter.
I searched the Internet using various search strings, both describing my problem and using log data copied from Console. I checked this Mac forum and tried 3 times to post a message (with one successful post, but to the wrong section!). I have read Tech blogs and everything else I can between shutdowns.
This message was written and saved several times. Any ideas?

Hi Miriam:
Thanks for taking the time for this. I have benefited as a lurker from help you have given to others. Thank you, always.
I replaced the power unit over a year ago (I believe) supplied by mail from Apple. I have the exact records, but it would take too much time to dig them up and I am under the shutdown gun right now. Also, I am typing as fast as my chubby little fingers can hit the keys so there will be typos: apologies. I will dig out l those records after I get this email off to you and set them aside for my next post.
Against all my better instincts I decided to try and cure the problem by upgrading the OS and am now running Mac OS 10.5.2 (see below). Immediately after the OS upgrade the shutdown problem reoccurred once, then disappeared. If it were not for that one occurrence I would have called it cured. I decided to wait and see. The computer shut down unexpectedly a couple of more times, but randomly and infrequently, not following the pattern I outlined originally so I just kept observing it. As of today, the full-blown problem has returned, as originally described, again, as follows:
While using any application, or even left unattended with no application running, with nothing connected to the ports, the computer shuts down as if a kill switch had be pushed. (Unlike before the OS upgrade, no kernal error report appears.) Upon first restart attempt, all sounds indicate restart is happening normally, but before the screen lights up it shuts down again. This incomplete startup happens once, then on the second attempt, it starts up normally, if somewhat slowly. After some time (15~30 minutes or so?) it shuts down again (I'll try to set a stopwatch on that).
The only user alteration of the system software immediately previous to this new round of shutdowns was allowing an Apple auto-update (Safari). As far as general heat issues are concerned, I have a temperature monitor application installed and keep an eye on it. Also, I take environmental measures to keep the work area cool and cool air moving around the CPU. At the moment Istat Pro 4.6 (newest, today) reports: CPU 75 degrees, Hard Drive 53, Atilla (my internal drive name) 61. I know this is different than the power unit overheating problem you mentioned.
I am beginning to suspect malware and will pursue that angle when I get time (got classes to teach for the next 8 hours). Hardware information you requested (or more, perhaps) is below (clipped from System Profiler).
Model Name: iMac G5
Model Identifier: PowerMac8,2
Processor Name: PowerPC G5 (3.1)
Processor Speed: 2 GHz
Number Of CPUs: 1
L2 Cache (per CPU): 512 KB
Memory: 1 GB
Bus Speed: 667 MHz
Boot ROM Version: 5.2.5f1
System Version: Mac OS X 10.5.2 (9C31)
Kernel Version: Darwin 9.2.0
Thank you again for your attention.
-- William Newman

Re: Activation Server shut down for Creative Suite 2, Acrobat 7 and Macromedia products

Software : Adobe Encore DVD 2.0 / UK, purchased october 24, 2006
Operating system : Windows XP home edition / SP3 Computer : Pentium 4 / 1,8GHz - 512 MB
Other software : Adobe Premiere 6.5 / Photoshop Elements 5.0 / QuickTime 7, etc.
My harddrive crashed and I lost all my software. I had to reinstall. Everything is okay now but when I activate Encore DVD 2.0, I get the message "Activation server shut down for ........." I searched for the free download (without activating) of the CS 2 Premium, but I cold not find it. I only found the normal CS 2.
Who can help me.

If what you want is not at this link, http://helpx.adobe.com/x-productkb/policy-pricing/creative-suite-2-activation-end-life.htm l that would indicate that Adobe did not provide a special version

Yoga wont shut down

I guess this is a windows issue, but it takes me multiple attempts to shut off my yoga because it automatically restarts. This is with the soft buttons on the right, but I believe it happens as often by physical power button. Have you looked what happens when you turn yours off... does the button stay lit and it slowly bounces on? Maybe you notice it is unexpectedly asleep when you turn it on?
I guess windows recognizes this, because it let's me send them info on it. Is windows so immature that I should expect this? I had no such drama in a decade on Macs.
Sometimes in a cold start, the screen stays black and the fans immediately run full speed in panic mode, but with no heat. I just have to hold the power button repeatedly. I have updated all windows, and only installed spotify, vlc, and Google earth. Didn't have this problem until recently... maybe just after violent crashes which ensued with the installations I mentioned. Thx

Press and hold the power button until it shuts down (about 5 seconds.)

IMac G5 shut down

The iMac I'm working on in a regular boot up, when cold, will stay on for one to two minutes, then...shut down. But... if I boot up in Open Firmware it will run forever. I do notice that the fan is runnign full tilt in Open Firmware and not in normal boot up. Is this related to the power supply problem, or something else?

Depending on your model <a href=http://docs.info.apple.com/article.html?artnum=301724<how to identify your iMac</a>, you may be eligible for Apple's Rev A repair extension program or Rev B Warranty Extension.
The fact that you fans run full tilt in OF is normal, but the fact that your machine shuts down when normally booted indicates the cpu is not being sufficiently cooled and the power supply unit may be failing. Look in your Console logs and see if your can find crash log that says something like "maximum temperature exceeded for 30 seconds". That will explain the shutdown.
Please let us know what happens,
Miriam

Problems shutting down a 6534

Hi,
I have searched the forums and couldn't find this sorry if its a rehash.
I reciently built a box with a 6534 and a celery 1.7.
Everything is fine it runs fine, doesn't heat up, actually very stable.
Except...
I can't shut it down.
It will shut down/hbrn8,suspend fine, but the power supply fan continues to spin and after a few seconds it will boot back up on its own. I can shut it down and then turn off the powersupply switch, turn it back on and it will stay off. But after I hit the power button, it will again act incorrectly when shutting down. I have replaced the power supply with a know good and it reacts the same.
any help would be appreciated.
bios to 1.4
1.7 celeron
6534 msi board
window 2k
320 megs ram (2 sticks could be problem?)
crappy pci video card sis 6326 (its a business machine not a gamer)
realtec nic
onboard sound
thanks
dex

For STR-1 mode: Standby mode in normal state where the system is "actively suspend". To re-activate system in this mode can be through keypress or mouse press buttons.
For STR-3 mode: Standby mode in power saving state where all active activities are being virtually saved into system memory. When this mode is activated, the system will direct go into a "fake shutdown" state to consume the least amount of power. To re-activate system in this mode is only through the power switch, once activated, the system will fall back to it's last active stage.
STR-3 mode is a recommend suspend mode for quiet and power saving step for a system.
For your case, what are the errors that occurred after a shutdown and a cold bootup?

Question about shutting down the middle tier while leaving the DB up

Hi,
We just successfully upgraded 11.5.10.2 from running on 9.2.0.8 SOLARIS SPARC 32-bit to 11.2.0.1 SOLARIS SPARC 64-bit.
I am in the process of rewriting the backup scripts. We used to do a once-a-week backup (zip) of the middle tier directories,
after shutting down EVERYTHING cold (MT first, then DB listener, the DB). Our DB consultant likes hot-only backups of the
DB so we are going to keep the DB running all the time and always do hot backups from the DB, but keep MT cold backup.
We want to keep our MT cold backup so we retain our downtime window that users expect (Saturday night - Sun morning).
So my question is ---- is there any issue with shutting down the entire MT- only (adstpall.sh) -- but leaving the DB up?
When I do a adstrtal (via my script) the next morning--- everything should just start fine with no DB bonce having been done, right?
In the past, once I have the MT down, wait 5 min, kill any stray FND processes, I usually go on to bounce the database
"for good measure". I am 99% sure that I don't have to do this... and that there is no harm in "not" doing this, just need
some confirmation.
MH
One more piece of information - Our concurrent managers shut down cleanly almost all of the time without putting jobs on hold.
We don't have many users (< 60) and while we do have autoinvoice that runs every 5 min, I haven't had to do a big bounce
with cmclean.sql very often-- only about once or twice a year when users lock each others tables and the cleanest fix is to bounce
everything --very rarely.

Hi,
So my question is ---- is there any issue with shutting down the entire MT- only (adstpall.sh) -- but leaving the DB up? There should be no issues.
When I do a adstrtal (via my script) the next morning--- everything should just start fine with no DB bonce having been done, right?Correct.
In the past, once I have the MT down, wait 5 min, kill any stray FND processes, I usually go on to bounce the database
"for good measure". I am 99% sure that I don't have to do this... and that there is no harm in "not" doing this, just need
some confirmation.You still need to wait for sometime for the CM to shutdown, that's all.
One more piece of information - Our concurrent managers shut down cleanly almost all of the time without putting jobs on hold.
We don't have many users (< 60) and while we do have autoinvoice that runs every 5 min, I haven't had to do a big bounce
with cmclean.sql very often-- only about once or twice a year when users lock each others tables and the cleanest fix is to bounce
everything --very rarely.You should be OK with your approach.
Thanks,
Hussein

Shuts down COLD

Similar Messages

Maybe you are looking for