🙂 Let's go digging.
1. Download and install the Windows debugging tools from here:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
2. Go to Start, All Programs, Debugging Tools For Windows, Windbg
Once you open Windbg, you will presented with a blank screen.
3. Click on "File > Symbol File Path". Here you will enter the symbols
path. Symbols are needed to effectively debug.
The path will be:
SRV
c:symbols
http://msdl.microsoft.com/download/symbols
4. Enter in this path and click OK. Now, go to "File > Save Workspace"
so that your symbols path is saved for future use.
5. Go to "File > Open Crash Dump" and load the file.
(An "Open Crash Dump" screen will appear ... doubleclick "My Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there.)
You will/should get a message to save base workspace information. Choose no.
Now you will get a debugging screen. It takes a little bit to run it,
as the symbols have to be downloaded as they are needed.
After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash. (It'll say "Probably caused by" ...)
Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
If you can, have a look at several of your minidumps for iTunes-closure-related-crashes (fingers crossed, the date-and-time-created for the minidump files might be able to allow you to identify the ones associated with iTunes). Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?