BSOD irql not less or equal

Windows7x64 FR (replaced Vista/x64)
6 GB Ram
80 GB Intel X25M SSD
320 GB Samsung internal SATA
2 TB Samsung internal SATA
1.5 TB WD external SATA
Corsair HX520 PSU
Asus P5B-E running Intel E6600, 7600GT, Antec Solo case with dual HD cooling fans up front.

System built 4.5 years ago.
Win7 re-installed 12/2010 on the SSD after my 2nd HD failure in one year.. both on WD740ADFD Raptors. The first Raptor HD failed in 01/2010 at which point I put in a warranty replacement Raptor and switched from Vista/64 to Win7/64. The Intel SSD replaced the Raptor HD for my OS drive at the time of the 12/2010 Raptor failure.

See attached bsod file. Unable to run the perfmon /report as it returns the following when I run it:

ASACPI.sys the 2005 version is a huge cause of BSODs

Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

BSOD seems to have been caused by TightVCN TightVNC: VNC-Compatible Free Remote Control / Remote Desktop Software
Reinstall this software or remove it

Code:

ASACPI.sys        fffff880`03c55000    fffff880`03c5d000    0x00008000    0x42476c4c    28/03/2005 06:30:36

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000c0000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa8008566b30, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cba100
 00000000c0000008 

CURRENT_IRQL:  2

FAULTING_IP: 
+0
fffffa80`08566b30 0300            add     eax,dword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  tvnserver.exe

TRAP_FRAME:  fffff880060a97b0 -- (.trap 0xfffff880060a97b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c0000008 rbx=0000000000000000 rcx=00000000c0000101
rdx=fffff880060a9c01 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa8008566b30 rsp=fffff880060a9948 rbp=fffffa8008586b60
 r8=fffffa8006101f30  r9=ffffffff40000100 r10=fffff80002d24a14
r11=fffffa8008585060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffffa80`08566b30 0300            add     eax,dword ptr [rax] ds:9c20:00000000`c0000008=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a871e9 to fffff80002a87c40

STACK_TEXT:  
fffff880`060a9668 fffff800`02a871e9 : 00000000`0000000a 00000000`c0000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`060a9670 fffff800`02a85e60 : fffffa80`08585060 fffffa80`09c5db60 00000000`00000000 fffff880`009e8180 : nt!KiBugCheckDispatch+0x69
fffff880`060a97b0 fffffa80`08566b30 : fffff800`02ad385c 00000000`00000000 fffffa80`09c5db60 00000000`00000000 : nt!KiPageFault+0x260
fffff880`060a9948 fffff800`02ad385c : 00000000`00000000 fffffa80`09c5db60 00000000`00000000 00000000`00000000 : 0xfffffa80`08566b30
fffff880`060a9950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xcc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02a85e60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xD1_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_nt!KiPageFault+260

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

Wow! That is fast service!

So two possible issues:
1) outdated asacpi.sys file
-- sure enough, mine is dated 2005:


2) TightVNC. I'll uninstall that as I'm not really using it. It was installed because I put PocketCloud on my iPad but never really use it for RDP purposes.. I use logmein instead.

Thanks. I'll repost here if any followup needed.

Will do. Off to reboot after running through the verifier setup.

Apologies for the new thread. I mis-remembered the posting instructions.

OK. It didn't take long to get a BSOD after enabling verifier.exe. As soon as I rebooted and loaded all the automatic startup stuff, I manually started Process Explorer and then started SpeedFan 4.4 at which point I got an immediate BSOD.

After the PC rebooted, I started verifier.exe, disabled it and restarted again, then ran the BSODD&SFC app, zipped it and here we are.