Windows 7: Win 7 BSOD page fault in non page area

traindaddy17 · 18 Oct 2013

I have an ASUS Win 7 laptop. It keeps giving me a BSOD at any time. I have uploaded a zip file with hopefully helpful info.

YoYo155 · 18 Oct 2013

Welcome :) .

One bugcheck is not enough to establish a pattern, if you have some more please upload those as well.

We can see that by looking at the stack that something called win32k in order refresh a window
(redraw) but it hung for some reason and that Kaspersky (klif.sys) could have been involved
in some way or another not much info here.

Code:

Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
0xfffff880050aafb0 : 0xfffff960000e0000 : "win32k!DereferenceW32Process <PERF> (win32k+0x0)"
0xfffff880050ab028 : 0xfffff960000ffc0d : win32k!RGNOBJ::bCopy+0x5d
0xfffff880050ab068 : 0xfffff960003c8500 : win32k!gpvwplHungRedraw
0xfffff880050ab088 : 0xfffff800030c5cee : nt!KiPageFault+0x16e
0xfffff880050ab090 : 0x0000000000000008 :  Trap @ fffff880050ab090
0xfffff880050ab0f8 : 0xfffff960001ad1fb : win32k!xxxSendMessageToClient+0x1f7
0xfffff880050ab168 : 0xfffff960001acaa7 : win32k!xxxSendMessageTimeout+0x2b6
0xfffff880050ab1a8 : 0xfffff960001687b5 : win32k!DEVLOCKOBJ::bLock+0x411
0xfffff880050ab1b8 : 0xfffff960001a7f5b : win32k!XDCOBJ::RestoreAttributes+0x3b
0xfffff880050ab248 : 0xfffff960001ae249 : win32k!ClearHungFlag+0x41
0xfffff880050ab278 : 0xfffff960001261f1 : win32k!xxxBeginPaint+0x2ad
0xfffff880050ab2d8 : 0xfffff960001bf2ec : win32k!NtUserBeginPaint+0x8c
0xfffff880050ab378 : 0xfffff960001c27bd : win32k!NtUserGetProp+0x6d
0xfffff880050ab3a8 : 0xfffff800030c6e53 : nt!KiSystemServiceCopyEnd+0x13
0xfffff880050ab3b0 : 0xfffffa80109d4b50 :  Trap @ fffff880050ab3b0
0xfffff880050ab3c8 : 0xfffff80003394eb9 : nt!CmpDoOpen+0x319

I see that you have a mix of RAM modules:

Code:

[Memory Device (Type 17) - Length 28 - Handle 0040h]
  Physical Memory Array Handle  003fh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  Elpida
  Serial Number                         
  Asset Tag Number                        
  Part Number                   EBJ41UF8BCS0-DJ-F 
[Memory Device (Type 17) - Length 28 - Handle 0041h]
  Physical Memory Array Handle  003fh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM0
  Bank Locator                  BANK 2
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  859B
  Serial Number                         
  Asset Tag Number                        
  Part Number                   CT51264BC160B.M16F

Did the issues start shortly after upgrading?

Please test the RAM for errors or else debugging a faulty / mismatched RAM is futile.
Testing the RAM:

Quote: Originally Posted by koolkat77

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+

Tip

Pay close attention to part 3 of the tutorial "If you have errors"
Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

If MEMTest86+ gives a clean bill of health remove the recently added module (RAM stick)
and run the system that way for a couple of days and observe the system's stability.

A final word for now, Win32k is mainly a graphic oriented driver but also interacts with other
components of the system I/O being one of them, I noticed your touchpad driver is pretty out dated
please update the driver.

Code:

lmvm syntp
Browse full module list
start             end                 module name
fffff880`06059000 fffff880`061be000   SynTP      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\SynTP.sys
    Image name: SynTP.sys

    Timestamp:        Fri May 06 05:28:49 2011

Keep us posted :) .