8 Replies Latest reply: Apr 20, 2010 6:43 AM by azpc
TexAIR Level 1 (0 points)

*I have diagnosed an issue in the aapltp.sys (touch pad) driver included with the MacOS 10.6.2 DVD. This issue causes a illegal access to be performed by this driver when the computer resumes from sleep (I have never reproduced it when resuming from hibernate or during normal operation). This issue occurs about once in every 10 resume operations, with both Windows 7 and Windows Vista. I have not experimented other versions of the OS.*

*The version of this driver included with 10.5.x DVD does not have this issue - this is a new regression.*

*In summary, KeyMagic (another apple driver) running on a system thread calls the OS for a dispatch (FxDevice::Dispatch). This ends up being routed to aapltp. While executing, aapltp dereferences a memory position offseted from a register that contains NULL. This causes an Access Violation which escalates into a BugCheck.*

*AFAIK Apple does not distribute driver symbols so I was unable to dig into the cause for the fault in this driver. I am appending some additional crashdump information that might be useful. If you require additional information, let me know. I can either provide you with the full crashdump of perform further analysis if you make the symbols available.*

________________________________________________________________________________ ____________

* *
* Bugcheck Analysis *
* *

This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004a7ea74, The address that the exception occurred at
Arg3: fffff88005134718, Exception Record Address
Arg4: fffff88005133f70, Context Record Address

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1

EXCEPTION_RECORD: fffff88005134718 -- (.exr 0xfffff88005134718)
ExceptionAddress: fffff88004a7ea74 (aapltp+0x000000000000ca74)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000005b
Attempt to read from address 000000000000005b

CONTEXT: fffff88005133f70 -- (.cxr 0xfffff88005133f70)
rax=0000000000000000 rbx=0000000000000004 rcx=fffffa80057899e0
rdx=0000057ffa876618 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004a7ea74 rsp=fffff88005134950 rbp=fffffa8005789d50
r8=fffff88004a7b140 r9=0000000000000000 r10=fffffa80056809e0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000057ffa99e188 r15=0000057ffa99e188
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1 ds:002b:00000000`0000005b=??
Resetting default scope



ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000000000005b

READ_ADDRESS: 000000000000005b

fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1



LASTCONTROLTRANSFER: from fffff88000e52f90 to fffff88004a7ea74

fffff880`05134950 fffff880`00e52f90 : fffffa80`05661e70 0000057f`fa9443a8 fffffa80`056809e0 fffffa80`056bbc50 : aapltp+0xca74
fffff880`051349b0 fffff880`00e5299f : 00000000`00000000 fffffa80`05661e70 fffffa80`056bbc50 fffffa80`056bbc50 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x4b8
fffff880`05134a30 fffff880`00e51f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05661fc2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`05134aa0 fffff880`00e57558 : fffffa80`04e2fb00 fffffa80`05661e70 fffffa80`04e2fb00 fffffa80`05661e70 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`05134b10 fffff880`00e41245 : fffffa80`05661e70 fffffa80`04160c30 fffffa80`04e8ea58 00000000`000f2008 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`05134b90 fffff880`04a672f6 : fffffa80`04160c30 fffffa80`056bcc90 00000000`00000000 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`05134bc0 fffff880`04a6660b : fffffa80`056bcc90 fffffa80`04e8c010 fffffa80`08897640 fffffa80`04e8ec20 : KeyMagic+0x32f6
fffff880`05134c30 fffff800`03334166 : fffffa80`04e00040 00000000`00000080 fffffa80`03cd1740 fffffa80`04e00040 : KeyMagic+0x260b
fffff880`05134d40 fffff800`0306f486 : fffff800`03209e80 fffffa80`04e00040 fffffa80`03ce6680 fffff880`0122ca90 : nt!PspSystemThreadStartup+0x5a
fffff880`05134d80 00000000`00000000 : fffff880`05135000 fffff880`0512f000 fffff880`05134770 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_NAME: aapltp+ca74


IMAGE_NAME: aapltp.sys


MacBook, Windows 7, Core 2 Duo 2.4GHz, 4GB RAM
  • TexAIR Level 1 (0 points)
    Hey, is this forum ever monitored by Apple devs?
  • TexAIR Level 1 (0 points)
    Ok, just had my first repro resuming from hibernate instead of sleep - same place, same stack-trace.

    So we can say that this can potentially happen on all resumes.

    (still assuming this forum is somewhat monitored by apple devs - after all I was told to use this vehicle by an "Apple Specialist" hotline person)

  • kernelkiani Level 1 (0 points)
    Same here. BSOD on every resume from sleep. Same aapltp.sys is reported in crashdump BSOD.
    Windows 7, 32-bit, Bootcamp 3.

    Message was edited by: kernelkiani
  • srujan Level 1 (0 points)
    I am having the same problem.
    BCCode: 1000007e
    BCP1: FFFFFFFFC0000005
    BCP2: FFFFF88005F13A74
    BCP3: FFFFF88003620718
    BCP4: FFFFF8800361FF70
    OS Version: 617600
    Service Pack: 0_0
    Product: 768_1

    I have been having this problem since updating to 3.1 drivers. The crash dump also points to aapltp.sys
  • Matthew Rossi Level 1 (5 points)
    I am also having this issue - except for me it's when I am going to sleep. Windows 7 Pro 64-bit. Any fix?
  • dislo Level 1 (0 points)
    Same here about one in every ten reboots I get a BSOD. I am running Windows 7 x64 on a second gen macbookpro.

    Message was edited by: dislo
  • GRiNSER Level 1 (0 points)
    Same here - very annoying!
    Trying older track pad enabler drivers, hope these work as you explained...

    Message was edited by: GRiNSER
  • azpc Level 1 (10 points)
    Thanks for posting this information in this forum. You just saved me a couple thousand dollars!

    Based on my experience if you want to get this problem fixed as soon as possible you need to do the following:

    1. www.apple.com/feedback

    2. Post a video of the problem on www.youtube.com

    3. Send www.apple.com/feedback a link to the video on youtube.

    4. Encourage others to visit your youtube video and to post their own.

    Good luck!