DBCC traceon 208

Hello,

A few days ago a SQL Server had a terrible response time due to the fact that the NT server operating system was running low on virtual memory. A simple reboot solved the problem. The reason why NT is brought to it's knees is the workload; that machine has to do too much in too little time.
There's a simple solution to this: migrate some of the applications to another server.
I'm telling this because this is the background for my question. Every time the NT is running low on virtual memory SQL Server seems to launch dbcc traceon 208 (visible in the error log). That traceon stuff is poorly documented, not supported by the helpdesk, ... so I was wondering if anyone knows what triggers that dbcc traceon 208 command, why it does that and what I can do with it.

Thanks,
Stef