Critical Process Died / Kernel Data Inpage Error

DarrylJohn

Active Member
Hi all,

Not expecting too much help on AVForums for a PC related issue... however I've been getting BSODs on and off, out of nowhere beginning a week or two ago.

It's not software as I installed a new OS.

I've ran memtest, no issues. I've ran furmark no issues, I've ran prime95... no issues.

I can create this on demand... I've had no issues since Saturday Eve (I uninstalled an audio driver nvidia had in, on Sunday morning). Thought it was fixed...

Played Warzone for a few hours Sunday, and monday evening and had no issues.

Today I installed Outlook (and as it's downloading data from the exchange) and having chrome open... The PC stopped functioning and locked. On the first BSOD, it said... Kernel Data Inpage Error & on the second it said Critical Process Died.

So that suggests to me it's the RAM... However, memtest came back fine? Puzzling. I'll try and just put one stick in and see if anything happens with that. I've never had RAM fail on me though that's part of a kit, so it's unusual.

Overview logs as below:

On Tue 06/10/2020 10:50:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100620-6609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xEF (0xFFFFC4885C3AD140, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 06/10/2020 10:50:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntdll.sys (ntdll!RtlLookupFunctionEntry+0x82)
Bugcheck code: 0xEF (0xFFFFC4885C3AD140, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED



On Tue 06/10/2020 10:40:11 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100620-6375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000000E, 0xFFFF8709CD9AC6F0, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 03/10/2020 21:54:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100320-13203-01.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF8004592E680)
Bugcheck code: 0x7A (0xFFFFB10BE99A1AF0, 0xFFFFFFFFC000000E, 0xA000003CC7DB121, 0xFFFFF8004592E680)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 03/10/2020 21:22:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100320-19234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xEF (0xFFFFAD83407C20C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 03/10/2020 21:08:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100320-5078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x154 (0xFFFFDE8EAC8C6000, 0xFFFFD08FAC1C5F30, 0x2, 0x0)
Error: UNEXPECTED_STORE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the store component caught an unexpected exception.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 

ShanePJ

Well-known Member
AVForums Sponsor
Although I cannot tell you what the fault is, I can tell you I have experienced a memory issue which took a few days to resolve and was a little random with different things failing (i'm presuming it was one block within the memory stick being accessed causing the issue).

After swapping many items within my Dad's PC, In the end I removed one of the paired of memory banks and it didn't miss a beat (lucky guess taking the right one out). I then replaced both banks with new memory and it worked for many years afterwards, but like I say, it was random with different issues
 

Monster900

Active Member
You don't say what hard drive you have but I had this sort of trouble when I was running my Samsung SSD in 'Rapid Mode'. Apparently it's not supported in Widows 10. I turned off 'Rapid Mode' in Samsung Magician and it fixed the problem.
 

The latest video from AVForums

Podcast: LG C1 OLED + JBL Synthesis SDR-35 First Thoughts, plus TV Show & Disc Reviews & more
Subscribe to our YouTube channel
Support AVForums with Patreon

Top Bottom