Actually i believe w3tc supports IIS. Or, at least it did.
Questions:
1. I know w3tc provides its own /wp-content/plugins/w3-total-cace/ini/web.config that one should use to help configure w3tc correctly and so i am curious if w3tc (unlikely) or maybe you added some or all of its contents into your existing web.config which could be confusing your server.
2. I know w3tc generates empty index.html and/or index.php files in some areas (to prevent showing empty directory listings) and so i wonder if, when you attempt to access your site, IIS is defaulting to viewing these empty pages. I will have more to say in #5.
3. You mentioned manually deleting the plugin but did you also delete: /wp-content/w3tc-config, and /wp-content/cache? Since you already deleted the actual plugin directory deleting these two remaining directories is more for cleanliness. Also, i am just curious if something is trying to access the w3tc’s old cache directory.
4. Does it show the WSoD even when attempting to access your WP admin page or does it only happen when accessing the public front-end?
5. Can you pop up your browser’s developer tools and visit one of these WSoD pages and see what the returning HTTP code is (under the ‘Network’ tab)? Is it reporting a 5## error e.g. 500 or 504? If not, then what is the return code?
6. Dumb question, but i assume you restarted IIS so as to flush out its own server cache from volatile memory?
Thanks