Kernel data inpage error

[annihilator2k7]

I'll start off by saying that any attempt I've made at changing settings in order for the BSoD to give me a minidump has been a failure. Any time the BSoD comes up, the error report gets stuck at 0% indefinitely.

This error has been popping up daily for a little over a week now, right after I upgraded my GPU, CPU, and CPU fan. The error does not appear to have any triggers as it happens either when the PC is under load or when it is idle with no programs open. I've monitored temps to make sure the CPU fan was correctly installed and the CPU never goes beyond 40C.

I've run Chkdsk which resulted in no errors.
I've run windows memory diagnostics which resulted no errors.
I've run sfc /scannow which found an errors that it could not automatically fix. I do not know how to find the error in the log file.

 

[softwaremaniac]

Give this a try. The file was created by kronckew, one of our colleagues. Tested it on my Laptop, and it worked!

Boot to Safe Mode.

Go to Start > All Programs > Accessories > Command Prompt
Right-click the Command Prompt, and select: Run as Administrator

At the Command Prompt, copy/paste (with the mouse) the following text inside the code box below, and press: Enter

@echo off
rem delete old files
del /q %windir%\logs\cbs\cbs.log
del /q c:\sfcdetails.txt
rem run sfc
sfc /scannow
rem filter out non essential junk from the cbs.log
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >c:\sfcdetails.txt 
rem open details in notepad
notepad c:\sfcdetails.txt
rem optional command to shut down & restart pc after running. this may be needed if
rem sfc replaces some critical files. uncomment (remove the 'rem') to activate.
rem shutdown -r
exit

When sfc is done, a file named sfcdetails.txt appears.
Please save the sfcdetails.txt file to the Desktop, and post it in your reply.

To run the program a second time, open the Command Prompt, right-click and select: Run as Administrator

This time, type in the following:

Code:
sfc /scannow
Press: Enter

When done, a file named sfcdetails.txt appears once again.

Please save the file to the Desktop, as sfcdetails2.txt, and post it in your reply.

 

[annihilator2k7]

Well it looks like faulty hardware to me, which is what I assumed it was. I was just hoping this wasn't the case, will wait for confirmation though.

Basically what happened was I accidentally bent some pins in the CPU when trying to install it, I successfully bent them back into place and it worked. I never expected it to last long though, so if this is the issue I won't be surprised.

 

[softwaremaniac]

It could be, but let's try this first: GUIDE: CNBJ2530.DPB and prncacla.inf Corruptions - Windows 8/8.1 - Sysnative Forums

 

[annihilator2k7]

The errors from sfc /scannow have been fixed. I'll post back at a later date if the blue screens stop.

 

[annihilator2k7]

The blue screens have not stopped. The error is always the same and it never attempts to create an error report. I noticed that just before it came up, I could not connect to websites. After closing chrome, I could not reopen it, and then the blue screen appeared.

 

[softwaremaniac]

Post a new zip file from the SF Tool.

 

[annihilator2k7]

Here is the updated SF file.

 

[softwaremaniac]

There are no minidumps included...

 

[annihilator2k7]

I stated in my first and fourth post that the blue screen is not allowing me to create minidump files. I've tried multiple different settings in order to create them but it always sits at 0% and never creates one.

 

[Mysers Briggs]

Can you take a screenshot of the blue screen? (if you are unable to get the dump files).

The exception stop error should give us a big indication to the cause.

 

[annihilator2k7]

Is there a way to change the settings of blue screens for them to show more information? As of now, the only thing it says is that it crashed, needs to restart, is "collecting data" which stays at 0%, and kernel_data_inpage_error. There is nothing else on the blue screen that gives any more information about the error.

 

[softwaremaniac]

Check your Windows folder for MEMORY.DMP file and upload it somewhere and post a link here.

 

[Mysers Briggs]

Are there any stop error codes?

View attachment 56681

The third parameter is the big clue as to the cause, if there are no dump files available.

 

[annihilator2k7]

Check your Windows folder for MEMORY.DMP file and upload it somewhere and post a link here.

For the fourth time, the blue screen is not creating a dump file. I've tried using settings for both complete memory dump as well as small memory dump (256 kb). Neither of these settings work and the blue screen sits at 0% for creating them.

Are there any stop error codes?

The third parameter is the big clue as to the cause, if there are no dump files available.

The only piece of information even remotely useful from the blue screens is the Kernel_Data_inpage_error message. Windows 8 blue screens are very uninformative. There are no stop error codes.

 

[Mysers Briggs]

That doesn't really help us then.

Given the dump files aren't being created, or even written to disk then I'm almost certain you have a failing drive.
I can suggest running SeaTools DOS to see if it finds an error.

You'll need to mount it to a USB or CD, then change your storage controller to IDE/SATA in the BIOS (If it isn't already set), run the short and long generic tests on your drives.
Then change the controller back to the original setting to boot into Windows.

Ah, my bad... I forgot there aren't stop codes on the bugcheck screen in Windows 8/8.1.

 

[annihilator2k7]

I have not had an error since my last post until just now where it said: Kernel_data_inpage_error (spaceport.sys)

The new info here is the spaceport.sys part.

I have yet to run the tests for SeaTools because I have not gotten around to finding a blank CD/USB, I cannot find a way to access BIOS (I've tried) and I did not receive any errors since then.

 

[annihilator2k7]

As a recap, since the issue is persisting. I was going to make a new thread since it's been a while but decided against it.
I have been experiencing random and somewhat infrequent crashes. Most of the time it occurs when I go to open Google Chrome. It also occurs when playing graphics intensive games for more than 30 minutes. The only source of information I have been able to acquire from the blue screens is the spaceport.sys file. This is pointed to about half the time.

I am using Windows 8.1, so the error screen provides little to no information.
-The BSOD freezes after it pops up, I have tried leaving it on the blue screen for over an hour and it does not even attempt to create a dump file. I have tried every setting for creating dump files and it always freezes. I cannot create dump files. Please do not ask me to do that.
-I have used memtest to scan memory and found no errors, I even replaced the memory and scanned again for no errors.
-I used seatools to check my hard drive and it resulted in no errors.
-I have run Chkdsk which resulted in no errors.
-I have run windows memory diagnostics which resulted in no errors.
-I have run /sfc scannow, fixed the errors it pointed to and it did not fix the BSODs

I noticed the errors first occurring after I replaced the CPU and GPU in December 2014. If it has something to do with either of those I would have to guess it was the CPU because I messed up on the installation process and bent the pins, I managed to unbend them and put it in and it has worked since then.

 

[usasma]

Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

Do you still need help with this problem?
I will be notified if you reply to this topic and will respond within 48 hours.

 

[annihilator2k7]

Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

Do you still need help with this problem?
I will be notified if you reply to this topic and will respond within 48 hours.

Thank you for the response! Yes I do still need help. I have not had a BSOD since my last post, but I'm sure that doesn't mean the issue fixed itself. I can be fairly patient between responses since the issue is so infrequent, I usually don't even think about it until it actually happens.