KERNAL_DATA_INPAGE_ERROR 0x7a while playing certain games, no dumps cr

Can you upload the screenshot directly to this site please. Screenshots and Files - Upload and Post in Seven Forums

I won't be able to glean anything from a screenshot but the STOP code may have a bearing on why the dumps aren't being recorded.

A 0x7A could be one of many things but it does include a corrupt page file as a possibility. Can you perform the following steps just in case, be aware that this is guesswork on my part though.

Check the cabling between your motherboard and HDD/SSD. Ensure connections are all fully seated correctly, try different cables if you have any spare.

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Run chkdsk. Disk Check

Open an elevated command prompt and type in or copy and paste sfc /scannow and hit enter.

Post back with the results.

A standard stop 0x7A crash dump shows .....

Code:

KERNEL_DATA_INPAGE_ERROR  (7a)
 The requested page of kernel data could not be read in.   Typically caused by
 a bad block in the paging file or disk controller error. Also see
 KERNEL_STACK_INPAGE_ERROR.
 If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
 it means the disk subsystem has experienced a failure.
 If the error status is 0xC000009A, then it means the request failed  because
 a filesystem failed to make forward progress.
 Arguments:
 Arg1: 8dd047f8, lock type that was held (value 1,2,3, or PTE address)
 Arg2: c0000056, error status (normally i/o status code)
 Arg3: 2d113864, current process (virtual address for lock type 3, or  PTE)
 Arg4: 902f90ba, virtual address that could not be in-paged (or PTE  contents if arg1 is a PTE address)

So here what we need in the crash dump is the second parameter, Arg2. In this case it is 0xC0000185 as per the screenshot. So it is a disc subsystem related BSOD.

The explanation of the error status (in absence of the crash dump) is:

Attachment 360902

So it is reporting a disc error.

May be it is the reason behind not recording the crash dump.

I would suggest Dakotaa to test the HDD using Data Lifeguard Diagnostic for Windows. Take both the short test and the extended test. Let us know the results.

MS have updated their advice on the SFC issue.
It seems that this is an error in the 'logic' rather than an actual problem.
There is no point in attempting to correct the apparent errors, since they will reappear as soon as another diagnostic is run (possibly without user intervention!).

Therefore, as far as these errors are concerned the current options are

• ignore the errors, and wait for MS to release the promised update to correct the SFC detections

• uninstall KB3022345 and hide the offered update until its either updated or replaced.

Take your pick!

There are no other errors in the SFC scan that need attention.

In your case, I would advise uninstalling the update and hiding it - it seems that it can increase instability in some systems.

Dakotaa said:

Results from the Data Lifeguard tests.

Nice.

Now do the first one of post #23.

Boozad said:

Check the cabling between your motherboard and HDD/SSD. Ensure connections are all fully seated correctly, try different cables if you have any spare.

If possible, get a new SATA cable, and try different unused SATA ports on the motherboard.