Yep, first thing to look.

Faced the same problem some time ago.

Turned out it was a bug in the application - closing opening connection "conn" in try, and closing "conn1" in catch.

Because the issue happened only after an exception in that particular piece of functionality it was also totally random, with no pattern to be found.

Try to match the timing of tempdb issues with exceptions recorded in the application log.