# Dr. Seuss Explains Computer Crashes

**URL:** <https://forum.kirupa.com/t/dr-seuss-explains-computer-crashes/35784>\
**Category:** random\
**Created:** [November 18, 2003, 2:17am UTC](https://forum.kirupa.com/t/dr-seuss-explains-computer-crashes/35784 "2003-11-18T02:17:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![David](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@David](https://forum.kirupa.com/u/David)\
**Post date:** [November 18, 2003, 2:17am UTC](https://forum.kirupa.com/t/dr-seuss-explains-computer-crashes/35784/1 "2003-11-18T02:17:19Z")

</div>

Dr. Seuss Explains Computer Crashes: Many of you have wondered why a  
computer crashes. It is usually very technical but maybe this will  
help.

If a packet hits a pocket on a socket on a port, and  
the bus is interrupted at a very last resort, and the  
access of the memory makes your floppy disk abort,  
then the socket packet pocket has an error to report.

If your cursor finds a menu item followed by a dash,  
and the double-clicking icon puts your window in the  
trash, and your data is corrupted cause the index  
doesn’t hash, then your situation’s hopeless and your system’s gonna  
crash!

If the label on the cable on the table at your house  
says the network is connected to the button on your  
mouse, but your packets want to tunnel to another  
protocol, that’s repeatedly rejected by the printer  
down the hall, and your screen is all distorted by the  
side effects of gauss, so your icons  
in the window are as wavy as a souse; then you may as  
well reboot and go out with a bang, 'cuz sure as I’m a  
poet, the sucker’s gonna hang!