Crashes with version 4.2.67.10

I wonder if this issue is related as well https://www.wilderssecurity.com/showthread.php?t=286832

 

To the ESET people.

Do you think this "issue" could be responsible for a BSOD in currently updated Windows 7 x32?

Stop 0x1a_3452 in process ekrn.exe

(I windbg'd the crash dump)

I cannot give more info, as I am currently performing 10 iterations of Windows Memory Diagnostic (extended) which will take until tomorrow sometime.

Followup_IP: nt!MiDeleteAddressesInWorkingSet+389 (int 3)

Image name is "memory_corruption"

I am running the WMDT now, will follow up w/ q24h of memtest 4.10 if needed, but I don't think this is a hardware issues as I have run Prime95 and Memtest on this box when it was built for MANY hours (days) to assure stability (it's mission critical, not overclocked!)

Thoughts?

 

Most likely not. The change causing problems was made between Dec 16 and Dec 22 and started to manifest after Dec 30. I, for one, am not aware of BSOD being one of the symptoms of the recent problem. Please upload the dump somewhere (ideally a complete or kernel memory dump) and pm me the link.