It looks like a Samsung Android Phone to me - please un-install it from your system. Also, if there is software associated with it (such as Samsung KIES) please uninstall that also.GT-I9100 USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_ANDROID\6&11B631E3&0&0000 This device cannot start.
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):[DEL] DuplexSecure - FAQ [/DEL]Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
[font=lucida console]**************************Sat Nov 17 06:17:26.211 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111712-41293-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]1 days 12:19:10.330[/B]
BugCheck Code: [B]BugCheck 9F, {3, fffffa8008800060, fffff802c9d188e0, fffffa8006ecde10}[/B]
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
Probably caused by :[B]atapi.sys[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8008800060, Physical Device Object of the stack
Arg3: fffff802c9d188e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8006ecde10, The blocked IRP
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x9F_3_IMAGE_atapi.sys[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz"
MaxSpeed: 2500
CurrentSpeed: [B]2500[/B]
BIOS Version 2001
BIOS Release Date 02/25/2009
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 13 07:41:39.166 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111512-29749-01.dmp]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111412-68000-01.dmp]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111312-26878-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]0 days 14:11:57.602[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff8027f018241, fffff8800ce44480, 0}[/B]
Probably caused by :[B]memory_corruption[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8027f018241, Address of the instruction which caused the bugcheck
Arg3: fffff8800ce44480, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x3B
PROCESS_NAME: [B]Steam.exe[/B]
FAILURE_BUCKET_ID: [B]MEMORY_CORRUPTION_STRIDE[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111212-31403-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]0 days 23:45:22.874[/B]
BugCheck Code: [B]BugCheck 116, {fffffa8008f56010, fffff8800758da88, ffffffffc00000b5, a}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments:
Arg1: fffffa8008f56010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800758da88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x116_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
[font=lucida console]**************************Sat Nov 17 06:17:26.211 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)[/B][/COLOR]
[COLOR=RED][B]ADIHdAud.sys Thu May 21 04:21:06 2009 (4A150EF2)[/B][/COLOR]
[COLOR=RED][B]a4bwcvqo.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
nvhda64v.sys Tue Jul 3 11:25:04 2012 (4FF30ED0)
intelppm.sys Wed Jul 25 22:26:48 2012 (5010AAE8)
[COLOR=RED][B]sptd.sys Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
yk63x64.sys Tue Sep 25 13:20:12 2012 (5061E7CC)
nvlddmkm.sys Fri Nov 9 05:17:51 2012 (509CD84F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 13 07:41:39.166 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ak6u1uev.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
ssudbus.sys Thu Aug 30 21:34:04 2012 (5040148C)
ssudmdm.sys Thu Aug 30 21:34:34 2012 (504014AA)
nvlddmkm.sys Tue Oct 2 14:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
[COLOR=RED][B]a5368rdo.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[/font]
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):[DEL] DuplexSecure - FAQ [/DEL]Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
[font=lucida console]**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111212-31403-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]0 days 23:45:22.874[/B]
BugCheck Code: [B]BugCheck 116, {fffffa8008f56010, fffff8800758da88, ffffffffc00000b5, a}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments:
Arg1: fffffa8008f56010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800758da88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x116_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
[font=lucida console]**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)[/B][/COLOR]
[COLOR=RED][B]ADIHdAud.sys Thu May 21 04:21:06 2009 (4A150EF2)[/B][/COLOR]
[COLOR=RED][B]a5368rdo.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
intelppm.sys Wed Jul 25 22:26:48 2012 (5010AAE8)
[COLOR=RED][B]sptd.sys Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
nvlddmkm.sys Tue Oct 2 14:21:13 2012 (506B3099)
[/font]
Does this mean that there were errors when running MemTest?memstest080 zrobilm 50 tests a mistake.
[font=lucida console]**************************Mon Nov 26 14:39:21.476 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112612-15428-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 6:00:41.185[/B]
BugCheck Code: [B]BugCheck 139, {3, fffff80007e7e690, fffff80007e7e5e8, 0}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+513 )[/B]
BugCheck Info: [B]KERNEL_SECURITY_CHECK_FAILURE (139)[/B]
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff80007e7e690, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff80007e7e5e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x139
PROCESS_NAME: [B]t6mp.exe[/B]
FAILURE_BUCKET_ID: [B]0x139_3_dxgmms1!VidSchiUpdateContextStatus[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
[font=lucida console]**************************Mon Nov 26 14:39:21.476 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ASACPI.sys Wed May 13 21:25:17 2009 (4A0B72FD)[/B][/COLOR]
[COLOR=RED][B]ADIHdAud.sys Thu May 21 04:21:06 2009 (4A150EF2)[/B][/COLOR]
[COLOR=RED][B]ahkie9gm.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
nvhda64v.sys Tue Jul 3 11:25:04 2012 (4FF30ED0)
intelppm.sys Wed Jul 25 22:26:48 2012 (5010AAE8)
[COLOR=RED][B]sptd.sys Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
nvlddmkm.sys Sun Nov 18 06:10:12 2012 (50A8C214)
[/font]
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: rspndr.sys
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x00000139 (0x0000000000000003, 0xfffff880001d48b0, 0xfffff880001d4808,
0x0000000045000000)
*** rspndr.sys - Address 0xfffff8800b1d48b0 base at 0xfffff88003e28000 DateStamp
0x0010aa46