Itunes makes my screen go BLACK and restart- will not work at all!

Question

hello fellow apple distressers,
hoping someone can help me as i would really appericiate it:):)!
everytime i try and open itunes my computer freezes then the screen goes black. after the screen goes black the computer restarts all on its own! when i log back into windows, after it has restarted, it tells me it has recovered from a +serious error+. when i searched for more information it gave me this error signature:
BCCode : 100000ea BCP1 : 8A1357A8 BCP2 : 8A0AD290 BCP3 : F78BACB4
BCP4 : 00000001 OSVer : 512600 SP : 3_0 Product : 768_1
i have tried uninstalling and reinstalling itunes annnddd quicktime, but still itunes refuses to co-operate, although funnily enough quicktime does work....
please help as i really need itunes to upload songs on to my ipod.
Btw, this happened after a virus and although this virus has been removed from the computer i think it may have damaged the itunes files:(
thanking you for reading this,
lovelifesmilepeace

Answer 1

wow blue screen of death that sounds bad...
Technically they're called STOP messages (because the PC stops after you get one of them). But "blue screen of death" (or BSOD) is the common terminology (because the PC stops after you get one of them).
C:\DOCUME~1\Abigail\LOCALS~1\Temp\\WERfd36.dir00\Mini012710-01.dmp
Good ... we've got the PC generating minidumps of the crashes. So we'll be able to interrogate those using Windows debugging tools to try to work out what is causing the crash.
First, track down where they are being stored on the PC. Usually that will be in the C:\Windows\Minidump\ directory. There should be files in there with names like "Mini(number-numbers).dmp"
(If you have "Hide filename extensions for known file types" enabled in Windows, 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.)
Once you've found where they're being stored, we'll have a look at them using windbg.
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:
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 ... 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 crash dumps. 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?