GraciBaby, I have been plagued by the same problem.
What I have found is the following. The problem occurs whenever you try to invoke the Windows Explorer Browse-to window and it involves ANY program: i.e. web browsers (Chrome, FF, Opera), third party programs such as media players (including iTunes). Any program which invokes the browse-to window will crash in the matter of a second along with the browser window itself.
The culprit is ONLY Apple Mobile Device Service. In order for the problem to occur, the AMDService needs to be running and you need to have connected your iDevice at least once before after a PC restart. The problem does not occur after a fresh system restart.
I have found no solution so far - problem seems not to be documented very well on the internet possibly due to its specificity. However, problem is widespread, as I have at least three confirmed friend cases.
Edit: Fully reinstalling iTunes and the AMDService does not fix the issue
There is a workaround: you must disable the Navigation pane in the WinExplorer Browse-to window for each of the applications you use to invoke this window. Of course, you need to do that on a fresh restart as otherwise the crash would occur too quickly for you to change the settings.
In order to remove the Navigation pane in the case of iTunes, for example, simply open your iTunes, go to Edit > Preferences > Advanced. To invoke the WinExplorer window, click on the "Change" button. From the WinExplorer window which appears, click on Organize > Layout, and untick Navigation pane. That's it.
The next time you invoke the Browse-to window, in iTunes, iTunes will no longer crash even with the AMDService running. SAME workaround is valid for any other application where there is an invoke of the Browse-to WinExplorer window.
Drawback - the workaround will "work" until you restart your PC - after which the Browse-to windows whose layout you changed will revert back and show the navigation pane.
I am desperate to know whether someone has come up with a real solution to this and with the exact cause as to why the AMDService in combination with invoked Browse-to Windows Explorer window lead to program crashes.