Possible out of date drivers:
Code:
SCDEmu fffff880`04072000 fffff880`04084000 Tue Aug 07 09:19:48 2007 (46b88d94) 00011e2f SCDEmu.SYS
gdrv fffff880`0a9ca000 fffff880`0a9d3000 Thu Mar 12 21:22:29 2009 (49b9d175) 000105ce gdrv.sys
SCDEmu.SYS gdrv.sys Remove the Gigabyte Easy Saver Power Utility The outdated version is known to cause crashes.
Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\Rares\033112-23322-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03c0c000 PsLoadedModuleList = 0xfffff800`03e51670
Debug session time: Sat Mar 31 09:14:01.847 2012 (UTC - 6:00)
System Uptime: 0 days 0:48:14.018
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 109b, 4000d, fffffa800cbca830}
Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
GetPointerFromAddress: unable to read from fffff80003ebb100
Probably caused by : eamonm.sys ( eamonm+7944 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 000000000004000d, Memory contents of the pool block
Arg4: fffffa800cbca830, Address of the block of pool being deallocated
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'tcpipreg' and 'atksgt.sys' overlap
POOL_ADDRESS: fffffa800cbca830
FREED_POOL_TAG: NtfI
BUGCHECK_STR: 0xc2_7_NtfI
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003db6be9 to fffff80003c88c40
STACK_TEXT:
fffff880`03199af8 fffff800`03db6be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`0004000d : nt!KeBugCheckEx
fffff880`03199b00 fffff880`026d0944 : fffffa80`0e4cd890 fffff880`00000000 fffffa80`0e4cd8f0 fffffa80`0d54dd00 : nt!ExDeferredFreePool+0x1201
fffff880`03199bb0 fffffa80`0e4cd890 : fffff880`00000000 fffffa80`0e4cd8f0 fffffa80`0d54dd00 fffffa80`00000000 : eamonm+0x7944
fffff880`03199bb8 fffff880`00000000 : fffffa80`0e4cd8f0 fffffa80`0d54dd00 fffffa80`00000000 00000000`00000001 : 0xfffffa80`0e4cd890
fffff880`03199bc0 fffffa80`0e4cd8f0 : fffffa80`0d54dd00 fffffa80`00000000 00000000`00000001 fffffa80`0c061ce0 : 0xfffff880`00000000
fffff880`03199bc8 fffffa80`0d54dd00 : fffffa80`00000000 00000000`00000001 fffffa80`0c061ce0 fffff880`0108d7af : 0xfffffa80`0e4cd8f0
fffff880`03199bd0 fffffa80`00000000 : 00000000`00000001 fffffa80`0c061ce0 fffff880`0108d7af 00000000`40000000 : 0xfffffa80`0d54dd00
fffff880`03199bd8 00000000`00000001 : fffffa80`0c061ce0 fffff880`0108d7af 00000000`40000000 fffffa80`0d54dd20 : 0xfffffa80`00000000
fffff880`03199be0 fffffa80`0c061ce0 : fffff880`0108d7af 00000000`40000000 fffffa80`0d54dd20 fffff880`00000000 : 0x1
fffff880`03199be8 fffff880`0108d7af : 00000000`40000000 fffffa80`0d54dd20 fffff880`00000000 fffff800`03c5b61e : 0xfffffa80`0c061ce0
fffff880`03199bf0 fffff880`01091cdb : fffffa80`0e4cd890 fffff800`03e292b8 fffffa80`0d54dd20 fffffa80`0c061ce0 : fltmgr!FltpKtmNotification+0x9f
fffff880`03199c60 fffff800`03c93001 : fffff880`01091c70 fffffa80`09af3040 fffffa80`09af3000 00000000`00000000 : fltmgr!FltpWaitForCommitFinalize+0x6b
fffff880`03199cb0 fffff800`03f23fee : 00000000`00000000 fffffa80`09af3040 00000000`00000080 fffffa80`09ad6ae0 : nt!ExpWorkerThread+0x111
fffff880`03199d40 fffff800`03c7a5e6 : fffff880`030a4180 fffffa80`09af3040 fffff880`030af040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03199d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
eamonm+7944
fffff880`026d0944 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: eamonm+7944
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: eamonm
IMAGE_NAME: eamonm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c18e225
FAILURE_BUCKET_ID: X64_0xc2_7_NtfI_eamonm+7944
BUCKET_ID: X64_0xc2_7_NtfI_eamonm+7944
Followup: MachineOwner
--------- The crashes are blaming ESET. ESET rarely causes crashes, so I suspect something else unless you are running an older version. Do you have the most up to date version of ESET and are its definitions up to date?
Can you provide us with more information by following the
http://www.sevenforums.com/crashes-d...tructions.html so we know what network adapters you are using.
If ESET is up to date, I suspect your network adapter drivers are either old or corrupted or both. It may also be your audio drivers since they share the same resources as the network adapter drivers. ESET itself can become corrupted, in which case a removal and re-install is in order.
How do I manually uninstall my Windows ESET security product? - ESET Knowledgebase will help with the uninstall of ESET for that troubleshooting step.