windows7 bluescreen crash help

Welcome!

Looks like you anti-virus ESET is causing the issues. Since I have not seen a lot of issues with ESET, I am going to assume you just have a corrupted driver.

Try uninstalling ESET and reinstalling it, or switch to another program like the free Microsoft Security Essentials.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\030910-14367-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82841000 PsLoadedModuleList = 0x82989810
Debug session time: Tue Mar  9 03:30:13.681 2010 (GMT-5)
System Uptime: 0 days 2:10:20.412
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\eamon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8241032e, 92eeb9cc, 0}

Probably caused by : eamon.sys ( eamon+532e )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8241032e, The address that the exception occurred at
Arg3: 92eeb9cc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
eamon+532e
8241032e 8b430c          mov     eax,dword ptr [ebx+0Ch]

TRAP_FRAME:  92eeb9cc -- (.trap 0xffffffff92eeb9cc)
ErrCode = 00000000
eax=850df100 ebx=850df280 ecx=00000001 edx=00000000 esi=8610ccd4 edi=845ad5a8
eip=8241032e esp=92eeba40 ebp=92eeba70 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
eamon+0x532e:
8241032e 8b430c          mov     eax,dword ptr [ebx+0Ch] ds:0023:850df28c=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8287d4bc to 8241032e

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
92eeba70 8287d4bc 850df1c8 8610cad8 867be1b4 eamon+0x532e
92eeba88 82a8162d 8b8273d2 92eebc30 00000000 nt!IofCallDriver+0x63
92eebb60 82a621d7 85078898 850c6f78 86719620 nt!IopParseDevice+0xed7
92eebbdc 82a8824d 00000000 92eebc30 00000040 nt!ObpLookupObjectName+0x4fa
92eebc38 82a805ab 005556e8 840c6f78 84431701 nt!ObOpenObjectByName+0x159
92eebcb4 82a8beb6 00555700 80000000 005556e8 nt!IopCreateFile+0x673
92eebd00 8288442a 00555700 80000000 005556e8 nt!NtCreateFile+0x34
92eebd00 775364f4 00555700 80000000 005556e8 nt!KiFastCallEntry+0x12a
005557a8 00000000 00000000 00000000 00000000 0x775364f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
eamon+532e
8241032e 8b430c          mov     eax,dword ptr [ebx+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  eamon+532e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: eamon

IMAGE_NAME:  eamon.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  498c37ad

FAILURE_BUCKET_ID:  0x8E_eamon+532e

BUCKET_ID:  0x8E_eamon+532e

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