Random restart

Your Dump Report

Code:

  Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, fffffa80039551a0, 10de055e, fffffa80043ad250}
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 : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+99 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
 using a physical memory address that was not allocated by
 the USBport driver.
Arg2: fffffa80039551a0, Device extension pointer of the host controller
Arg3: 0000000010de055e, PCI Vendor,Product id for the controller
Arg4: fffffa80043ad250, Pointer to Endpoint data structure
Debugging Details:
------------------
 
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff88003c4de4e to fffff800030bc600
STACK_TEXT:  
fffff880`02f1ba38 fffff880`03c4de4e : 00000000`000000fe 00000000`00000005 fffffa80`039551a0 00000000`10de055e : nt!KeBugCheckEx
fffff880`02f1ba40 fffff880`03be1a45 : 00000000`00000003 fffffa80`043ad010 00000000`00000000 fffff880`053e2000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`02f1ba80 fffff880`03be3737 : fffffa80`043ad250 fffffa80`043ad010 00000000`00000000 fffffa80`039551a0 : usbohci!OHCI_PollAsyncEndpoint+0x99
fffff880`02f1bae0 fffff880`03c21e8b : 00000000`00000002 fffffa80`043ad010 fffffa80`039551a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
fffff880`02f1bb10 fffff880`03c269b1 : 00000000`00000040 00000000`00000004 fffffa80`043ad010 fffffa80`03955050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`02f1bb40 fffff880`03c32043 : fffffa80`039551a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`02f1bba0 fffff880`03c22f89 : fffffa80`03955050 00000000`00000000 fffffa80`04d4d702 fffffa80`03955a10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff880`02f1bc00 fffff880`010744ce : fffffa80`04d4d000 fffffa80`03955a10 fffffa80`04d4d750 fffffa80`03955a28 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bc30 fffffa80`04d4d000 : fffffa80`03955a10 fffffa80`04d4d750 fffffa80`03955a28 fffff880`009eb180 : sptd+0x424ce
fffff880`02f1bc38 fffffa80`03955a10 : fffffa80`04d4d750 fffffa80`03955a28 fffff880`009eb180 00000000`00000000 : 0xfffffa80`04d4d000
fffff880`02f1bc40 fffffa80`04d4d750 : fffffa80`03955a28 fffff880`009eb180 00000000`00000000 fffff880`009efec0 : 0xfffffa80`03955a10
fffff880`02f1bc48 fffffa80`03955a28 : fffff880`009eb180 00000000`00000000 fffff880`009efec0 00000000`00000022 : 0xfffffa80`04d4d750
fffff880`02f1bc50 fffff880`009eb180 : 00000000`00000000 fffff880`009efec0 00000000`00000022 00000000`00000000 : 0xfffffa80`03955a28
fffff880`02f1bc58 00000000`00000000 : fffff880`009efec0 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffff880`009eb180
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
usbohci!OHCI_PollAsyncEndpoint+99
fffff880`03be1a45 8bd3            mov     edx,ebx
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  usbohci!OHCI_PollAsyncEndpoint+99
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: usbohci
IMAGE_NAME:  usbohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc06
FAILURE_BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollAsyncEndpoint+99
BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollAsyncEndpoint+99
Followup: MachineOwner
---------

The Cause per report
usbohci.sys,
Usbohci.sys is located in the folder C:\Windows\System32\drivers.
The driver can be started or stopped from Services in the Control Panel or by otherprograms. It is a Windows system file. The program has no visible window. The file is a trustworthy file from Microsoft. There is no detailed description of this service. usbohci.sys seems to be a compressed file. Therefore the technical security rating is 0% dangerous.

Actual, Probable cause
SPTD.

These reports are a roadmap to a solution and sometimes several are needed to reach our destination.

Solution
Uninstall Daemon Tools or other Virtualization Program which use the SPTD driver. Then uninstall SPTD with this tool.
http://www.duplexsecure.com/en/downloads

Based upon your Dump report I must make the following additional suggestions:

Virus Scan
SFC /scannow

www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Use your computer, if another BSOD occurs with the same problem, we may have to unisntall Usbochci.sys. and reinstall current. I am not suggesting this now as it is a MS driver and the problem will be most likely corrected with the SPTD removal. If another BSOD occurs with a different report, we will analyze further.

In an attempt to offer the most efficient service to all our members, a study is being prepared on BSOD involving SPTD. We would appreciate your reporting back to us a week after you have been BSOD free. Thanks for your help.