bsod multiple times daily

I suspect your Logitech Setpoint drivers are the cause. Are your mice/keyboard batteries fresh? Could you possibly remove them and try a different set?

...Summary of the Dumps:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 10 10:32:30.635 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:38.978
BugCheck C9, {23b, fffff88005967818, fffff980099fadc0, 0}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_23b
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 10 10:37:21.500 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:16.232
BugCheck C9, {23b, fffff88005938818, fffff9800dfa4dc0, 0}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_23b
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 10 10:35:03.268 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:41.001
BugCheck C9, {23b, fffff88005967818, fffff98009c48dc0, 0}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_23b
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 13:55:55.052 2010 (UTC - 4:00)
System Uptime: 0 days 4:30:15.753
BugCheck 3B, {c0000005, fffff80002db50bf, fffff88008633770, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  rundll32.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

i hate to be the bearer of bad news, but i use wired mice and keyboard. no batteries :/

and i had another crash.

This one shows an AFD callback trying to retrieve data from a pointer in the RDX register via AfdFastConnectionReceive, but that of course is invalid (and given it's a kernel-mode driver, you get a bugcheck). Given history (I've seen many of these before) and the fact it's crashing in a network application that would be stressing some of these features (azureus), the most likely culprit is the network driver not handling offload well. I would update it to the latest version if you've not done so already, and then you would want to run the commands below to disable the tcp chimney / offloading feature to see if that helps.

Code:

// network driver from 2009, probably old considering it's nvidia:
1: kd> lmvm nvmf6264
start             end                 module name
fffff880`04178000 fffff880`041c9500   nvmf6264   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
    Image name: nvmf6264.sys
    Timestamp:        Thu Jul 30 19:48:18 2009 (4A723142)
    CheckSum:         0005B9A8
    ImageSize:        00051500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Commands to run:
netsh interface tcp set global rss=disabled
netsh interface tcp set global chimney=disabled
netsh interface tcp set global netdma=disabled
netsh interface tcp set global autotuninglevel=disabled

You may also wish to reset your winsock provider to it's defaults, although this one can potentially break applications with LSPs installed on the system:
netsh winsock reset

[nvidia][/nvidia]

For Nvidia drivers, you can find it right here

Run cmd.exe as an administrator and type those commands in at the prompt.

Download the updated drivers to your desktop. Through device manager, uninstall the old driver(s). Install the new ones. Reboot.

Very good and thanks for the update and for following suggestions. Good job. We hope your BSOD problems are gone, Make sure your system is still configured for mini dumps and keep us updated. :)