Frequent BSOD

Hello and Welcome !

First thing i noticed is that you have a combination of ESET and Zone Alarm both are notorious for BSOD. Please uninstall Zone Alarm and ESET and install Microsoft Security Essentials. Follow this link for more help on this BSOD vs. Internet Security !! « Captain Debugger

If that didn't stop BSOD the Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger


Update the Following Drivers

Code:

cv2k1.sys    Thu Dec 07 23:23:05 2006
pcouffin.sys Tue Dec 05 20:09:30 2006
agrsm64.sys  Mon Nov 10 20:31:35 2008

Follow this article for help in Updating Drivers Driver Troubleshooting !! « Captain Debugger


Problematic Devices Listed:

Code:

Photosmart D110 series ROOT\MULTIFUNCTION\0000 This device is disabled.
Base System Device PCI\VEN_197B&DEV_2383&SUBSYS_30FB103C&REV_00\4&39D5C7A5&0&0328 The drivers for this device are not installed.
Bluetooth Device (Personal Area Network) BTH\MS_BTHPAN\6&64C0F18&0&2 This device is disabled.
TAP-Win32 Adapter V9 ROOT\NET\0000 This device is disabled.
TAP-Win32 Adapter V9 #2 ROOT\NET\0002 This device is disabled.
Base System Device PCI\VEN_197B&DEV_2384&SUBSYS_30FB103C&REV_00\4&39D5C7A5&0&0428 The drivers for this device are not installed.
TAP-Win32 Adapter V9 ROOT\NET\0003 This device is disabled.
Teredo Tunneling Pseudo-Interface ROOT\*TEREDO\0000 This device cannot start.
Not Available ACPI\ENE0100\3&2411E6FE&1 The drivers for this device are not installed.
Base System Device PCI\VEN_197B&DEV_2382&SUBSYS_30FB103C&REV_00\4&39D5C7A5&0&0028 The drivers for this device are not installed.

Bugcheck:

Code:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002c9fec8
Debugging Details:
------------------
 
BUGCHECK_STR:  0x7f_8
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002cd6ca9 to fffff80002cd7740
STACK_TEXT:  
fffff880`009eec68 fffff800`02cd6ca9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009eec70 fffff800`02cd5172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eedb0 fffff800`02c9fec8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02f1cfc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x60
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02cd5172 90              nop
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------

Hope this helps,
Captain