Question
35233 views

Windows 8.1 BSOD Kernel Data Inpage Error and Critical Process Died

TonSchepers asked on

I keep getting either Kernel Data inpage Error BSOD or Critical Process Died BSOD. And they occur at random so it's hard to pinpoint what the exact problem is, outside it saying it's caused by driver: ntoskrnl.exe with the Kernal Data Inpage error BSOD and caused by driver: NTFS.sys with the Critical Process Died.

I've clean installed my laptop about 3 times now, and it doesn't work out, I've been trying to find whatever the problem is but I can't figure it out.

Hopefully I'll be able to fix it after I get some help here.

Kernal Data Inpage Error

052214-32546-01.dmp

22-5-2014 09:29:17 KERNEL_DATA_INPAGE_ERROR 0x0000007a

fffff6e8`001d7d30

ffffffff`c000003f 

00000000`3cac0be0

ffffd000`3afa6000

ntoskrnl.exe

ntoskrnl.exe+153fa0

x64

ntoskrnl.exe+153fa0

C:\WINDOWS\Minidump\052214-32546-01.dmp

4

15

9600

146.013

22-5-2014 09:30:22

Critical Process Died

051914-34421-01.dmp

19-5-2014 17:36:46

CRITICAL_PROCESS_DIED

0x000000ef

ffffe000`1bf88900

00000000`00000000

00000000`00000000

00000000`00000000

Ntfs.sys

Ntfs.sys+11be8

x64

ntoskrnl.exe+153fa0

C:\WINDOWS\Minidump\051914-34421-01.dmp

4

15

9600

287.944

19-5-2014 17:39:14

Sorry that I posted the bluescreenView report like this because I don't know how to copy it like most people do when they ask a question.

Thanks in advance

77 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Thanks very much!


We have two bug checks:


KERNEL_DATA_INPAGE_ERROR (7a)

This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.


BugCheck 7A, {fffff6e8001d7d30, ffffffffc000003f, 3cac0be0, ffffd0003afa6000}


The 2nd parameter of the bug check is 0xc000003f which indicates a cyclic redundancy check (CRC) checksum error occurred. Windows' Memory Manager detected corruption of a pagefile page while performing an in-page operation. The data read from storage does not match the original data written.

CRITICAL_PROCESS_DIED (ef)

This indicates that a critical system process died.

BugCheck EF, {ffffe0001bf88900, 0, 0, 0}

2: kd> !process ffffe0001bf88900 3
GetPointerFromAddress: unable to read from fffff80342957000
PROCESS ffffe0001bf88900
    SessionId: none  Cid: 0274    Peb: 7ff76425e000  ParentCid: 01e8
    DirBase: 1160ff000  ObjectTable: ffffc0006a79b6c0  HandleCount: <Data Not Accessible>
    Image: wininit.exe

The critical system process that died was wininit.exe which is the Service Control Manager. It starts, stops and interacts with Windows service processes.

------------------------------

Overall, it looks like you have a faulty hard drive. I would please do the following though to be sure there's not a software file system conflict:

ESET may be causing file system conflicts with Malwarebytes Pro, so please remove and replace both with Windows Defender for temporary troubleshooting purposes:


ESET removal -
http://kb.eset.com/esetkb/index?page=content&id=SOLN2788


Windows Defender (how to turn on after removal) -
http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

Regards,

Patrick

Debugger/Reverse Engineer.
7 people found this helpful

Abuse history


progress