BSOD, Reference Pointer

I have a Dell Vostro 1520, with Windows 7 Ultimate 64 bit.

Please help.

I ran the debugging program and derived this, see below:

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

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Tue Jan 19 15:57:20.985 2010 (GMT-6)
System Uptime: 0 days 0:01:03.889
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 18, {0, fffffa800c9f59c0, 2, ffffffffffffffff}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for PCTCore64.sys -
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Probably caused by : PCTCore64.sys ( PCTCore64!PiRegister+1c39f )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa800c9f59c0, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object?s reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x18
PROCESS_NAME: pctsSvc.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002a1ffac to fffff80002a89f00
STACK_TEXT:
fffff880`07f01628 fffff800`02a1ffac : 00000000`00000018 00000000`00000000 fffffa80`0c9f59c0 00000000`00000002 : nt!KeBugCheckEx
fffff880`07f01630 fffff880`01020987 : fffffa80`0d2c7b88 fffff8a0`03368490 00000000`00000460 00000000`00000460 : nt! ?? ::FNODOBFM::`string'+0x46661
fffff880`07f01690 fffff880`010216d1 : fffff8a0`03368490 00000000`c000000f fffff880`07f01770 fffff880`07f01760 : PCTCore64!PiRegister+0x1c39f
fffff880`07f016c0 fffff880`01004c33 : 00000000`00000000 00000000`00000468 fffffa80`0daf92c0 00000000`c000000d : PCTCore64!PiRegister+0x1d0e9
fffff880`07f017b0 fffff800`02da23a7 : fffffa80`0daf93d8 fffff880`07f01c60 fffffa80`0c2f7610 fffffa80`0daf92c0 : PCTCore64!PiRegister+0x64b
fffff880`07f019d0 fffff800`02da2c06 : fffff880`07f01bb8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`07f01b00 fffff800`02a89153 : ffffffff`ffffffff fffffa80`0c0fd360 00000000`05c2f0a0 fffff800`00000024 : nt!NtDeviceIoControlFile+0x56
fffff880`07f01b70 00000000`73672dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05c2f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73672dd9

STACK_COMMAND: kb
FOLLOWUP_IP:
PCTCore64!PiRegister+1c39f
fffff880`01020987 488b4b28 mov rcx,qword ptr [rbx+28h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: PCTCore64!PiRegister+1c39f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PCTCore64
IMAGE_NAME: PCTCore64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4af35032
FAILURE_BUCKET_ID: X64_0x18_PCTCore64!PiRegister+1c39f
BUCKET_ID: X64_0x18_PCTCore64!PiRegister+1c39f
Followup: MachineOwner
---------