‘Blue Screen of Death’ hits some iPhone 5s owners

“The infamous “blue screen of death” seems to have expanded from Windows PCs to iPhones,” Lance Whitney reports for CNET.

“Several iPhone 5S owners report that their phones are turning a mean shade of blue and then restarting,” Whitney reports. “Users chiming in on the Apple Support Communities and MacRumors forums said the problem occurs when they use the Numbers app in Apple’s iWork suite, which comes free with the new iPhones. But a couple of people report that it also happens when using the ESPN ScoreCenter app.”

Read more in the full article here.

“Videos detailing the issue show that multitasking between apps seems to trigger the BSOD. iPhone 5S users are also reporting random reboots during device use,” Tom Warren reports for The Verge. “Apple has released iOS 7.0.2 to primarily fix lock-screen security bugs, but the latest version does not address the reboot issues.”

Warren reports, “One workaround to alleviate the iWork-related reboots is to disable iCloud syncing for Apple’s Pages, Keynote, and Numbers apps.”

Read more in the full article here.

MacDailyNews Take: Well, now, there’s some good PR. At least make iOS crash to a different color, Apple. Sheesh.

40 Comments

  1. This is not a bad thing. When we see how Tim handles this blunder, more people will realize what has to happen. When are the lemmings on this site going to quit calling everyone a troll who points out the reality of what’s going on with the once great company? Never? Yeah, that’s what I thought. Flame on… this time in blue.

    1. @Jay Morrison

      I won’t call you a troll, but I will ask why you insist on pretending that all Apple product rollouts were flawless when Steve Jobs was in charge. If memory serves, he was CEO during iPhone 4 Antennagate (an overblown issue) and the MobileMe rollout (a true fiasco).

      The 5S has been out for less than a month, the issue seems to be affecting a very small number of users exercising a somewhat isolated use case, and the problem may be something that can be fixed quickly. Please get a little perspective.

      1. Exactly. I could go on for hours talking about all the things Apple did wrong when Jobs was running the show, and even more when he wasn’t.

        I suspect that those who think Tim Cook’s performance is somehow inferior to Jobs’ just haven’t been around long. I’ve been working with Apple products since the late-70’s, so I’ve seen it all, and I’ve been there through thick and thin.

        Product development – especially pushing the envelope – is messy. There are bugs, fixes, and even recalls. Sometimes things go really wrong. No design is perfect and there will always be flaws. Get over it.

        So far, I haven’t seen a single thing that Apple’s done (or hasn’t done) under Tim Cook’s leadership that Steve Jobs couldn’t have done himself. Well, except for giving everybody vacation time for the holidays. Jobs was too much of a hard-ass for that. Maybe it’s good – I don’t know. I’m not the CEO of Apple, and neither is anybody else unless they’re Tim Cook.

          1. Non-existing cracks in Mac Cubes… What was reported as cracks were MOULD LINES. antenna-gate was a coordinated FUD attack by competitors in the United States evident by the fact that no iPhone 4 models—unmodified from the models sold in the US—demonstrated any such problems when released in the rest of the world’s nations. . . but I will grant you inviting Eric Schmidt onto Apple’s Board of Director’s was a world class screw-up.

    2. Apple and it’s old school operating systems cannot keep up with the competition. Apple is about to feel the wrath of what it is like to have to keep up with the Jones’s!

      1. Way to deflect! Apple’s BSOD is better because after we have a hard crash, we automatically reboot! Yay!

        It is getting more and more ridiculous what lengths fanboys will go to defend their religions.

        Apple may be the best, but it needs to improve significantly to achieve anything close to perfection. This is increased evidence that iOS7 is simply not up to reasonable longtime Apple users’ standards. Try again, Cook & Co.

          1. Scott, congratulations on your kindergarten words of the day.

            Jobs would have used them effectively on the iOS development team if this happened under his watch. Now self-proclaimed Apple fans just deny that there is an issue and attack anyone who states otherwise. The juvenile behavior does nothing for your credibility, and it sure as hell doesn’t reflect well on Apple either. Good companies make mistakes, great companies own up to them and fix them.

            We shall see if Cook chooses to allow Apple to slip from great to good — on the software quality front, a lot of us are having more and more concerns. On the hardware front, all seems well.

    1. I had a lockup when an iMessage arrived while my screen was locked. I tried to swipe the message to routinely enter my PIN and reply to the message, but the screen became unresponsive, so I had do a shutdown/restart to get back to normal.

  2. Melodramatic much?

    Death implies a measure of permanence. Though Windows machines can certain blue screen and come back in working order, the term “Blue Screen of Death” was coined to describe a situation where the OS was completely hosed, not just rebooted – in other words, “dead”.

    Tying an OS hang that results in a quick reboot to the infamous BSOD on Windows is a bit of a stretch, don’t you think?

  3. I ran into one issue where Safari just quits. I tried clearing the app, but it still quit. A reboot of the phone fixed it. I’m confident Apple will address this soon enough. As stated earlier, it’s pretty much impossible to release something like a new OS and have it be flawless out the gate. On top of that, I’m sure many Apps still need to be tweeked as well as be made 64 bit. Patience Padwan, I’m sure the engineers at Apple are still putting in long days getting this thing as close to perfect as they can. Unlike most non iOS devices, it’s very easy to run updates when they’re made available. Should be interesting to see how things stand six months from now.

  4. Yep, Cook & Ive have Apple clicking on all cylinders and are giving employees a shitload of time off since they have successfully FUBARed the iPhone into a tacky mess for the hipsters.

    First, slow sales of the plastic craptastic 5C and now the BSOD imported.

    Nice work, have a cigar.

    scha·den·freu·de noun \ˈshä-dən-ˌfrȯi-də\
    : a feeling of enjoyment that comes from seeing or hearing about the troubles of other people
    Origin
    German, from Schaden damage + Freude joy
    First Known Use: 1895
    http://www.merriam-webster.com/dictionary/schadenfreude

  5. I’ve had frequent freezes and restarts since I installed iOS 7 on my iPad 3. No “blue screen” though. It occurs at any time without using iWork. There are no particular apps that seem to cause it, although App Store upgrades may do it if they are large files. iTunes synching will usually cause it too. Forced restarts take about ten minutes before I can use my iPad again. My friend’s iPad has the same problem – random restarts through the day and they do not have iWork.

  6. Between this report and the 2% crashing apps reports on the 5s, I’m getting the idea that the APIs for the A7 aren’t quite ironed out yet. Again, I’m betting it’s the usual bad memory management coding, the scourge of modern programming. But this is a new CPU and is going to have quirks. We’ll see as the ‘bleeding edge’ reports continue.

  7. GoodReader is blue-screening my 5S on exit, but I’ve had no other such promises. The developer has been very responsive, and is hoping to find a fix before Apple does.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.