I would find it hard to believe that a CSS file would cause an error like this to occur, which leads me to think that there is something going on outside of that (within the application itself). Do you have any other error logs available? Or have you tried configuring the customErrors within your web.config to possible serve the full error messages on your deployed site?