Windows 7 Professional hanging frequently while working.

It looks as if Semantic is causing the issue. Please remove all Norton products with this tool: ftp://ftp.symantec.com/public/englis...moval_Tool.exe

Replace it with Microsoft Security Essentials.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_Bluescreen logs.zip\Bluescreen logs\061410-23088-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8284f000 PsLoadedModuleList = 0x82997810
Debug session time: Mon Jun 14 04:52:21.278 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:52.088
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000f6, Referencing user handle as KernelMode.
Arg2: 00000064, Handle value being referenced.
Arg3: 88550cd8, Address of the current process.
Arg4: 905a55ee, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------

Unable to load image \??\C:\Program Files\Common Files\Symantec Shared\SPBBC\SPBBCDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SPBBCDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for SPBBCDrv.sys
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS

BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82b83f03 to 8292bd10

STACK_TEXT:  
886f59dc 82b83f03 000000c4 000000f6 00000064 nt!KeBugCheckEx+0x1e
886f59fc 82b88766 00000064 88550cd8 88550958 nt!VerifierBugCheckIfAppropriate+0x30
886f5a90 82a732b4 00000064 00000000 00000000 nt!VfCheckUserHandle+0x14f
886f5ac0 82a7316e 00000064 10000000 85686f78 nt!ObReferenceObjectByHandleWithTag+0x13b
886f5ae4 82b91736 00000064 10000000 85686f78 nt!ObReferenceObjectByHandle+0x21
886f5b0c 905a55ee 00000064 10000000 85686f78 nt!VerifierObReferenceObjectByHandle+0x21
WARNING: Stack unwind information not available. Following frames may be wrong.
886f5b74 90569279 80000350 00000064 886f5bb0 SPBBCDrv+0x4d5ee
886f5b94 9056948e 00000064 886f5bb0 886f5c4c SPBBCDrv+0x11279
886f5bb4 905681a0 8b70afb8 886f5c4c 00000000 SPBBCDrv+0x1148e
886f5bd4 90568720 886f5c4c 886f5c1c 8b70afb8 SPBBCDrv+0x101a0
886f5bec 90568e0c 886f5c4c 886f5c1c 886f5c4c SPBBCDrv+0x10720
886f5c20 9056cdf0 00000000 886f5cbc 8e10efc0 SPBBCDrv+0x10e0c
886f5c3c 9056bb65 886f5c4c 8d4aefe8 905b16d0 SPBBCDrv+0x14df0
886f5c74 8b1c8c8d 8e10efc0 886f5cc4 886f5ca4 SPBBCDrv+0x13b65
886f5c84 8b1cb13a 886f5cc4 c0000001 8d4c2fd0 SYMEVENT+0xfc8d
886f5ca4 8b1cd3d5 886f5cbc 8a54efd0 00000064 SYMEVENT+0x1213a
886f5d24 8289244a 00000064 0011f7e0 0011f7d8 SYMEVENT+0x143d5
886f5d24 00000064 00000064 0011f7e0 0011f7d8 nt!KiFastCallEntry+0x12a
0000003b 00000000 00000000 00000000 00000000 0x64


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SPBBCDrv+4d5ee
905a55ee 3975fc          cmp     dword ptr [ebp-4],esi

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  SPBBCDrv+4d5ee

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SPBBCDrv

IMAGE_NAME:  SPBBCDrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b2712e4

FAILURE_BUCKET_ID:  0xc4_f6_VRF_SPBBCDrv+4d5ee

BUCKET_ID:  0xc4_f6_VRF_SPBBCDrv+4d5ee

Followup: MachineOwner
---------

0: kd> lmvm SPBBCDrv
start    end        module name
90558000 905c2000   SPBBCDrv T (no symbols)           
    Loaded symbol image file: SPBBCDrv.sys
    Image path: \??\C:\Program Files\Common Files\Symantec Shared\SPBBC\SPBBCDrv.sys
    Image name: SPBBCDrv.sys
    Timestamp:        Mon Dec 14 23:39:00 2009 (4B2712E4)
    CheckSum:         00074F14
    ImageSize:        0006A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4