Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Tuesday August 23 2016, @04:16PM   Printer-friendly
from the BBSoD-BIG-Blue-Screen-of-Death dept.

from the beat-this dept.

Via El Reg, Richard Chirgwin asks if anyone has seen a dramatic failure of Microsoft's OS. One assumes that he is referring to very public instances.

In Topper style, he starts off with a real beauty[1] that was spotted in Thailand.

In the comments, cornz 1 mentions seeing every screen at Schiphol Airport (Amsterdam) BSoD'd; Shadow Systems says he had to go to the other side of town when his branch bank's ATM BSoD'd; Robert Helpmann wasn't thrilled when the hotel elevator that was to take him up 20something storeys was showing a BSoD; James 51 also notes that Blue Screens are not a thing of the past, as his wife's Windows 10 update BSoD'd.

[1] If you have Facebook blocked, I have saved you the trip to Blake Sibbit's Facebook page.

Hat tips to TechWorm (though I wish you wouldn't put parts of your content behind scripts) and to Archive.is (which will run scripts for you on their machines).


Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by DannyB on Tuesday August 23 2016, @04:44PM

    by DannyB (5839) Subscriber Badge on Tuesday August 23 2016, @04:44PM (#392205) Journal

    To continue what?

    To install Windows 10 from the BSOD maybe?

    --
    People today are educated enough to repeat what they are taught but not to question what they are taught.
    • (Score: 2) by SomeGuy on Tuesday August 23 2016, @06:48PM

      by SomeGuy (5632) on Tuesday August 23 2016, @06:48PM (#392240)

      Under Windows 95/98/ME the errors reported by BSODs were not always truly fatal, and they would often let you attempt to continue... usually with bad results. In fact the "BSOD" was introduced in Windows 3.0 and was intended for use as a somewhat general purpose full screen error message, with the logic being some kinds of errors might occur from a full screen DOS session. They were used for certain kinds of disk read errors, in which you would also normally want to continue. As I recall, some of these "BSOD" disk errors were still possible to see in Windows 9x.

      • (Score: 2) by Joe Desertrat on Tuesday August 23 2016, @08:47PM

        by Joe Desertrat (2454) on Tuesday August 23 2016, @08:47PM (#392291)

        Under Windows 95/98/ME the errors reported by BSODs were not always truly fatal, and they would often let you attempt to continue... usually with bad results.

        Yeah, I think that was a deliberate trick to get you to expose more data to file corruption.

      • (Score: 0) by Anonymous Coward on Thursday August 25 2016, @06:45PM

        by Anonymous Coward on Thursday August 25 2016, @06:45PM (#393128)

        As I recall, some of these "BSOD" disk errors were still possible to see in Windows 9x.

        Not sure if I'm really not misunderstanding you.... But I've seen full screen BSOD disk errors in Windows XP and Windows 7, sunshine.
        Haven't seen 'em in Win 8.1, though I try to stay the hell away from 8.1. And I don't have enough experience yet in 10, we only just upgraded our company and I refuse to support Microsoft any longer at home.

  • (Score: 4, Interesting) by zocalo on Tuesday August 23 2016, @04:45PM

    by zocalo (302) on Tuesday August 23 2016, @04:45PM (#392206)
    I've noticed digital advertising & passenger information screens on numeous occassions in a Windows BSoD situation, but the largest and most public was one of those in Jelačića Trg in Zagreb Croatia - not a five story monster, but in a very public place where many people catch the metro and shop. I've also seen (on just one occassion!) one that had crashed out to a Linux prompt on a trade stand, albeit some years ago now; props to Intel for using Linux in the first place, and for all the freebies their sales droid gave my colleague and myself when we fixed it for them. :)
    --
    UNIX? They're not even circumcised! Savages!
  • (Score: 0) by Anonymous Coward on Tuesday August 23 2016, @04:52PM

    by Anonymous Coward on Tuesday August 23 2016, @04:52PM (#392210)

    As a Windows driver developer, all I can see in the first picture is that the bugcheck was PAGE_FAULT_IN_NONPAGED_AREA (someone touched a bad pointer) and the faulting code was (likely) in FTDI's serial driver. I hope the sign owner at least sent FTDI the dump so that they could fix their crappy code - or maybe the bug has been fixed already and this machine has been sitting untouched in a closet for 10 years.

    • (Score: 2, Informative) by Anonymous Coward on Tuesday August 23 2016, @05:36PM

      by Anonymous Coward on Tuesday August 23 2016, @05:36PM (#392217)
      • (Score: 1, Insightful) by Anonymous Coward on Tuesday August 23 2016, @06:32PM

        by Anonymous Coward on Tuesday August 23 2016, @06:32PM (#392231)

        So not only are their driver developers shit but so is their management. In that case I hope they didn't get the dump.

      • (Score: 3, Touché) by DannyB on Tuesday August 23 2016, @06:45PM

        by DannyB (5839) Subscriber Badge on Tuesday August 23 2016, @06:45PM (#392239) Journal

        You wouldn't have to worry about whether you had clone FTDI chips if you would stop using Arduino and just use a 555 which is the proper way to blink an LED.

        --
        People today are educated enough to repeat what they are taught but not to question what they are taught.
        • (Score: 2, Informative) by anubi on Wednesday August 24 2016, @05:39AM

          by anubi (2828) on Wednesday August 24 2016, @05:39AM (#392476) Journal

          Since the FTDI fiasco, I had to find alternatives to FTDI chips:

          CH340G ( Dream City - Chinese )

          CP2102 ( Silicon Labs )

          PL2303 ( Prolific Technologies )

          These have different packages and pinouts, and require their driver, but are functional drop-in replacements. I designed my stuff to use the CH340G.

          So far, I have had no more problems.

          --
          "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]
          • (Score: 2) by DannyB on Wednesday August 24 2016, @04:47PM

            by DannyB (5839) Subscriber Badge on Wednesday August 24 2016, @04:47PM (#392653) Journal

            “It’s no good, it’s no good!” says the buyer — then goes off and boasts about the purchase.", Prov 20:14, NIV

            Of course, a better solution would be a single, open source driver, for poor Windows users, that works with all FTDI chips and clones.

            --
            People today are educated enough to repeat what they are taught but not to question what they are taught.
    • (Score: 2) by tibman on Tuesday August 23 2016, @08:43PM

      by tibman (134) Subscriber Badge on Tuesday August 23 2016, @08:43PM (#392289)

      Fatal exception 0e happens for so many random things. It just looks to me like you are pushing an anti-FTDI agenda. It is so out of place here that it makes me think every AC commenting on FTDI is the same sockpuppet.

      There's no need to invent some BS reasons to hate on FTDI. They have plenty of real reasons.

      --
      SN won't survive on lurkers alone. Write comments.
      • (Score: 1) by anubi on Wednesday August 24 2016, @06:01AM

        by anubi (2828) on Wednesday August 24 2016, @06:01AM (#392486) Journal

        This FTDI thing burned a lot of people. I am one of them. It made a lot of work for me to re-layout the PCB so I could use an alternative part.

        Its not in my nature to sell something I know is apt to cause my customer a lot of problems.

        That was the prime reason I started building Arduino-compatibles in the first place. I could not trust a large complex system to reliably do sequences of simple primitives. Actually, it is more my problem, as things got so big I could no longer understand exactly what the thing was going to do under any circumstances.

        There is not much harm done if an advertising display shows BSOD, but what if this is in some sort of robotics like a bottling plant? A computer that had just a fraction of second's inattentiveness to the process could easily result in tens of thousands of dollars worth of spoiled product. I do not work for the big guys.. as I have a hard time working with managers that want to see name brands all over everything. I work for the small guy on his way to becoming big. If the big guy wants me, I have to report to him, not his non-technical management minion.

        We are not all the same sock puppet, cause I know *I* did not author a lot of anonymous posts I have seen on the same subject.

        --
        "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]
        • (Score: 2) by tibman on Wednesday August 24 2016, @01:30PM

          by tibman (134) Subscriber Badge on Wednesday August 24 2016, @01:30PM (#392556)

          They certainly did lose customers over their driver update shenanigans. But the ACs assertion that this BSOD was caused by FTDI is really out there.

          --
          SN won't survive on lurkers alone. Write comments.
  • (Score: 2) by MichaelDavidCrawford on Tuesday August 23 2016, @09:09PM

    by MichaelDavidCrawford (2339) Subscriber Badge <mdcrawford@gmail.com> on Tuesday August 23 2016, @09:09PM (#392306) Homepage Journal

    but that five-storey BSoD made me smile, then it made me laugh.

    --
    Yes I Have No Bananas. [gofundme.com]
    • (Score: 0) by Anonymous Coward on Wednesday August 24 2016, @02:09AM

      by Anonymous Coward on Wednesday August 24 2016, @02:09AM (#392414)

      Glad to be of service.

      -- OriginalOwner_ [soylentnews.org]

  • (Score: 0) by Anonymous Coward on Tuesday August 23 2016, @09:21PM

    by Anonymous Coward on Tuesday August 23 2016, @09:21PM (#392311)

    that Windows is not ready for the desktop and your average user.

    • (Score: 0) by Anonymous Coward on Tuesday August 23 2016, @09:41PM

      by Anonymous Coward on Tuesday August 23 2016, @09:41PM (#392323)

      Who says it was the users fault? looks more like a bad developer, in this case.

      ( yes windows sucks, but blame the correct parties or you just look silly )

  • (Score: 2) by srobert on Tuesday August 23 2016, @10:19PM

    by srobert (4803) on Tuesday August 23 2016, @10:19PM (#392345)

    EOM

  • (Score: 0) by Anonymous Coward on Wednesday August 24 2016, @06:02AM

    by Anonymous Coward on Wednesday August 24 2016, @06:02AM (#392488)

    My mother called, said her computer had performed an illegal function, wanted to know if she should call the police. Never occured to her with the 409 scam, though. And a blue screen of death killed my grandfather. It said, "fatal error". He said, "sorry", and went to make his maker, which thankfully resides no where near Remond, WA. This could spread. It's like the Ring: Or the RotRing of death, also courtesy of Micro$Oprt. Bastards. Killing my family slowly. Now only I am left, locked in my fortress of solicitude, running only linux, but worried about the systemd. They howl, when them come. I batten the doors. So far I have been able to keep it at bay, but it is only a matter of time.

  • (Score: 2) by Nuke on Wednesday August 24 2016, @02:16PM

    by Nuke (3162) on Wednesday August 24 2016, @02:16PM (#392574)

    The links are to pictures so small that you cannot read whet is going on. Yes I can recognise it as a BSOD, but not much good for adding to a crash gallery like this one :-

    http://telcontar.net/store/archive/CrashGallery/?page=5 [telcontar.net]

  • (Score: 0) by Anonymous Coward on Monday August 29 2016, @09:21PM

    by Anonymous Coward on Monday August 29 2016, @09:21PM (#394934)

    Among the folks sending in their experiences/photos, there was one that did top the touchstone example.
    SIX storey #fail at Manchester Piccadilly Station [theregister.co.uk]

    There are plenty more we'll give you in the coming weeks

    (Photos aren't behind cross-site gimmicks this time.)

    -- OriginalOwner_ [soylentnews.org]

  • (Score: 0) by Anonymous Coward on Tuesday September 06 2016, @02:54AM

    by Anonymous Coward on Tuesday September 06 2016, @02:54AM (#397954)

    Multiple folks have mentioned an elevator/lift.
    The one running Lose98 after EoL made me smile.
    More BSODs for your schadenfraude [theregister.co.uk]

    -- OriginalOwner_ [soylentnews.org]

  • (Score: 0) by Anonymous Coward on Tuesday September 20 2016, @03:30AM

    by Anonymous Coward on Tuesday September 20 2016, @03:30AM (#404107)

    BSODs of the week: From GRUB to nagware [theregister.co.uk]

    It's not always Microsoft's fault. [...] the bootloader is corrupted [...] a hard drive that's not there
    [...]
    No collection would be complete without an example of Microsoft not thinking about where its Windows 10 upgrade strategy might pop up ... like in public advertising billboards

    -- OriginalOwner_ [soylentnews.org]