@Ztruker, never noticed the difference between GenuineIntel & AuthenticAMD in 0x124?
4 or 5 of the dumps show Authe3nticAMD as the cause.
@Mashalien, were those BSODs at boot when driver verifier was enabled this BSOD? No dump showed driver verifier enabled.
The 0x4E look like to be caused by drivers, it looks like something keeps attempting to free memory that was already freed. Though that would give usually a different BSOD than a 0x4E (IME), but as we have only a minidump the memory descriptors of the addresses with which this driver attempted to free the memory cannot be checked.
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000075305, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000170001786cc, 0