[SOLVED] KERNEL_DATA_INPAGE_ERROR Caused By Driver: ntoskrnl.exe - Windows 8.1 x64

[velozity]

My PC Specs:

Operating System:
Windows 8.1 64-bit

CPU:
Intel Core i3 3227U @ 1.90GHz 50 °C
Ivy Bridge 22nm Technology

RAM:
4.00GB Single-Channel DDR3 @ 798MHz

Motherboard:
Acer Aspire Z3-605 (SOCKET 0) 28 °C

Graphics:
AIO LCD (1920x1080@60Hz)
Intel HD Graphics 4000 (Acer Incorporated [ALI])
1024MB ATI AMD Radeon HD 8670A (Acer

The Error Dump:

==================================================
Dump File : 012015-28390-01.dmp
Crash Time : 20/01/2015 4:21:08 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000000
Parameter 3 : ffffe001`462185f0
Parameter 4 : 00007fff`5a827240
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1509a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1509a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\012015-28390-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 157,799
Dump File Time : 20/01/2015 4:21:59 PM
==================================================

 

[Jared]

Can you please provide the information required by following these instructions.

https://www.sysnative.com/forums/bs...ons-windows-10-8-1-8-7-and-windows-vista.html

 

[cluberti]

This is an inpage error crash with the first param as a 4 - that means it's a bum PTE (with an error status of 0x0, so even worse) and unless there's a kernel dump to go with this, a minidump is already going to be useless in determining root cause (even a kernel dump might be a wild goose chase, to be fair, given the bugcheck and params). Just fyi, I'd recommend before anything else doing a physical RAM test to make sure this isn't a physical memory problem to start, just to be safe.

https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-with-memtest86.html