BSOD Stop: *0x7A *NTFS.sys KERNEL_DATA_INPAGE_ERROR

[front360]

Anybody wishing to help,

Once a week I'm getting BSOD's with KERNEL_DATA_INPAGE_ERROR, Stop Code: 0x0000007A, NTFS.sys at idle and while gaming. Physical memory dump usually FAILED with status 0xC0000010, except maybe twice dmp was created.

I believe they may be from a failing HDD. In Event Viewer I've been seeing, 'The device, \Device\Ide\iaStor0, did not respond within the timeout period' and Kernel errors. I keep running CHKDSK(/f, /r and even /b) which has found errors of different types and fixes them each time. For example, correcting errors in volume bitmap, deleting corrupt attributes, and read failure with Windows replacing bad clusters. I know there are 4 KB in bad sectors.
SeaTools for DOS also repaired clusters(or sectors, I forgot which) just the other day.

I was wondering what else I can try, to diagnose the bsod stop code? I already ran memtest86 for two hours without error.

If you need any other info, just ask. Thanks in advance.
Don

 

[front360]

Any ides?

 

[front360]

2 views of upload files so far, but still no help yet.

HELLO??

 

[front360]

Do you need any more info?

 

[front360]

Should I In-Place Upgrade?

I just received another BSOD while gaming with The Sims 3. The Stop Code was 0x0F4. I seem to be getting the 0x0F4 Stop code now instead of the 0x07A. What can I try, I really need help please?

Thanks,
Don

 

[front360]

Please view my BSOD data...

 

[cluberti]

After taking a look, these are indeed inpage errors (moving data from disk to memory), so your suspicions about disk could be spot on. I'd suggest testing your RAM for errors to be safe, but if the memory checks out OK you really could be looking at a bad disk.

 

[front360]

Thanks for helping me try to diagnose my errors.

 

[Axel49]

I have ran into the exactly same problem as you told, involving the ntfs.sys pointout.

The diagnosis blue screen is the same including error codes, however, I am not running gaming software.

I have had problems with STOP 0x7A several times and one time appearing 0xF4. However, this time (today) is the very first time the ntfs.sys is being shown up.

I have made a preliminary diagnosis of the earlier appearances of these STOP conditions and blue screen, mostly without any Kernel dump (HDD inaccessible).

My preliminary diagnosis was that a mail file (a Microsoft .pst file, managed by the Office Outlook 2010). This is because these mail files were flagged as being eligible for indexing by the builtin "Windows Search" service, which is designed to index even Microsoft mail files. It seemed to me that stopping this service can cause these STOP errors with blue screen to disappear.
This was my primary issue in trying to solve the matter. After this test I found that obviously one of my mail files was defective, caused by a COPY operation over the network, one or more file blocks were dropped and seemed to have been replaced by binary zeroes or some corresponding internal code. I have not inspected the binary content of the file, but the Outlook has tried to repair it and failed, I cannot sort the content by columns and it is clear that the file is defective.

So I unflagged the critical file from being indexed and have alloved the "Windows Search" service to run again, But again, today I got this harmful STOP 0x7A again with the ntfs.sys file pointed out as the cause.

Maybe, I still have some defective file in computer - I do not know and if the defect is logical (i e, one file holds information pointing out another file for example) it would not be detectable by general HDD and file checkout software and therefore it is hard to locate the malicious file.

So my conclusion is that if you see these STOP 0x7A errors and possibly the STOP 0xF4 error so you can try to disable the "Windows Search" service. Due to its purpose and its transparent indexing of all local files in the computer it seems to be a sensitive component to possibly defective files in the computer.

Then allow the computer to run with the "Windows Search" in disabled state. If you are happy, you will not see these STOP errors again - and if needed, you can look for some tool to locate the defective file(s) causing the STOP error condition. But if they are left untouched they will not disturb you.

Not a full solution, but a small step on the way, possibly helpful.

 

[front360]

Thanks, I will look into Windows Search and Indexing.