BSOD Kernel_Data_Inpage_Error STOP:0x0000007A

Windows 7 x64, up to date. 1 Chrome tab, Explorer, foobar2000 (media player) running. Had one a month ago, though I don't remember if it was the same error. It didn't happen again so I never looked into it. Then it happened on the 6th, yesterday, and again just now.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40010ef0, ffffffffc000009d, 24044abe0, fffff880021de000}

Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+633 )

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.

Arguments:
Arg1: fffff6fc40010ef0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 000000024044abe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880021de000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

I'm not sure how to read the crash dump. It seems to suggest at first the likely culprit is failing RAM, then it says disk hardware error.

Any help would be appreciated.

axe0 said:

It suggest that there's an issue with the disk, it has trouble connecting to it.
Use CrystalDiskInfo to check the health of the disk

I thought this would be the most likely thing to fail, as this is the first SSD I ever bought. It's quite old.

There were no errors the past two days, but it happened again an hour or so ago. This time there was only a Youtube video playing in Chrome. I noticed before the blue screen that the monitors briefly changed colors slightly, like a flash, but the display didn't go out. Then I noticed my dark themed taskbar turned light, then the error screen came up. It was the same error as before. It makes me worry something is wrong with the graphics card, but maybe symptoms like that can be caused by the system disk failing. I don't know.

Added transfer test from the OCZ utility.

axe0 said:

You could try to reseat / seat the GPU in a different slot, GPU issues are sometimes the true cause behind this kind of crashes.

I'm still kind of suspecting the SSD, but I'm not sure if there's a way to test it further besides installing the OS on another drive and just eliminating it.

I did find a thread where someone was having F4 errors, which is what the one I had just now said instead of 7A. In that case it was the OCZ Vertex failing, but they never reported what it showed in Crystal Disk Info.

Here's what the dump said just now:

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa800de2c8e0, Terminating object
Arg3: fffffa800de2cbc0, Process image file name
Arg4: fffff80001f72060, Explanatory message (ascii)

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

ETW minidump data unavailable

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.24024.amd64fre.win7sp1_ldr.180112-0600

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  Z97X-Gaming 5

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F7

BIOS_DATE:  09/18/2015

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  Z97X-Gaming 5

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: fffffa800de2c8e0

BUGCHECK_P3: fffffa800de2cbc0

BUGCHECK_P4: fffff80001f72060

KERNEL_LOG_FAILING_PROCESS:  

PROCESS_NAME:  csrss.exe

CRITICAL_PROCESS:  csrss.exe

EXCEPTION_CODE: (Win32) 0xec96060 (248078432) - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0xec96060 - <Unable to get error code text>

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1C'00000000 (cache) 1C'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xF4

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  

ANALYSIS_SESSION_TIME:  02-17-2018 16:14:28.0536

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80001fde7f2 to fffff80001cb92a0

STACK_TEXT:  
fffff880`191729d8 fffff800`01fde7f2 : 00000000`000000f4 00000000`00000003 fffffa80`0de2c8e0 fffffa80`0de2cbc0 : nt!KeBugCheckEx
fffff880`191729e0 fffff800`01f9b476 : 00000000`00000001 fffffa80`0ec96060 fffffa80`0de2c8e0 00000000`00000001 : nt!PspCatchCriticalBreak+0x92
fffff880`19172a20 fffff800`020a6ff4 : 00000000`00000001 ffffffff`ffffffff fffffa80`0de2c8e0 fffff800`00000008 : nt! ?? ::NNGAKEGL::`string'+0x25756
fffff880`19172a70 fffff800`01cc9183 : ffffffff`ffffffff fffffa80`0ec96060 fffffa80`0de2c8e0 fffffa80`0ef78680 : nt!NtTerminateProcess+0x284
fffff880`19172ae0 00000000`76e49b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02c0ddd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e49b6a


THREAD_SHA1_HASH_MOD_FUNC:  e9460336222f4471d8ae88a3d24ad7df3aff8ef1

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b7475b3755a5c84d1f18f5ec8bb85d67e0c31524

THREAD_SHA1_HASH_MOD:  f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP: 
nt!PspCatchCriticalBreak+92
fffff800`01fde7f2 cc              int     3

FAULT_INSTR_CODE:  5c8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PspCatchCriticalBreak+92

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5a58dc54

IMAGE_VERSION:  6.1.7601.24024

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_ec96060_nt!PspCatchCriticalBreak+92

BUCKET_ID:  X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_ec96060_nt!PspCatchCriticalBreak+92

PRIMARY_PROBLEM_CLASS:  X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_ec96060_nt!PspCatchCriticalBreak+92

TARGET_TIME:  2018-02-17T20:41:12.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-01-12 11:03:32

BUILDDATESTAMP_STR:  180112-0600

BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.24024.amd64fre.win7sp1_ldr.180112-0600

ANALYSIS_SESSION_ELAPSED_TIME:  611

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_csrss.exe_bugcheck_critical_process_ec96060_nt!pspcatchcriticalbreak+92

FAILURE_ID_HASH:  {51b4f0bf-e65c-f93d-fddc-b63dab148b03}

Followup:     MachineOwner

axe0 said:

Is the SSD firmware up to date?

Yeah. It wasn't in that screenshot of the transfer rate test, but that is OCZ's utility, and it checks.

axe0 said:

Boot in safe mode and see if the system crashes in safe mode as well.

It's been two full days without errors now. A couple more and I will start to think it's not a hardware problem.
I remembered reading a comment that someone was getting errors when they suspended the computer. I don't use sleep or suspend, but I do regularly password lock it. For some reason I have the impression that locking has some similarities with suspend/sleep.

If I understand correctly, and the errors stop as long as I'm not locking the computer, then it's a driver at fault. I'm not sure how I could figure out which one. I could look back at the dump file dates and see what I installed just before then.

Or maybe it is hardware and locking the computer just causes the error to occur, or occur more frequently.
Either way I will use a different drive as the system drive next time I do a clean install. How soon that happens depends on if I can figure this out or not. It was only in the fall that I last reinstalled Windows.