Solved Getting BSOD often of a sudden

[Rares]

7xBSOD since today, hourly at :15 minutes

Windows 7 x64 Ultimate SP1 OEM
What is the age of system (hardware): 1.6 years
What is the age of OS installation (have you re-installed the OS?): I reinstalled in January 2012

System specs:
AMD Phenom II x6 1090T 3.2 Ghz
ATI Radeon HD 5830 1GB (Gigabyte)
RAM 12 GB DDR3 1333 Mhz
MB Gigabyte MA 770T-UD3

ESET is up to date, and im using the motherboard's network and sound adaptor.

____________________________________________________

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: c2
BCP1: 0000000000000007
BCP2: 000000000000109B
BCP3: 000000000004000D
BCP4: FFFFFA800CBCA830
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\033112-23322-01.dmp
C:\Users\admin\AppData\Local\Temp\WER-43773-0.sysdata.xml

____________________________________________________

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: d1
BCP1: 0000000000001028
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88009F1333B
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

____________________________________________________


I couldn't download that program for the .dmp files but i uploaded them to the site.

Also it seems that i get the BSOD at every hour at around :15 mins. It's official. I crash every hour at :15.
I tested the memory aswell, no problems found. I don't understand this i mean since today i haven't had more than 2 BSOD's since i bought this PC.

 

[Rares]

Any help please? I updated anything i could think of after the 3rd crash...i don't know what to do anymore

 

[writhziden]

Possible out of date drivers:

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.

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-debugging/96879-blue-screen-death-bsod-posting-instructions.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.

 

[Rares]

Yeah i added more info. ESET is up to date, im using the motherboard's network adapter and sound card.

 

[writhziden]

Have you re-installed the drivers and the ESET software by doing a full uninstall of each, and then installing again?

To fully re-install a driver, use the following steps.

1. First, download the latest driver. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Find the device you are trying to uninstall by expanding the appropriate set of devices
8. Right click the device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

To fully re-install ESET: How do I manually uninstall my Windows ESET security product? - ESET Knowledgebase must be used to uninstall it first. Then install the latest version.

 

[Rares]

Right so: In all the time i had this computer i just had 2 BSOD's. I do not believe the drivers and ESET are causing any of those.
I took my time yesterday to never let my computer timer to not advance in time. When i opened it up it was at 10:45. Then i changed the timer at 10:30, and when it got to 11:05 i would turn it back 35 minutes. And that's it i haven't had a single crash. Still this isn't solved just a temporary fix.

 

[writhziden]

ESET is directly blamed in every one of the crash reports.

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-debugging/96879-blue-screen-death-bsod-posting-instructions.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.

Crashing every hour: Do you by chance have an SSD?

 

[Rares]

Right i forgot about that! I knew i was missing something in system specs. No i have a Western Digital Caviar Green 2TB 5400RPM

 

[writhziden]

Have you uninstalled and then re-installed ESET and the drivers mentioned?

If you have, it's possible you have a virus causing this, or some software you installed is trying to access the internet without permissions and ESET is complaining. Run a full scan of your system for viruses/malware using ESET. Also, download, install, and update Malwarebytes : Free anti-malware, anti-virus and spyware removal download Then start Malwarebytes (do not accept when asked to start the trial version) and run a full scan of your system.

If the virus and malware scans come up clean, you could try to http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html and see if there is an application or service that is causing conflicts with ESET.

 

[Rares]

Yea man thanks for the help. It was ESET alright..i reinstalled it now it works fine.

 

[writhziden]

That's great news! Glad it's solved.