There goes another thread on Random Shutdowns blocked by apple...

it may have something to do with someone saying 'don't buy a macbook under any circumstances', which I'd have to disagree with, they are good computers I can't wait till mine is repaired!

I can understand why the threads might be locked...but I don't agree with it. Even though the random shut down threads end up consisting of people badmouthing the product, it is still an open forum that should give people the right to free speech.
In general I would still really like to own a Macbook, and from what I've seen, I dont see how a new OS could address the issue, as more often then not a logic board replacement does fix the issue. The reason why a lot of new logic boards don't seem to help could be because they're boards from the same "batch" being used.
I dunno, technically if you spend a lot of time around these forums it's easy to get a really bad taste for almost anything, but people should still realise that there's still not a ridiculously high chance that they'll run into any serious issues.
Take posts/threads in this forum realistically, but people need to realise that you're often not going to find anything BUT negative comments posted in places like this, so it's not always fair to turn down a new computer because of prevalent issues.
I would not be able to wait and wait just because some people are still having certain issues. Bite the bullet...buy your new computer, and things should be fine. If they're not, applecare is more then willing to back you up and get you up and running asap.

Similar Messages

After a year, another chain of random shutdowns

can anybody tell what's going on with my computer from a remote desktop? by now that should be easy.
i had random shutdowns problems last year, one month after buying my macbook pro, but they seemed over after the download of the oct.2006 firmware. now they're back. as random as they were. could it be possible that the new battery update clashed with something? the appearance seem to have occurred just after that update. maybe a coincidence. but i had started to have battery failures - computer shutdowns at 95% of battery charge, with 28 cycles count - and was about to go replace it (the sick battery).
just i cant stand abandoning my computer in a dark room with many others, so i didn't turn it in and kept it on ACDC.
anybody may guess what i should do to avoid a premature death?

There's nothing anyone here can do about this. We're all just users like you. Was the phone still covered by warranty? Was there an explanation from Apple?

MacBook Pro Core Duo 15" Random Shutdown worsening

Have had my MBP for over 18 months now, and any glitches have been software so far.
Two nights ago, I was working on my MBP and suddenly went into an unwakeable sleep. After resetting, I could start up intermittently up to 5 minutes, but it seems to have gotten worse, to where I'm at a point where I can only manage a few seconds of startup before it blacks out again, either off or again, into an unwakeable darkness.
It's the same with just battery, battery & AC, or just AC. It wont stay on long enough for me to start from CD, neither will it stay on to let me Firewire my info/account to another Mac.
At times when I cannot start at all, I can hear a small 'electrical snap' (best description I can give) when pressing the power button, whichever combination of power source I use. I guess this is normal, but I wouldn't notice it usually.
For anyone who've had their MacBook Pro with "Random Shutdown" fixed by Apple out of warranty, could you give an example of cost?
Thanks
Sion Joyce

i dread to think how much it would cost, but i was having random shutdown problems as of last week. completely out of the blue
but, the latest Firmware update seems to have solved it! not before i went and bought another battery of course
one thing i have noticed though is the eta on the battery fullness is completely random now, it'll go from having about a minute left to having an hour and 30mins

Apple is there going to be an update for the iPod 4?

is there going to be an update for iPod 4

As Apple said in June, iOS 7 is not compatible with the 4G iPod. Not enough RAM
All the iOS devices compatible (iPhone 4 and later, iPad 2 and later, and 5G iPod touch) with iOS 7 have at least 512 MB of memory (RAM). The 4G iPod only has 256 MB

Another Random Shutdown Thread!

Hey all
So, ive got the random shutdown prob. Ive downloaded the firmware update and when I go to install it im told its not needed, I tried the battery update..and still the prob persists. Is it just that my battery is a dud?
Thanks !
Kasra

Yeah, I was suprised about that too. I'm sitting outside the Apple Store right now with my replacement. I demonstrated the crash once to the guy by running yes, and then it crashed again on him while he was trying to look at the logs.
This one's a week 32. I'm currently running yes in two Terminal windows and all seems well. Let's hope it stays this way!
edit: I think the problem with my old MacBook was with the temperature sensors or with the fans, because I didn't hear the fans kick in once while I was using it and the fans just kicked in on this one. Strange thing is, it crashed even when it was cool to the touch. Just thought that was worth mentioning...

Shuts down when entering Yahoo Groups --npYState.dll is only located in Mozilla's block list in 2 locations? Obvioiusly they either are not blocked or there is another problem?? Please advise

When opening Yahoo Groups Firefox immediately shuts down. NSBrowserOpt.dll is not in the component file........
npYState.dll is only located in 2 locations of Mozilla's Blocklist.
Obviously these files are either not blocked or there is another problem not addressed in the Help topics???

I think this problem may be caused by Yahoo's changes making it incompatible with the klatest version of FireFox.
This is suddenly affecting many many people who use Firefox and are members of Yahoo Groups. All these people say they themselves changed nothing and have not been locked out before when using Firefox. But suddenly, within the last week, they are.
What did Mozilla do or what did Yahoo do to cause this problem? I can say that I was not blocking cookies and after trying a number of things to fix it, I went to Yahoo's home page and navigated to my group from here.
This problem is not anything a user did. Either Firefox is at fault or Yahoo is. I want to know which company is at fault and when they are going to fix it.

Running another thread not to block UI

I do some heavy operation inside the actionPerformed (load images from File Chooser, resize it for display and populate it in the ScrollPane etc) and I realize that the windows freezes until the whole operation is finished. And it doesn't really help that I do repaint() or validate(). I make some research and some of the books and people from forums say that I actually needed to dispatch another thread to run the heavy operation. So that I won't block the UI interface and can update things accordingly. But the problem is, I don't have any clear example to understand this concept. How to clean up the thread after operation finished. How can a thread notify the progress back and etc. I need to know how much images has been loaded so that I can update the progress bar and so on. Can anyone help me point out a good example? :D

Think I should show my code snippet to you
public void actionPerformed(ActionEvent e) {
        if (e.getSource() == BtnBrowse) {
            int returnVal = fcSelectFile.showDialog(this,"Select");
            if (returnVal == JFileChooser.APPROVE_OPTION) {
                file= fcSelectFile.getSelectedFiles();
                //This is where a real application would open the file.
                Thread worker=new Thread(){
                        public void run(){
                            int count=0;
                            selectedFile=new JLabel[file.length];
                            while(count<file.length)
                            {   final int index=count;
                                String actualFile=file[count].toString();
                                String fileName= file[count].getName();
                                selectedFile[count]=new JLabel(createImageIcon(actualFile,fileName));
                                SwingUtilities.invokeLater(new Runnable(){
                                public void run(){
                                PnlImageHolder.add(selectedFile[index]);
                                PnlImageHolder.repaint();
                                PnlImageHolder.validate();
                                count++;
                worker.start();
                ScpImageScroller.getViewport().add(PnlImageHolder);
}

I am going on vacation and do not have other Apple products. Is there some way to retrieve my iMac info? on another pc?

I AM GOING ON VACATION AND DO NOT HAVE OTHER APPLE PRODUCTS. IS THERE A WAY TO RETRIEVE MY IMAC INFO?

IS THERE A WAY TO RETRIEVE MY IMAC INFO?
Are you asking if another computer, Mac or PC, can connect to your Mac at home over the internet and access your data? If so, it is a bit challenging for a novice, but yes, it can easily be done with the right software on both computers.

When I got the prompt to update my iPod Touch 4th generation, the update claimed to have over 200 new features including Siri. Is there going to be another update that would make this a true statement?

When I got the prompt to update my iPod Touch 4th generation, the update claimed to have over 200 new features including Siri. Is there going to be another update that would make this a true statement?

No Siri on 4G Footnote 2 of
Apple - iOS 6 - iPhone, iPad, and iPod touch get 200+ new features.
says:
Siri is available on iPhone 4S, iPhone 5, iPad (3rd generation), and iPod touch (5th generation) and requires Internet access.

Close a blocking wait thrad by another thread

Hi all
I have a lookup method which makes a blocking wait and I want to close this lookup if the content not available for 10 seconds.
What I have done is put this lookup in a thread(LookupThread) and used separate thread(TimeCheckThread) for calculate the elapsed time.
This is my idea
public class LookupThread extends Thread
    Calendar cal = Calendar.getInstance();
    boolean closed = false;
    public TimeCheckThread getTimeChecker()
        return new TimeCheckThread();
    public void run()
        lookMethod(); // this is the blocking wait
    public class TimeCheckThread extends Thread
        long startTime = cal.getTimeInMillis();
        public void run()
            // strted looking for elapsed time
            while(true)
                cal = Calendar.getInstance();
                if(cal.getTimeInMillis()-startTime > 10000 & !closed)
                    // if 10 seconds elapsed close the thread which makes the blocking wait
                    LookupThread.super.stop();
                    closed = true;
                    // to exit from time check thread
                    break;
    public static void main(String args[])
        LookupThread v = new LookupThread();
        v.getTimeChecker().start();
        v.start();
}The problem is closing of thread is deprecated.
LookupThread.super.stop();So any idea to handle those blocking wait situations and assign a return time other than this approach?

WirajR wrote:
Also TimeCheckThread eats of CPU time for 10 seconds use a java.util.Timer instead
>Also TimeCheckThread eats of CPU time for 10 seconds use a java.util.Timer instead
Hi
I think this is the most suit to my requirement. Totally different way, but acceptable.
To EJP
Ur solution seems great to replace following code segment
public class TimeCheckThread extends Thread
        long startTime = cal.getTimeInMillis();
        public void run()
            // strted looking for elapsed time
            while(true)
                cal = Calendar.getInstance();
                if(cal.getTimeInMillis()-startTime > 10000 & !closed)
                    // if 10 seconds elapsed close the thread which makes the blocking wait
                    LookupThread.super.stop();
                    closed = true;
                    // to exit from time check thread
                    break;
    }like following
public class TimeCheckThread extends Thread
       public void run()
                    TimeCheckThread.sleep(10000);
                    LookupThread.super.stop();
}To Peter__Lawrey
Why don't you make the blocking lookup block for only 10 seconds?Any idea to implement such blocking lookup block?
My blocking operation is a looking for RTP video stream. It waits until server sends the video

Is there going to be another iPod touch 2 generation iOS update?, Is there going to be another iPod touch 2 generation iOS update?, Is there going to be another iPod touch 2 generation iOS update?

Is there going to be an iOS update for an iPod touch 2 generation?

Since we are all only end users like yourself, nobody here would know such information, and it's against the Terms of Use of these forums to discuss such things.
However, with that said, it's likely that the 4.2.1 update is the last the 2G iPod Touch will ever see, but again only Apple only knows.
B-rock

Random shutdowns/backlight shutoff.

Hi - I'll try to keep this saga brief, but that may be a tall order considering the circumstances.
Back story:
The first time I sent my iBook G4 in to AppleCare was June 2006, when the display was showing a single, pixel-high line across the bottom of the screen (about 1/2 inch up from the bottom) when I would adjust the angle of the lid. It came back fixed, but with a worse display issue! Instead of just a line, the screen would now flicker (NOT a backlight problem, in random stripes across the display itself) and turn to grayscale instead of the normal colors. It did this in response to the slightest vibrations (typing, touching the trackpad) and adjustments of the lid. I sent it in again with explicit information about what caused the malfunction and how to replicate it.
The iBook was promptly sent back to me, without any contact being made beforehand, because the techs "couldn't recreate the problem." Great. Allow me to note that I "recreated" the problem the FIRST time I booted it up out of the return box from AppleCare - within about thirty seconds. Needless to say, at this point I was less than pleased. I wound up taking the iBook into the university bookstore, where we have an Apple tech but not a full genius bar. I was able to show him the problem in person and leave the iBook in his care. Several days later, I found out that he had to ship it off to AppleCare anyway because it was something they'd looked at before.
It finally came back and yes, the display was no longer going wonky, but I now had a lid that would not align properly and thus would not latch, a non-working microphone, and a small scratch on my LCD. I had let the lid and scratch slide for a couple of weeks, but was getting ready to call Apple Care about the microphone (I needed it for a class) when my hard drive decided to take a nosedive. Over a series of a few crashes, in the midst of which I was able to back up my most important materials - thank goodness - the hard drive completely died and the iBook would eventually either only boot up to a blue screen, a gray screen with the apple and spinning gear, a gray screen with nothing, or a blue screen with an OS 9 icon in the middle. Off it went to Apple Care, AGAIN.
It came back today with a new hard drive. I used it for a few minutes before retrieving my power source, thinking it would be fine since though my battery runs down quickly, it was showing a 65% charge and I had a few minutes. At this time, I was still using the pre-installed Panther and getting ready to reinstall Tiger and all my other stuff. I was chatting on iChat when the iBook completely shut down.
I went and got my power source, plugged it in, and booted back up. I got an error message saying my date and time was set to some time before 2001... Except when I actually checked my clock/calendar, it was set to the correct time. My friend suggested I might need to do a PMU reset, so I shut down and did so.
The iBook worked fine for a couple of hours, until my backlight randomly turned off. It did NOT go to sleep - the backlight just turned off. This has never happened to me before - I could barely make out the outline of my open windows on the screen, so I knew it was the backlight out and not a crash. I closed the lid and the backlight flickered on the way down. When I re-opened it, the light came back on.
Several hours later, after I'd reinstalled Tiger, with a 99-100% charged battery, with my power source plugged in and the light green - another crash. I believe this was an ACTUAL crash, like the first one I described. I attempted to restart the iBook and it wouldn't power back up. I tried several times, then did another PMU reset, and it finally booted back up.
MOMENTS after it powered back up from crash #2, crash #3 occurred. Or so I thought. The iBook would again not respond to the power button, so I shut the lid and heard a chime after it was shut. I reopened the lid and the iBook was booting back up. I don't know if this was a backlight malfunction I mistook as a crash, or what.
Note: none of the times the laptop actually CRASHED did I get a low battery warning or any advance indication I was having some sort of a power failure.
On to another backlight failure: it was about an hour after the last crash. I was configuring some World of Warcraft settings in windowed mode, with the battery at full charge and the power source plugged in and green. The screen went black and the laptop made a clicking/swishing noise I associate with shutting down. As I was preparing to throw it at the wall (kidding) I noticed that I still felt a slight vibration and heard a slight humming from the body of the iBook. I listened and looked carefully, and sure enough, the iBook was still running, but the backlight had again failed. (Apparently the backlight shutting down is the noise I'm familiar with.) I moved my cursor around, tried hitting "esc" and doing other "wake up" things but nothing would work. This time, shutting and reopening the lid also did nothing. I couldn't see anything to do a regular shutdown, so I did a hard shutdown by holding down the power button. Upon rebooting, the backlight worked like a charm.
Thirty minutes after this, I experienced another actual crash - complete shutdown of the system. I was playing World of Warcraft in fullscreen mode when the screen went black and all system stopped. No noise, no vibrations - it was definitely off this time. I attempted to power back up but again the iBook would not respond to the power button. I closed and reopened the lid, and it still would not respond. I reset the PMU and nothing happened. Finally, I removed and reinserted the battery and it then booted up. Upon booting this time, I again got the clock/calendar set to pre-2001 message, and yet the clock and calendar were both set to the correct time. The battery showed 97% charge, and the power supply had been connected the entire time.
So, that leads me to now. I have no clue what is wrong with it at this point and I am absolutely frustrated that every time I send this thing into Apple Care it comes back with problems - either the same problems, not fixed, or entirely new problems it didn't have before.
I'd really appreciate it if somebody could give me a clue what might be going on here. I repaired permissions, attempted to repair the disk (no repair was necessary) and am currently getting all the updates to take me from OS X 10.4 to 10.4.8. I'm just frustrated because I'm the only person I know out of a whole bunch of very happy Mac customers to have this many problems - I really feel like I have a lemon, but I was told last time I spoke to Mac that they won't completely replace my unit unless I have the SAME problem repaired three times. I'll avoid getting ranty here, and I do plan to call Apple Care in the morning (Saturday 12/1) but I thought I'd post here anyway to see if anybody had any ideas or anecdotes they'd like to share.
Some ideas I have that could be wrong:
-- Logic board failure (Could explain the prior display issues and hard drive failure, I think)
-- Battery (I know it's not holding a charge well, but I don't see what that would have to do with the backlight)
-- Backlight out (Unrelated to crashes?)
That's all I've got. Any help would be greatly appreciated.

Hi, and welcome to Apple Discussions.
random stripes across the display itself
Sounds like the infamous logic board problem that plagued the iBook G3 (Dual USB).
When the iBook does a hard shutdown, it would be normal to get the message about the date being wrong. It's possible that if it automatically connects to the internet, it may immediately automatically reset so that when you check it, it's correct.
Backlight problems? Again, familiar to many G3 owners:
http://discussions.apple.com/thread.jspa?threadID=207731&tstart=0
AppleCare's your best bet, but this will give you some "light" reading and something to think about until you get them called.
Good luck.

Random Shutdown Because of Heat Sensors?

I bought my white MacBook in mid-May (week 19 production) and it worked fine with the exception of a whine when I did not have the iSight Cam on, the occasional mooing after using the computer heavily then using the CPU lightly for a while, and the discoloration. If you ask me it wasn't that much of a set back because this computer was fast and reliable... or so I had thought!
All of a sudden about a week ago, after I had the discoloration fixed, thanks to AppleCare (which only took 5 days), my computer shut down randomly in the middle of light usage...
At first I had thought that my external hard drive was the problem and I was very upset that this had happened. I tried to reboot my computer, but all that would happen was the usual DVD drive start up sound and then it would turn off again. I tried about 5 times to restart it with no luck, so I walked away. About 20 minutes later I was able to start it back up...
After not using my external hard drive for a day, it happened again, in the middle of normal internet browsing and listening to music it randomly shutdown. I thought that maybe it was an OS 10.4.7 issue, because I had not had any problems with x.6, so I erased and restarted from scratch, and once again, another MacDeath. Once again, I thought it to be my fault in my installation of 2Gb of RAM. I re-installed the custom 2x256 RAM that came with the computer ( and will remain in my hands forever, because you can't even pay someone to take away a stick of 256Mb RAM these days) well after the old RAM was forcefully shoved back in, it died again! This is when I started to get mad...
I put up with the whinning, I put up with the heat, I put up with the discoloration (for a while), but now this? WHY!
Over the next week it happened almost daily and sometimes when I would turn on my computer after it being off for at least 5 hours, it would load my home screen and after about a minute I would hear the fan come on for a few seconds, and then it would die again. I noticed that most times that my MacBook would shutdown unexpectedly, the fan had just turned on for a few seconds or I was playing a game and the fan was already on...
So today I called AppleCare and I had to wait about 30 minutes before I talked to someone... (When I called last time about discoloration, the wait was about 5 minutes) So either there are more and more angry customers calling, or Apple is firing employees to increase their stock value...?
When I finally got through the man told me that it was most likely not the Logic Board, but instead FAULTY HEAT SENSORS and/or FAULTY HEAT SINK APPLICATION. I won't lie I have seen Core Duo Temp show readings as high as 91 C (about 196 degrees F). I knew that this things got hot, but not so hot as to start a fire if left on too long....
So I am getting a box from DHL tomorrow (woohoo) MacB. and I get to part ways again, but this time, from reading many threads, I assume our time apart will be much longer approaching around 2 WEEKS!!!
All I hope is that AppleCare will fix the heat sensors that are supposed to shutdown the computer when it gets overheated.... I have to go to school in about a month and I will not have time to deal with these kinds of issues! I really like the MacBook and all of it's features, but I did not sign up to get a MacDieOnMeBook!
APPLE USE SOME OF THE 24% SALE INCREASE THIS QUARTER TO HELP YOUR LOYAL CUSTOMERS WHO HAVE BEEN WITH YOU THROUGH THE GOOD AND THE BAD!
MB 2GHz White 2GB RAM - 250 GB External HD Mac OS X (10.4.6)

As of yet i'm not exactly sure about the heatsink problem, although a few in here have reported machines that work well after having this part replaced, while others who only had the MLB replaced reported a recurrence of the problem.
as for the volume indicator, i noticed that mine did that too, but it was in fact muted whether or not the tool bar indicated it. i dismissed this as a small quirk, similar to when my volume indicator didnt change as i pressed the volume buttons on my old laptop. but so long as there was an acknowledging "squirt" noise on the computer indicating change of volume, that shouldnt be a problem.
good luck withyour MB

Catching an exception thrown from another thread

I have a SocketServer that creates new threads to handle incoming clients. If one of the threads throw a SQLException is it possible to catch that exception in the SocketServer that created that thread.
I tried implementing this code and I cannot get the server to catch an exception thrown in the thread. Are my assumptions correct?
I was reading something about Thread Groups and implementing an uncoughtException() method, but this looked like overkill.
Thanks for your time!
Some Example code would be the following where the ClientThread will do a database query which could cause an SQLException. I'd like to catch that exception in my Socket Server
      try
             new ClientThread( socketServer.accept() , host, connection ).start();
      catch( SQLException e )
             System.out.println( "DataSource Connection Problem" );
              e.printStackTrace();
      }

hehe, why?
The server's job is to listen for an incoming message from a client and pass it off to a thread to handle the client. Otherwise the server will have to block on that incoming port untill it has finished handling the client and usually there are many incoming clients continuously.
The reason I would want to catch an exception in the server based on the SQLException thrown in the thread is because the SQLException is usually going to be due to the fact the datasource connection has become unavalable, or needs to be refreshed. This datasource connection is a private variable stored in the socket server. The SocketServer now needs to know that it has to refresh that datasource connection. I would normally try to use somesort of flag to set the variable but to throw another wrench into my dilemma, the SocketServer is actually its own thread. So I can't make any of these variables static, which means I can't have the thread call a method on teh socket server to change the status flag. :)
I guess I need implement some sort of Listener that the thread can notify when a datasource connection goes down?
Thanks for the help so far, I figured java would not want one thread to catch another thread's exceptions, but I just wanted to make sure.

Will the console log show a history of random shutdowns?

My macbook has suddenly started the random shutdown problem. It started a couple of days ago, I'd had no problems up until then. At one point today it was shutting down immediately on waking from sleep, and then would only stay on for about two minutes with the fans racing before, bang, off it would go. I left it alone in exasperation, then returned to try again, and this time it lasted around an hour before shutting down repeatedly again. I will need to take it home to the UK to my local Apple service centre and I am worried that if it doesn't actually shut down in front of them when they have it they will tell me there is no problem and won't repair it. I know that this macbook has the RSS issue now but it really is random, so can I prove it from the console log? I looked through this just now and of course most of it means nothing to me but I did notice that there was a line saying "cause of last shutdown -72" occuring many times since this started. Does anyone know what this refers to and will it show that the problem is definitely happening?

What does the holding the button down trick do?
From the Apple article I referenced in your earlier thread:
"If your MacBook is in a state where it will not remain on long enough to install the update, wait for the issue to reproduce itself. Once the MacBook has turned itself off, turn the computer on the by holding the power button down. Keep the button down until you hear a single long tone. Once you hear the tone you can release the button, install the recommended updates, and restart as you would expect."
Allegedly, this throttles the CPU to 1 GHz.
And I am slightly worried that a2dox says that the
problem returned even after the repair..!
Different experiences for different people, during the period when Apple had not yet figured out the problem. Their contract repair facility was doing different repairs, some getting heat sink replacements, some logic board replacements, some both, and, later, some a differently designed heat sink. When one of those repairs didn't fix the problem, they would do another.

There goes another thread on Random Shutdowns blocked by apple...

Similar Messages

Maybe you are looking for