ie8 fix
madison

Bountiful BSODs and beautiful dialogs [cool bugs]

By | October 17, 2008, 5:08pm PDT

Summary: Hope you enjoy these these cute images of Windows blue screens of death, assorted lame dialogs, and miscellaneous failures. (Apple folks: although most of these don’t apply to you, no gloating please!)

Hope you enjoy these these cute Windows blue screens of death, assorted lame dialogs, and miscellaneous failures. (Apple folks: no gloating please!)

Bountiful BSODs and beautiful dialogs [Friday cool bugs]

Bountiful BSODs and beautiful dialogs [Friday cool bugs]

Bountiful BSODs and beautiful dialogs [Friday cool bugs]

Bountiful BSODs and beautiful dialogs [Friday cool bugs]

Bountiful BSODs and beautiful dialogs [Friday cool bugs]

Bountiful BSODs and beautiful dialogs [Friday cool bugs]

[All images from the The Daily WTF, a great source of failure and bugs. Annotatations by yours truly.]

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Michael Krigsman is a recognized authority on the causes and prevention of IT failures.

Disclosure

Michael Krigsman

Michael Krigsman writes and speaks about technology in a manner that most observers consider to be fair and balanced. Michael believes that writing about IT failures, which often have complex causes, creates a unique obligation to be reasonable and accurate in both reporting and analysis.

Michael maintains active personal and professional relationships with enterprise technology buyers, vendors, analyst firms (or individual analysts), consultants, and system integrators. As CEO of Asuret, Michael sells and delivers paid services to members of these same groups.

Vendors regularly reimburse Michael's out-of-pocket travel expenses to attend industry conferences and events. Conference organizers frequently waive entry fees when Michael attends industry events. Michael often speaks at industry conferences and events.

He is a member of the Enterprise Irregulars, a loose association of consultants, investors, industry representatives, analysts, and users of enterprise software.

For daily updates on Michael's activities, follow him on Twitter.

Biography

Michael Krigsman

Michael Krigsman is CEO of Asuret, Inc., a consulting company dedicated to reducing technology implementation failures. Asuret's suite of software tools improve the success rate of enterprise software deployments by quantifying and measuring governance issues that cause most project failures. Michael led the research effort underlying Asuret's model of collective intelligence and its practical application to reducing IT failures in consulting environments. He is a recognized authority on the causes and prevention of IT failures and is frequently quoted in the press on IT project and related CIO issues. He is considered an enterprise software industry "influencer" and provides advice to technology buyers, vendors, and services firms.

Previously, Michael served as CEO of Cambridge Publications, which develops tools and processes for software implementations and related business practice automation projects. Michael has been involved with hundreds of software development projects, for companies ranging from small startups to Fortune 500 organizations. Michael graduated with an M.B.A. from Boston University and a B.A. from Bard College. He is a Board member of the America's Cup Hall of Fame and the Herreshoff Marine Museum in Bristol, RI.

25
Comments

Join the conversation!

Just In

Nyahahahahahahahaha!!!!!!
bendib 5th Aug 2009
I know this is an old post, but still!!! I, a linux user, will now be saving the images for future laughs.
0 Votes
+ -
And ...
n0neXn0ne 17th Oct 2008
... there is more where that came from.



^o^


0 Votes
+ -
Contributr
That is soooo funny
mkrigsman@... 18th Oct 2008
Seeing rows and rows of blue screens like that happy
failed to even prevent total Microsoft domination of the enterprise and desktop OS, what does that tell you of the competition's quality...totally crap I'd say.
0 Votes
+ -
I really don't know...
n0neXn0ne 17th Oct 2008
...What you are defending.

^o^
0 Votes
+ -
He's defending
TedKraan 21st Oct 2008
BSOD's naturally.

^o^
0 Votes
+ -
See here.
0 Votes
+ -
At least the Apple crashes
frgough Updated - 18th Oct 2008
show some variety.
0 Votes
+ -
Apple: Crash Different (nt)
NonZealot 18th Oct 2008
.
0 Votes
+ -
Thank you! I needed a good laugh! Suppose I should have added my work station at the office to the list of photos. Had to do a security update, system BSOD's on the mandatory reboot. Reboot again, system performs sluggishly. Shrug shoulders go back to fully functional Linux desktop and send e-mail for ITS to come fix their POS system... again. Continue productive work on Linux system that has been running smooth and fast for... hmmm, I have to look when I get back to work Monday! Been so long since I have rebooted I don't know how long it's been running! devil

The real irony is at least 3 times a week I see Windows work stations at my office BSOD. Again these are ITS supported systems. Meanwhile my Linux workstation just chugs right along day after day after day... TCO at it's finest! devil


Thanks for the laugh though! I am off to Laguna Seca for the races!! Pit row passes to boot! It's nice having friends in the right places!
0 Votes
+ -
Contributr
Really glad you enjoyed it
mkrigsman@... 18th Oct 2008
I decided to toss in some lighter posts in addition to the really heavy process failure ones. So, thanks for the feedback.
0 Votes
+ -
How inept is your IT Dept
AllKnowingAllSeeing 18th Oct 2008
that you'd be able to see three BSOD's at your office each week?

I've seen it 3 times in the last five years at my place of work.

Hire a real IT team, BSOD doesn't show up.

Now That's TCO! wink
0 Votes
+ -
Not my job.
Linux User 147560 19th Oct 2008
And I don't really care too much since is rarely affects me directly. Then again I also run Linux in the office along with Windows. Two identical Dell systems with the exception being hard drives, the Linux machine has more and bigger drives.

I have a performance log I keep on both machines, pretty simple log really. It is used to track reboots and why along with total uptime available between reboots, issues and such. The bottom line:

Mandatory reboots in the last 6 months I have been tracking
- Windows = 39
- Linux = 3

Scheduled Shutdown/reboots
- Windows = 1
- Linux = 1

System Errors that halted work flow
- Windows = 87
- Linux = 17

System errors that required extensive intervention (BSOD/Kernel Panic)
- Windows = 4
- Linux = 0

Average time available (average uptime)
- Windows = 6.35 days
- Linux = 93.15 days

Identical systems, the Linux machine gets pounded on harder than Windows (90% Linux 10% Windows usage split). Hire who you want, Windows still costs more and has more issues in my experience. And the workstations that are having issues... they are identical to the rigs I am running in my office. devil
0 Votes
+ -
Contributr
Compelling points
mkrigsman@... 19th Oct 2008
Of course, it doesn't change the fact that Windows has a richer set of apps available.
0 Votes
+ -
RE: Compelling points
n0neXn0ne Updated - 19th Oct 2008
It doesn't change the fact that they are Linux equivalents .



I would guess that the LSE made their decision based on "Windows has a richer set of apps available". Go figure...
^o^


Over a six month interval the number of mandatory reboots
was: Six. Once for each patch Tuesday of the month. The
only other reason I can think for a "mandatory" reboot is the
un/installation of software. Which, at 33 (removing the six
for the patch Tuesday), seems unusual.
0 Votes
+ -
Answer is easy...
Linux User 147560 19th Oct 2008
some of the work flow interruptions were significant enough that in order to restore system performance a reboot was required. Otherwise the system would perform sluggishly. So it would start with a work flow interruption that would result in a mandatory reboot to correct what ever the issue was in the first place. devil
...the process(es) that were consuming CPU/memory. No need to reboot.
0 Votes
+ -
The system would've become even more unstable.
n0neXn0ne Updated - 20th Oct 2008
Somethings only a reboot can fix. wink

^o^
Perhaps he should learn a little bit more about Windows. It seems his knowledge about it is seriously lacking.

Anyone who needs to keep a journal should instead focus on the root problem and not the symptoms. I don't have a log. You know why? Because I don't have problems.
0 Votes
+ -
@ye: You are right..
TedKraan 21st Oct 2008
You can fix it with Task manager, if you are a bit patient.

However it's 2008 patience is thin and waiting for a bad programmed OS to find a way to restore itself is sooo.. last millenium.
Windows software is on a billion screens out there. If you ran Mac software a billion times a day how many glitches would pop up there for Macs? Quite a bit considering the huge amount of patches that have finally been done at Apple. If you take a look at kiosk software you will find that most of it is tacked together using non Microsoft tools and these soon fail.

The notion that the single user Mac machine can handle kiosks or any other type of commercial work left unattended is a total joke. Mac software does not power kiosks because it is too flaky and costs too much to use.

I have had no blue screens of death in Vista. Forced reboots is as bad as it gets in Vista and I can turn that off if I want to as a server manager or desktop manager. XP, before service pack 2 did have a few blue screens of death but it is incredibly rare in Vista.

Older Windows from last century had a lot of blue screens of death which is why the vast majority of Windows power users moved to NT and then XP. The Macs also had the blue screen of death in slow downs when you tried to work them in a corporate or even home setting. If you don't know what the time clock cursor of death is then you don't use your Mac for more than web surfing and email. Load up your Macs and then load up a Windows XP or Vista box and tell me which one hangs up first.

This still happens in modern Macs and I had hoped that when Apple had moved away from their own OS software and to FreeBSD that the Macs would improve and be useful in a corporate setting but their own code under FreeBSD is equally crappy and Mac users are still getting the hour glass of infinite wait even today.
0 Votes
+ -
Lighten up
frgough 18th Oct 2008
and learn to laugh.
0 Votes
+ -
RE: ... kiosks ...
n0neXn0ne 19th Oct 2008
Not only kiosks ...



^o^


Also note that Linux and regular FreeBSD can be used in kiosks because both are fully functioning hardened Unix and Linux which are far, far more powerful than the Mac ever will be in spite of FreeBSD running the Mac the regular FreeBSD not broken by Apple is a much better choice for server work and for desktop use Ubuntu and Kubuntu kick the Macs ass in both utility, speed and reliability. Get rid of the Apple bad code on the front end and you understand why everyone is moving to Linux here in the future. The gizmo world for Linux is also more powerful than the crap that Apple does for its gizmos as well.
0 Votes
+ -
Nyahahahahahahahaha!!!!!!
bendib 5th Aug 2009
I know this is an old post, but still!!! I, a linux user, will now be saving the images for future laughs.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix
Click Here
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix