SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff980b4d1ae70, address trying to free
Arg2: fffff980b4d1a2da, address where one bit is corrupted
Arg3: 0000000000474190, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
Yeah, for sure, single bit error means bad RAM.
You can see the corruption here:
3: kd> dd fffff980b4d1a2da
fffff980`b4d1a2da 47474745 47474747 47474747 47474747
fffff980`b4d1a2ea 47474747 47474747 47474747 47474747
fffff980`b4d1a2fa 47474747 47474747 47474747 47474747
fffff980`b4d1a30a 47474747 47474747 47474747 47474747
fffff980`b4d1a31a 47474747 47474747 47474747 47474747
fffff980`b4d1a32a 47474747 47474747 47474747 47474747
fffff980`b4d1a33a 47474747 47474747 47474747 47474747
fffff980`b4d1a34a 47474747 47474747 47474747 47474747
Notice the 5 should be a 7:
5 = 0b0101
7 = 0b0111
That bit flipped. Cosmic ray?