This problem was reported for some S3 graphics chips and is caused by a bug in their driver. Updating the S3 graphics driver (www.s3graphics.com) to at least version 139412 solves the issue. If you do not know which graphics chip you have, look here.