Well, "they" are ( or is it is) "me" if that makes sense. I own that domain, and posted the files there to make them available to others should they wish to see them.
I have looked at the minidump files with WinDbg and below is what looks important to me:
MiniDump 1:
BugCheck 1000008E, {c0000005, 8054a0ba, ef1ca5dc, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+b4 )
Followup: Pool_corruption
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
PROCESS_NAME: svchost.exe
IMAGE_NAME: Pool_Corruption
Minidump 2:
BugCheck 1000008E, {c0000005, 8054a168, eee3683c, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+162 )
Followup: Pool_corruption
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
PROCESS_NAME: bmctl.exe
IMAGE_NAME: Pool_Corruption
Minidump 3:
BugCheck 1000008E, {c0000005, 805a33d6, ee63fc18, 0}
Probably caused by : ntkrpamp.exe ( nt!NtAcceptConnectPort+18c )
Followup: MachineOwner
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
PROCESS_NAME: svchost.exe
IMAGE_NAME: ntkrpamp.exe
Minidump 4:
BugCheck 19, {20, e35f543b, e35f577b, c684704}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+2a3 )
Followup: MachineOwner
BAD_POOL_HEADER (19)
PROCESS_NAME: iexplore.exe
IMAGE_NAME: ntkrpamp.exe
Minidump 5:
BugCheck 10000050, {8e7000a8, 0, 805badb7, 0}
Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+13 )
Followup: MachineOwner
PROCESS_NAME: services.exe
IMAGE_NAME: ntkrpamp.exe
I have Googled ntkrpamp.exe and the consensus seems to be that it is a driver problem, but how do I find what driver to remove/update?
Bad memory is also an option, but I have tried running with only one of the two chips installed, the swapped them around to see if the problem would go away, but it did not. Also, Memtest has run for days with no errors.