BSOD during normal use, error 0x7a (kernel data inpage error)

[Soultxtx]

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.

 

[Soultxtx]

Haven't seen any replies or views on the files. Am I missing any files that you guys need?

 

[axe0]

Hi Soultxtx,

Welcome to the 7forums and apologies for the delay.

Are you still in need of help?

 

[Soultxtx]

Hi Axe0,

I would love to have some help. Since my last post, I've updated tons of different drivers and my BIOs. I'm not sure if I need to redo the dump file analysis that I had in my first post.

Could you take a look at the attached file on my initial post? I haven't had a BSOD since the updates but I can't tell for sure if I'm just lucky or it is actually fixed.

 

[axe0]

It's clear that your disk(s) is/are failing, but the attached zip does not contain enough information to tell which onces are failing. At least the disk with Windows installed on is causing issues.

Bugcheck code 0000007A
Arguments fffff8a0`014d6a68 ffffffff`c000000e 00000001`df503860 fffff960`001747a0
Debug session time: Sun Oct 23 11:15:28.695 2016 (UTC + 1:00)
System Uptime: 2 days 9:55:48.051

2: kd>  !thread fffffa800bd28830 e
GetPointerFromAddress: unable to read from fffff800032ff000
THREAD fffffa800bd28830  Cid 02a4.04f4  Teb: 000007fffffd3000 Win32Thread: fffff900c01da010 RUNNING on processor 2
IRP List:
    Unable to read nt!_IRP @ fffffa800e18f7c0
Not impersonating
GetUlongFromAddress: unable to read from fffff8000323dc18
Owning Process            fffffa800b9a1260       Image:         csrss.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      13368377     
Context Switch Count      45567425       IdealProcessor: 3                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x000007fefcb03740
Stack Init fffff880094dfc70 Current fffff880094df1a0
Base fffff880094e0000 Limit fffff880094d8000 Call 0
Priority 14 BasePriority 13 UnusualBoost 1 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           Call Site
fffff880`094df448 fffff800`03138212 nt!KeBugCheckEx
fffff880`094df450 fffff800`030ea54f nt! ?? ::FNODOBFM::`string'+0x3143a
fffff880`094df530 fffff800`030d0799 nt!MiIssueHardFault+0x28b
fffff880`094df600 fffff800`030c056e nt!MmAccessFault+0x1399
fffff880`094df760 fffff960`001747a0 nt!KiPageFault+0x16e (TrapFrame @ fffff880`094df760)
fffff880`094df8f8 fffff960`001a6977 win32k+0x1447a0
fffff880`094df900 fffff900`c08a1100 win32k+0x176977
fffff880`094df908 00000000`00000010 0xfffff900`c08a1100
fffff880`094df910 00000000`0000000d 0x10
fffff880`094df918 fffff900`c01eeec8 0xd
fffff880`094df920 fffff900`00000000 0xfffff900`c01eeec8
fffff880`094df928 00000000`00000000 0xfffff900`00000000

2: kd> .fnent fffff800`03138212
Debugger function entry 00000225`7a207d30 for:
(fffff800`03102750)   nt! ?? ::FNODOBFM::`string'+0x3143a   |  (fffff800`03102788)   nt!vDbgPrintExWithPrefixInternal

BeginAddress      = 00000000`000e4f9f
EndAddress        = 00000000`000e5921
UnwindInfoAddress = 00000000`001c82bc

Unwind info at fffff800`0321b2bc, 10 bytes
  version 1, flags 4, prolog 0, codes 0

Chained info:
BeginAddress      = 00000000`0009f190
EndAddress        = 00000000`0009fcd0
UnwindInfoAddress = 00000000`001c0970

Unwind info at fffff800`03213970, 18 bytes
  version 1, flags 0, prolog 22, codes a
  00: offs 22, unwind op 1, op info 0	UWOP_ALLOC_LARGE FrameOffset: 98.
  02: offs 1b, unwind op 0, op info f	UWOP_PUSH_NONVOL reg: r15.
  03: offs 19, unwind op 0, op info e	UWOP_PUSH_NONVOL reg: r14.
  04: offs 17, unwind op 0, op info d	UWOP_PUSH_NONVOL reg: r13.
  05: offs 15, unwind op 0, op info c	UWOP_PUSH_NONVOL reg: r12.
  06: offs 13, unwind op 0, op info 7	UWOP_PUSH_NONVOL reg: rdi.
  07: offs 12, unwind op 0, op info 6	UWOP_PUSH_NONVOL reg: rsi.
  08: offs 11, unwind op 0, op info 5	UWOP_PUSH_NONVOL reg: rbp.
  09: offs 10, unwind op 0, op info 3	UWOP_PUSH_NONVOL reg: rbx.
2: kd> ln nt+0009f190
Browse module
Set bu breakpoint

(fffff800`030f2190)   nt!MiWaitForInPageComplete   |  (fffff800`030f2cd0)   nt!MiIsFaultPteIntact
Exact matches:
    nt!MiWaitForInPageComplete (<no parameter info>)


// More 'complete' stack
fffff880`094df448 fffff800`03138212 nt!KeBugCheckEx
fffff880`094df450 fffff800`030ea54f nt!MiWaitForInPageComplete+0x3143a
fffff880`094df530 fffff800`030d0799 nt!MiIssueHardFault+0x28b
fffff880`094df600 fffff800`030c056e nt!MmAccessFault+0x1399
fffff880`094df760 fffff960`001747a0 nt!KiPageFault+0x16e (TrapFrame @ fffff880`094df760)
fffff880`094df8f8 fffff960`001a6977 win32k+0x1447a0
fffff880`094df900 fffff900`c08a1100 win32k+0x176977
fffff880`094df908 00000000`00000010 0xfffff900`c08a1100
fffff880`094df910 00000000`0000000d 0x10
fffff880`094df918 fffff900`c01eeec8 0xd
fffff880`094df920 fffff900`00000000 0xfffff900`c01eeec8
fffff880`094df928 00000000`00000000 0xfffff900`00000000

 

[Soultxtx]

Well that's disappointing. Wait so would it be the current boot drive (samsung 1TB ssd)? One of the slave drives inside also has windows installed on it but is not used as the boot drive (hitachi 1TB hdd).

What diagnostics can I run to determine the health of my drives? I've used crystaldiskinfo for my hdd's and ssdlife (free edition) for my ssd. Both tools show that I have "healthy" drives. I can't seem to get the SMART values for my ssd using the free edition however. Is there any other information that you may need?

 

[axe0]

As mentioned, I cannot tell with the current information.
I would need you to upload a msinfo32.nfo file:

Please search for "msinfo32" (without quotes) and press enter,

• save it as msinfo32.nfo,
• in explorer go to the directory where it is saved,
• right click the msinfo32.nfo file,
• choose 'send to' or 'copy to',
• choose 'compressed (zipped) folder',
• upload the zip file.

http://www.sevenforums.com/attachme...bsod-atikmpag-sys-ss-2016-03-26-12.49.51-.png​

 

[Soultxtx]

Attached is the msinfo32 file you wanted.

 

[axe0]

It looks like your system has more problems, like your partitioning being improper.

Diagnostics Test

 HDD TEST

   Note

Please run HDTune first, in the order posted!

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log :arrow: Check Disk (chkdsk) - Read Event Viewer Log

 

[Soultxtx]

In regards to the HDD Test and chkdsk tests, did you want me to do one for each of my slave drives or just the boot drive that I'm using currently (Samsung SSD)

Will get these test running in the meantime.

 

[axe0]

I would recommend to perform these tests on all drives that are connected.

It often occurs that not (only) the boot drive is having issues.

 

[Soultxtx]

I just got another I/O error and went into event viewer to see what was going on. I've included screenshots but I think it's for sure my Samsung SSD and the HDTune results. The error states that it's Disk 3 that's causing the problems and that corresponds to my Samsung SSD. I've looked through the other warnings and it seems that Disk 3 is the only one that comes up.

I'm still working through the other hard drives benchmarks and chkdsk.

 

[axe0]

What data is in the information tab of the events of 'Disk'?

 

[Soultxtx]

I'll copy paste the text in the 'general' and 'details' tabs from one of the events.

Event 51, Disk

General: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

Details:

- System
- Provider
[ Name] Disk
- EventID 51
[ Qualifiers] 32772
Level 3
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-11-06T03:11:26.903698500Z
EventRecordID 469414
Channel System
Computer AndrewT-PC
Security

- EventData

\Device\Harddisk3\DR3
040080000100000000000000330004802D0100000E0000C0000000000000000000000000000000003FD37E0300000000FFFFFFFF010000005800000800000000E9200A1282032040000002003C0000000000080000000000B842CE1280FAFFFF0000000000000000B038891480FAFFFF000000000000000068917F44000000002A00447F916800010000000000000000000000000000000000000000000000000000000000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00800004 00000001 00000000 80040033
0008: 0000012D C000000E 00000000 00000000
0010: 00000000 00000000 037ED33F 00000000
0018: FFFFFFFF 00000001 08000058 00000000
0020: 120A20E9 40200382 00020000 0000003C
0028: 00080000 00000000 12CE42B8 FFFFFA80
0030: 00000000 00000000 148938B0 FFFFFA80
0038: 00000000 00000000 447F9168 00000000
0040: 7F44002A 01006891 00000000 00000000
0048: 00000000 00000000 00000000 00000000
0050: 00000000 00000000


In Bytes

0000: 04 00 80 00 01 00 00 00 ..€.....
0008: 00 00 00 00 33 00 04 80 ....3..€
0010: 2D 01 00 00 0E 00 00 C0 -......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 3F D3 7E 03 00 00 00 00 ?Ó~.....
0030: FF FF FF FF 01 00 00 00 ÿÿÿÿ....
0038: 58 00 00 08 00 00 00 00 X.......
0040: E9 20 0A 12 82 03 20 40 é ..‚. @
0048: 00 00 02 00 3C 00 00 00 ....<...
0050: 00 00 08 00 00 00 00 00 ........
0058: B8 42 CE 12 80 FA FF FF ¸BÎ.€úÿÿ
0060: 00 00 00 00 00 00 00 00 ........
0068: B0 38 89 14 80 FA FF FF °8‰.€úÿÿ
0070: 00 00 00 00 00 00 00 00 ........
0078: 68 91 7F 44 00 00 00 00 h‘D....
0080: 2A 00 44 7F 91 68 00 01 *.D‘h..
0088: 00 00 00 00 00 00 00 00 ........
0090: 00 00 00 00 00 00 00 00 ........
0098: 00 00 00 00 00 00 00 00 ........
00a0: 00 00 00 00 00 00 00 00 ........

 

[Soultxtx]

Hi axe0, I just experienced another BSOD and figured it might be wise to upload another zip file using the forum's required dmp/information packager.

I had one additional BSOD right now and another one 1 day ago.

 

[axe0]

How's it going with the chkdsk and other tests?

 

[Soultxtx]

Sorry for the delay - haven't been home for much the past few days. Here are all the HD Tune screenshots you requested. I did chkdsk for all my drives but can't seem to locate the logs in event viewer.

 

[axe0]

For the boot drive it would be something like 'wininit' you need to search for, everything else should be 'chkdsk'.

 

[Soultxtx]

So I ended up redoing the chkdsk since my previous runs were nowhere to be found.

 

[axe0]

Looks good, let's see if Windows keeps complaining about paging problems.