Thank you kindly, adam. Although it didn't give us a name of a component, that screen indicated that the PC has been collecting dumps of the crashes, which indicates a way forward.
First we'd better check to see if the PC has been collecting minidumps (rather than other forms of memory dump.
Go Start and click "Computer".
Doubleclick "Local Disk" (Usually it's your C: drive.)
Doubleclick "Windows".
Is there a folder called "Minidump" in there? If so, doubleclick on that.
Are there files in there called "Mini(number-numbers).dmp"?
(If you have "Hide filename extensions for known file types" enabled on the PC, the ".dmp" extension may not appear on the dump files. The numbers in the file name will be different for each minidump, if minidumps are present.)
If you can track down where the minidumps are being located, next we'll use WinDbg (Windows Debugging tools) to interrogate the minidumps to see if that turns up the name of a component (or components).
1. Download and install the Windows debugging tools from here (If you've got a 64-bit Vista, use the 64-bit version of the tools):
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 "Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there.)
*If you get a dialog at this point saying you don't have permission to open the file, try this:* OK out of the permission warning dialog. Right-click on the minidump file (In the "Open Crash Dump" screen), and select "Properties". Click the "Security" tab. Click the "Advanced" button. Click "Continue". Check the "Include inheritable permissions from this object's parent" checkbox, and click OK. Click Yes when the Windows security box comes up. Close the "properties" screens at this point, and go back to "Open Crash Dump", and try doubleclicking on the minidump again.
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 iPod-connection-related-crashes (fingers crossed, the date-and-time-created for the minidump files, or the numbers in the filename of the minidumps which indicate the date of the crash, might be able to allow you to identify the ones associated with plugging in the iPod). 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?
