4 crashes with for different errors but still all more or less memory related.
So course of action: my earlier advises are the best I can come up with.
How are the temperatures?
Core Temp also
SIV - System Information Viewer
You could go ahead, dust and re-seat the RAM modules.
What happened in the last 4 weeks? Crashfree until now?
-DG
Code:
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: 0000000000000028, memory referenced
Arg2: 0000000000000002, 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: fffff80002ccfbd0, address which referenced memory
**********************************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8009974b30, Terminating object
Arg3: fffffa8009974e10, Process image file name
Arg4: fffff80002f948b0, Explanatory message (ascii)
*********************************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002cc73a2, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a082110, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
********************************************************************************************
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: ffffffffffffff89, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002fdba26, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)