Ok, windows users here is a quick fix until woody gets back:
Open a command prompt (Start->Run... type in "cmd" [without the quote] and hit Ok...) and run each of these one at a time (be sure to type them exactly. if you make mistakes the fix wont work)
Code:
echo 127.0.0.1 yieldbuild.com >> %SystemRoot%\system32\drivers\etc\hosts
echo 127.0.0.1 ads.digitalpoint.com >> %SystemRoot%\system32\drivers\etc\hosts
echo 127.0.0.1 tag.contextweb.com >> %SystemRoot%\system32\drivers\etc\hosts
To be fair to woody, blocking ads kills his ad-revenue and makes running the site more difficult. However there is no point in keeping crashing ads that make the site unusable, so I don't feel too terrible explaining how to block the offending domains.
edit: To explain what that does.... every operating system has to look up the IP address of a domain name when you request a page (for example: no computer can access ih8mud.com directly. They must first query a nameserver for the IP address where the server for ih8mud is located. In this case it is actually 204.10.140.65) before it can connect to it. Windows will check what is known as the "hosts" file first though (before it contacts a nameserver) to see if the domain is listed there. These commands add lines to the hosts file which tell windows that the IP address of the offending domain is
actually your own computer 
Now,
obviously you aren't the host, and windows knows this but it never questions the hosts file, so it simply cannot load the ads. It's a crafty way to get around the ads and these changes apply all over windows, not just to IE.