BSOD after idling, Bugcheck code: 0x7A Error: KERNEL_DATA_INPAGE_ERROR

[migoreng]

Scenario: Came back to the computer after about 3 hours of idling and tried to go onto the internet via google chrome, at this point the PC locked up and crashed with giving a BSOD. Whocrashed showed the following error. Please note I have added chkdsk logs as well.

Any help would be greatly appreciated. Thanks

BSOD:
On Wed 22/08/2018 11:51:53 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082218-62696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x7A (0xFFFFF6FB40000430, 0xFFFFFFFFC000000E, 0x20018E1E7880, 0xFFFFF68000086000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 22/08/2018 11:51:53 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!MmUnlockPages+0xE9E)
Bugcheck code: 0x7A (0xFFFFF6FB40000430, 0xFFFFFFFFC000000E, 0x20018E1E7880, 0xFFFFF68000086000)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Snick]

Hi migoreng,
Welcome to SevenForums!
I couldn't open the second dmp in your submission. Weird!
Are your drivers up to date?
Is Windows Update current?
Have you scanned for viruses? Malwarebytes free
Have you run a RAM test?
Click rb:, type mdsched.exe in the Search box, and select it. Reboot now! It needs to run for several passes, let the tool complete.

Check the Event Viewer to find the results of the memory tests. To do this, you can perform the following:

[FONT=&quot]1. Click [/FONT]rb:
[FONT=&quot]2.In Searchbox type: Event Viewer[/FONT]
[FONT=&quot]3.[/FONT][FONT=&quot]Under Administrative Tools, click on View event logs[/FONT]
[FONT=&quot]4. Locate and collapse the Windows Logs category[/FONT]
[FONT=&quot]5. Click on System
6. Locate items that is tagged MemoryDiagnostics-Results under the Source tab[/FONT]


Nic

 

[migoreng]

Hi Snick,
Thanks for replying and giving me some tips. I seem to have now encountered another type of BSOD error. I have attached my report and also see below.

I have done the following:
Drivers - I have updated them
Run Malwarebytes scan - scan came back good on c drive. when i tried to scan all drives it crashed.
Ram Test - Failed, I ran it for 8 passes and it failed on the first pass around 85%
memtest86 - Failed on the first pass at test 4 and test 7, So I stopped it

I swapped the RAM with another identical stick and re-tested it on the Ram test and it passed and i do not seem to get that original BSOD error anymore.

But now I am getting a new BSOD error. I should note that I have been running Speccy to keep an eye on my pc temps.

Temps:
CPU - 31-40 c depending on applications
MB - 34 c
Graphics card - 33-40's depending on applications
Storage drives:
SSD 1 - 31-33 c
SSD 2 - 29c
HD - 29 c

NEW BSOD ERROR:
crash dump file: C:\Windows\Minidump\082918-21387-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800C22D6D0, 0xFFFFFA800C22D9B0, 0xFFFFF80003BA8540)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This bug check is typically caused by a thermal issue. It's suggested that you do temperature checking on your CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Thanks

 

[migoreng]

New attachment I think I forgot to upload with reply.

 

[Snick]

Not a problem. ntoskrnl.exe is a common error that appears in most dmps.
@axe0 is the expert on BSOD on SevenForums and is pretty busy, please PM axe0
I'm currently studying for BSOD!
Nic

 

[cwsink]

Hi migoreng,

Have you performed diagnostics on your drives? The system event log shows several instances of a drive controller error.

Event[51226]:
  Log Name: System
  Source: Disk
  Date: 2018-08-26T20:27:50.256
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ReceptionVRE-PC
  Description: 
The driver detected a controller error on \Device\Harddisk3\DR4

I'm not sure which drive that is but the some of the bugchecks suggest a problem reading from the pagefile. Do you have your pagefile on the HDD or multiple pagefiles, perhaps? I think you probably need to run hardware diagnostics to check the health of your drives based on what I've seen.