QUOTE(Buttsex @ Oct 12 2009, 11:37 PM)
You can try just a regular fork bomb, they're fairly simple. Just time how long it takes your computer to memory overflow.
I know this is pedantic, but a fork bomb doesn't cause problems because memory is used up; it causes problems because the OS's process table becomes filled (not because of memory constraints, just because the process table only holds a finite number of processes). I think Windows uses a shared, copy-on-write memory model (I know
Unix/Linux/Mac OS X does), so 1 notebook.exe process uses roughly the same amount of memory as 1,000,000.