Random BSOD BCCode F4

This has been a problem for the last few days. I cleaned out my PC with some compressed air, closed everything back up and since then I have had these BSOD. Normally the thing will just do a hard crash and not even display the BSOD screen. This last time I got lucky and decided this was beyond my knowledge sphere. so here are the files it generated. Someone who can intemperate these things, have fun.

**EDIT** Attached correct documents. Sorry about improper format. I literally made this account today.

You may go back inside the computer and see if you accidentally knocked a wire loose. Check the cables on both ends of the hard drives as well as reseating the ram modules. Check all the wiring, it's easy to move something or knock something loose without realizing it.

Also please follow these instructions Blue Screen of Death (BSOD) Posting Instructions

GravityzCatz, I'll look at it again tomorrow, but the dump files are not giving me much to go on. As I stated above I would check the wiring to the hard drives and the memory. I'm getting some references to I/O data and memory issues. There are several mentions of the MSAHCI, which is Microsoft's AHCI driver. With that coupled with the I/O data, it leads me to believe there is a problem with the hard drive.

Also, don't worry about the forgotten file. That's no problem at all.

Code:

---- ETW minidump data unavailable-----
KERNEL_LOG_FAILING_PROCESS:  <NULL>
PROCESS_OBJECT: fffffa800efc2870
IMAGE_NAME:  csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000 
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0xF4_c0000005

Code:

---- ETW minidump data unavailable-----
KERNEL_LOG_FAILING_PROCESS:  
PROCESS_OBJECT: fffffa800eeafb30
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

At this point I would run Western Digitals' diagnostic program from DOS running the short and long tests. WD Support / Downloads / SATA & SAS / WD Black
I think you may also need to run Checkdisk


I would also run the system file checker, which will test the system files for any missing or corrupted files SFC /SCANNOW Command - System File Checker

OK, just let me know. We'll hope for the best.

Give me a minute tolook at the files

I still believe that you dislodged some of the ram or the wiring when you were cleaning out the computer. It is easy to do, I've done it myself. I would check the wiring on everything, especially the hard drives and I would completely remove the ram, after turning the computer off and draining any residual power, and reinstall it. You are still getting I/O errors which means data cannot be read to or from your hard drives. This can also be caused by ram. If you still can't find it

Please Run Memtest86+

   Information

Please download from this site http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you mat have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.

Also run the sfc /scannow and the checkdisk with the /f /r switches again from a command prompt in the link I provided above.