Problem Devices:
Code:
Marvell 91xx Config ATA Device IDE\PROCESSORMARVELL_91XX_CONFIG_____________________1.01____\6&1B887581&0&1.1.0 The drivers for this device are not installed.
Antivirus Software:
Code:
avastsvc.exe c:\program files\avast software\avast\avastsvc.exe 1524 8 200 1380 3/2/2012 10:44 AM 7.0.1407.0 43.72 KB (44,768 bytes) 3/2/2012 8:22 AM
avastui.exe c:\program files\avast software\avast\avastui.exe 2952 8 200 1380 3/2/2012 10:44 AM 7.0.1407.0 3.84 MB (4,031,368 bytes) 3/2/2012 8:22 AM
msmpeng.exe c:\program files\microsoft security client\antimalware\msmpeng.exe 576 8 200 1380 3/2/2012 10:44 AM 3.0.8402.0 12.48 KB (12,784 bytes) 4/27/2011 6:21 PM
Having two security programs that accomplish the same task can cause instability on the system.
Possible outdated drivers:
Code:
wdcsam64 fffff880`0624d000 fffff880`06250880 Wed Apr 16 02:39:08 2008 (4805bb2c) 0000d887 wdcsam64.sys
Rt64win7 fffff880`0ffc6000 fffff880`0fff8000 Thu Feb 26 02:04:13 2009 (49a65b0d) 0002eb30 Rt64win7.sys
wdcsam64.sys
Rt64win7.sys
Update both of the above drivers...
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\auutumn\Windows_NT6_BSOD_jcgriff2\030212-8268-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`03296670
Debug session time: Fri Mar 2 08:43:16.446 2012 (UTC - 7:00)
System Uptime: 0 days 0:21:39.446
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8007801b30, fffffa8007801e10, fffff800033d18b0}
Probably caused by : wininit.exe
Followup: MachineOwner
---------
4: 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: fffffa8007801b30, Terminating object
Arg3: fffffa8007801e10, Process image file name
Arg4: fffff800033d18b0, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa8007801b30
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: wininit.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: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`068f30e8 fffff800`034585e2 : 00000000`000000f4 00000000`00000003 fffffa80`07801b30 fffffa80`07801e10 : nt!KeBugCheckEx
fffff880`068f30f0 fffff800`0340599b : ffffffff`ffffffff fffffa80`07ca2b60 fffffa80`07801b30 fffffa80`07801b30 : nt!PspCatchCriticalBreak+0x92
fffff880`068f3130 fffff800`03385448 : ffffffff`ffffffff 00000000`00000001 fffffa80`07801b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`068f3180 fffff800`030cced3 : fffffa80`07801b30 fffff800`c0000006 fffffa80`07ca2b60 00000000`009f0df0 : nt!NtTerminateProcess+0xf4
fffff880`068f3200 fffff800`030c9470 : fffff800`0311967f fffff880`068f3b78 fffff880`068f38d0 fffff880`068f3c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`068f3398 fffff800`0311967f : fffff880`068f3b78 fffff880`068f38d0 fffff880`068f3c20 00000000`ffe8b4d8 : nt!KiServiceLinkage
fffff880`068f33a0 fffff800`030cd2c2 : fffff880`068f3b78 00000000`00a70000 fffff880`068f3c20 00000000`ffe8fb88 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`068f3a40 fffff800`030cbe3a : 00000000`00000000 00000000`ffe83900 00000000`00a4b001 00000000`00a70000 : nt!KiExceptionDispatch+0xc2
fffff880`068f3c20 00000000`77b18f55 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`009f13b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b18f55
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe
Followup: MachineOwner
---------
A windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...
To supplement the excellent advice given by Vir Gnarus:- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
- Use HD Diagnostic to find your hard disk manufacturer and also to find the diagnostic tools provided by that manufacturer. Run all tests through those diagnostic tools to determine whether the hard disk is faulty.
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.