BSOD Page Fault in nonpaged area after gaming


  1. Posts : 24
    Windows 7 Home Premium 64 bit SP1
       #1

    BSOD Page Fault in nonpaged area after gaming


    This BSOD just started a little bit ago, and im fairly sure its WoW (private server). I downloaded a new launcher and after Ive played, soon after I get that. Im posting this just to make sure its actually what it is, because it could be something else.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi Cgamon.

    Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
    Code:
    Windows 7 Kernel Version 7600 MP (3 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Learn how to install Windows 7 Service Pack 1 (SP1)
    Service Pack and Update Center - Microsoft Windows

    The display driver is failing here:
    Code:
    fffff880`070e8a48  fffff880`018a0f83Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
     atikmpag+0x3f83
    And it is extremely old.
    Code:
    fffff880`0189d000 fffff880`018d1000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Thu Jan 14 07:40:57 2010 (4B4E7D31)
        CheckSum:         0003A5A5
        ImageSize:        00034000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Use the "Automatically Detect and Install" option from Download Drivers.

    Let us know the results.
    __________________________________________________________________________________________
    Code:
    BugCheck 50, {fffff8ffc24e4988, 1, fffff960000666b0, 5}
    
    Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!RGNOBJ::bOffset+f0 )
    
    Followup: MachineOwner
    -----------------------------------------------------------------------------------
    BugCheck 3B, {c0000005, fffff96000154283, fffff880070e9060, 0}
    
    Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )
    
    Followup: MachineOwner
    ---------
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:14.
Find Us