iPod on x64 + PC sleep mode = fail?

  • Thread starter Sharky.
  • 8 comments
  • 2,362 views
Sharky.

Sharky.

MX-5 gang
Premium
11,969
New Zealand
Christchurch
Long story short, the 64-bit Apple Mobile Device USB driver is making my W7 64-bit system blue-screen up the wazoo for some unknown reason. It'll happen about 15-20 minutes after bringing the computer out of sleep (not consistently though, which is odd... but I have my suspicions), and it throws up a DRIVER_POWER_STATE_FAILURE BSOD.

Now, some times I leave my iPod connected to my computer even when the computer is in sleep mode, and I know in the case of the two most recent blue-screens, my iPod was connected to the computer at the time - I'm not sure if my iPod was connected when the previous BSODs occured, but it probably was. This is leading me to believe that there's something rotten in Apple's 64-bit iPhone/iPod/iPad driver that's making the system go tits up if I have my iPod (third-gen 32GB touch, but that's not relevant) connected while the computer wakes from sleep mode.

The BSOD lists a 9F error (DRIVER_POWER_STATE_FAILURE) & ntoskrnl.exe as the faulting process (as pretty much every BSOD does); WinDBG analysis pinpoints the cause as usbaapl64.sys - the Apple Mobile Device USB driver, which is what's made me believe it's *something* to do with having my iPod connected via USB...

WinDBG analysis (for the geeks):
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004f35780, fffff80000ba2748, fffffa80051e36a0}

*** WARNING: Unable to verify timestamp for usbaapl64.sys
*** ERROR: Module load completed but symbols could not be loaded for usbaapl64.sys
Probably caused by : usbaapl64.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8004f35780, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa80051e36a0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa8004256060

IMAGE_NAME:  usbaapl64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bb410ef

MODULE_NAME: usbaapl64

FAULTING_MODULE: fffff88008c31000 usbaapl64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  swarm.exe

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00ba26f8 fffff800`02ce71b3 : 00000000`0000009f 00000000`00000003 fffffa80`04f35780 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`02c846a6 : fffff800`00ba2830 fffff800`00ba2830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00ba27a0 fffff800`02c83a26 : fffff800`02e28700 00000000`002468e4 00000000`00000000 fffffa80`05751c60 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`02c8457e : 00000056`ab53e607 fffff800`00ba2e88 00000000`002468e4 fffff800`02df6f08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`02c83d97 : fffff800`02df2ec1 fffffa80`002468e4 fffffa80`05890d38 00000000`000000e4 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`02c7e765 : 00000000`00000000 fffffa80`042ce770 00000000`00000000 fffff880`03a29db0 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02c7e57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`097aebe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbaapl64.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_usbaapl64.sys

Followup: MachineOwner
---------
I'll try and see if I can induce a BSOD through one method or another (leave iPod connected, stick computer in sleep, wait a few minutes, bring computer out of sleep, wait for system failure); if I can get a BSOD on command (but knowing Windows, it won't give me one when I want it... only when I don't want one will it blow up in my face) then I should have pinpointed what's making my computer explode, but not why it's doing it - which is what I really want to know, so I might have some idea how to fix it.


Has anyone else been experiencing issues like this (leaving an iDevice connected via USB will make your 64-bit computer die shortly after resuming from sleep)? I'm using iTunes 9.2 (usbaapl64.sys version 1.49.0.0) - reinstalled for good measure, Windows 7 Ultimate x64 and a third-gen iPod touch (equivalent to iPhone 3GS) running 4.0. There are a stack of reports on the internet of an older version of the USB driver (1.35 iirc) and iTunes 8 causing the exact same blue screens, so I don't believe this is something that only happens to 1% of people.

(interestingly, my 32-bit laptop has BSOD due to the GEARAspiWDM driver, which is also something installed by iTunes... on that note, no "zomg don't use iTunes lololol" posts please, I've tried several iTunes alternatives and personally thought they were worse to use than iTunes is)
 
I have had problems with my brother's Zune. I forgot what it was, but I think it slowed the boot-up process by 10x or something like that.
 
No, I haven't. That requires either a BIOS setting or switching the USB wires to +5vsb on the mobo though doesn't it?

That shouldn't really be relevant anyway, as I connect my iPod via the USB ports in my monitor - which are thus powered independently of the computer itself. Unless it's *that* that's making it all go boom...
 
Sharky.
No, I haven't. That requires either a BIOS setting or switching the USB wires to +5vsb on the mobo though doesn't it?

That shouldn't really be relevant anyway, as I connect my iPod via the USB ports in my monitor - which are thus powered independently of the computer itself. Unless it's *that* that's making it all go boom...
Click to expand...

Possibly. I've had nothing but bad experiences with Monitor USB ports. To be honest I don't understand the appeal, as you have to connect the monitor to the computer via USB anyway. Might as well just get a USB extension. Since the monitor USB ports are powered independently of the PC USB ports perhaps you are getting some conflict.

I haven't noticed a BIOS setting but their may be one. However, in Windows 7 it should be an option in the Advanced Power Management section.
 
I'm not sure what might be going on with your computer, but I have just tried to replicate your issue. I am running Windows 7 Professional x64 and I just plugged in my iPad directly into my computer's USB port and put the computer to sleep. I waited a few minutes, then waked up the computer. I repeated this again, this time plugging in my iPhone 3G. In both cases, the computer waked up fine without BSODing or even a sign of hiccup (of course usbaapl64.sys is installed).

Just FYI, in Advanced Power Settings, I have USB selective suspend setting enabled.
 
Yeah, the blue screens aren't consistent, that's the thing. I'd rather they were, to be frank - because then I'd know that having my iPod connected on resume = bad idea. As it stands, it seems completely random as to whether it'll blow up in my face or not.

I can live with a random BSOD once a week or so, but in an ideal world...
 
I'd stop using that monitor USB port. It's likely getting power from the monitor and data (obviously) to and from the computer and there's a conflict with that.
 
Ironically (or not), it hasn't blue-screened since I posted this thread :lol: I suspect you have a point regarding the monitor's USB port, because I've noticed that it seems a bit hit and miss as to whether the port is powered/recognises devices when the monitor's getting a signal via DVI or HDMI - sometimes the computer won't register that I've plugged the iPod into one of the ports in the monitor (monitor in DVI input mode), necessitating an unplug and replug of the iPod USB cable. With the monitor in HDMI mode (ie when I'm using my PS3) sometimes the iPod won't charge, which points towards the monitor's USB ports being a bit funky.
 

Latest Posts

Back