New
#1
BSOD during normal use, error 0x7a (kernel data inpage error)
I'm getting BSOD during normal use (whether it be web browsing or during a game). Memtest86 got 0 errors in 4 passes. CrystalDiskInfo and SSDlife both say that my drives are "healthy." CPU temps tend to hover between 40-60 degrees Celsius.
I've attached the dump files as the forum rules stated. Since this could be a drivers issue, I included a drivers list as well.
Here are some dump analysis from WhoCrashed.
On Sun 10/23/2016 3:15:28 AM your computer crashed
crash dump file: C:\Windows\Minidump\102316-8954-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1447A0)
Bugcheck code: 0x7A (0xFFFFF8A0014D6A68, 0xFFFFFFFFC000000E, 0x1DF503860, 0xFFFFF960001747A0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 10/23/2016 3:15:28 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1447A0)
Bugcheck code: 0x7A (0xFFFFF8A0014D6A68, 0xFFFFFFFFC000000E, 0x1DF503860, 0xFFFFF960001747A0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 10/20/2016 5:18:16 PM your computer crashed
crash dump file: C:\Windows\Minidump\102016-9594-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0x7A (0xFFFFF6FC8060FCC8, 0xFFFFFFFFC000000E, 0x17A1B1880, 0xFFFFF900C1F99008)
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 10/19/2016 5:51:43 PM your computer crashed
crash dump file: C:\Windows\Minidump\101916-9859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0x7A (0xFFFFF6FB40000800, 0xFFFFFFFFC000000E, 0xA1C08884, 0xFFFFF68000100000)
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 Tue 10/18/2016 1:31:55 AM your computer crashed
crash dump file: C:\Windows\Minidump\101816-9469-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0x7A (0xFFFFF6FC5000F3C0, 0xFFFFFFFFC000000E, 0x16301F880, 0xFFFFF8A001E78134)
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.