2 BSOD in last 2 days happening overnight

[dschnob]

I randomly get a BSOD. Although the frequency has been rare, I have experienced the last 2 over the last 2 nights. When investigating this issue about 6 months ago, something led me to believe that it was either a defective hard drive or a video card driver issue but my drivers appear to be up to date. One forum suggested that the most recent video driver has issues but this has not been confirmed and finding previous drivers is difficult.

I have followed the instructions and attached the DM Log Collector.

Any/all help would be very much appreciated as I am running out of options to try.

 

[BorisTheAnimal]

Hi, did a fast look through the dump files and most of them point to faulty hardware, specifically the hard-drive and ram. Though before going too fast forward I would recommend you doing these steps:

A run of Memtest86+

Diagnostic Test

 RAM TEST

:ar: Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Diagnostics Test

 HDD TEST

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

   Note

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

:ar: Run chkdsk
Disk Check - Windows 7 Help Forums

:ar: 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.

/Boris

 

[axe0]

Copy/paste of my post?

You're right, but only the HDD tests are necessary as it looks like for now.
The 0xF4 is usually caused by hard drive errors, what also this time is the case.
Below show IOERR, meaning Input/Output errors.
Input/Output errors means that the data can't be read from the hard drive.

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: fffffa800b493b10, Terminating object
Arg3: fffffa800b493df0, Process image file name
Arg4: fffff80003bc1e70, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800b493b10

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]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`02ef60e8 fffff800`03c53cb2 : 00000000`000000f4 00000000`00000003 fffffa80`0b493b10 fffffa80`0b493df0 : nt!KeBugCheckEx
fffff880`02ef60f0 fffff800`03c0ad8b : ffffffff`ffffffff fffffa80`0a8b0b50 fffffa80`0b493b10 fffffa80`0b493b10 : nt!PspCatchCriticalBreak+0x92
fffff880`02ef6130 fffff800`03b75484 : ffffffff`ffffffff 00000000`00000001 fffffa80`0b493b10 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29ce6
fffff880`02ef6180 fffff800`038bc853 : fffffa80`0b493b10 fffff800`c0000006 fffffa80`0a8b0b50 00000000`00420c30 : nt!NtTerminateProcess+0xf4
fffff880`02ef6200 fffff800`038b8e10 : fffff800`0393e929 fffff880`02ef6b78 fffff880`02ef68d0 fffff880`02ef6c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02ef6398 fffff800`0393e929 : fffff880`02ef6b78 fffff880`02ef68d0 fffff880`02ef6c20 00000000`77ae9004 : nt!KiServiceLinkage
fffff880`02ef63a0 fffff800`038bcc42 : fffff880`02ef6b78 00000000`00460000 fffff880`02ef6c20 00000000`77b0e6bc : nt! ?? ::FNODOBFM::`string'+0x48074
fffff880`02ef6a40 fffff800`038bb7ba : 00000000`00000000 00000000`77ae9007 00000000`0043b801 00000000`00460000 : nt!KiExceptionDispatch+0xc2
fffff880`02ef6c20 00000000`779e8996 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`004211f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779e8996


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

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

 

[dschnob]

I suspected a possible HD issue. Thanks for the feedback so far. I am going to run some HD tests.