Windows 7: BSOD windows 7 64bit help me

ASACPI.sys        fffff880`055ed000    fffff880`055f5000    0x00008000    0x42476c4c    3/27/2005 9:30:36 PM                        
SSPORT.sys        fffff880`0932c000    fffff880`09334000    0x00008000    0x42fbda34    8/11/2005 6:07:32 PM                        
secdrv.SYS        fffff880`092f4000    fffff880`092ff000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
speedfan.sys        fffff880`01de2000    fffff880`01de9000    0x00007000    0x45168798    9/24/2006 8:26:48 AM                        
hardlock.sys        fffff880`0726e000    fffff880`072bac00    0x0004cc00    0x456f10e7    11/30/2006 12:12:07 PM                        
aksdf.sys        fffff880`07a00000    fffff880`07a0fe00    0x0000fe00    0x458033cc    12/13/2006 12:09:32 PM                        
PxHlpa64.sys        fffff880`013ce000    fffff880`013d9ae0    0x0000bae0    0x475dd06d    12/10/2007 6:49:01 PM                        
adfs.SYS        fffff880`07be5000    fffff880`07bfd000    0x00018000    0x48640195    6/26/2008 3:52:37 PM                        
timntr.sys        fffff880`01a51000    fffff880`01b2b000    0x000da000    0x48ca818c    9/12/2008 9:49:48 AM                        
tifsfilt.sys        fffff880`073d2000    fffff880`073e9000    0x00017000    0x48ca81c4    9/12/2008 9:50:44 AM                        
snman380.sys        fffff880`01c00000    fffff880`01c3b000    0x0003b000    0x48cfe82c    9/16/2008 12:09:00 PM                        
tdrpm147.sys        fffff880`01c56000    fffff880`01dda000    0x00184000    0x48f31f78    10/13/2008 5:14:16 AM                        
MTiCtwl.sys        fffff880`03fef000    fffff880`03ff8000    0x00009000    0x490ffc82    11/4/2008 2:40:50 AM

Loading Dump File [C:\Users\K\Desktop\122209-21262-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`03018000 PsLoadedModuleList = 0xfffff800`03255e50
Debug session time: Tue Dec 22 03:03:03.157 2009 (GMT-5)
System Uptime: 0 days 0:03:16.999
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\CSFile.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CSFile.sys
*** ERROR: Module load completed but symbols could not be loaded for CSFile.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000002, fffff800030b87f8, fffff880035a13a0, fffff880035a1440}

Unable to load image \SystemRoot\system32\drivers\PCTCore64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PCTCore64.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore64.sys
Probably caused by : CSFile.sys ( CSFile+132b )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000002, The exception code that was not handled
Arg2: fffff800030b87f8, The address that the exception occurred at
Arg3: fffff880035a13a0, Exception Record Address
Arg4: fffff880035a1440, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000002 - {Not Implemented}  The requested operation is not implemented.

FAULTING_IP: 
nt!RtlRaiseStatus+18
fffff800`030b87f8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

EXCEPTION_RECORD:  fffff880035a13a0 -- (.exr 0xfffff880035a13a0)
ExceptionAddress: fffff800030b87f8 (nt!RtlRaiseStatus+0x0000000000000018)
   ExceptionCode: c0000002
  ExceptionFlags: 00000001
NumberParameters: 0

CONTEXT:  fffff880035a1440 -- (.cxr 0xfffff880035a1440)
rax=fffff88001382be0 rbx=00000000c0000002 rcx=fffff880035a1440
rdx=fffffa80059cda60 rsi=fffffa80059cda60 rdi=fffffa80059cda60
rip=fffff800030b87f8 rsp=fffff880035a1380 rbp=0000000000000001
 r8=fffffa80053dae70  r9=0000000000000002 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=fffffa80058dc4d0 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00000282
nt!RtlRaiseStatus+0x18:
fffff800`030b87f8 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h] ss:fffff880`035a1538=fffff800030b87f8
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000002 - {Not Implemented}  The requested operation is not implemented.

LAST_CONTROL_TRANSFER:  from fffff8800137632b to fffff800030b87f8

STACK_TEXT:  
fffff880`035a1380 fffff880`0137632b : fffffa80`047d7070 fffff880`00f64ea4 fffffa80`059cda60 fffffa80`059cda60 : nt!RtlRaiseStatus+0x18
fffff880`035a1920 fffffa80`047d7070 : fffff880`00f64ea4 fffffa80`059cda60 fffffa80`059cda60 fffffa80`047e2590 : CSFile+0x132b
fffff880`035a1928 fffff880`00f64ea4 : fffffa80`059cda60 fffffa80`059cda60 fffffa80`047e2590 fffff880`00f636af : 0xfffffa80`047d7070
fffff880`035a1930 fffff880`00f636af : fffffa80`058dc4d0 00000000`00000000 00000000`00000008 00000000`00000000 : fltmgr!FltpPassThrough+0x594
fffff880`035a19b0 fffff800`0339d40e : fffffa80`047d7070 00000000`00000001 fffffa80`059cda60 00000000`00000000 : fltmgr!FltpDispatch+0x9f
fffff880`035a1a10 fffff800`0308f0b4 : fffff800`0328c740 fffffa80`047c1010 fffffa80`03a1b600 00000000`00000000 : nt!IopDeleteFile+0x11e
fffff880`035a1aa0 fffff880`013a8b85 : fffffa80`047c1010 00000000`00000000 fffffa80`053d8c00 fffffa80`053d8c00 : nt!ObfDereferenceObject+0xd4
fffff880`035a1b00 fffffa80`047c1010 : 00000000`00000000 fffffa80`053d8c00 fffffa80`053d8c00 00000000`00000008 : PCTCore64+0x1eb85
fffff880`035a1b08 00000000`00000000 : fffffa80`053d8c00 fffffa80`053d8c00 00000000`00000008 fffff880`00f6981e : 0xfffffa80`047c1010


FOLLOWUP_IP: 
CSFile+132b
fffff880`0137632b ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  CSFile+132b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CSFile

IMAGE_NAME:  CSFile.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b20aad1

STACK_COMMAND:  .cxr 0xfffff880035a1440 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_CSFile+132b

BUCKET_ID:  X64_0x7E_CSFile+132b

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