BSOD Page Fault In Non Paged Area


  1. Posts : 679
    Windows 7 professional X64
       #1

    BSOD Page Fault In Non Paged Area


    Hey guys. It's me again.

    Seems my system is detecting that when one issue is fixed it will put out another one out of nowhere.
    This time I am getting an alsysio64.sys BSOD that might be related to ntoskrnl.exe.

    Ati Drivers have been giving me a hard time so I wouldn't be surprised if this issue was caused by them at all, this started happening after a Windows scheduled updated ocurred last night.

    Whenever the system boots up and loads the desktop it will crash. However when I restart it it will be back to normal, no need to run in safe mode.

    I've noticed however... that before the crash occurs, the core temp gadget does not expand to show CPU information. And the second it does, my computer crashes. Upon restart it will load properly, perhaps it is a coincidence. I just find it strange that my system has given me so many issues since I've upgraded to an FM2 platform.

    Anyway.. I've attached both of the latest minidumps if you need better information than what I can provide.

    Thank you very much
      My Computer


  2. Posts : 679
    Windows 7 professional X64
    Thread Starter
       #2

    Yep, as quickly as I disabled coretemp from startup the BSOD has stopped happening. I rebooted 5 times trying to reproduce the error and it's just like no BSOD ever happened. This is very strange.
    The latest windows update might have caused an issue with coretemp drivers?
      My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #3

    Does look like the BSOD was caused by Coretemp Driver Reference Table - ALSysIO64.sys

    Uninstall and reinstall the software (Latest available) see if that helps.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffa8016000000, 0, fffff88009f8761e, 2}
    
    *** WARNING: Unable to verify timestamp for ALSysIO64.sys
    *** ERROR: Module load completed but symbols could not be loaded for ALSysIO64.sys
    
    Could not read faulting driver name
    Probably caused by : ALSysIO64.sys ( ALSysIO64+361e )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffffa8016000000, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88009f8761e, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800044c2100
    GetUlongFromAddress: unable to read from fffff800044c21c0
     fffffa8016000000 Nonpaged pool
    
    FAULTING_IP: 
    ALSysIO64+361e
    fffff880`09f8761e 4c8b4c0af0      mov     r9,qword ptr [rdx+rcx-10h]
    
    MM_INTERNAL_CODE:  2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  Core Temp.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800a9be6c0 -- (.trap 0xfffff8800a9be6c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000001a rbx=0000000000000000 rcx=fffff8801be70ba8
    rdx=000001fffa18f464 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88009f8761e rsp=fffff8800a9be858 rbp=fffff8800a9beb60
     r8=000000000031f648  r9=56125de6be7ebcf3 r10=7b445fe62de3ffae
    r11=fffff880110001e8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    ALSysIO64+0x361e:
    fffff880`09f8761e 4c8b4c0af0      mov     r9,qword ptr [rdx+rcx-10h] ds:fffffa80`15fffffc=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800043066a4 to fffff80004289c40
    
    STACK_TEXT:  
    fffff880`0a9be558 fffff800`043066a4 : 00000000`00000050 fffffa80`16000000 00000000`00000000 fffff880`0a9be6c0 : nt!KeBugCheckEx
    fffff880`0a9be560 fffff800`04287d6e : 00000000`00000000 fffffa80`16000000 fffffa80`0b18f600 fffff880`110001e8 : nt! ?? ::FNODOBFM::`string'+0x43836
    fffff880`0a9be6c0 fffff880`09f8761e : fffff880`09f86c77 00000000`e00c31e8 00000000`0b18f648 fffffa80`0000ad54 : nt!KiPageFault+0x16e
    fffff880`0a9be858 fffff880`09f86c77 : 00000000`e00c31e8 00000000`0b18f648 fffffa80`0000ad54 fffff6fc`400e0c78 : ALSysIO64+0x361e
    fffff880`0a9be860 00000000`e00c31e8 : 00000000`0b18f648 fffffa80`0000ad54 fffff6fc`400e0c78 fffffa80`0aa43560 : ALSysIO64+0x2c77
    fffff880`0a9be868 00000000`0b18f648 : fffffa80`0000ad54 fffff6fc`400e0c78 fffffa80`0aa43560 fffff880`09f85375 : 0xe00c31e8
    fffff880`0a9be870 fffffa80`0000ad54 : fffff6fc`400e0c78 fffffa80`0aa43560 fffff880`09f85375 00000000`e00c31e8 : 0xb18f648
    fffff880`0a9be878 fffff6fc`400e0c78 : fffffa80`0aa43560 fffff880`09f85375 00000000`e00c31e8 00000000`c0000002 : 0xfffffa80`0000ad54
    fffff880`0a9be880 fffffa80`0aa43560 : fffff880`09f85375 00000000`e00c31e8 00000000`c0000002 fffffa80`0aa43598 : 0xfffff6fc`400e0c78
    fffff880`0a9be888 fffff880`09f85375 : 00000000`e00c31e8 00000000`c0000002 fffffa80`0aa43598 00000000`00000001 : 0xfffffa80`0aa43560
    fffff880`0a9be890 00000000`e00c31e8 : 00000000`c0000002 fffffa80`0aa43598 00000000`00000001 00000000`00000001 : ALSysIO64+0x1375
    fffff880`0a9be898 00000000`c0000002 : fffffa80`0aa43598 00000000`00000001 00000000`00000001 00000000`00000004 : 0xe00c31e8
    fffff880`0a9be8a0 fffffa80`0aa43598 : 00000000`00000001 00000000`00000001 00000000`00000004 fffffa80`0aa43560 : 0xc0000002
    fffff880`0a9be8a8 00000000`00000001 : 00000000`00000001 00000000`00000004 fffffa80`0aa43560 fffff800`045a8b57 : 0xfffffa80`0aa43598
    fffff880`0a9be8b0 00000000`00000001 : 00000000`00000004 fffffa80`0aa43560 fffff800`045a8b57 fffffa80`0b26e220 : 0x1
    fffff880`0a9be8b8 00000000`00000004 : fffffa80`0aa43560 fffff800`045a8b57 fffffa80`0b26e220 fffff880`0a9beb60 : 0x1
    fffff880`0a9be8c0 fffffa80`0aa43560 : fffff800`045a8b57 fffffa80`0b26e220 fffff880`0a9beb60 fffffa80`0b26e220 : 0x4
    fffff880`0a9be8c8 fffff800`045a8b57 : fffffa80`0b26e220 fffff880`0a9beb60 fffffa80`0b26e220 fffffa80`0aa43560 : 0xfffffa80`0aa43560
    fffff880`0a9be8d0 fffff800`045a93b6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
    fffff880`0a9bea00 fffff800`04288ed3 : fffffa80`0b216730 00000000`00000001 fffffa80`0b1e7b50 fffff800`04584734 : nt!NtDeviceIoControlFile+0x56
    fffff880`0a9bea70 00000000`7770138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`001ef7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7770138a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ALSysIO64+361e
    fffff880`09f8761e 4c8b4c0af0      mov     r9,qword ptr [rdx+rcx-10h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  ALSysIO64+361e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ALSysIO64
    
    IMAGE_NAME:  ALSysIO64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e18f201
    
    FAILURE_BUCKET_ID:  X64_0x50_ALSysIO64+361e
    
    BUCKET_ID:  X64_0x50_ALSysIO64+361e
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm ALSysIO64
    start             end                 module name
    fffff880`09f84000 fffff880`09f8d000   ALSysIO64 T (no symbols)           
        Loaded symbol image file: ALSysIO64.sys
        Image path: \??\C:\Users\Aguilar\AppData\Local\Temp\ALSysIO64.sys
        Image name: ALSysIO64.sys
        Timestamp:        Sun Jul 10 06:27:45 2011 (4E18F201)
        CheckSum:         000069F7
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      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 09:54.
Find Us