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 -----
ATTEMPTEDSWITCH_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
DEBUGFLR_IMAGETIMESTAMP: 47685ec5
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: WRONG_SYMBOLS
BUGCHECK_STR: 0xB8
LASTCONTROLTRANSFER: 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 ?? ???
SYMBOLSTACKINDEX: 4
SYMBOL_NAME: applemtm+53b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: applemtm
IMAGE_NAME: applemtm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------

My MBP crashed with exactly the same dump. The crashes occurred during a StandBy operation (My MBP crashed regularly but not reproducably while trying to stand by/sleep).
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\vas\Desktop\Mini070508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srvc:symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpspsp2rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Jul 5 22:53:49.999 2008 (GMT-7)
System Uptime: 0 days 22:33:47.814
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck B8, {0, 0, 0, 0}
* WARNING: Unable to verify timestamp for applemtm.sys
* ERROR: Module load completed but symbols could not be loaded for applemtm.sys
Probably caused by : applemtm.sys ( applemtm+53b )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
ATTEMPTEDSWITCH_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:
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: DRIVER_FAULT
BUGCHECK_STR: 0xB8
PROCESS_NAME: System
LASTCONTROLTRANSFER: from 80544c3b to 804f9c12
STACK_TEXT:
bace7ccc 80544c3b 000000b8 ffffffff 00000202 nt!KeBugCheck+0x14
bace7cdc 8054498b bace7d24 88d3b418 bab40120 nt!ScPatchFxe+0x46
bace7cf0 80502b17 88d3b488 88d3b418 804fad6c nt!KiSwapContext+0x2f
bace7cfc 804fad6c 00000000 00000000 8a19a4b0 nt!KiSwapThread+0x6b
bace7d24 b7022569 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x1c2
bace7d50 b7067e4a 8a0c2a30 00000000 8a37efb0 Wdf01000!FxWaitLockInternal::AcquireLock+0x3a
bace7d6c b939853b 8a0c2ae8 75e65b78 8a19a480 Wdf01000!imp_WdfWaitLockAcquire+0xc9
WARNING: Stack unwind information not available. Following frames may be wrong.
bace7d8c b9398651 75c81210 89eee008 bace7de8 applemtm+0x53b
bace7d9c b70421b2 764c7c80 7652beb8 bace7dc0 applemtm+0x651
bace7de8 b7042253 b7073a08 89ad4140 89b38378 Wdf01000!FxRequestBase::CompleteSubmittedNoContext+0x63
bace7e00 b70195d3 89eee12f 89ad4140 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0x97
bace7e1c b701968d 01b38378 88a9ed80 bace7e48 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x195
bace7e2c 804f053f 8a053350 89eee008 89b38378 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
bace7e48 804f13e2 8a053350 89eee008 88a9ed80 nt!IopUnloadSafeCompletion+0x1d
bace7e78 b9843ee5 89eee008 892f5ee0 8a25c028 nt!IopfCompleteRequest+0xa2
bace7ee0 b9844b57 89bdc4a8 00000000 8a25c7d8 USBPORT!USBPORT_CompleteTransfer+0x373
bace7f10 b9845754 026e6f44 8a25c0e0 8a25c0e0 USBPORT!USBPORT_DoneTransfer+0x137
bace7f48 b9846f6a 8a25c028 80545aac 8a25c230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
bace7f74 b9854fb0 8a25c028 80545aac 8a25c028 USBPORT!USBPORT_DpcWorker+0x224
bace7fb0 b9855128 8a25c028 00000001 89edc578 USBPORT!USBPORT_IsrDpcWorker+0x37e
bace7fcc 80544e5f 8a25c64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
bace7ff4 805449cb b3f6362c 00000000 00000000 nt!KiRetireDpcList+0x61
bace7ff8 b3f6362c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
805449cb 00000000 00000009 0081850f bb830000 0xb3f6362c
STACK_COMMAND: kb
FOLLOWUP_IP:
applemtm+53b
b939853b ?? ???
SYMBOLSTACKINDEX: 7
SYMBOL_NAME: applemtm+53b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: applemtm
IMAGE_NAME: applemtm.sys
DEBUGFLR_IMAGETIMESTAMP: 47685ec5
FAILUREBUCKETID: 0xB8_applemtm+53b
BUCKET_ID: 0xB8_applemtm+53b
Followup: MachineOwner
Message was edited by: tourist604

Similar Messages

Windows xp ticket cache read causes crash

UPDATE Old title: Error calling function Protocol status: 1312 FormatMessage failed with 1815 
 
I have written an application that authenticates to kerberos using the KerberosLoginModule. It used to work fine on all OS�s. (Windows 98, 2k, xp and Linux tested.) 
Now I have upgraded my application to java 1.5 code. And it still works fine on all tested OS�s, except Windows xp. Wich in first case does not even throw�s a error. It just exits in javaws. If I run it manually with java -jar I get the following output: 
 
Error calling function Protocol status: 1312 
FormatMessage failed with 1815 
 
UPDATE: 
After some more messing around I found out it craches because it want to read the ticket cache. 
Now I can understand there are some differences in ticket cache versions, but then java could choose not to read the ticket, like under linux. But why does it crash under Windows XP if it only try's to read a ticket? 
Now I can only choose between no ticket cache at all on all os's, or to build in a Windows XP filter for the ticket cache option. 
Both not very good solutions. Why is this and how can it be solved? 
 
Message was edited by: 
[email protected]

The meeting was quite successful as I can obtain a a ticket from the Win2k KDC now by Acquire TGT using AS Exchange (I have to enter my logon username/password because we have a Novell Logon and not WinLogon...) which results in Commit Succeeded.
But the ticket is not stored in the Windows XP credential/ticket cache, klist tgt says "Error calling function LsaCallAuthenticationPackage: 0
Format message failed with 1815", klist tickets says "Cached tickets: (0)" and kerbtray is empty!
And I stll receive the same error messages as mentioned earlier: "Error calling function Protocol status: 1312
Eine angegebene Anmeldesitzung ist nicht vorhanden. Sie wurde gegebenenfalls bereits beendet."
Do you have any suggestions/ideas what could be wrong with my system/configuration?
Message was edited by:
Santacruzshores
Message was edited by:
Santacruzshores

Pciimaq.sys causes nt40 to crash during booting?

I'm trying to install a 1408 IMAQ card. Anyhow, the system running
NT40+SP6 does not manage to boot anymore. It allways presents me with a
blue-screen,
telling me that PCIIMAQ.SYS causes some kind of adress error.
What can I do to fix this?
Regards,
Thomas jennewein

Is the IMAQ board in the computer when this crash occurs? Do the crash occur if the boasrd is out of the computer. If you can boot without the board in, you probably have a bad board. If it still does not boot, can you boot in safe mode and uninstall the driver or it won't even let you select which mode to boot in?

CC 2014 (18.1.0) | Text Field editing causing crashes (Windows)

Greetings;
I've noticed lately that when saving files from CC 2014 to a CS6 format - and having those files edited on Mac, in either CS6 or CC - when re-opening those files text fields have been causing crashes on the Windows client. When that same file is opened and text fields are edited on the Mac client, a prompt will just appear stating "Cannot Edit text" - yet it still allows it.
This has caused multiple issues for our teams as it has created files we're starting to refer to as "mine fields" - as working with the .ai file is like playing Russian roulette with text fields, you never know which one is going to crash the file.
I would love to work with a team member from Adobe to help find a resolution to the problem, and I'm willing to provide any additional details that might aid in that process.
Thanks!

Hello Pureweb,
Please upload the crashdumps on some file sharing website say Dropbox and share the link with us by sending a mail to "[email protected]". We will analyze the dump and will suggest you the workaround appropriately.
In parallel, please check that you do not have any 3rd Party plugins installed in it. Please try to remove them one-by-one and see which one causes the crashes or do reverse i.e. remove all the 3rd party plugins. Or Uninstall Ai and check at following location:
C:\Program Files\Adobe\Adobe Illustrator CC 2014
Please verify that nothing is left at above location on uninstalling Ai. Then try a fresh install and see if Ai works.
Also, verify that you have the updated Wacom drivers on your system. This might be an issue with the 3rd party program as well. One of the user who was having a similar issue reported on the Ai forum that one of the 3rd party Stahl's ImageWorx DTG RIP - a program for printing to a Direct To Garment printer was causing the issue. So, you may check if the similar thing is not happening in your case.
Regards,
Dhirendra

Windows Overlay Filter (wof.sys), file in Windows 8.1, is associated with BSOD in Windows 10 bld 9879

BSOD in Win 10 build 9879 is with bug check 0x1e. Wof.sys is a file that is in Win 8.1. HP g7-1310us (refurbished) laptop has been having BSOD's even when it had Win 7 installed. Checked RAM, hardware, and SATA disk but there is no specific lead to why BSOD's
happen routinely. Interestingly, there were no problems while this laptop was running Ubuntu 14. Any details on what Windows Overlay Filter driver named wof.sys does? Also, could this error be caused by faulty CPU? It has an Intel i3-2350M CPU @2.3Ghz, x64
based processor.
==================================================
Dump File         : 121114-22984-01.dmp
Crash Time        : 12/11/2014 5:23:05 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000008
Parameter 4       : 00000000`00000000
Caused By Driver : Wof.sys
Caused By Address : Wof.sys+1e40
File Description : Windows Overlay Filter
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.4.9879.0 (fbl_release.141103-1722)
Processor         : x64
Crash Address     : ntoskrnl.exe+161109
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\121114-22984-01.dmp
Processors Count : 4
Major Version     : 15
Minor Version     : 9879
Dump File Size    : 282,776
Dump File Time    : 12/11/2014 5:26:16 PM
==================================================
Gilda Sanchez

Here is the CPU data:
Intel(R) Processor Identification Utility
Version: 5.01.20140910
Time Stamp: 2014/12/11 19:28:20
Operating System: 6.2-9200-
Number of processors in system: 1
Current processor: #1
Active cores per processor: 2
Disabled cores per processor: 0
Processor Name: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
Type: 0
Family: 6
Model: 2A
Stepping: 7
Revision: 29
Maximum CPUID Level: D
L1 Instruction Cache: 2 x 32 KB
L1 Data Cache: 2 x 32 KB
L2 Cache: 2 x 256 KB
L3 Cache: 3 MB
Packaging: µPGA/BGA
Enhanced Intel SpeedStep(R) Technology: Yes
MMX(TM): Yes
Intel(R) SSE: Yes
Intel(R) SSE2: Yes
Intel(R) SSE3: Yes
Intel(R) SSE4: Yes
Intel(R) AES-NI: No
Intel(R) AVX: Yes
Enhanced Halt State: Yes
Execute Disable Bit: Yes
Gilda Sanchez

Access violation (0xC0000005) cause crash

Access violation (0xC0000005) cause crash. The crash report is as blow. It may be caused by the function IMAQ FillHole. How this function crash?
Who knows why? Thank you!
#Date: 2014年8月12日 14:21:51
#OSName: Windows 7 Ultimate
#OSVers: 6.1
#OSBuild: 7600
#AppName:
#Version: 12.0 32-bit
#AppKind: AppLib
#AppModDate: 08/12/2014 06:17 GMT
#LabVIEW Base Address: 0x30000000
<LVExec>
{"a":[
"vi": "D\\VISION_SYSTEM\\build\\MyProgram.exe\\IMAQ FillHole",
"ctx": "主应用程序实例",
"type": "subVI"
"vi": "D\\VISION_SYSTEM\\build\\MyProgram.exe\\ccd2表面2二值化.vi",
"ctx": "主应用程序实例",
"type": "subVI"
</LVExec>
<DEBUG_OUTPUT>
2014/8/12 16:48:15.894
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash 0x0: Crash caught by NIER
minidump id: 6e35643f-8ff2-49e6-bbde-98bac2ffa48a
ExceptionCode: 0xC0000005$N
</DEBUG_OUTPUT>
0x307277B4 - lvrt <unknown> + 0
0x30727B38 - lvrt <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77CA5A74 - ntdll <unknown> + 0
0x77C8B3C8 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
Solved!
Go to Solution.
Attachments:
ccd2表面2二值化.vi ‏21 KB

Hi,
please stick with your original thread! Don't create double posts!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Windows 7 and classpnp.sys safe mode loop.

Hello,
First of all this is an outline to the system I am running.
Acer Aspire X1800
Brought as a Windows Vista Home Premium 32bit, has now been upgraded to the equivalent in Windows 7.
Intel® Core™2 Quad processor
NVIDIA® GeForce® 7100 and nForce® 630i
4 GB of DDR2 667/800 MHz SDRAM (single-channel support on two DIMMs)
Serial ATA hard disk 1 TB
AMI PnP BIOS compatible with SMBIOS 2.4
PCI Express® 2.0 x16 slot
PCI Express® 2.0 x1 slot
Integrated NVIDIA® GeForce® 7100 graphics solution
PCI Express® 2.0 x16 graphics card support (low-profile)
I have been running Windows 7 now for some time a month or two and have no problems until now. I wanted to put my computer into safe mode so I can install the second disc of Fallout 3 Game of the year Edition. Frist of all I restarted the computer and used the F8 trick which did not work. The computer just booted into regular old Windows 7. So then I went through the msconfig way of things.
Now it is important to note that I had this problem when installing Fallout 3 on the same machine but running Vista. However the computer managed to "fix" it self back then.
The computer loads through all the drivers until it gets to C:\windows\system32\drivers\classpnp.sys
It stops loading here and tries to go into safe mode. The computer then comes up with a message saying entering Windows safe mode (or words to that effect) and lists some of the system details. The screen then changes to a blank screen with a mouse cursor in the middle of it. The computer then shuts down and begins to restart itself. It has gone into a infinite loop of restarts.
Ideas I have tried.
Pressing F8 brings up the boot menu, i have tried all options available in that. Nothing worked.
Interrupting the start up with a fake power cut. This resulted in the computer showing two options. Start Windows normally and start Windows recovery. Neither worked.
I have tried renaming the problem file C:\windows\system32\drivers\classpnp.sys to C:\windows\system32\drivers\classpnp.old
This resulted in the computer loading until the next value C:\windows\system32\drivers\disk.sys The computer then did all the usual loading. However before restarting the it showed the dreaded blue screen of death. It was over before i could see the error message that it contained.
I have tried resetting to a prior system date. this does not work either.
Other than that I have not been able to get into windows or anything else. The reason I am able to post this is a have access to another computer for the mean time.
Any ideas on this would very appreciated
Cheers
*EDIT*
Because the computer is Acer it should have a working E Recovery on it. However i can't remember if i deleted this or not. Will try using the hidden partition in the near future. This will most likely send me back to Vista but its a risk I am willing to take at this stage.

Hello Limbix
Thank you for your initial problem and the follow-up discussion on such a conundrum of a problem. As evidenced by the number of hits under Google for "Windows 7 boot sequence classpnp.sys" and 0 fixes, this problem is systematic of this OS. As
such, this is a ticking time bomb waiting for the most inopportune time to strike.
Furthmore, this problem has been known since RC1 of Windows 7. The problem still persists and there is no known remediation method.
KB 925810 is a unique solution when the OS is healthy. When this phenomena occurs, KB 925810 is a hoax for Laptop users and systems purchased from a vendor without a hardcopy of the OS media. For Home builts with a purchased hardcopy of the OS, KB 925810
is the option. But the option is to reinstall as opposed to a repair.
Using Ubuntu, to effect change by replacing CLASSPNP.SYS with a 6.1.7600.16385 version has produced mixed results. In addition, the method of downloading any file is fraught with problems of possible infection or worse yet a trojan. This essentially
leaves Option 2 and 4 as the SOP for this OS failure mode on laptops.
Problem:
New Toshiba A500 i7 with 8 Gig - Windows 7 Professional (Business)
A series of three critical patches were deployed to this machine at 9:30 pm on 5/26/2010 from Windows Update.  At 6:30 am 5/27/2010, the machine was discovered to have restarted and was stuck at the Starting Windows logo. Here were
the initial steps taken to remediate the problem.
Step 1. CTRL-ALT-DEL was used multiple times to restart the machine.
Results: The machine did not restart.
Step 2. Power recycled the machine.  Windows 7 offered to Launch Windows Repair on the OS. The repair was selected and completed with a request to restart.
Results: The machine stops at the Starting Windows logo. Still stuck.
Step 3. Restarted the machine through a power recycle. Pressed F8, selected last known good and restarted.
Results: The machine stops at the Starting Windows logo. Still stuck.
Step 4. Restarted the machine through a power recycle. Pressed F8, selected Advanced options.
Results: No options were available.
Step 5. Restarted the machine through a power recycle. Pressed F8, selected Boot loggin and restarted.
Results: The machine stops at the Starting Windows logo. Still stuck.
Step 6. Restarted the machine through a power recycle. Pressed F8, selected Safe Mode with Networking.
Results: The machine's last entry for the loading list was on
CLASSPNP.SYS and hung up.
Step 7. Began researching for the Windows 7 boot loading list for the before and after sequences to see if CLASSPNP.SYS was the culprit.
Results: Found this discussion and many more. Spent too much time researching for a solution. Most ended in silence.
Step 8. Considered taking the STATA drive and putting into an external enclosure.
Results: Did not take this step as the machine is under warranty. It was purchased in April, 2010.
Step 9. Going back over the Google research, discussion
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/64a52415-f9aa-448e-b79c-f4d9d27836c3 has Moderator Tim Quan MSFT stating that
"To obtain the phone numbers for specific technology request, please refer to the website listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS"
This support site will take a user to a list of vendors. The Toshiba link was selected. The link is the Toshiba home page. The Support link was
selected and a direct call was made to Toshiba at 7:30 am on 5/27/2010. A Toshiba case was opened. All 9 steps were presented to the support person and as directed the machine was put into a Factory reset mode.
Results: The machine has completed rebuilding as of 11:11 am 5/27/2010. Windows update patching is continuing the assult to be "secure".
Comments: One thing is certain, to be secure in one sense is have a machine in an inoperable state. However business cannot operate in an inoperable state. Neither
can a business operate in an insecure state. So, to receive an OS patch which causes the machine to be inoperable, has the quest to be secure been reduced to inoperability?
Suggestion: This problem needs more eyes and a better tracking method.
1. Is this a vendor issue, e.g. Motherboard, Memory, Hardware?
     1a. Is this lot specific?
     2a. Is there a driver mismatch?
2. Is this a process/sequence issue?
3. Is there a recovery process other than "Scorched earth"?
Sincerely,
John
risc of KY

AutoVue viewer caused crash while viewing .XSLX documents.

We use AutoVue Desktop Deployment Viewer incorporated in our application (using JNI). When viewing XLSX (Microsoft Excel) documents on Windows 8.1 x64 system it caused crash of application. It's reproducible only on Windows 8 (8.1 or Server2012) systems. If we set compatibility mode (Windows 7) then problem isn't reproducible.

I would recommend you log a ticket with customer support

Photoshop CC Content - Aware Move Tool causes crash

Does anyone have any ideas why this is happening? Content Aware Move tool causes crash every time so far with tiff and jpegs and its getting frustrating!
I have Windows 8.1 Pro with 8GB RAM
NVIDIA GeForce GT 650M Graphics
Photoshop CC 64 bit

Thanks for the reply JJMack - I have to be honest, i'm not exactly sure what i'm looking for here!
Source
Adobe Photoshop CC 2014
Summary
Stopped working
Date
06/04/2015 09:45
Status
Report sent
Description
Faulting Application Path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: Photoshop.exe
Application Version: 15.2.2.310
Application Timestamp: 5480338c
Fault Module Name: FaceDetection.dll
Fault Module Version: 2.2.6.32411
Fault Module Timestamp: 52e12400
Exception Code: c0000005
Exception Offset: 000000000001704d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: e87c
Additional Information 2: e87c816cbb2acbf5e54624fc2b1f98cc
Additional Information 3: 1879
Additional Information 4: 1879b998534215d47b0a850e45784427
Extra information about the problem
Bucket ID: 2dac81db98a57fddf5997edfd40ba6eb (85993531415)

Windows 8.0 error 0xc0000185+ \WINDOWS\System32\drivers\mountmgr.sys

So basicly what hapenned I was skypeing with some friends and suddenly my skype froze as it happened very often i pressed the CTRL+ALT+Del button to end skype
But suddenly a message popped up in the left bottom corner of my screen it says windows is not working
I was wondered why it would give me a message like this while i still could play a game at the same time => minecraft
i got the following reports shown at a bluescreen
error: error 0xc0000185
File: \WINDOWS\System32\drivers\mountmgr.sys
There also was an option to press F8 wich would lead me to another vluescreen that gave me different option i tried all of them and it kept showing me this error
I do not have any windows 8 install disc since it was preset on my computer and i don't know what to do if anyone can help me please reply to this and thank you for your time

This is clearly an issue with the drivers in your boot image. Yes, for boot image driver issues you must update the boot image and ensure it's been updated on the DPs for it to be effective.
It happens before you get a change to select a TS because its an issue with the boot image itself which must fully load for anything task sequence wise to actually happen.
When testing boot image image issues, always make sure that you know which boot image you are updating and which one was downloaded to the system as its possible they are two different things.
Also, for SP1 CU3, the boot images are based on Win 8 so make sure that you are using Win 8 compatible drivers in the boot image itself.
Jason | http://blog.configmgrftw.com

Windows 8.1 Pro Metro Apps Crash in Desktop mode

Everytime i switch from metro apps to my windows 8.1 desktop, the apps crash after a few seconds like switching apps on my ipad.
my desktop can run however many programs and not crash when switching between windows. how can i work on project siena if i have too save all my work just to google one little thing..on google and switch back,
browse myy files, find the saved one, open it, wiat for it too load, find where i was, and paste the code. everytime. for every little thing. even if i wanna check my email.
or if project siena was a desktop program i could just switch windows, google what i need, copy, switch back, paste. just like that.

Hi,
Since when you have this problem?
Did you appliyed windows updates recently ?
++
HK.
Hicham KADIRI | IT Consultant /Director. MCP - MCSA - MCTS - MCSE - MCITP - MCT

Photoshop CS4 and graphic cards. Can cause crashing?

Since upgrading to CS4 I seem to have increased crashing.
Here are my system specs.
Mac 2 x 2.66 GHz Dual-Core Intel Xeon
9 GB of Ram
250 GB internal dedicated scratch disc
NVDIA GeForce 7300 GT with 256 VRAM
After having endless techs look at my machine and upgrading everything. I am beginning to suspect the graphics card.
With OpenGL can a underperforming video card cause crashing in photoshop especially with massive file sizes ( multilayered CMYK poster sized files the can exceed 7 GB)?

Did you install the 11.0.1 update?
Is your OS up to date with patches?
Have you tried disabling OpenGL in preferences to avoid using the GPU/Graphics card?

Satellite C660-23M - driver causing crash when program starts

I have loaded a CAD program on my new 64bit laptop, the program will start then stops and windows closes it. In the crash reports the modules ntddll.dll and aticfx.dll both seem involved. Could there be some conflict, can I update a driver somehow?
I have seen a report on a gaming website that the aticfx.dll isa the problen on the c660 range.
Please help or the machine goes back to the shop.
PS I have tried running in compatibility mode and disabling antivirus but the problem is unchanged
Regards Ian

Hi
I think the CAD application is not fully compatible with the preinstalled graphic card driver.
The ntddll.dll files is part of the windows system and aticfx.dll file seems to be a part of the graphic card driver and therefore I think that you would need to use another graphic card driver.
The notebook seems to support an Intel HM55 HD graphic card. Try to update the driver using the newest version from the Intel page.

Barn doors transition causes crash

Dear Community,
Applied barn doors transition to a project in CS4. Stored that project in 2010.
Opened the project in CS6 CC - and barn doors caused crashes - so I cleaned off the old and applied replacement barn door transitions in CS6 CC.
Once the wipe is applied - its fairly stable - sometime crashes sometimes doesn't.
If I apply a broder colour to the wipe - all ok.
If I then apply a border thickness - crash every time.
System;
Premiere Pro CS6 - 6.0.3 (001 (MC: 264587)) through cloud membership
Updated and current
Win 7 Pro - SP1 - 64 Bit
Source footage SONY EX3 - .mp4 and still image .png's
No error messages - just crash and need to restart PP CS6
Try to apply colour and border to a barn door transition causes the error
This worked before on the smae project when created in CS4
Not running other software at the time
NewBlueFX modules installed but not applied to this area of sequence
i7 - 3.20GHz, 16GB RAM, SSD OS drive, 4 x drive RAID on LSI RAID card, - No I/O hardware
I am using Are you using Mercury Playback Engine Acceleration and CUDA
Problem occurs during normal edit - as soon as I start to adjust the barn doors wipe - I don't get to compression
Thanks
Dave

Doies it help anyone that I just received this from the email address; [email protected];
Hello,
You have received this email because the content you posted below has been rejected by our moderators.
Re: Barn doors transition causes crash
posted Jun 5, 2013 5:15 PM
Since the original report earlier today - I now just have to put the timeline scrubber over the barn doors transition and PP CS6 closes without an error message and without saving. The unfortunate part here is there doesn't seem to be any record or log of the crashes to be able to disseminate whats going wrong.
Barn doors worked in CS4 - and the only change in this project is the re-opening in CS6 CC."
Question; Did I put something in there that was defammatory, rude, obnoxious, incorrect or un-helpful?
If anyone here believes I did, I sincerely apologise for the need of moderators to have intervened... and for causing any offence.

HT5704 Hi, Two recent updates for my iPhone have caused crashes (down the white lead via iTunes).I have "fixed" but not sure of the cause?

Hi,
Two recent updates for my iPhone have caused crashes (down the white lead) via iTunes.
I have "fixed" but I don't know the cause?
Each time the update does n't complete.
The download does n't happen.
The computer & internet connection are good.
It is as if the Apple server does n't complete?
The phone stays in recovery mode, until you reset and rebuild in iTunes.
All software is up to date, but I can't find the cause
ANY IDEAS?
Regards,
P.
<Email Edited by Host>

No error messages.
It just fails to complete the download, so recovery mode is the next step.
This can be over a period of eight hours or more!
I have so many (original) Apple USB leads that I would n't know if I have been using the same one (if it was faulty).
Does this sound like a "common" problem?

Windows xp, minidump, applemtm.sys caused crash

Similar Messages

Maybe you are looking for