Unexpected Shutdown. .dmp and .xml Files Included.

[YukonTrooper]

Hey, guys. I'd like to start off by saying the forum here is great. I've already learned much about Windows 7 by just browsing this forum. Now, on to my problem:

I'm getting unexpected shutdowns and am not sure why. I've included my .dmp file and .xml file that Windows says explains the issue. I'm hoping maybe some debug expert could translate those files for me. All help is greatly appreciated!

 

[zigzag3143]

Hey, guys. I'd like to start off by saying the forum here is great. I've already learned much about Windows 7 by just browsing this forum. Now, on to my problem:

I'm getting unexpected shutdowns and am not sure why. I've included my .dmp file and .xml file that Windows says explains the issue. I'm hoping maybe some debug expert could translate those files for me. All help is greatly appreciated!

This crash was caused by your daemon tools (sptd.sys). I would remove it, to see if it fixes the problems

I would also run a system file check
type cmd in search>right click and run as admin>sfc /scannow (note the space between sfc and "/")

Let us know the results

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\032210-11218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
Debug session time: Mon Mar 22 08:22:10.897 2010 (GMT-4)
System Uptime: 0 days 8:18:47.850
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {50, 2, 1, fffff80002cd5b2e}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+424ce )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000050, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cd5b2e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f030e0
 0000000000000050 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireSpinLockRaiseToDpc+e
fffff800`02cd5b2e 4889742450      mov     qword ptr [rsp+50h],rsi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  einsteinbinary

TRAP_FRAME:  fffff88003192920 -- (.trap 0xfffff88003192920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000e4ec00 rbx=0000000000000000 rcx=fffffa80061fe900
rdx=fffff88000ec67c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd5b2e rsp=fffff88003192ab0 rbp=fffffa80061fe8b0
 r8=fffffa80076d0c70  r9=0000000000000050 r10=fffffa80061fa010
r11=fffff88003192ca8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeAcquireSpinLockRaiseToDpc+0xe:
fffff800`02cd5b2e 4889742450      mov     qword ptr [rsp+50h],rsi ss:fffff880`03192b00=fffffa80066bd050
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ccc469 to fffff80002cccf00

STACK_TEXT:  
fffff880`031927d8 fffff800`02ccc469 : 00000000`0000000a 00000000`00000050 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`031927e0 fffff800`02ccb0e0 : 00000000`00008000 fffffa80`061fe8a0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03192920 fffff800`02cd5b2e : fffffa80`066bd050 fffffa80`061fe010 00000000`00000000 fffffa80`066bda10 : nt!KiPageFault+0x260
fffff880`03192ab0 fffff880`00e4db6e : fffffa80`066bd050 fffff880`04465ba2 fffffa80`08110010 fffffa80`061fe8a0 : nt!KeAcquireSpinLockRaiseToDpc+0xe
fffff880`03192b00 fffff880`00e4ddc4 : fffffa80`066bda10 fffff880`044800d8 00000000`00000000 fffffa80`00000009 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x9e
fffff880`03192b70 fffff800`02cb7935 : fffffa80`061fe250 fffff880`044b012a fffffa80`061fe4e0 fffffa80`066be6a0 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`03192ba0 fffff800`02ccf516 : fffffa80`076d0c0b 00000000`00000000 00000000`00000000 fffffa80`076d0a60 : nt!IopUnloadSafeCompletion+0x55
fffff880`03192bd0 fffff880`044665d9 : fffffa80`066bd050 fffffa80`077be100 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`03192cb0 fffff880`04466ab7 : fffffa80`08110002 fffffa80`076d0a60 00000000`ffffffff fffffa80`066bdea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`03192d90 fffff880`0446464f : fffffa80`066bdea8 fffffa80`066bd1a0 fffffa80`066be040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`03192df0 fffff880`04455f89 : fffffa80`066bd050 00000000`00000000 fffffa80`06518702 fffffa80`066bdea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`03192e30 fffff880`010654ce : fffffa80`06518000 fffffa80`066bdea8 fffffa80`06518750 fffffa80`066bdec0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`03192e60 fffffa80`06518000 : fffffa80`066bdea8 fffffa80`06518750 fffffa80`066bdec0 00000000`00000000 : sptd+0x424ce
fffff880`03192e68 fffffa80`066bdea8 : fffffa80`06518750 fffffa80`066bdec0 00000000`00000000 00000000`74992450 : 0xfffffa80`06518000
fffff880`03192e70 fffffa80`06518750 : fffffa80`066bdec0 00000000`00000000 00000000`74992450 00000000`74992450 : 0xfffffa80`066bdea8
fffff880`03192e78 fffffa80`066bdec0 : 00000000`00000000 00000000`74992450 00000000`74992450 00000000`00000022 : 0xfffffa80`06518750
fffff880`03192e80 00000000`00000000 : 00000000`74992450 00000000`74992450 00000000`00000022 00000000`00000000 : 0xfffffa80`066bdec0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sptd+424ce
fffff880`010654ce ??              ???

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  sptd+424ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sptd

IMAGE_NAME:  sptd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ad24632

FAILURE_BUCKET_ID:  X64_0xA_sptd+424ce

BUCKET_ID:  X64_0xA_sptd+424ce

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

 

[YukonTrooper]

Wow, thanks for the quick reply. I do not have Daemon Tools installed at this time, although I believe I did in the past, which accounts for sptd.sys being in my system32\drivers folder. What can cause a dormant driver file to crash the system? I did a system file check and it completed with no errors. Should I just delete sptd.sys?

 

[zigzag3143]

Wow, thanks for the quick reply. I do not have Daemon Tools installed at this time, although I believe I did in the past, which accounts for sptd.sys being in my system32\drivers folder. What can cause a dormant driver file to crash the system? I did a system file check and it completed with no errors. Should I just delete sptd.sys?

\
Yep. delete it. May have to do it in safe mode.

 

[YukonTrooper]

Thanks for the help!