Hello and Welcome to SF !
We need the complete logs
Blue Screen of Death (BSOD) Posting Instructions
Based on the crash dump you attached it's pointing to Windows Kernel which may not be the problem. Lets start with basics
Run a
Hardware Diagnostic !! « Captain Debugger follow this thread
Run
SFC /SCANNOW Command - System File Checker
You have sptd.sys which is notorious for BSOD. Use this article and remove the driver
DuplexSecure - FAQ Update the following Drivers: Code:
smwdm.sys Mon Mar 28 19:49:36 2005
LVUSBSta.sys Sat May 12 05:10:49 2007
e100b325.sys Sat Nov 17 00:23:32 2007
Use this guide for more help
Driver Troubleshooting !! « Captain Debugger Bugcheck: Code:
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82549343, The address that the exception occurred at
Arg3: 80ebdc38, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!TimersProc+111
82549343 ff8000010000 inc dword ptr [eax+100h]
TRAP_FRAME: 80ebdc38 -- (.trap 0xffffffff80ebdc38)
ErrCode = 00000002
eax=07ce0b20 ebx=00000000 ecx=00000000 edx=00000000 esi=ff1c9a60 edi=ff1c9a6c
eip=82549343 esp=80ebdcac ebp=80ebdcc8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
win32k!TimersProc+0x111:
82549343 ff8000010000 inc dword ptr [eax+100h] ds:0023:07ce0c20=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8249843c to 82549343
STACK_TEXT:
80ebdcc8 8249843c 00000004 0186fbfc 8255c425 win32k!TimersProc+0x111
80ebdd04 82498586 00000004 00000002 8b4af400 win32k!RawInputThread+0x61f
80ebdd18 8255c440 00000004 0186fbfc 80ebdd34 win32k!xxxCreateSystemThreads+0x4a
80ebdd28 8307f79a 00000004 0186fc3c 779464f4 win32k!NtUserCallNoParam+0x1b
80ebdd28 779464f4 00000004 0186fc3c 779464f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0186fc3c 00000000 00000000 00000000 00000000 0x779464f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!TimersProc+111
82549343 ff8000010000 inc dword ptr [eax+100h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!TimersProc+111
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cbe5b31
FAILURE_BUCKET_ID: 0x8E_win32k!TimersProc+111
BUCKET_ID: 0x8E_win32k!TimersProc+111
Followup: MachineOwner
Hope this helps,
Captain