BSOD intermitent seriously slow response

kzavala9 · Jan 18, 2012

Windows 7 . . .x64
- original installed VISTA upgraded to 7 VIA OEM upgrade disk
- Upgraded 500 GB HD after previous HD crash
- OS installation last re-installed May 11

I have had issues with this computer off and on for nearly 1 year. It was just sitting in the closet for the last 6 months. Now I am ready to try and get it working correctly. I am not an expert but I can (usually) follow instructions.

Any help would be greatly appreciated.

writhziden · Jan 18, 2012

Code:

[list=1]
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\kzavala9\Windows_NT6_BSOD_jcgriff2\011612-36597-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c60650
Debug session time: Mon Jan 16 09:27:03.984 2012 (UTC - 7:00)
System Uptime: 0 days 1:37:54.401
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40009bc0, ffffffffc0000185, d84c860, fffff88001378000}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff80002cca288
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40009bc0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000000d84c860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88001378000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  avgchsva.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880056dd500 -- (.trap 0xfffff880056dd500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880056dd7a8 rbx=0000000000000000 rcx=fffffa8007da5790
rdx=fffff8a003216640 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001377ffb rsp=fffff880056dd690 rbp=fffffa80085e2e20
 r8=fffff880056dd810  r9=fffff8a003216640 r10=0000000000000000
r11=fffff880056dd700 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
Ntfs!TxfTransDoNextUndo+0x4b:
fffff880`01377ffb 4088bc2438000000 mov     byte ptr [rsp+38h],dil ss:0018:fffff880`056dd6c8=70
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b0a842 to fffff80002a9ad00

STACK_TEXT:  
fffff880`056dd1e8 fffff800`02b0a842 : 00000000`0000007a fffff6fc`40009bc0 ffffffff`c0000185 00000000`0d84c860 : nt!KeBugCheckEx
fffff880`056dd1f0 fffff800`02ac272f : fffffa80`09206010 fffff880`056dd360 fffff800`02ccd500 fffffa80`09206010 : nt! ?? ::FNODOBFM::`string'+0x37bba
fffff880`056dd2d0 fffff800`02aa8fa9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffffa80`034d5bf0 : nt!MiIssueHardFault+0x28b
fffff880`056dd3a0 fffff800`02a98e2e : 00000000`00000008 fffff880`01378000 00000000`00000100 fffff8a0`03216640 : nt!MmAccessFault+0x1399
fffff880`056dd500 fffff880`01377ffb : 00000000`00000000 ffff0100`00000000 fffff8a0`0e047b40 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`056dd690 fffff880`01381efd : fffffa80`07da5790 fffff8a0`03216640 fffff880`056dd810 00000000`00000000 : Ntfs!TxfTransDoNextUndo+0x4b
fffff880`056dd7b0 fffff880`012497d3 : 00000000`00000000 fffffa80`085e2e20 fffff880`056dda80 fffff800`02a76400 : Ntfs!TxfTransMgrAbort+0x40d
fffff880`056dd920 fffff800`02d27f26 : 00000000`00000458 fffff8a0`0020a000 fffff8a0`03216640 00000000`00000000 : Ntfs!TxfKtmNotification+0x7e3
fffff880`056dda00 fffff800`02d26131 : 00000000`00000458 fffffa80`085e2e20 fffff800`02bd61d0 fffff8a0`03216640 : nt!TmpSetNotificationResourceManager+0xf2
fffff880`056dda80 fffff800`02e87cdb : fffffa80`00000006 fffff800`00000008 00000000`00000001 fffffa80`083e7d20 : nt!TmpNotifyAllEnlistmentsTransaction+0x19d
fffff880`056ddb00 fffff800`02d20dfe : 00000000`00000000 fffff880`056ddc60 00000000`00000001 fffffa80`083e7d20 : nt!TmpTxActionDoRollback+0x19b
fffff880`056ddb50 fffff800`02ee852d : fffffa80`083e7d20 00000000`00000001 00000000`00000000 00000000`00000001 : nt!TmRollbackTransaction+0x17e
fffff880`056ddba0 fffff800`02a99f93 : fffffa80`085ffb60 000007fe`ff46e860 fffffa80`083e7d20 00000000`0007f6e0 : nt!NtRollbackTransaction+0x5d
fffff880`056ddbe0 00000000`773827ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`034af528 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773827ba


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff88001378000 - Ntfs!TxfTransDoNextUndo+50
	[ 01:00 ]
    fffff88001378003-fffff88001378008  6 bytes - Ntfs!TxfTransDoNextUndo+53 (+0x03)
	[ 41 0f ba a4 24 88:00 00 00 00 00 00 ]
    fffff8800137800c-fffff8800137801d  18 bytes - Ntfs!TxfTransDoNextUndo+5c (+0x09)
	[ 0f 73 2c 8a 05 f4 f7 ee:00 00 00 00 00 00 00 00 ]
    fffff88001378020-fffff88001378028  9 bytes - Ntfs!TxfTransDoNextUndo+70 (+0x14)
	[ 48 8d 15 39 14 f3 ff b9:00 00 00 00 00 00 00 00 ]
    fffff8800137802a-fffff88001378032  9 bytes - Ntfs!TxfTransDoNextUndo+7a (+0x0a)
	[ 19 c0 e8 af 1d eb ff b8:00 00 00 00 00 00 00 00 ]
    fffff88001378034-fffff88001378038  5 bytes - Ntfs!TxfTransDoNextUndo+84 (+0x0a)
	[ 19 c0 e9 28 13:00 00 00 00 00 ]
    fffff8800137803b-fffff8800137803e  4 bytes - Ntfs!TxfTransDoNextUndo+8b (+0x07)
	[ 48 39 ba e0:00 00 00 00 ]
    fffff88001378042-fffff88001378045  4 bytes - Ntfs!TxfTransDoNextUndo+92 (+0x07)
	[ 0f 85 b7 02:00 00 00 00 ]
    fffff88001378048-fffff8800137804b  4 bytes - Ntfs!TxfTransDoNextUndo+98 (+0x06)
	[ 83 89 34 01:00 00 00 00 ]
    fffff8800137804e-fffff8800137807e  49 bytes - Ntfs!TxfTransDoNextUndo+9e (+0x06)
	[ 10 4c 8d 72 30 49 8b ce:00 00 00 00 00 00 00 00 ]
    fffff88001378082-fffff8800137808b  10 bytes - Ntfs!TxfTransDoNextUndo+d2 (+0x34)
	[ 41 0f ba 6d 04 09 48 8d:00 00 00 00 00 00 00 00 ]
    fffff8800137808f-fffff88001378098  10 bytes - Ntfs!TxfTransDoNextUndo+df (+0x0d)
	[ 48 89 4c 24 40 48 8d 84:00 00 00 00 00 00 00 00 ]
    fffff8800137809c-fffff880013780c1  38 bytes - Ntfs!TxfTransDoNextUndo+ec (+0x0d)
	[ 48 89 44 24 38 4c 89 74:00 00 00 00 00 00 00 00 ]
    fffff880013780c5-fffff880013780d0  12 bytes - Ntfs!TxfTransDoNextUndo+115 (+0x29)
	[ 45 8b c7 48 8d 54 24 60:00 00 00 00 00 00 00 00 ]
    fffff880013780d2 - Ntfs!TxfTransDoNextUndo+122 (+0x0d)
	[ 02:00 ]
    fffff880013780d5-fffff880013780e4  16 bytes - Ntfs!TxfTransDoNextUndo+125 (+0x03)
	[ e8 f2 3d eb ff 8b c8 89:00 00 00 00 00 00 00 00 ]
    fffff880013780e7-fffff8800137810a  36 bytes - Ntfs!TxfTransDoNextUndo+137 (+0x12)
	[ ef 41 0f ba 75 04 09 3b:00 00 00 00 00 00 00 00 ]
    fffff8800137810c - Ntfs!TxfTransDoNextUndo+15c (+0x25)
	[ 02:00 ]
    fffff8800137810f-fffff88001378121  19 bytes - Ntfs!TxfTransDoNextUndo+15f (+0x03)
	[ 49 8b d4 49 8b cd e8 76:00 00 00 00 00 00 00 00 ]
    fffff88001378124-fffff88001378136  19 bytes - Ntfs!TxfTransDoNextUndo+174 (+0x15)
	[ c0 75 20 48 8b 05 ca 8c:00 00 00 00 00 00 00 00 ]
    fffff88001378139-fffff88001378140  8 bytes - Ntfs!TxfTransDoNextUndo+189 (+0x15)
	[ 48 89 0a 33 c0 e9 20 12:00 00 00 00 00 00 00 00 ]
    fffff88001378143-fffff8800137814b  9 bytes - Ntfs!TxfTransDoNextUndo+193 (+0x0a)
	[ 8b 4c 24 50 3b cf 0f 8d:00 00 00 00 00 00 00 00 ]
    fffff8800137814f-fffff88001378153  5 bytes - Ntfs!TxfTransDoNextUndo+19f (+0x0c)
	[ 41 f6 85 34 01:00 00 00 00 00 ]
    fffff88001378156-fffff88001378161  12 bytes - Ntfs!TxfTransDoNextUndo+1a6 (+0x07)
	[ 40 74 25 49 89 1e c7 44:00 00 00 00 00 00 00 00 ]
    fffff88001378164-fffff8800137819e  59 bytes - Ntfs!TxfTransDoNextUndo+1b4 (+0x0e)
	[ 4c 8d 0d f5 12 f3 ff 4c:00 00 00 00 00 00 00 00 ]
    fffff880013781a1-fffff880013781a2  2 bytes - Ntfs!TxfTransDoNextUndo+1f1 (+0x3d)
	[ ba 27:00 00 ]
    fffff880013781a6-fffff880013781d4  47 bytes - Ntfs!TxfTransDoNextUndo+1f6 (+0x05)
	[ 89 4c 24 30 48 89 44 24:00 00 00 00 00 00 00 00 ]
    fffff880013781d7-fffff880013781f5  31 bytes - Ntfs!TxfTransDoNextUndo+227 (+0x31)
	[ 4c 8d 0d 82 12 f3 ff 4c:00 00 00 00 00 00 00 00 ]
    fffff880013781f8-fffff880013781fe  7 bytes - Ntfs!TxfTransDoNextUndo+248 (+0x21)
	[ f0 45 01 bc 24 10 02:00 00 00 00 00 00 00 ]
    fffff88001378201-fffff88001378219  25 bytes - Ntfs!TxfTransDoNextUndo+251 (+0x09)
	[ 8b 54 24 68 48 8b 4c 24:00 00 00 00 00 00 00 00 ]
    fffff8800137821c-fffff8800137822c  17 bytes - Ntfs!TxfTransDoNextUndo+26c (+0x1b)
	[ 4c 8d 0d 3d 12 f3 ff 4c:00 00 00 00 00 00 00 00 ]
    fffff8800137822e-fffff8800137824a  29 bytes - Ntfs!TxfTransDoNextUndo+27e (+0x12)
	[ 19 c0 41 8b d6 49 8b cc:00 00 00 00 00 00 00 00 ]
    fffff8800137824d-fffff88001378261  21 bytes - Ntfs!TxfTransDoNextUndo+29d (+0x1f)
	[ 48 8d 15 0c 12 f3 ff 41:00 00 00 00 00 00 00 00 ]
    fffff88001378264-fffff880013782bf  92 bytes - Ntfs!TxfTransDoNextUndo+2b4 (+0x17)
	[ f0 81 66 10 ff ff ff fc:00 00 00 00 00 00 00 00 ]
    fffff880013782c2-fffff880013782cd  12 bytes - Ntfs!TxfTransDoNextUndo+312 (+0x5e)
	[ 48 89 02 49 8b 06 48 89:00 00 00 00 00 00 00 00 ]
    fffff880013782d1-fffff880013782d7  7 bytes - Ntfs!TxfTransDoNextUndo+321 (+0x0f)
	[ 09 74 08 f0 81 4e 10:00 00 00 00 00 00 00 ]
    fffff880013782db-fffff880013782e0  6 bytes - Ntfs!TxfTransDoNextUndo+32b (+0x0a)
	[ 08 33 c0 e9 80 10:00 00 00 00 00 00 ]
    fffff880013782e3-fffff880013782f3  17 bytes - Ntfs!TxfTransDoNextUndo+333 (+0x08)
	[ 49 8b 06 48 89 46 40 4c:00 00 00 00 00 00 00 00 ]
    fffff880013782f5-fffff880013782fc  8 bytes - Ntfs!TxfTransDoNextUndo+345 (+0x12)
	[ 44 8b 74 24 50 e9 e2 04:00 00 00 00 00 00 00 00 ]
    fffff880013782ff-fffff88001378315  23 bytes - Ntfs!TxfTransDoNextUndo+34f (+0x0a)
	[ 48 83 c2 50 4c 8d 76 30:00 00 00 00 00 00 00 00 ]
    fffff88001378318-fffff88001378322  11 bytes - Ntfs!TxfTransDoNextUndo+368 (+0x19)
	[ 41 0f ba 6d 04 09 41 83:00 00 00 00 00 00 00 00 ]
    fffff88001378325-fffff8800137833d  25 bytes - Ntfs!TxfTransDoNextUndo+375 (+0x0d)
	[ 10 48 8b 44 24 58 48 83:00 00 00 00 00 00 00 00 ]
    fffff88001378341-fffff8800137834a  10 bytes - Ntfs!TxfTransDoNextUndo+391 (+0x1c)
	[ 48 89 4c 24 30 48 8d 8c:00 00 00 00 00 00 00 00 ]
    fffff8800137834e-fffff8800137836a  29 bytes - Ntfs!TxfTransDoNextUndo+39e (+0x0d)
	[ 48 89 4c 24 28 48 89 44:00 00 00 00 00 00 00 00 ]
    fffff8800137836e-fffff8800137837e  17 bytes - Ntfs!TxfTransDoNextUndo+3be (+0x20)
	[ e8 65 3b eb ff 44 8b f0:00 00 00 00 00 00 00 00 ]
    fffff88001378381-fffff880013783a2  34 bytes - Ntfs!TxfTransDoNextUndo+3d1 (+0x13)
	[ ef 41 0f ba 75 04 09 3b:00 00 00 00 00 00 00 00 ]
    fffff880013783a4 - Ntfs!TxfTransDoNextUndo+3f4 (+0x23)
	[ 02:00 ]
    fffff880013783a7-fffff880013783ba  20 bytes - Ntfs!TxfTransDoNextUndo+3f7 (+0x03)
	[ 49 8b d4 49 8b cd e8 de:00 00 00 00 00 00 00 00 ]
    fffff880013783bd-fffff880013783d1  21 bytes - Ntfs!TxfTransDoNextUndo+40d (+0x16)
	[ c0 75 14 48 8b 05 31 8a:00 00 00 00 00 00 00 00 ]
    fffff880013783d4-fffff880013783d9  6 bytes - Ntfs!TxfTransDoNextUndo+424 (+0x17)
	[ 44 3b f7 0f 8d cb:00 00 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3671 errors : !Ntfs (fffff88001378000-fffff88001378fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\kzavala9\Windows_NT6_BSOD_jcgriff2\011612-35693-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02ca2670
Debug session time: Mon Jan 16 17:01:35.028 2012 (UTC - 7:00)
System Uptime: 0 days 0:33:14.776
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80082604b0, fffffa8008260790, fffff80002ddd8b0}

Probably caused by : csrss.exe

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

0: 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: fffffa80082604b0, Terminating object
Arg3: fffffa8008260790, Process image file name
Arg4: fffff80002ddd8b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80082604b0

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:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05bd4ac8 fffff800`02e645e2 : 00000000`000000f4 00000000`00000003 fffffa80`082604b0 fffffa80`08260790 : nt!KeBugCheckEx
fffff880`05bd4ad0 fffff800`02e1199b : ffffffff`ffffffff fffffa80`026c2b60 fffffa80`082604b0 fffffa80`082604b0 : nt!PspCatchCriticalBreak+0x92
fffff880`05bd4b10 fffff800`02d91448 : ffffffff`ffffffff 00000000`00000001 fffffa80`082604b0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`05bd4b60 fffff800`02ad8ed3 : fffffa80`082604b0 fffff880`c0000006 fffffa80`026c2b60 fffffa80`0821d4a0 : nt!NtTerminateProcess+0xf4
fffff880`05bd4be0 00000000`774115da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02e5dfd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774115da


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
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\kzavala9\Windows_NT6_BSOD_jcgriff2\011712-44569-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c9a670
Debug session time: Tue Jan 17 21:09:23.012 2012 (UTC - 7:00)
System Uptime: 0 days 0:09:37.760
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80053f4b30, fffffa80053f4e10, fffff80002dd58b0}

Probably caused by : wininit.exe

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

0: 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: fffffa80053f4b30, Terminating object
Arg3: fffffa80053f4e10, Process image file name
Arg4: fffff80002dd58b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80053f4b30

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  WerFault.exe

BUGCHECK_STR:  0xF4_WerFault.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002e5c5e2 to fffff80002ad1c40

STACK_TEXT:  
fffff880`025b1ac8 fffff800`02e5c5e2 : 00000000`000000f4 00000000`00000003 fffffa80`053f4b30 fffffa80`053f4e10 : nt!KeBugCheckEx
fffff880`025b1ad0 fffff800`02e0999b : ffffffff`ffffffff fffffa80`026d7060 fffffa80`053f4b30 fffffa80`05a81340 : nt!PspCatchCriticalBreak+0x92
fffff880`025b1b10 fffff800`02d89448 : ffffffff`ffffffff 00000000`00000001 fffffa80`053f4b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`025b1b60 fffff800`02ad0ed3 : fffffa80`053f4b30 fffff880`000000ff fffffa80`026d7060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`025b1be0 00000000`774e15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0016d218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774e15da


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  wininit.exe

FAILURE_BUCKET_ID:  X64_0xF4_WerFault.exe_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_WerFault.exe_IMAGE_wininit.exe

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


[/list]

If you are overclocking anything, please stop.

You had a hard disk problem, possibly mechanical; could be a hard disk failing. It also resulted in a memory corruption.
- 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).
- 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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
A windows system process was terminated unexpectedly. Do the following steps.
- Update all drivers that you are able to. If you need help finding a driver, let us know. The following drivers should be updated first.
  Code:
  
  OA009Ufd fffff880`01093000 fffff880`010bc3a0 Tue Jun 03 03:30:37 2008 (48450f3d) 0002c9c2 OA009Ufd.sys OA009Vid fffff880`03e9f000 fffff880`03eea100 Mon Aug 25 07:46:09 2008 (48b2b7a1) 0004e5fd OA009Vid.sys
  You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.
  1. Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
  2. Driver Search Methods provides driver manufacturers and links to their homepages.
  There are a few methods for updating drivers.
  To fully re-install a driver, use the following steps.
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Find the device you are trying to uninstall by expanding the appropriate set of devices
  6. Right click the device
  7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer
  10. Install the latest driver for the device once Windows starts.
  Alternatively:
  1. Login as an adminstrative user.
  2. Click Start Menu
  3. Click Control Panel
  4. Click Hardware and Sound
  5. Click Device Manager (the last link under Devices and Printers)
  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
  11. Install the latest driver for the device once Windows starts.
- Run Windows Update and install all updates.
- Check for viruses.
  
  Download and install the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not start the trial) and make sure it is updated. Do not run a scan yet.
  Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet
  Download the Fakerean removal tool but do not run it yet.
  Start your computer in http://www.sevenforums.com/tutorials/69585-safe-mode.html
  Unzip VIPRE Rescue and let it run.
  Run a full scan with Malwarebytes.
  Run the fakerean removal tool.
- Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.
Same as 2.

Thanks to Dave76 for help understanding possible causes.

BSOD intermitent seriously slow response

kzavala9

New member

My Computer

writhziden

Closed by request.

My Computer

Similar threads