Loading Dump File [D:\Downloads\mike\041017-4281-01.dmp]
Debug session time: Mon Apr 10 09:11:27.731 2017 (UTC + 2:00)
System Uptime: 0days 0:05:31.349
BugCheck D1, {fffff8026e831670, ff, c7, fffff8026e831670}Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247 )
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8026e831670, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000c7, value 0 = read operation, 1 = write operation
Arg4: fffff8026e831670, address which referenced memory
ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.
BUGCHECK_STR: DISABLED_INTERRUPT_FAULT
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
Loading Dump File [D:\Downloads\mike\041717-4437-01.dmp]
Debug session time: Mon Apr 17 14:07:05.883 2017 (UTC + 2:00)
System Uptime: 3 days 8:55:51.155
BugCheck 1000007F, {8, ffff8c00dcca6bf0, d65860f1, fffff80321e5e70d}
Probably caused by : ntkrnlmp.exe ( nt!PpmIdleExecuteTransition+10d )
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc). Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff8c00dcca6bf0
Arg3: 00000000d65860f1
Arg4: fffff80321e5e70d
BUGCHECK_STR: 0x7f_8
BAD_STACK_POINTER: 00000000d65860f1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
UNALIGNED_STACK_POINTER: 00000000d65860f1
Loading Dump File [D:\Downloads\mike\042417-4218-01.dmp]
Debug session time: Mon Apr 24 14:27:31.682 2017 (UTC + 2:00)
System Uptime: 0 days 1:32:23.393
BugCheck A, {5d80b6, ff, 2c, fffff80017adf17f}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+4f )
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.
Arg1: 00000000005d80b6, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 000000000000002c, 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: fffff80017adf17f, address which referenced memory
DUMP_FILE_ATTRIBUTES: 0x8
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
Loading Dump File [D:\Downloads\mike\042417-4578-01.dmp]
Debug session time: Mon Apr 24 17:22:19.373 2017 (UTC + 2:00)
System Uptime: 0 days 2:54:20.082
BugCheck 124, {0, ffff9002de326028, be000000, 200135}
Probably caused by : GenuineIntel
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon.
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_CACHE
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache