IRQL_NOT_LESS_OR_EQUAL Error in Windows 10

hey everyone i have been getting this a lot lately playing games. running windows 10 on amd 9590 chip two 970s and 32gb of g.skill ram i get these almost three or four times a day, any and all help is much appreciated,

thanks



Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\033016-9968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff802`0a890000 PsLoadedModuleList = 0xfffff802`0ab6ecd0
Debug session time: Wed Mar 30 18:38:48.499 2016 (UTC - 6:00)
System Uptime: 0 days 1:03:14.227
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.....................................
Cannot read PEB32 from WOW64 TEB32 00007364 - Win32 error 0n30
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ca61f82f4, ff, 0, fffff8020a8b0267}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000ca61f82f4, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8020a8b0267, address which referenced memory

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000ca61f82f4

CURRENT_IRQL: 0

FAULTING_IP:
nt!PpmIdleExecuteTransition+787
fffff802`0a8b0267 498b8740060000 mov rax,qword ptr [r15+640h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: AV

PROCESS_NAME: System

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

DPC_STACK_BASE: FFFFD0012899CFB0

TRAP_FRAME: ffffd00128995720 -- (.trap 0xffffd00128995720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000074ad rbx=0000000000000000 rcx=000000000000000e
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020a8b0267 rsp=ffffd001289958b0 rbp=0000000000000000
r8=000011832eb52885 r9=0000008000000000 r10=0000000000000020
r11=00000000000000e8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!PpmIdleExecuteTransition+0x787:
fffff802`0a8b0267 498b8740060000 mov rax,qword ptr [r15+640h] ds:00000000`00000640=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8020a9dd2e9 to fffff8020a9d2760

STACK_TEXT:
ffffd001`289955d8 fffff802`0a9dd2e9 : 00000000`0000000a 0000000c`a61f82f4 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffd001`289955e0 fffff802`0a9dbac7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd001`28995720 fffff802`0a8b0267 : ffffe000`af772010 00000000`00da7a64 ffffe000`b1b35c80 ffffd001`2d36e180 : nt!KiPageFault+0x247
ffffd001`289958b0 fffff802`0a8af92b : 00000000`00000000 00000000`00000002 ffffe000`af7720f0 00000000`00000000 : nt!PpmIdleExecuteTransition+0x787
ffffd001`28995b00 fffff802`0a9d54ec : ffffffff`00000000 ffffd001`2d36e180 ffffd001`2d37acc0 ffffe000`b02d2080 : nt!PoIdle+0x33b
ffffd001`28995c60 00000000`00000000 : ffffd001`28996000 ffffd001`28990000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8020a8b0267 - nt!PpmIdleExecuteTransition+787
[ 48:49 ]
1 error : !nt (fffff8020a8b0267)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption
---------