Kernel Data Inpage Error & Critical Process Died - Windows 8.1 Pro

Toggle sidebar Toggle sidebar
D

DrShloickerstein

Reputable
Apr 13, 2014
26
0
4,530
I have had several blue screens of CRITICAL_PROCESS_DIED and one instance of KERNEL_DATA_INPAGE_ERROR now, and I'm pretty stuck on what to do about it, although I haven't tried reinstalling windows yet and I would try to avoid that if at all possible :)
I think it has something to do with my SSD; I just ran this seagate test thing (http://www.seagate.com/support/downloads/item/seatools-win-master/) and my SSD failed the short and long generic test while my other drives were fine...

Specs:
i7 4770k
GTX 770 2gb
MSI Z87-G45 Gaming Motherboard
Vertex 3 SSD 250gb
Western Digital Caviar Blue 500gb HDD, and Black 1tb
Windows 8.1 Pro

I tend to have crashes if I start opening programs as soon as I boot to desktop, and it also becomes unresponsive sometimes when I play games on the SSD, which makes me think it's the SSD. It it on the way out?? Thanks in advance
 
Sort by date Sort by votes
D

DrShloickerstein

Reputable
Apr 13, 2014
26
0
4,530
Sorry for the long reply. I can't see any code; where would I find it? I found a log but all it seems to show is the times I started the test and when it failed. I gets to 77% on the outer scan I think (always 77%) if that helps.
I did have a problem with windows updates where it constantly told me that if failed to configure, but I seemed to make that go away but still after I get one of these two blue screen errors it will say failed to configure updates when I boot up again.

PS: Um I just had a look at Windows Update and there were just 12 important updates out of nowhere, so I tried installing five of them (I've heard that you shouldn't install too many at a time) and restarted but on restart it again 'failed to configure updates.' What is going on??
 
Upvote 0 Downvote
SuperSoph_WD

SuperSoph_WD

Glorious
Jul 30, 2014
6,758
3
45,960
Hey there, DrShloickerstein!

Sorry to hear about your issues with the system! :(
If you suspect any of the drives as the source of the issue, I'd recommend you to use their brand-specific diagnostic tools. Usually those that work with HDDs are not really designed to give accurate results for SSDs as well.
For your WD drive, I'd suggest you to download Data LifeGuard Diagnostics tool here: http://products.wdc.com/support/kb.ashx?id=jOub4M
Make sure you run the QUICK and EXTENDED test from the utility, so that you get detailed results about the health and SMART status of the hard drive.
For the SSD, I'd recommend you to check this thread with some third-party suggestions on the specific testing tools: http://www.tomshardware.co.uk/answers/id-1926483/ssd-diagnostic-tools.html

Good luck! Keep me posted with the results! :)
SuperSoph_WD
 
Upvote 0 Downvote
D

DrShloickerstein

Reputable
Apr 13, 2014
26
0
4,530
Well I ran that Data LifeGuard Diagnostics tool on my D drive (500gb) and it passed on both the short and long tests, but I haven't got round to testing the terabyte drive yet. I looked at my SSD on both programs on that forum and they both said it was perfectly fine, but I didn't have to run any tests from what I could see. Did I do something wrong?
 
Upvote 0 Downvote
SuperSoph_WD

SuperSoph_WD

Glorious
Jul 30, 2014
6,758
3
45,960

I'm glad to hear there's nothing wrong with the storage devices! No, I don't think you did anything wrong whatsoever. The SSD diagnostic tools usually just collect the comprehensive data about the SSD's health and lifespan. There are no moving parts in the solid-state, that's why the diagnostics do not require extensive testing as it does with the hard drives.
However, if there is nothing wrong with the drives, I'd suggest you to use the Windows Repair options to fix the these BSOD errors or at least try to see the error code and post it here. It might help us determine if it's a hardware-related issue and which component is the source.

Keep me posted! :)
SuperSoph_WD
 
Upvote 0 Downvote
D

DrShloickerstein

Reputable
Apr 13, 2014
26
0
4,530
Sorry what repair options do you mean exactly? I'll make sure to record the error messages on future blue screens. You're probably already aware of this but I forgot to say; in the blue screen it says that it is collecting error data and that I should wait for it to complete but so far it's never got beyond 0% and I've had to force my PC to shut down. Would you recommend that I leave it for longer and give it more chance to collect data?
 
Upvote 0 Downvote
SuperSoph_WD

SuperSoph_WD

Glorious
Jul 30, 2014
6,758
3
45,960


The Windows Installation disk has the option to Recover the OS from a serious error. It has these System recovery options that will get to several repair tools/features. Here's a tutorial from MS that might shed some light: http://www.eightforums.com/tutorials/2269-system-recovery-options-boot-windows-8-a.html

I would even try a clean install on the SSD, if you don't have any essential data on it. However, I'm not certain that this will fix the problem, especially if the issue is hardware-related. Have you tested any of the other components?
Like memtest on the RAM? GPU, CPU temps?
Here are some threads:
How to test the GPU: http://www.tomshardware.co.uk/answers/id-2189736/test-graphic-card-working-fine.html
How to test the memory: http://www.tomshardware.co.uk/faq/id-1906201/test-memory-memtest.html
Motherboard or CPU: http://www.tomshardware.co.uk/forum/289442-30-motherboard

Keep me posted.
SuperSoph_WD
 
Upvote 0 Downvote
D

DrShloickerstein

Reputable
Apr 13, 2014
26
0
4,530
Well I did the startup repair and it said that it couldn't fix it, but I got a log file (srttrail):

tartup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎27/‎05/‎2015 09:00:41 (GMT)
Number of repair attempts: 2

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = F:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot status indicates that the OS booted successfully.

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = F:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 63 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot status indicates that the OS booted successfully.

---------------------------
---------------------------
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom