Solved BSOD playing BF4, ntoskrnl

[Squirel]

Hi,

Been getting BSOD recently when playing BF4 though it sometimes crashes when I'm not in BF4 too, is it memory issue?

Files attached.

Thanks!

 

[essenbe]

Hello, Squirel and welcome to the forums. I will try to help you with this. First,I need you to do a couple of things.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

You only had 2 dump files which is what we use to debug with. Both dump files had different error codes, but listed basically the same cause.

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.
[COLOR=red]If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
[/COLOR]If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50068280, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000002c581880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00d050034, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
 
[COLOR=red]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.[/COLOR]
[COLOR=red]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

CRITICAL_OBJECT_TERMINATION (f4)
[COLOR=red]A process or thread crucial to system operation has unexpectedly exited or been
terminated.
[/COLOR]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: fffffa800e686670, Terminating object
Arg3: fffffa800e686950, Process image file name
Arg4: fffff800031d9e20, Explanatory message (ascii)
Debugging Details:
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BUCKET_ID:  X64_[COLOR=red]0xF4_IOERR_IMAGE[/COLOR]_csrss.exe
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_csrss.exe

An I/O error is typically a hard drive

Your hard drive is apparently showing errors or has failed/is failing.

I don't know what hard drive(s) you have, because of no system specs. But I would suggest you backup all personal data to an external source, first thing. I would then run Seatools for DOS on all Mechanical Hard drives, Internal and external (http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3)

Please let me know the results of the test.

 

[Squirel]

Thanks! Will post results of the test. Hope it's not one of my newer drives. Just got the Samsung SSD about a month ago and the WD Black is less than year old.

 

[essenbe]

If you use external drives, check those too, both the long test and the short test. Don't run it on the SSD. I would run check disk too. http://www.sevenforums.com/tutorials/433-disk-check.html

 

[Squirel]

Replaced main hard drive with another SSD. Haven't had any issues since. Thanks!

 

[essenbe]

Great news. I'm glad everything is working for you. Good job. Thanks for letting us know.