Get rid of Symantec Software and use MSE..
Norton Removal tool:
Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Administrator\Downloads\bsod files\Windows_NT6_BSOD_jcgriff2\081711-17674-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c8f670
Debug session time: Wed Aug 17 17:11:21.970 2011 (UTC - 6:00)
System Uptime: 0 days 8:44:15.813
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff80002ace6ec}
Unable to load image \SystemRoot\system32\DRIVERS\scmndisp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
Probably caused by : scmndisp.sys ( scmndisp+16d1 )
Followup: MachineOwner
---------
1: 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: 0000000000000000, 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: fffff80002ace6ec, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf9100
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeWaitForSingleObject+13c
fffff800`02ace6ec f00fba2e07 lock bts dword ptr [rsi],7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009e6d80 -- (.trap 0xfffff880009e6d80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000001ec481 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ace6ec rsp=fffff880009e6f10 rbp=0000000000000000
r8=fffff78000000008 r9=0000000000000000 r10=0000000000000000
r11=fffff880009e9180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x13c:
fffff800`02ace6ec f00fba2e07 lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ac61e9 to fffff80002ac6c40
STACK_TEXT:
fffff880`009e6c38 fffff800`02ac61e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009e6c40 fffff800`02ac4e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009e6d80 fffff800`02ace6ec : fffffa80`085c7ed0 fffff880`0149319a 00000000`00000001 00000000`abababab : nt!KiPageFault+0x260
fffff880`009e6f10 fffff880`016f1982 : 00000000`00000000 fffffa80`00000000 fffff880`009e6f00 00000000`00000000 : nt!KeWaitForSingleObject+0x13c
fffff880`009e6fb0 fffff880`01b086d1 : 00000000`00000000 00000000`00000088 00000000`00000001 00000000`00000000 : ndis!NdisWaitEvent+0x32
fffff880`009e6ff0 00000000`00000000 : 00000000`00000088 00000000`00000001 00000000`00000000 fffff880`014283e0 : scmndisp+0x16d1
STACK_COMMAND: kb
FOLLOWUP_IP:
scmndisp+16d1
fffff880`01b086d1 ?? ???
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: scmndisp+16d1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: scmndisp
IMAGE_NAME: scmndisp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45add4b3
FAILURE_BUCKET_ID: X64_0xA_scmndisp+16d1
BUCKET_ID: X64_0xA_scmndisp+16d1
Followup: MachineOwner
---------