
Quote: Originally Posted by
Peaches491
Just like it said, a random BSOD during bootup.

Hi and welcome
the two files that caused this crash are both involved in the win 7 security system and often fail on "cracked" versions. there is no info as to what else they are used for. there is also some info that these can also be viral
If your softeare is legal and activated. I would
Run a system file check
type cmd in search>right click and run as admin>sfc /scannow
if you get errors in that you should leet us know
If you are overclocking stop
Ken J+
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\011710-23774-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Sun Jan 17 17:48:19.708 2010 (GMT-5)
System Uptime: 0 days 0:02:27.581
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff880047697ea, fffff880038e1770, 0}
Probably caused by : spsys.sys ( spsys+197ea )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff880047697ea, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880038e1770, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
spsys+197ea
fffff880`047697ea 42 ???
CONTEXT: fffff880038e1770 -- (.cxr 0xfffff880038e1770)
rax=0000000000000000 rbx=0000000000000004 rcx=0000000000000108
rdx=0000000000000001 rsi=00000000000002e0 rdi=fffff8a002804000
rip=fffff880047697ea rsp=fffff880038e2150 rbp=00000000000001a8
r8=0000000000000004 r9=000000000000007c r10=000000000000009c
r11=00000000000004f4 r12=0000000000010835 r13=0000000000000001
r14=00000000000008c4 r15=0000000000000834
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
spsys+0x197ea:
fffff880`047697ea 42 ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: sppsvc.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880047697ea
STACK_TEXT:
fffff880`038e2150 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : spsys+0x197ea
FOLLOWUP_IP:
spsys+197ea
fffff880`047697ea 42 ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: spsys+197ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: spsys
IMAGE_NAME: spsys.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a085e7a
STACK_COMMAND: .cxr 0xfffff880038e1770 ; kb
FAILURE_BUCKET_ID: X64_0x3B_spsys+197ea
BUCKET_ID: X64_0x3B_spsys+197ea
Followup: MachineOwner
---------