Apple iTunes 10.0.1 = BSOD in Windows 7

Question

Okay! I always upgrade to the latest version of software, chiefly as a test bed for others with whom I consult. I have been running Windows 7 since it was released (well before actually ).
I have never ever had a BSOD for any reason on ANY of my Windows 7 machines. Until today. I upgraded iTunes from 10.0.68 to 10.0.1, and now, as I navigate around iTunes, I either get a program has stopped working and will be closed message, or the BSOD. The BSOD message, high flyover is the error was in Memory_Management.
Here are my computer specs:
Model: HP Pavilion DV6756
OS: Windows 7 64-bit
Memory: 3 Gigabytes
CPU: Intel Centrino
Anyone else having as much fun as I am?

Answer 1

I see the system has been saving memory dumps for the crashes. With any luck, if we interrogate the dump files with the 64-bit version of WinDbg, we can track down the component causing the crash.
1. Download and install the 64-bit version of Windows debugging tools from here:
http://www.microsoft.com/whdc/devtools/debugging/install64bit.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:
SRVc:symbolshttp://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 ... navigate to C:\Windows\MEMORY.DMP\, or C:\Windows\Minidump\, and doubleclick on one of the dump files 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 dump 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 dump file 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.
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 the dumps that seem to be associated with the BSODs. 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?