Yet another Runescape-related BSOD


  1. Posts : 9
    Windows 7 Ultimate 64 bit
       #1

    Yet another Runescape-related BSOD


    Alright, well I'm back with another BSOD, one I've surprisingly never seen before. I previously had a lot of issues with running runescape and pandora or runescape and netflix together at the same time. Well I just ran into an issue with running runescape with pandora again... I can play any other game with the highest settings and i'm fine, but you pair runescape and pandora, all hell breaks loose. I resently fixed all of my previous BSODs by updating to to latest AMD beta GPU drivers, and I also just installed a new Samsung 840 EVO, seeing as it's a page issue i'm wondering if it has something to do with that. Well thank you in advance!
      My Computer


  2. Posts : 81
    Windows 7 Ultimate X64
       #2

    Your RAM is corrupted:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: fffff8800c01b870, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88001865e00, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800020fc100
    GetUlongFromAddress: unable to read from fffff800020fc1c0
     fffff8800c01b870 Nonpaged pool
    
    FAULTING_IP: 
    Npfs!NpReadDataQueue+70
    fffff880`01865e00 4c8bbc24b0200000 mov     r15,qword ptr [rsp+20B0h]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800c019630 -- (.trap 0xfffff8800c019630)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001865e00 rsp=fffff8800c0197c0 rbp=0000000000000001
     r8=0000000000000000  r9=0000000000000004 r10=fffffa8006ce0190
    r11=fffff8800c0198e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    Npfs!NpReadDataQueue+0x70:
    fffff880`01865e00 4c8bbc24b0200000 mov     r15,qword ptr [rsp+20B0h] ss:0018:fffff880`0c01b870=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80001f42bf0 to fffff80001ec4bc0
    
    STACK_TEXT:  
    fffff880`0c0194c8 fffff800`01f42bf0 : 00000000`00000050 fffff880`0c01b870 00000000`00000000 fffff880`0c019630 : nt!KeBugCheckEx
    fffff880`0c0194d0 fffff800`01ec2cee : 00000000`00000000 fffff880`0c01b870 fffff880`009c0100 fffff880`0c0198f0 : nt! ?? ::FNODOBFM::`string'+0x4518f
    fffff880`0c019630 fffff880`01865e00 : fffff8a0`0846ebd0 fffffa80`06d495d0 00000000`00000001 fffff8a0`024b8aa0 : nt!KiPageFault+0x16e
    fffff880`0c0197c0 fffff880`01865d32 : fffff880`0c019880 fffff8a0`024b8af0 00000000`00000000 00000000`00000000 : Npfs!NpReadDataQueue+0x70
    fffff880`0c019830 fffff880`01865ab5 : fffffa80`06d496a0 fffffa80`077e5e10 00000000`00000000 fffffa80`06d495d0 : Npfs!NpCommonRead+0x18e
    fffff880`0c0198b0 fffff800`021cec3b : 00000000`00000000 fffffa80`077e5e10 00000000`00000000 fffffa80`06d495d0 : Npfs!NpFsdRead+0x51
    fffff880`0c019910 fffff800`021aed53 : fffffa80`077e5e10 fffffa80`077e5e10 fffffa80`077e5e10 fffff800`0203fe80 : nt!IopSynchronousServiceTail+0xfb
    fffff880`0c019980 fffff800`01ec3e53 : fffffa80`08477001 00000000`00000f24 00000000`00000001 00000000`0ec8f824 : nt!NtReadFile+0x631
    fffff880`0c019a70 00000000`73f22e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`06acea08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73f22e09
    
    
    STACK_COMMAND:  kb
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    Followup: memory_corruption
    ---------
    My advice would be to run Memtest86, and check to see if there are any errors. If errors do show up, I'm sorry to say your RAM is indeed corrupted and will need a replacement soon.

    Best of luck,

    PeregrineX
      My Computer


  3. Posts : 9
    Windows 7 Ultimate 64 bit
    Thread Starter
       #3

    PeregrineX said:
    Your RAM is corrupted:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: fffff8800c01b870, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88001865e00, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800020fc100
    GetUlongFromAddress: unable to read from fffff800020fc1c0
     fffff8800c01b870 Nonpaged pool
    
    FAULTING_IP: 
    Npfs!NpReadDataQueue+70
    fffff880`01865e00 4c8bbc24b0200000 mov     r15,qword ptr [rsp+20B0h]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800c019630 -- (.trap 0xfffff8800c019630)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001865e00 rsp=fffff8800c0197c0 rbp=0000000000000001
     r8=0000000000000000  r9=0000000000000004 r10=fffffa8006ce0190
    r11=fffff8800c0198e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    Npfs!NpReadDataQueue+0x70:
    fffff880`01865e00 4c8bbc24b0200000 mov     r15,qword ptr [rsp+20B0h] ss:0018:fffff880`0c01b870=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80001f42bf0 to fffff80001ec4bc0
    
    STACK_TEXT:  
    fffff880`0c0194c8 fffff800`01f42bf0 : 00000000`00000050 fffff880`0c01b870 00000000`00000000 fffff880`0c019630 : nt!KeBugCheckEx
    fffff880`0c0194d0 fffff800`01ec2cee : 00000000`00000000 fffff880`0c01b870 fffff880`009c0100 fffff880`0c0198f0 : nt! ?? ::FNODOBFM::`string'+0x4518f
    fffff880`0c019630 fffff880`01865e00 : fffff8a0`0846ebd0 fffffa80`06d495d0 00000000`00000001 fffff8a0`024b8aa0 : nt!KiPageFault+0x16e
    fffff880`0c0197c0 fffff880`01865d32 : fffff880`0c019880 fffff8a0`024b8af0 00000000`00000000 00000000`00000000 : Npfs!NpReadDataQueue+0x70
    fffff880`0c019830 fffff880`01865ab5 : fffffa80`06d496a0 fffffa80`077e5e10 00000000`00000000 fffffa80`06d495d0 : Npfs!NpCommonRead+0x18e
    fffff880`0c0198b0 fffff800`021cec3b : 00000000`00000000 fffffa80`077e5e10 00000000`00000000 fffffa80`06d495d0 : Npfs!NpFsdRead+0x51
    fffff880`0c019910 fffff800`021aed53 : fffffa80`077e5e10 fffffa80`077e5e10 fffffa80`077e5e10 fffff800`0203fe80 : nt!IopSynchronousServiceTail+0xfb
    fffff880`0c019980 fffff800`01ec3e53 : fffffa80`08477001 00000000`00000f24 00000000`00000001 00000000`0ec8f824 : nt!NtReadFile+0x631
    fffff880`0c019a70 00000000`73f22e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`06acea08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73f22e09
    
    
    STACK_COMMAND:  kb
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    Followup: memory_corruption
    ---------
    My advice would be to run Memtest86, and check to see if there are any errors. If errors do show up, I'm sorry to say your RAM is indeed corrupted and will need a replacement soon.

    Best of luck,

    PeregrineX
    I ran it for 24 hours maybe 2-3 weeks ago and there were no errors at all, I ran it through one set and everything was fine just now
      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 02:44.
Find Us