CRITICAL_PROCESS_DIED and KERNEL_DATA_INPAGE_ERROR BSOD

chokatochew

Reputable
Sep 16, 2014
1
0
4,510
So I bought this new computer last year, and it's still pretty good, but for the past few weeks, I had a problem with my PC. It started lagging after the boot, and it lags outrageously for around 5 minutes. Sometimes, the lag would result to a BSOD, which is CRITICAL_PROCESS_DIED or KERNEL_DATA_INPAGE_ERROR. My OS is Windows 8. What should I do? System Restore didn't work for me, it said that the volume was used by another program. Please help me! :(
 
Solution
Agreed. This sounds like a CPU problem. If the system is still under warrantee then take it back for a new CPU. You can either underclock the CPU or raise its voltage to get the system to boot again to verify if we are right.

JimF_35

Distinguished
Agreed. This sounds like a CPU problem. If the system is still under warrantee then take it back for a new CPU. You can either underclock the CPU or raise its voltage to get the system to boot again to verify if we are right.
 
Solution
overall, it sounds like you have a failing hard drive.

-ok, kernel inpage error indicates that a driver can not be loaded into memory because of a storage error
the other bugcheck is caused because a critical process exited most likely csrss.exe got a error when it needed storage (IO error) and had to exit, it is a required process so windows bugchecked.

your system 5 min lag on boot could also be a hard drive failing to seek and getting errors and lots of retries. (or a disk error accessing your pagefile.sys)

now if this is a desktop system, I would guess that your hard drive is failing.
if this is a laptop system, you have to check one other thing first and that is are you starting your system from sleep? or from a hibernation mode?

so, I would check the drive data cables and power cables. do a chksdk /r /f on the drive to repair any filesystem corruption. then run a cmd.exe as a admin and start the system file checker utility
sfc.exe /scannow to check for corrupted core system files.
(let me know if the command fails to fix a problem)

if these don't find a problem, you want to go to you control panel virtual memory settings, turn off the virtual memory, reboot. rename the pagefile.sys to pagefile.old, go back and turn on the virtual memory and reboot.

also, make sure there is plenty of space on you disk drive if you have certain types of driver bugs the pagefile.sys will grow in size until it gets to its max size and returns a error.

any chance your drive is a solid state drive?