Bsod page_fault_in_nonpaged_area


  1. Posts : 28
    Windows 7 Professional x64
       #1

    Bsod page_fault_in_nonpaged_area


    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 4105

    Additional information about the problem:
    BCCode: 50
    BCP1: FFFFFA8009904CF8
    BCP2: 0000000000000000
    BCP3: FFFFF88008B9F794
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1


    My computer is a laptop not even a year old. I have been getting random BSOD every so ofter usually when coming out of sleep however this err just stated to appear. Please help me i have windows 7 Professional 64 bit, and i thought the err was from Norton however i uninstalled it and i am still getting this err and it is completely random. attached is all the info you should need to help me.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    brodiewf said:
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 4105

    Additional information about the problem:
    BCCode: 50
    BCP1: FFFFFA8009904CF8
    BCP2: 0000000000000000
    BCP3: FFFFF88008B9F794
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1


    My computer is a laptop not even a year old. I have been getting random BSOD every so ofter usually when coming out of sleep however this err just stated to appear. Please help me i have windows 7 Professional 64 bit, and i thought the err was from Norton however i uninstalled it and i am still getting this err and it is completely random. attached is all the info you should need to help me.
    BTW if you didnt remove Norton with their removal tool you probably have fragments left.

    These two were caused by your Ad-Aware driver (KernExplorer64.sys) You should remove it and then run memtestx86 as indicated below.


    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.



    DMP
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\092510-37565-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*C:\symbols;*Symbol information ;srv*e:\symbols
    *Symbol information
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`0345c000 PsLoadedModuleList = 0xfffff800`03699e50
    Debug session time: Sat Sep 25 23:34:19.890 2010 (GMT-4)
    System Uptime: 0 days 13:16:17.356
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffa80091405e8, 0, fffff88008de7794, 0}
    
    Unable to load image \??\C:\Program Files (x86)\Lavasoft\Ad-Aware\KernExplorer64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for KernExplorer64.sys
    *** ERROR: Module load completed but symbols could not be loaded for KernExplorer64.sys
    
    Could not read faulting driver name
    Probably caused by : KernExplorer64.sys ( KernExplorer64+1794 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffa80091405e8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88008de7794, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800037040e0
     fffffa80091405e8 
    
    FAULTING_IP: 
    KernExplorer64+1794
    fffff880`08de7794 0fb75058        movzx   edx,word ptr [rax+58h]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  AAWService.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800915b760 -- (.trap 0xfffff8800915b760)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8009140590 rbx=0000000000000000 rcx=fffff8a0001feeb1
    rdx=fffff8a00edc86f1 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008de7794 rsp=fffff8800915b8f0 rbp=fffffa800874f000
     r8=fffff8a00edc86f0  r9=0000000000000050 r10=fffff880009e9780
    r11=fffff8a0001feeb0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    KernExplorer64+0x1794:
    fffff880`08de7794 0fb75058        movzx   edx,word ptr [rax+58h] ds:8530:fffffa80`091405e8=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000354cf14 to fffff800034cc740
    
    STACK_TEXT:  
    fffff880`0915b5f8 fffff800`0354cf14 : 00000000`00000050 fffffa80`091405e8 00000000`00000000 fffff880`0915b760 : nt!KeBugCheckEx
    fffff880`0915b600 fffff800`034ca82e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`037b2dad : nt! ?? ::FNODOBFM::`string'+0x42837
    fffff880`0915b760 fffff880`08de7794 : 00000000`c0000001 fffffa80`0874f000 00000001`00000034 fffff880`0915b980 : nt!KiPageFault+0x16e
    fffff880`0915b8f0 00000000`c0000001 : fffffa80`0874f000 00000001`00000034 fffff880`0915b980 00000000`00000000 : KernExplorer64+0x1794
    fffff880`0915b8f8 fffffa80`0874f000 : 00000001`00000034 fffff880`0915b980 00000000`00000000 00000000`00240022 : 0xc0000001
    fffff880`0915b900 00000001`00000034 : fffff880`0915b980 00000000`00000000 00000000`00240022 fffff8a0`05c946a0 : 0xfffffa80`0874f000
    fffff880`0915b908 fffff880`0915b980 : 00000000`00000000 00000000`00240022 fffff8a0`05c946a0 00000000`00000000 : 0x1`00000034
    fffff880`0915b910 00000000`00000000 : 00000000`00240022 fffff8a0`05c946a0 00000000`00000000 fffffa80`072f8530 : 0xfffff880`0915b980
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    KernExplorer64+1794
    fffff880`08de7794 0fb75058        movzx   edx,word ptr [rax+58h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  KernExplorer64+1794
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: KernExplorer64
    
    IMAGE_NAME:  KernExplorer64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4be3e1d3
    
    FAILURE_BUCKET_ID:  X64_0x50_KernExplorer64+1794
    
    BUCKET_ID:  X64_0x50_KernExplorer64+1794
    
    Followup: MachineOwner
    ---------
    old drivers needing updates
    Code:
    tosrfnds.sys        fffff880`06800000    fffff880`0680c000    0x0000c000    0x42d35898    7/12/2005 01:43:52                        
    tosrfcom.sys        fffff880`02d4e000    fffff880`02d66e80    0x00018e80    0x42edd326    8/1/2005 03:45:42                        
    tosporte.sys        fffff880`04d2f000    fffff880`04d41000    0x00012000    0x452c9dbc    10/11/2006 03:31:08                        
    tosrfbnp.sys        fffff880`06a19000    fffff880`06a23e80    0x0000ae80    0x45616da3    11/20/2006 04:56:03                        
    agrsm64.sys        fffff880`06a2d000    fffff880`06b60000    0x00133000    0x456ca041    11/28/2006 16:46:57                        
    tosrfbd.sys        fffff880`04db5000    fffff880`04dd7f00    0x00022f00    0x45dd76b8    2/22/2007 06:55:52                        
    tosrfusb.sys        fffff880`06a00000    fffff880`06a0c580    0x0000c580    0x45e58319    2/28/2007 09:26:49                        
    Tosrfhid.sys        fffff880`04dd8000    fffff880`04ded700    0x00015700    0x45e68682    3/1/2007 03:53:38                        
    BisonCam.sys        fffff880`04c00000    fffff880`04cb3980    0x000b3980    0x46c5367c    8/17/2007 01:47:40                        
    adfs.SYS        fffff880`02c23000    fffff880`02c3b000    0x00018000    0x48640195    6/26/2008 16:52:37
      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 10:29.
Find Us