windows xp, minidump, applemtm.sys caused crash
hi, my mbp just crashed in windows xp.
remained minidump said, applemtm.sys caused crash...
^^ i know this info is too little figure out the problem...
but, is there anyone faced like this one?
-------- minidump -----
ATTEMPTED SWITCH_FROMDPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: 00000000, Original thread which is the cause of the failure
Arg2: 00000000, New thread
Arg3: 00000000, Stack address of the original thread
Arg4: 00000000
Debugging Details:
------------------
*** Kernel symbols are WRONG. Please fix symbols to do analysis.
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
*******************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the NT_SYMBOLPATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*******************************************************************
*******************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the NT_SYMBOLPATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*******************************************************************
FAULTING_MODULE: 804d9000 nt
DEBUG FLR_IMAGETIMESTAMP: 47685ec5
CUSTOMER CRASHCOUNT: 1
DEFAULT BUCKETID: WRONG_SYMBOLS
BUGCHECK_STR: 0xB8
LAST CONTROLTRANSFER: from 80547c4b to 804fbf0e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacd3c8c 80547c4b 000000b8 ffffffff 00000202 nt+0x22f0e
bacd3ce4 b7e06569 00000000 00000000 00000000 nt+0x6ec4b
bacd3d10 b7e4be4a 8a1711d8 00000000 8a451e08 Wdf01000+0x15569
bacd3d2c b7fcb53b 8a171290 75dc0430 8a23fbc8 Wdf01000+0x5ae4a
bacd3d4c b7fcb651 75bae3b8 8a00de70 bacd3da8 applemtm+0x53b
bacd3d5c b7e261b2 760ef150 75dfc680 bacd3d80 applemtm+0x651
bacd3da8 b7e26253 b7e57a08 8a203978 89f10ea8 Wdf01000+0x351b2
bacd3dc0 b7dfd5d3 8a00df97 8a203978 00000000 Wdf01000+0x35253
bacd3ddc b7dfd68d 01f10ea8 8962e450 bacd3e08 Wdf01000+0xc5d3
bacd3dec 804f280d 8a46c5a8 8a00de70 89f10ea8 Wdf01000+0xc68d
bacd3e08 804f36b0 8a46c5a8 8a00de70 8962e450 nt+0x1980d
bacd3e38 b99210d5 8a00de70 88da4980 8a2d3028 nt+0x1a6b0
bacd3ea0 b9921d47 895bd170 00000000 8a2d37d8 USBPORT+0xa0d5
bacd3ed0 b9922944 026e6f44 8a2d30e0 8a2d30e0 USBPORT+0xad47
bacd3f08 b992413a 8a2d3028 80548abc 8a2d3230 USBPORT+0xb944
bacd3f34 b993224b 8a2d3028 80548abc 8a2d3028 USBPORT+0xd13a
bacd3f70 b99323c2 8a2d3028 00000001 8a34a834 USBPORT+0x1b24b
bacd3f8c ba6b8d54 8a2d364c 6b755044 00000000 USBPORT+0x1b3c2
bacd3fbc 8a34adb2 8a34a310 b993225c bacd3fd0 sptd+0x11d54
bacd3fc0 8a34a310 b993225c bacd3fd0 80547e6f 0x8a34adb2
bacd3fc4 b993225c bacd3fd0 80547e6f 8a2d364c 0x8a34a310
bacd3fc8 bacd3fd0 80547e6f 8a2d364c 8a2d3028 USBPORT+0x1b25c
bacd3fcc 80547e6f 8a2d364c 8a2d3028 00000000 0xbacd3fd0
bacd3fd0 8a2d364c 8a2d3028 00000000 00000000 nt+0x6ee6f
bacd3fd4 8a2d3028 00000000 00000000 b401ff4a 0x8a2d364c
bacd3fd8 00000000 00000000 b401ff4a 6803fe95 0x8a2d3028
STACK_COMMAND: kb
FOLLOWUP_IP:
applemtm+53b
b7fcb53b ?? ???
SYMBOL STACKINDEX: 4
SYMBOL_NAME: applemtm+53b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: applemtm
IMAGE_NAME: applemtm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
remained minidump said, applemtm.sys caused crash...
^^ i know this info is too little figure out the problem...
but, is there anyone faced like this one?
-------- minidump -----
ATTEMPTED SWITCH_FROMDPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: 00000000, Original thread which is the cause of the failure
Arg2: 00000000, New thread
Arg3: 00000000, Stack address of the original thread
Arg4: 00000000
Debugging Details:
------------------
*** Kernel symbols are WRONG. Please fix symbols to do analysis.
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
***********************************************************************
* *
* *
* 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: nt!_KPRCB *
* *
***********************************************************************
*******************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the NT_SYMBOLPATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*******************************************************************
*******************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the NT_SYMBOLPATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*******************************************************************
FAULTING_MODULE: 804d9000 nt
DEBUG FLR_IMAGETIMESTAMP: 47685ec5
CUSTOMER CRASHCOUNT: 1
DEFAULT BUCKETID: WRONG_SYMBOLS
BUGCHECK_STR: 0xB8
LAST CONTROLTRANSFER: from 80547c4b to 804fbf0e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacd3c8c 80547c4b 000000b8 ffffffff 00000202 nt+0x22f0e
bacd3ce4 b7e06569 00000000 00000000 00000000 nt+0x6ec4b
bacd3d10 b7e4be4a 8a1711d8 00000000 8a451e08 Wdf01000+0x15569
bacd3d2c b7fcb53b 8a171290 75dc0430 8a23fbc8 Wdf01000+0x5ae4a
bacd3d4c b7fcb651 75bae3b8 8a00de70 bacd3da8 applemtm+0x53b
bacd3d5c b7e261b2 760ef150 75dfc680 bacd3d80 applemtm+0x651
bacd3da8 b7e26253 b7e57a08 8a203978 89f10ea8 Wdf01000+0x351b2
bacd3dc0 b7dfd5d3 8a00df97 8a203978 00000000 Wdf01000+0x35253
bacd3ddc b7dfd68d 01f10ea8 8962e450 bacd3e08 Wdf01000+0xc5d3
bacd3dec 804f280d 8a46c5a8 8a00de70 89f10ea8 Wdf01000+0xc68d
bacd3e08 804f36b0 8a46c5a8 8a00de70 8962e450 nt+0x1980d
bacd3e38 b99210d5 8a00de70 88da4980 8a2d3028 nt+0x1a6b0
bacd3ea0 b9921d47 895bd170 00000000 8a2d37d8 USBPORT+0xa0d5
bacd3ed0 b9922944 026e6f44 8a2d30e0 8a2d30e0 USBPORT+0xad47
bacd3f08 b992413a 8a2d3028 80548abc 8a2d3230 USBPORT+0xb944
bacd3f34 b993224b 8a2d3028 80548abc 8a2d3028 USBPORT+0xd13a
bacd3f70 b99323c2 8a2d3028 00000001 8a34a834 USBPORT+0x1b24b
bacd3f8c ba6b8d54 8a2d364c 6b755044 00000000 USBPORT+0x1b3c2
bacd3fbc 8a34adb2 8a34a310 b993225c bacd3fd0 sptd+0x11d54
bacd3fc0 8a34a310 b993225c bacd3fd0 80547e6f 0x8a34adb2
bacd3fc4 b993225c bacd3fd0 80547e6f 8a2d364c 0x8a34a310
bacd3fc8 bacd3fd0 80547e6f 8a2d364c 8a2d3028 USBPORT+0x1b25c
bacd3fcc 80547e6f 8a2d364c 8a2d3028 00000000 0xbacd3fd0
bacd3fd0 8a2d364c 8a2d3028 00000000 00000000 nt+0x6ee6f
bacd3fd4 8a2d3028 00000000 00000000 b401ff4a 0x8a2d364c
bacd3fd8 00000000 00000000 b401ff4a 6803fe95 0x8a2d3028
STACK_COMMAND: kb
FOLLOWUP_IP:
applemtm+53b
b7fcb53b ?? ???
SYMBOL STACKINDEX: 4
SYMBOL_NAME: applemtm+53b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: applemtm
IMAGE_NAME: applemtm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
MacBook Pro, Mac OS X (10.5.2)