BSoD, memory dump failed

[Berbe]

[Updated] BSoD at random times

Hello,

These days, I get BSoD in strange conditions: during startup, or during use, no pattern could be found.

The thing is, the memory dumps could not be written properly, which for me suggests trouble at the disk I/O level.
chkdsk has been run on startup and completed successfully.

How to investigate?

[EDIT]
Another BSoD with, this time, a successful dump!

The attached archive has been changed for the most recent data.

 

[axe0]

As usual with the 0xF4, Input Output errors.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

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

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

ETW minidump data unavailable

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0       

BIOS_DATE:  07/17/2014

BASEBOARD_PRODUCT:  G750JM

BASEBOARD_VERSION:  1.0       

BUGCHECK_P1: 3

BUGCHECK_P2: fffffa8011486b10

BUGCHECK_P3: fffffa8011486df0

BUGCHECK_P4: fffff8000358e6d0

PROCESS_OBJECT: fffffa8011486b10

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_[COLOR="red"]IOERR[/COLOR]

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

STACK_TEXT:  
fffff880`059e79c8 fffff800`0361d082 : 00000000`000000f4 00000000`00000003 fffffa80`11486b10 fffffa80`11486df0 : nt!KeBugCheckEx
fffff880`059e79d0 fffff800`03542d7b : ffffffff`ffffffff fffffa80`10f15750 fffffa80`11486b10 fffffa80`11486b10 : nt!PspCatchCriticalBreak+0x92
fffff880`059e7a10 fffff800`0353f904 : ffffffff`ffffffff 00000000`00000001 fffffa80`11486b10 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29c66
fffff880`059e7a60 fffff800`03285ed3 : fffffa80`11486b10 fffff880`c0000006 fffffa80`10f15750 fffffa80`12657060 : nt!NtTerminateProcess+0xf4
fffff880`059e7ae0 00000000`76d5dc7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01b1dd18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d5dc7a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0xF4_[COLOR="red"]IOERR[/COLOR]_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_[COLOR="red"]IOERR[/COLOR]_IMAGE_csrss.exe

PRIMARY_PROBLEM_CLASS:  X64_0xF4_[COLOR="red"]IOERR[/COLOR]_IMAGE_csrss.exe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_[COLOR="Red"]ioerr[/COLOR]_image_csrss.exe

FAILURE_ID_HASH:  {183378f4-a174-8cab-8ad7-e5d860a58439}

Followup:     MachineOwner