I have a .NET application that is run off of a shared network drive.
About 5 users (out of 100) periodically have their entire machines
deadlock when they try to run the application.  I was able to
reproduce the issue a couple times on one of the user's machines.  One
time I had the Task Manager open when I launched the app and the Task
Manager also stopped responding (ctrl-alt-delete did nothing either)

I tried re-installing the .NET Framework, but I was still able to get
the machine to lock up when I launched the application.  I also tried
running the application locally and was not able to get the machine to
lock up though this is not an ideal solution.  The reason we run it
from the shared drive is so that we do not have to distribute updates
to every user.

I did some research and read about how deadlocks can occur in mixed-
mode dlls if you try to run managed code in the DllMain of the
unmanged code, but we do not have any unmanaged code in our app.  Even
if we did, that would only deadlock the process it is running in and
not the whole machine, correct?  It seems like the machine is
deadlocking when the CLR is loading the application but before it
starts executing b/c the splash screen for the app isn't shown before
the machine stops responding.  Does anyone have any ideas on what
could be causing this behavior?