Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD again, please help

15 Dec 2010   #1

Windows 7 Professional x64
BSOD again, please help

I'm getting a BSOD. Help is very much appreciated, you guys are awesome =D. Thanks in advance.

- x64
- originally XP on system
- Full retail

- Age of system 3-4 years old
- Age of OS installation around 7 months

My System SpecsSystem Spec
15 Dec 2010   #2

Windows 7 Ultimate 32 bit

Hi and welcome to the forum. I looked at your two dumps from October as well as your latest dump to try to get a feel for what is going on. All three dumps indicate memory corruption.
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

Error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
You latest dump is error code A; note the usual causes. This dump directly blames eamon.sys. Eset. Eset is know to cause BSOD's on some Win 7 systems. I suggest you uninstall it using this removal tool:Tool. Download and install Microsoft Security Essentials in its place. Make sure Windows Firewall is turned on. Let's see if this clears up the problem. Post back and let us know. If you get another BSOD, upload it and we will go from there.

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e45e50
Debug session time: Wed Dec 15 19:19:06.581 2010 (GMT-5)
System Uptime: 0 days 7:00:16.422
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {3000000031ec, 2, 1, fffff80002c63d8e}

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
Probably caused by : eamon.sys ( eamon+5b07 )

Followup: MachineOwner

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

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 a kernel debugger is available get the stack backtrace.
Arg1: 00003000000031ec, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c63d8e, address which referenced memory

Debugging Details:

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb00e0


fffff800`02c63d8e ff87ec010000    inc     dword ptr [rdi+1ECh]





TRAP_FRAME:  fffff88007379460 -- (.trap 0xfffff88007379460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003c65748 rbx=0000000000000000 rcx=fffff880009e7840
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c63d8e rsp=fffff880073795f0 rbp=fffff88007379728
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff800`02c63d8e ff87ec010000    inc     dword ptr [rdi+1ECh] ds:9b48:00000000`000001ec=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c77ca9 to fffff80002c78740

fffff880`07379318 fffff800`02c77ca9 : 00000000`0000000a 00003000`000031ec 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`07379320 fffff800`02c76920 : 00000000`00000000 fffff880`009e7180 fffffa80`024992a0 fffffa80`0294e060 : nt!KiBugCheckDispatch+0x69
fffff880`07379460 fffff800`02c63d8e : fffff8a0`03419c00 fffff980`0e7d3108 fffff8a0`03419c70 fffff880`012ea961 : nt!KiPageFault+0x260
fffff880`073795f0 fffff880`01301642 : fffffa80`03c65748 00000000`00000000 fffff8a0`00000000 00000000`00000001 : nt!CcFlushCache+0x11e
fffff880`073796f0 fffff880`012b09e7 : 00000000`00000000 fffff8a0`07c3dc70 00000000`00000000 00000000`00000001 : Ntfs!NtfsFlushUserStream+0x92
fffff880`07379770 fffff880`01301bbd : fffffa80`02e8b010 fffffa80`03718180 fffffa80`06085001 fffffa80`012ab100 : Ntfs!NtfsFlushVolume+0x2c7
fffff880`073798a0 fffff880`013025f0 : fffffa80`02e8b010 fffffa80`054fd8c0 fffffa80`0561d720 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`07379980 fffff880`010c123f : fffffa80`054fdc60 fffffa80`054fd8c0 fffffa80`02e8b010 fffff880`073799a8 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`073799f0 fffff880`010bf6df : fffffa80`0349d040 fffffa80`0484d040 fffffa80`0349d000 fffffa80`054fd8c0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`07379a80 fffff880`03475b07 : fffffa80`054fd8c0 00000000`00000801 fffffa80`0294e060 00000000`0280f710 : fltmgr!FltpDispatch+0xcf
fffff880`07379ae0 fffffa80`054fd8c0 : 00000000`00000801 fffffa80`0294e060 00000000`0280f710 00000000`00000000 : eamon+0x5b07
fffff880`07379ae8 00000000`00000801 : fffffa80`0294e060 00000000`0280f710 00000000`00000000 fffffa80`0484d040 : 0xfffffa80`054fd8c0
fffff880`07379af0 fffffa80`0294e060 : 00000000`0280f710 00000000`00000000 fffffa80`0484d040 fffffa80`054fd8c0 : 0x801
fffff880`07379af8 00000000`0280f710 : 00000000`00000000 fffffa80`0484d040 fffffa80`054fd8c0 fffff800`02f8eca9 : 0xfffffa80`0294e060
fffff880`07379b00 00000000`00000000 : fffffa80`0484d040 fffffa80`054fd8c0 fffff800`02f8eca9 00000000`00000002 : 0x280f710


fffff880`03475b07 ??              ???


SYMBOL_NAME:  eamon+5b07

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  eamon.sys


FAILURE_BUCKET_ID:  X64_0xA_eamon+5b07

BUCKET_ID:  X64_0xA_eamon+5b07

Followup: MachineOwner
My System SpecsSystem Spec
15 Dec 2010   #3

Windows 7 Professional x64

Alright, thanks a ton. I'll let you know if it happens again
My System SpecsSystem Spec

15 Dec 2010   #4

Windows 7 Ultimate 32 bit

You are very welcome - and we will be here.:)
My System SpecsSystem Spec

 BSOD again, please help

Thread Tools

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:52.
Twitter Facebook Google+