[Resonance]

I never understood why they would let something as critical as this get through:

Windows2000, NT, XP
================
Crash csrss.exe (thus W2K, NT, XP) through the command console. I tried writing the same program in Perl, and it did in fact crash my system. I did not see a BSOD, just automatically froze for a millisecond then rebooted.

# The Perl code was very simple:

while($x=1) {
print "testing\t\b\b\b\b\b\b\b";
}

csrss.exe seems to have a problem handling many backspaces after a tab when being displayed in the command console. As this loops infinitely, it tries to access memory out of the scope of this string value, and causes csrss.exe to crash. Any programming language that has access to the command console, and execute programs, can do this. As long as it is displayed, it will crash, so even a text file in the console will do so. There are some instances when the bug will not be replicated. For more info check out the following. This will work in service pack 2 or less than, or before xp sp1.

http://homepages.tes...kspace-bug.html
http://www.zappadoodle.com


Win98
=====
A fun way to crash a win98 machine 100% of the time is by setting an infinite loop through debug.exe

a 100
cli
jmp 101

g


The second line makes the CPU stop listening to any commands from any other process, such as windows, and "jmp 101" loops it... so it hangs.

On some Win98 machines if you put this under START-->RUN
"c:\con\con" and hit enter, it would crash. (windows has reserved system variables and you cannot use these as filenames apparently - so you CANNOT name a file "com3", "prn", "con", list goes on...)

Lovely, isn't it? Man, I love Microsoft.

[SlashRaid]

Ah yes, the best way to crash anything... Through junk at it till it breaks.