help with BSOD

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_061910-28750-01[1].zip\061910-28750-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`04411000 PsLoadedModuleList = 0xfffff800`0464ee50
Debug session time: Sat Jun 19 13:16:25.187 2010 (GMT-4)
System Uptime: 0 days 4:20:25.263
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88003764180, 2}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003764180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
 
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  cit200.exe
CURRENT_IRQL:  d
STACK_TEXT:  
fffff800`00ba28d8 fffff800`0442f443 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03764180 : nt!KeBugCheckEx
fffff800`00ba28e0 fffff800`04489cf7 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffffa80`07213000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff800`00ba2970 fffff800`049f7895 : fffff800`04a1c3c0 fffff800`00ba2b20 fffff800`04a1c3c0 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00ba2a70 fffff800`0447daf3 : 00000000`1eacffec fffff800`00ba2b01 fffffa80`05f7bf00 fffff800`00ba2cd0 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00ba2aa0 fffff800`044c1fbc : fffffa80`06fe2940 00000000`00000000 fffffa80`054f8000 00000000`00000004 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00ba2c30 fffff800`0448b47e : fffffa80`083eb7b8 00000000`00088644 00000000`00000000 fffff880`108afb16 : nt!KxWaitForLockOwnerShip+0x30
fffff800`00ba2c60 fffff880`10608c3f : 00000000`00000000 fffffa80`07f1b000 fffffa80`083ec000 fffffa80`07417cb0 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x7e
fffff800`00ba2cb0 fffff880`046d91cf : fffffa80`07111480 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x87
fffff800`00ba2d00 fffff880`1074cfcd : fffffa80`06ff6250 fffffa80`07213000 fffffa80`07213000 00000000`00000022 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff800`00ba2d30 fffffa80`06ff6250 : fffffa80`07213000 fffffa80`07213000 00000000`00000022 fffffa80`07213000 : nvlddmkm+0xa3fcd
fffff800`00ba2d38 fffffa80`07213000 : fffffa80`07213000 00000000`00000022 fffffa80`07213000 00000000`00000000 : 0xfffffa80`06ff6250
fffff800`00ba2d40 fffffa80`07213000 : 00000000`00000022 fffffa80`07213000 00000000`00000000 00000000`00000000 : 0xfffffa80`07213000
fffff800`00ba2d48 00000000`00000022 : fffffa80`07213000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07213000
fffff800`00ba2d50 fffffa80`07213000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07111480 : 0x22
fffff800`00ba2d58 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`07111480 00000000`00000000 : 0xfffffa80`07213000
 
STACK_COMMAND:  kb
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME:  Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------

speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
whfltr2k whfltr2k.sys Fri Jan 26 03:04:37 2007 (45B9B615)
vbtenum vbtenum.sys Mon Mar 05 07:17:00 2007 (45EC0A3C)
BTHidMgr BTHidMgr.sys Mon Mar 05 07:17:15 2007 (45EC0A4B)
VComm VComm.sys Mon Mar 05 07:17:28 2007 (45EC0A58)
VcommMgr VcommMgr.sys Mon Mar 05 07:17:48 2007 (45EC0A6C)
PxHlpa64 PxHlpa64.sys Wed Mar 12 21:58:17 2008 (47D88A39)
LVUSBS64 LVUSBS64.sys Sat Jul 26 11:06:36 2008 (488B3D7C)
elrawdsk elrawdsk.sys Sat Jul 26 13:59:09 2008 (488B65ED)
LV302V64 LV302V64.SYS Thu Apr 30 18:43:26 2009 (49FA298E)
NuidFltr NuidFltr.sys Fri May 08 04:53:31 2009 (4A03F30B)
amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) [/CODE]

List of out dated drivers.

Yes. Please follow this procedure:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Kaspersky from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Kaspersky using this free tool: Removal tool for Kaspersky Lab products
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

You can reinstall Kaspersky (if you like) once we've finished troubleshooting.
The problem isn't that the files aren't the latest - it's that there's a problem with one of the Kaspersky files even though it has the correct date. We don't know if it's a problem with Kaspersky in general - or it's a problem with a corrupted file (that's why we recommend the free Microsoft Security Essentials)

the cit200 is a linksys skype phone. never had probs with this. i shall uninstal the kis and see if that helps.

just removing kis now

will report back in a jiffy got to reboot

Remove it totally using the removal tool and run without it until we get the problem resolved. It is a known cause of BSOS's on some systems. Install MSE for protection in the meantime. MSE is a Microsoft product and will not crash the system. Avast is another one that seems to work very well with Win 7.

Also, please see post #6 regarding TuneUp Utilities.

okey doke kis has been removed im putting on mse

just updating is there a prob with tune up utilities ?

Very good. We will see what we have from there.

I and I think Carl, too, have seen many cases where the Anti Virus has caused more problems than it solved. I always suggest MSE.