Windows 7: BSOD from iPhone connecting to iTunes (0x000000fe)

mastman · 03 Feb 2012

Unlike other posts i reviewed here, iTunes opens fine and is stable. It is only after connecting my iPhone (both my old 3GS and current 4S) that the PC throws a BSOD. It sometimes takes hours before this happens, but today it was still in the middle of syncing when it happened.
Thanks, mastman

Win 7 pro 32 bit w/ SP1
Not original OS, was XP Pro
Did clean install of Win 7 in Oct. 09 (not an upgrade installation)
(prob full retail version, can't recall)
PC is probably ~6 years old - HP a1520n

From Speccy:
Operating System
MS Windows 7 32-bit SP1
CPU
AMD Athlon 64 X2 3800+ 43 °C
Manchester 90nm Technology
RAM
2.00 GB Single-Channel DDR @ 167MHz (2.5-3-3-7)
Motherboard
ASUSTek Computer INC. NAGAMI2 (Socket 939) 40 °C
Graphics
Acer X233H (1920x1080@60Hz)
Acer X233H (1920x1080@60Hz)
512MB GeForce 9500 GT (EVGA) 50 °C
Hard Drives
977GB Western Digital WDC WD10 EADS-00L5B1 SCSI Disk Device (ATA)
244GB SAMSUNG SAMSUNG SP2504C SCSI Disk Device (ATA)
Optical Drives
HL-DT-ST DVDRRW GSA-H21L ATA Device
Audio
Realtek High Definition Audio
Operating System
MS Windows 7 32-bit SP1
Installation Date: 19 October 2009, 11:53

mastman · 03 Feb 2012

OK, looks like my edit did not allow adding the requisite ZIP file. Here it is.

Dave76 · 04 Feb 2012

I'm having an issue with your dump file, but will use the info I have.

Are you getting any crashes when the phone is not connected?

The crashing program is iTunes and blaming the usbehci.sys Windows driver - EHCI eUSB Miniport Driver
Are you using a USB hub to connect your phone?
The report is showing an invalid physical address, which would indicate a driver error.

The crash is STOP 0x000000FE: BUGCODE_USB_DRIVER
Usual causes: USB device driver
This indicates that an error has occurred in a Universal Serial Bus (USB) driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
	using a physical memory address that was not allocated by
	the USBport driver.
Arg2: 866ff0e0, Device extension pointer of the host controller
Arg3: 10de026e, PCI Vendor,Product id for the controller
Arg4: 8663594c, Pointer to Endpoint data structure

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  iTunes.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 9192ded9 to 82cecef4

STACK_TEXT:  
807e2e00 9192ded9 000000fe 00000005 866ff0e0 nt!KeBugCheckEx+0x1e
807e2e2c 9197cf3d 7cc7f100 866ff028 8663594c USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x152
807e2e70 9197d86e 866fffe0 8663594c 86635a4c usbehci!EHCI_sMode_PollEndpointSlot+0x45
807e2e88 9197fdf9 866fffe0 8663594c 00000001 usbehci!EHCI_sMode_PollEndpoint+0x36
807e2e9c 9192dcb4 866fffe0 8663594c 82c49108 usbehci!EHCI_PollEndpoint+0x27
807e2eb8 9192e155 866ff0e0 86635702 82c49108 USBPORT!MPf_PollEndpoint+0x96
807e2edc 9192e05c 00000004 86635868 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xf0
807e2efc 9192db56 866ff028 866357a8 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18
807e2f24 9192d9ce 866357a8 866ff720 866ff002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x17d
807e2f48 82c861b5 866ff72c 866ff002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e2fa4 82c86018 807c2120 853c4568 00000000 nt!KiExecuteAllDpcs+0xf9
807e2ff4 82c857dc e5daa960 00000000 00000000 nt!KiRetireDpcList+0xd5
807e2ff8 e5daa960 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82c857dc 00000000 0000001a 00d6850f bb830000 0xe5daa960


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_sMode_PollEndpointSlot+45
9197cf3d 50              push    eax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c04b6

FAILURE_BUCKET_ID:  0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+45

BUCKET_ID:  0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+45

Followup: MachineOwner
---------

Look at the information on this link, if applicable to your system, run it.
Stop error code 0x0000009F or Stop error code 0x000000FE on a Windows 7-based or Windows Vista-based computer that uses certain AMD USB EHCI host controllers

Also seeing this error repeated several times.

Code:

The device, MpKsl7bab8020, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_MPKSL7BAB8020\0000.

mastman · 08 Feb 2012

Thanks Dave76. No, the crashes only occur when my iPhone is connected. It also happened with my old 3GS. I do have a USB hub attached (iRocks IR-4100), but only use it for flash drives, never for my iPhone. I will check out the "stop error..." link to see if it applies. I do not know what the last item is. This HP PC is an old Media Center 2005 version. When i installed Windows 7, i did it as a clean install to a brand new HDD. Perhaps it is some legacy hardware on the MB?
-mastman

Dave76 · 09 Feb 2012

You're welcome.
Good to see you have isolated the cause.

Update your motherboard drivers from the Asus support site, a newer USB driver may help.

mastman · 17 Feb 2012

Nope, no joy. Crashed again. No mobo driver updates available from Asus, and have not found any for USB. This machine was not made in anticipation of Win 7, and i guess i am lucky that i have not had more difficulties with driver issues. I will just have to be careful to save active docs before i sync my phone. I only do this once a week or so, but perhaps will try focusing on a wireless sync instead. Thanks for your suggestions. - mm

Dave76 · 18 Feb 2012

Wireless sounds like the best way to sync your phone.

Let us know if you have any other issues.

Windows 7: BSOD from iPhone connecting to iTunes (0x000000fe)

BSOD from iPhone connecting to iTunes (0x000000fe) problems?