Kernel Data Inpage Error & Critical Process Died BSOD ... I'm stuck :(

Toggle sidebar Toggle sidebar
K

KiefBC

Reputable
Sep 13, 2014
5
0
4,520
When does this happen? Randomly. I went 2 days without seeing it, and then i saw it 5x in one day. I have reinstalled Windows 8.1 and I have refreshed my Installation. I have run all diagnostics through Alien Autotopsy, The Alienware RAM/Graphics/etc stress-test on failure bootings, AND used Glary Ultilities 2015 to check my registry, hdd, ssd, etc. None of the tests show any errors.
Can anyone please help me?



  • KERNEL_DATA_INPAGE_ERROR 0x0000007a

    CRITICAL_PROCESS_DIED 0x000000ef

    KERNEL_DATA_INPAGE_ERROR 0x0000007a

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

091014-6687-01.dmp 2014-09-10 10:59:35 PM KERNEL_DATA_INPAGE_ERROR 0x0000007a fffff6e8`00124a30 ffffffff`c00000c0 00000001`4a9acbe0 ffffd000`24946000 ntoskrnl.exe ntoskrnl.exe+153fa0 x64 ntoskrnl.exe+153fa0 C:\Windows\Minidump\091014-6687-01.dmp 8 15 9600 284,912 2014-09-10 11:03:15 PM

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

091114-7843-01.dmp 2014-09-10 11:56:32 PM CRITICAL_PROCESS_DIED 0x000000ef ffffe001`17b00080 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+153fa0 x64 ntoskrnl.exe+153fa0 C:\Windows\Minidump\091114-7843-01.dmp 8 15 9600 284,912 2014-09-11 12:00:08 AM

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

091114-6296-01.dmp 2014-09-11 8:51:51 PM KERNEL_DATA_INPAGE_ERROR 0x0000007a fffff6fc`00d71dd8 ffffffff`c00000c0 00000001`45384860 fffff801`ae3bb460 srv.sys srv.sys+77460 x64 ntoskrnl.exe+153fa0 C:\Windows\Minidump\091114-6296-01.dmp 8 15 9600 284,912 2014-09-11 8:58:29 PM
Click to expand...

Specs of PC:


  • Alienware X51 R2
    Intel i7 4790
    8GB RAM
    AMD R9 270X 2GB
    Crucial 256GB SSD
    Seagate 1TB HDD
 
Solution
K
An answer/update for everyone.

Got my PC looked @, and it was my RAM. I removed my 1 stick of 4GB RAM and bought a 8GB RAM (Why did Dell not pay for this? Their PC came DOA... and their support is fucking awful and useless). The BSODs seemed to cease.

After toying around, and everything else. I have noticed one thing, I can leave my computer on (After i fixed the RAM) idling forever, it will not crash. I can play SMITE for 2 hours, it won't crash. I play Wasteland 2 for more than 40min, it crashes, and boots, and crashes, and boots, and crashes, till it finally takes me to "Recovery" i click restart, i get the hard-drive is not in the hot-seat, and then i turn off my PC, let it stay powered off for ~45seconds, turn it back on and it...
Sort by date Sort by votes
K

KiefBC

Reputable
Sep 13, 2014
5
0
4,520


I have LITERALLY replied to you 10x and everytime i do. My computer crashes. So here it is in a simple form, as im not writing it all out again.

Uninstall any recent updates to drivers, windows and BIOS
- I have formatted my C: SSD and re-installed winsows 8.1

Update windows if there are pending updates
- No updates available

Update drivers
- Dell System Analysis, AlienAutotopsy, Driver Revive, and mroe all say they are up-to-date

Update BIOS
- Tried and says its on the current firmware

Check for viruses
- Ran ESET, Malwarebytes, and a few more, nothing comes up

A few more crashes now, i couldn't get a Dump of my one prior to this srv.sys since when it crashed.. i guess it deleted it. The other one was "SpacePort.sys" and was also a KERNEL_DATA_INPAGE_ERROR.

================================================== Dump File : 091514-7281-01.dmp Crash Time : 2014-09-15 10:39:02 AM Bug Check String : KERNEL_DATA_INPAGE_ERROR Bug Check Code : 0x0000007a Parameter 1 : fffff6fc`0057b620 Parameter 2 : ffffffff`c00000c0 Parameter 3 : 00000001`380c3860 Parameter 4 : fffff800`af6c4e38 Caused By Driver : srv.sys Caused By Address : srv.sys+52e38 File Description : Product Name : Company : File Version : Processor : x64 Crash Address : ntoskrnl.exe+153ca0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\091514-7281-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 9600 Dump File Size : 284,912 Dump File Time : 2014-09-15 10:45:52 AM ==================================================

 
Upvote 0 Downvote
K

KiefBC

Reputable
Sep 13, 2014
5
0
4,520


I'm not able to roll back as when i created my last system restore point, it overwrote my past one, so my restore point just brings me back to the beginning of the problem.

I'm going to try installing Windows 7 instead of 8 and see if this fixes the problem.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
A kernel in page error means a driver tried to read data from storage into memory and that read failed for some reason.

check your physical connections from your sata port to your hard drive, make sure the drive is spinning and the data connection is good, or move your sata port to another port in case the port failed. bad cable connections can make and break connections many times a second.
It is best to put your port on the primary sata controller not a secondary controller if you have one.

if your drive is older, you may find it useful to turn off virtual memory reboot, rename the pagefile.sys to pagefile.old
then turn on the virutal memory again and reboot.
after the new pagefile is created, delete pagefile.old

you might also go into BIOS and see if there is a setting for you sata controller that enables hot swapping. if the drive gets disconnected for some reason
it will autoreconnect and prevent kernel inpage bugchecks.

 
Upvote 0 Downvote
K

KiefBC

Reputable
Sep 13, 2014
5
0
4,520


I'm not very knowledgable on the inside components of a PC. Would you happen to have any links on this? As if its that, i most likely can fix it, just don't want to wreck it! :)

My drive is pretty much brand new. This computer is not even 3 months old.

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
You may also want to uninstall Glary Ultilities 2015. I think I just looked at a system that was running it that was corrupted memory because of a driver bug. (remove it and make sure it was not the cause of your problem.)

-----
sorry, you should maybe google a video on how to install a hard drive. You will basically open your case, find your hard drive and there will be two connectors going to it. You will want to unplug the connector and replug it back in or just push one the end of each one to make sure it is seated fully.
--------
The other potential problem is that on a new spinning drive it takes time to do a full format of the drive before windows is installed. A lot of people installing save hours of waiting for a full format to complete and just do a quick format that only takes a few seconds. Problem is the full format will locate and mark sectors with intermittent read/write errors as bad sectors. (normal for a large drive) But the quick format skips this. Later if your operating system drivers are installed on these sectors when the driver attempts to load you get a error. The system will try several times but if it can not copy without a error it will generate a kernel inpage bugcheck. Windows 8 will repair the system over time if it can, windows 7 you have to do the repair.



 
Upvote 0 Downvote
K

KiefBC

Reputable
Sep 13, 2014
5
0
4,520
An answer/update for everyone.

Got my PC looked @, and it was my RAM. I removed my 1 stick of 4GB RAM and bought a 8GB RAM (Why did Dell not pay for this? Their PC came DOA... and their support is fucking awful and useless). The BSODs seemed to cease.

After toying around, and everything else. I have noticed one thing, I can leave my computer on (After i fixed the RAM) idling forever, it will not crash. I can play SMITE for 2 hours, it won't crash. I play Wasteland 2 for more than 40min, it crashes, and boots, and crashes, and boots, and crashes, till it finally takes me to "Recovery" i click restart, i get the hard-drive is not in the hot-seat, and then i turn off my PC, let it stay powered off for ~45seconds, turn it back on and it boots normally in ~5seconds.

I got one error code, and its dump file. All BSODs since my RAM fix have had the same code "ntoskrnl.exe+153ca0"

==================================================
Dump File : 092114-7765-01.dmp
Crash Time : 2014-09-21 12:44:34 PM
Bug Check String :
Bug Check Code : 0xc000021a
Parameter 1 : ffffc000`8e5ba3f0
Parameter 2 : ffffffff`c0000006
Parameter 3 : 00007ffd`32a874ec
Parameter 4 : 00000022`8be0e6c0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153ca0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+153ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092114-7765-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 284,912
Dump File Time : 2014-09-21 12:51:14 PM
==================================================

EDIT: The BSODs happen regardless of whats running. Now the BSODs aren't even readible. The screen is blue and has a static appearence, making it unreadable. Think of Screen-Tearing, but with pixels instead of actual screen tearing.

Here is another DUMP, this time, it is from "Critical Process Died". This occurred when i did a Clean Boot (via Microsoft's Website). I haven't gotten this since i fixed my RAM issue.


Here is a collection of dump files from the various dumps i have gotten.

https://drive.google.com/file/d/0B76df2GHcYRFbENBbXduZzlLZ00/edit?usp=sharing
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom