Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

josielinnea

macrumors regular
Original poster
Dec 15, 2007
238
13
Stockholm
This morning I updated iTunes to 8.0 from 7.X-something. When the update was finished, I connected my iPhone and the computer bluescreen-ed on me and said a device was corrupted and the computer would shut down to protect itself.

I booted up again, no problem until I connected the iPhone - bluescreen and shutdown again. I tried another USB-port. Same result. After a few tries Windows wouldn't even boot, I had to repair windows and go back to a system restore point a few days ago (when I hadn't updated iTunes).
So after an hour the computer finally worked again.
I connected the iPhone to another computer to see if it was the phone that is the problem, but nothing that shouldn't happen happend. Connected it to my own computer, now with iTunes 7 and everything worked fine. Had to restore my iPhone cause it was seriously f*cked up, rebooting and rebooting after that bluescreen and it wouldn't shut off at all. But after the restore everything worked.
So now a couple of hours later after testing that everything worked and nothing crashed (could even update my apps!!! :D) I tried to upgrade iTunes to 8.0 again.

And voila! Bluescreen and the computer shuts itself down to protect itself from this corrupted device. It only happens when iTunes is 8.0, not the previous versions.


Am I the only one?
 
Many have reported this issue. I managed to avoid a BSOD myself. I have read that many are able to successfully connect their iPod/iPhone by unplugging their USB printer or moving the iPod/iPhone USB connection to a bank that is not shared by another USB device.

I moved my iPhone cable to another port before I plugged it in the first time with iTunes 8.0 and it did not BSOD for me.

The problem stems from the updated usb driver that is included with iTunes 8.0.
 
I have already tried different USB-outlets on my computer - all give the horrible bluescreen.. :-( Do anyone know of a workaround or what the driver is called so I could have it removed?
 
A better solution although more expensive would be to buy a Mac!!

(someone had to say it)
 
I believe the #1 suspect is windows vista (yet again)

I am one of those who have to put up with Vista every day. Never really liked it and is buying a MBP as soon as the new one arrives but:The way I see it, you can't blame the OS when a program's not working. Let's say Micrsoft Word 2008 makes OSX crash. Who's to blame? OSX not beeing compatible with Word or vice versa?
 
Well it isn't just Vista-I have Windows XP professional and it is doing the same thing...really I WANT a MAC, but this computer is only 2 years old. Thanks for the fixes everyone...you have saved me hours of frustration (other than what I already went through):D
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.