BSODS while playing CSGO (PAGE_FAULT_IN_NONPAGED_AREA (50)

[b00m666]

Hey,

Ever since i got new RAM in my pc i've experienced random BSODS with random errors, lately it was quiet but recently when i started picking up on CSGO it kept coming back ( Note: it only occured reguraly on CSGO and no other game)

I understand that it could be an RAM stick gone bad but doesn't that seem odd to you? Since it's litteraly brand new ( and it's only one brand since the two came in a kit of 16 gb 2600MHZ)

To further help you understand the error, i'll paste the memory dump and a Bios screenshot of my memory.

SS:

Memory Dump:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`03095e90
Debug session time: Sat Aug 15 13:06:48.072 2015 (UTC + 1:00)
System Uptime: 0 days 2:17:58.821
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdb018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff95fe00b67e4, 8, fffff95fe00b67e4, 5}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

16.0: kd:x86> !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: fffff95fe00b67e4, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff95fe00b67e4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


READ_ADDRESS: fffff95fe00b67e4

FAULTING_IP:
+1
fffff95f`e00b67e4 ?? ???

MM_INTERNAL_CODE: 5

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000

FAILED_INSTRUCTION_ADDRESS:
+1
fffff95f`e00b67e4 ?? ???

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

BUCKET_ID: INVALID_KERNEL_CONTEXT

FAILURE_BUCKET_ID: INVALID_KERNEL_CONTEXT

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:invalid_kernel_context

FAILURE_ID_HASH: {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}

Followup: MachineOwner
---------

Thanks in advance, and feel free to ask any question if you require some more information.

 

[Layback Bear]

Could you complete this tutorial.

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[b00m666]

Done, althought obviously i deleted the file with the ipconfig in it.