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: Random and frequent BSODs

05 Nov 2012   #11
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

OK, will keep Best of luck!


My System SpecsSystem Spec
.
06 Nov 2012   #12
Entombed

Windows 7 Home Premium 64bit
 
 

Ok, I just got back from a 2nd shift at work and see that I had 2 more BSODs. It does not seem like it is happening as frequently and I'm not getting the system hangs either. Here's the diag.
My System SpecsSystem Spec
06 Nov 2012   #13
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

I requested some other person to look at this thread, the best debugger I know, from whom I usually learn how to do it.

I hope he will suggest you the right way, please wait for him
My System SpecsSystem Spec
.

06 Nov 2012   #14
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Either you have a bad drive or your old ESET drivers are flaking out. Update ESET to latest, or remove it altogether. As for the drives, it seems you've done everything aside from checking the SMART values with CrystalDiskInfo. If those all come up clean, then it still may very well be the drive, or some connection issue like a loose data/power cable or motherboard malfunction. I personally would lean on the drive itself (the SSD) being suspect.

Analysts:

For 0xF4 crashes, you often want to look at the raw stack for the crashed thread to see if there's any NTSTATUS error codes lying around inside it. !analyze -v will tell you the overall problem was that this critical Windows thread received a c0000006 NTSTATUS code during its operation, which means an I/O error occurred when attempting to shove something from disk to RAM. This specific NTSTATUS code it gives you will not give you the I/O error it came across, but almost always that can be discovered in the raw stack.

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8006167060, Terminating object
Arg3: fffffa8006167340, Process image file name
Arg4: fffff80002fc8460, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa8006167060

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`037fbe38 fffff800`03050822 : 00000000`000000f4 00000000`00000003 fffffa80`06167060 fffffa80`06167340 : nt!KeBugCheckEx
fffff880`037fbe40 fffff800`02ffce0b : ffffffff`ffffffff fffffa80`0677e6a0 fffffa80`06167060 fffffa80`06167060 : nt!PspCatchCriticalBreak+0x92
fffff880`037fbe80 fffff800`02f7bf04 : ffffffff`ffffffff 00000000`00000001 fffffa80`06167060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`037fbed0 fffff800`02cc8253 : fffffa80`06167060 fffff800`c0000006 fffffa80`0677e6a0 00000000`00b50c80 : nt!NtTerminateProcess+0xf4
fffff880`037fbf50 fffff800`02cc4810 : fffff800`02d13b7f fffff880`037fca38 fffff880`037fc790 fffff880`037fcae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`037fc0e8 fffff800`02d13b7f : fffff880`037fca38 fffff880`037fc790 fffff880`037fcae0 00000000`00b51990 : nt!KiServiceLinkage
fffff880`037fc0f0 fffff800`02cc8642 : fffff880`037fca38 00000000`000135e8 fffff880`037fcae0 00000000`00b51468 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`037fc900 fffff800`02cc71ba : 00000000`00000000 000007fe`fd40d8c0 00000000`00000001 00000000`000135e8 : nt!KiExceptionDispatch+0xc2
fffff880`037fcae0 00000000`76f99c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00b513b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f99c12


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

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

1: kd> !niemiro.rawstack
dps fffff880037fb000 fffff880037fcc68
fffff880`037fb000  fffff800`02e0cff4 nt!_imp_NtOpenSymbolicLinkObject+0x5aec
fffff880`037fb008  fffff800`02c112ec hal!HalpTscStallExecutionProcessor+0xe8
fffff880`037fb010  fffff880`037fbeb8
fffff880`037fb018  fffff800`02c4a000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`037fb020  fffff880`01247a98 Ntfs!NtfsFsdRead+0x1b8
fffff880`037fb028  fffff880`0123b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`037fb030  fffff880`012a1600 Ntfs!__PchSym_ <PERF> (Ntfs+0x66600)
fffff880`037fb038  fffff880`037fc680
fffff880`037fb040  00000000`00000000
fffff880`037fb048  fffff800`02d08a16 nt!iswctype_l+0xc6

...

fffff880`037fc020  00000000`00000000
fffff880`037fc028  000007fe`fd40d8c0
fffff880`037fc030  00000000`c000000e
fffff880`037fc038  00000000`00000000
fffff880`037fc040  00000000`00000000

...

fffff880`037fc138  00000000`00000000
fffff880`037fc140  00000000`00000000
fffff880`037fc148  fffff880`04922a1eUnable 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
 eamonm+0x1ca1e
fffff880`037fc150  00001f80`0010005f
fffff880`037fc158  0053002b`002b0033

...

1: kd> !error c000000e
Error code: (NTSTATUS) 0xc000000e (3221225486) - A device which does not exist was specified.
1: kd> lmvm eamonm
start             end                 module name
fffff880`04906000 fffff880`049df000   eamonm   T (no symbols)           
    Loaded symbol image file: eamonm.sys
    Image path: \SystemRoot\system32\DRIVERS\eamonm.sys
    Image name: eamonm.sys
    Timestamp:        Thu Dec 09 00:29:20 2010 (4D006930)
    CheckSum:         00037F5C
    ImageSize:        000D9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Aside from the spattering of c0000006 errors, there's one that mentions a device it tried to access (most likely a storage device) just didn't exist, so this is most likely the I/O error it was talking about - that or a c0000005 (memory referenced was bad) I also found. Either it tried using a bad value that ended up attempting to access a completely nonexistent device, or there was a device, but it disappeared and was subsequently removed prior to this attempt to access it, which often occurs in a very ugly and unexpected manner.

I noticed also that an ESET driver was present here, which from the looks of it is quite old. Perhaps this driver incidentally scrubbed the pointer to the device, which caused it to say device not found (cuz it's a bad value), which ends up giving the c0000006 error.
My System SpecsSystem Spec
07 Nov 2012   #15
Entombed

Windows 7 Home Premium 64bit
 
 

Oops, just seeing the replies now. I didn't see that this rolled over to a second page. Reading now!!!
My System SpecsSystem Spec
Reply

 Random and frequent BSODs




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random, Frequent BSODs
Hi guys, Let me just start out by saying that my understanding of the technical side of computers is really, really limited, so go easy on me! Basically, I'm posting because over the past week or so I've been getting BSODs fairly regularly. My Acer laptop is about 1.5 years old, and to be...
BSOD Help and Support
Different, Frequent, and Random BSODs
Motherboard: ASUS P5QL/EPU RAM : 8GB DDR2-1066 GSkill PC8500 Video: nVidia GeForce GTX 460 Cyclone GDDR5 1GB 2 HDD: WD Black Cavilier 1TB and a Seagate 2TB Windows Ultimate x64 started geting these random crashes about the same time my older HDD 120 IDE went out. Which is when the Seagate...
BSOD Help and Support
Frequent, random BSoDs for over a year
Hey, I keep getting random BSoDs. It usually happens either shortly after I cold-boot, or several hours later when I'm idling while doing homework somewhere else or something. The error codes and system files in question are not consistent. They used to happen once every few weeks, but they've...
BSOD Help and Support
FREQUENT RANDOM BSoDs
Hi Everyone, i have built a new computer in the past 6 months and get frequent random BSoDs and it drives me nuts!! these are random and can happen under idle or while listeningto music, theres no one thing that triggers it, the errors are varied from MEMORY_MANAGMENT, BAD_POOL_HEADER,...
BSOD Help and Support
frequent random BSODs
Hi folks. I've got a 6-month old OEM, original install of Win7 X64. Until a couple of weeks ago it was stable: no BSODs. Then there was one. Now I'm lucky if I can get through a session without one. They seem to be of random types, according to windbg, though there have been a number of ones...
BSOD Help and Support
Constant, Random BSODs - Gotten more frequent
Here are the mini dumps, I could really use some help as the crashes are happing more and more often: Thanks!
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 21:41.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App