Facing 0x0000000a BSOD, again.

[eddman]

OK, I sort of fixed this BSOD some time ago which was memory related, but now it's back, although not as frequent as before and I think this time the culprit is something else.

Could you please look at these dump files.

Thanks in advance.

 

[carwiz]

It still appears to be memory related; However, this can be caused by faulty drivers and/or malware. The failure was caused by an attempt to start a program thread at a bad address. On previous errors, were you instructed to run Memtest86+ and scan for malware? I'm looking over your drivers and will get back.

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`02f03761 48893cc2        mov     qword ptr [rdx+rax*8],rdi
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+181
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c
IMAGE_NAME: [B][U] memory_corruption[/U][/B]
FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181
BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181
Followup: MachineOwner
---------
1: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff800`02ee3769 : 00000000`0000000a ffffca7f`ffffffd8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`02ee23e0 : 00000000`00000001 fffffa80`013583d0 00000000`00000000 fffffa80`01665cc0 : nt!KiBugCheckDispatch+0x69
fffff800`02f03761 : fffffa80`0384cc58 00000000`00000000 fffffa80`0384cb50 fffff800`02ea690b : nt!KiPageFault+0x260
fffff800`02ea704e : 00000000`0000003f 00000000`00000004 00000000`00000000 fffffa80`03781090 : nt!MiUnlinkFreeOrZeroedPage+0x181
fffff800`0317ae6a : fffffa80`0384cb50 00000000`00000080 fffffa80`0384c040 fffff800`02ed4ef9 : nt!MmZeroPageThread+0x541
fffff800`02ed4f06 : fffff800`03056e80 fffffa80`0384cb50 fffff800`03064cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16