nickdaniels.com


Some Windows crash pictures

Some superbly exciting pictures of Windows, and Windows software crashing and otherwise misbehaving.

These screenshots were all from my own PC, and collected in a fairly short space of time. As a developer, I always have loads of applications open at once (e.g. SQL Server Enterprise Manager + Query Analyzer, Outlook, Visual Source Safe, about 5 or 6 IE windows and 2 or 3 copies of Visual Studio .NET). It seems Windows can't really cope with this and the memory eventually fragments to an unusable level. Here's the results...



Here's a screenshot of Windows Task Manager not responding. After I took this screenshot, I had to open another task manager to kill this one with.

Here's SQL Server up to its usual tricks. Nice error!

Despite having at least 100MB of actual RAM (not SWAP) left, Visual Studio decided it couldn't be bothered to run.

Don't ya just love it when the arrow which is supposed to hide items on the systray just turns into a blob? Happens all the time to me. An example above.
How about when you minimize a DOS Prompt and then un-minimize it again, it leaves a load of crap on the screen behind it.

This one's always nice. A popup window in IE. It just hangs up for no reason, and when you try and close it, you're told it's busy. However, it nicely offers to close the window anyway for you. Of course, no matter how many times you click OK, it just doesn't close.
Now and again, when I try and go into Tools -> Options in Internet Explorer, it comes up with this one.

It looks like this is a bit of a "if in doubt, just show this error", rather than the usual "Critical Error" or "Unknown Error".

This is MS SQL Query Analyzer trying to cancel a query (just a SELECT query, mind). The circled area is the time it's taken to cancel it - nearly 24 hours! You'd think it'd give up! (It never did cancel. I had to kill it)


I tried to quit Excel once, and up came this error message. 'nuff said.

Now and again, the menu in Notepad just doesn't appear. Nice.

And my IE menus disappear now and again, too. What you find is, if you close a load of applications, it will appear again, so it's obviously some kind of memory fragmentation issue. I wish Microsoft would sort things like this out, rather than charging you a fortune for the latest great new GUI.

OK, so you just shouldn't be writing 16-bit applications any more these days, but if that's all you've been provided with, then you don't have much choice. They do crash very easily, though... All you have to do is try and load them, and they die!