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: Getting randomly a BSOD

18 Mar 2013   #1
Vrs

Windows 7 32 bit
 
 
Getting randomly a BSOD

Hi everyone,

The first time that a BSOD appearded was a month ago. But today i get 4 BSOD's in 30 min.
I just start-up the PC and thats it. I didn't make use of the PC and the BSOD appeared. At this moment i use my PC for 1 hour and its just fine. Hope some one could help me. The files are added.

Regards,
Vrs


My System SpecsSystem Spec
.
18 Mar 2013   #2
Saurabh A

Windows 7 64bit
 
 

Hi Vrs,

It appears that the 'attached file' is not a valid archive; does not open the contents.
Please refer to the following tutorial to capture and share fresh details of the 'crash dump': Blue Screen of Death (BSOD) Posting Instructions

Do reply with the information; will take it forward.


My System SpecsSystem Spec
19 Mar 2013   #3
Vrs

Windows 7 32 bit
 
 

Thx for your response. I hope this one is valid.
My System SpecsSystem Spec
.

20 Mar 2013   #4
Saurabh A

Windows 7 64bit
 
 

Hi Vrs,

Crash dump looks fine this time; thank you for the response.

The mini-dump analysis:
Probably caused by : ntkrnlmp.exe driver
Related to 'NT Kernel & System'
Code:
Loading Dump File [C:\Errors\SF_19-03-2013\031813-28485-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0x8343c000 PsLoadedModuleList = 0x8357c230
Debug session time: Tue Mar 19 01:34:20.061 2013 (UTC + 5:30)
System Uptime: 0 days 0:03:52.700
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, 8349f094}

Probably caused by : ntkrnlmp.exe ( nt!KiSignalSynchronizationObjectEx+21 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8349f094, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8359b828
Unable to read MiSystemVaType memory at 8357bd80
 00000000 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!KiSignalSynchronizationObjectEx+21
8349f094 8901            mov     dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

TRAP_FRAME:  b329bc00 -- (.trap 0xffffffffb329bc00)
ErrCode = 00000002
eax=00000000 ebx=89820af0 ecx=00000000 edx=00000002 esi=00000000 edi=88c79d40
eip=8349f094 esp=b329bc74 ebp=b329bc88 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!KiSignalSynchronizationObjectEx+0x21:
8349f094 8901            mov     dword ptr [ecx],eax  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8349f094 to 83474c3b

STACK_TEXT:  
b329bc00 8349f094 badb0d00 00000002 8368d4db nt!KiTrap0E+0x2cf
b329bc88 8349ef70 80dfb120 89820ae8 b329bcbc nt!KiSignalSynchronizationObjectEx+0x21
b329bcd4 8363ad40 00000000 00000001 00000000 nt!KeReleaseMutant+0x118
b329bd24 8347185a 00000520 00000000 05d9fdf8 nt!NtReleaseMutant+0x72
b329bd24 77a07094 00000520 00000000 05d9fdf8 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
05d9fdf8 00000000 00000000 00000000 00000000 0x77a07094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSignalSynchronizationObjectEx+21
8349f094 8901            mov     dword ptr [ecx],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiSignalSynchronizationObjectEx+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50e793ce

FAILURE_BUCKET_ID:  0xA_nt!KiSignalSynchronizationObjectEx+21

BUCKET_ID:  0xA_nt!KiSignalSynchronizationObjectEx+21

Followup: MachineOwner
---------
Another crash:
Probably caused by: eamonm.sys driver
Relates to: 'ESET Amon driver' / 'ESet NOD32 antivirus system monitor driver'
Code:
*******************************************************************************
*                                                                             *
*                        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: 00000007, Attempt to free pool which was already freed
Arg2: 0000109b, (reserved)
Arg3: 08050017, Memory contents of the pool block
Arg4: 8864f298, Address of the block of pool being deallocated

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  eamonm+129e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: eamonm

IMAGE_NAME:  eamonm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c18e21e

FAILURE_BUCKET_ID:  0xc2_7_eamonm+129e

BUCKET_ID:  0xc2_7_eamonm+129e

Followup: MachineOwner
Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A.

Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
This error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Bug Check 0xC2: BAD_POOL_CALLER
The BAD_POOL_CALLER bug check has a value of 0x000000C2. This indicates that the current thread is making a bad pool request.

You may try the following steps to see if they are helpful:

1. Use the uninstaller tool to remove 'Eset' Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase > Restart the system > Download and install 'Microsoft Security Essentials' http://windows.microsoft.com/en-IN/w...tials-download > Recheck results to see if the issue re-occurs.

2. Run the 'Disk Check' (Command Prompt) using the steps mentioned in 'Option 2' in this tutorial: Disk Check

3. Perform 'Windows Updates' Install Windows updates and check if the error still occurs.

4. If the issue persists, try enabling the 'Driver Verifier' Driver Verifier - Enable and Disable
This will put more stress on the drivers; expecting the unstable/vulnerable ones to collapse.

Hope this helps. Do reply with the findings.


My System SpecsSystem Spec
20 Mar 2013   #5
Vrs

Windows 7 32 bit
 
 

Hi Saurabh,

Realy thanks for your comment. I gonna try this and let you know if this fixed my problem.

Regards,
Vrs
My System SpecsSystem Spec
20 Mar 2013   #6
Vrs

Windows 7 32 bit
 
 

Hi Saurabh,

I started with scanning my C and D Disk with "Disk Check" but there were no Errors founded.
After this Disk check i did update my windows and make use of Drive verifier.
After this i had to start-up and before i get in windows i get the blue screen. This blue screen pops up each time at a restart up so i had to make use of the safe mode to get in windows.
When i get in, i disabled Drive verifier and the blue screen at the start up where gone.
At last i tryed to uninstal Eset anti virus and instal Microsoft Security Essentials. I used again the Drive verifier but the blue screens at the start up appeared again till i put it off in safe mode. I attach a file of the last two blue screens that appeared at the start up. Mabey its helpfull.

I know the Drive verifier is a stress test for the drivers. So is it possible that windows can start up with Drive verifier (without blue screens)? At some parts my windows was out of date so i solved this and mabey the blue screens too. I will let you know if i get one.

Thx for your time.

Regards,
Vrs
My System SpecsSystem Spec
22 Mar 2013   #7
Vrs

Windows 7 32 bit
 
 

Hi Saurabh,

I have use my PC for a couple of days and without gething any blue screen.
It's looks like that my antivirus (Eset NOD32) was the problem.
When i uninstalled this program i get another problem. If i want to upload a file on the internet and it doesnt matter where to upload them (Example: on this forum or an attachment in your mail) my internet connection was shutdown. To solve this (Mabey this is helpfull for other people) goto Control panel > Hardware and Sounds > Device Manager. Right click at Network Adapters > Properties. Goto the tab Advanced and in the properties dialog you will find "Task Offload". Put this value at "OFF" and the upload problem is solved.

Again thanks for your help.

Regards,
Vrs
My System SpecsSystem Spec
23 Mar 2013   #8
Saurabh A

Windows 7 64bit
 
 

Hi Vrs,

One possible reason for 'system crash' was the 'eamonm.sys driver' which relates to 'ESET Amon driver' / 'ESet NOD32 antivirus system monitor driver'. Glad that the system did not crash after the 'program removal'; thank you for the confirmation.

Thank you for sharing valuable inputs in regards to the 'Task Offload' function in the 'Network Interface Card'. Do reply if you have any further questions; glad to assist.

My System SpecsSystem Spec
Reply

 Getting randomly a BSOD




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD-PC Freezes randomly-Driver Verifier BSOD's at User Log-On
Hello, As the thread shows im having lots and lots of little(and big) crashes. Im attaching the SF log and any help will be appreciated Many thanks, Dimitris
BSOD Help and Support
BSOD whilst playing Games, also sometimes just randomly BSOD
Not sure what is going wrong with my comp, i recently over clocked it and set it to 4.0GHz if that helps?
BSOD Help and Support
BSOD randomly (no specific trigger) Commonly an IRQL issue on BSOD
Hi, My computer has been unstable for quite some time and after memory tests, changing graphics cards, many driver variations and a couple of fresh OS installs a while ago it is still not stable. The difficulty is that it doesn't seem to be triggered by anything specific so it makes debugging...
BSOD Help and Support
BSOD randomly and PC freezes randomly
Hi guys, my pc has been acting weird lately, it has began randomly crashing frequently. I turn it on and after 3 or so minutes of random activity it just freezes or gives me a blue screen error. Sometimes while playing BF3, it freezes. Problem signature: Problem Event Name: BlueScreen ...
BSOD Help and Support
BSOD semi-randomly. Self built computer. (BSOD dump.zip included)
64 bit, full retail. Hardware is 1 month old (built myself) OS was installed when I built it from a USB drive (did not include an optical drive in the build) SPECS: i5 2500k ATI 7850 GPU corsair tx650 PSU ASRock Extreme3 Gen3 motherboard Corsair vengance 1600 ddr3 ram (2x4gb)...
BSOD Help and Support
BSOD randomly (?) When waking laptop after sleeping, BSOD pic attached
Is Windows 7 . . . - x64 - the original installed OS on the system? Windows 7 Ultimate x64 - an OEM or full retail version? Retail - What is the age of system (hardware)? ~1 year - What is the age of OS installation (have you re-installed the OS?) ~1 year, I installed it when I got the...
BSOD Help and Support


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 16:53.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App