Discussion in 'other anti-malware software' started by erikloman, May 25, 2012.
Why isn't it the very latest code? The very latest stable code I mean
hello i have a question about a BSOD i get now sometimes because in the past we had a APC_INDEX_MISMATCH BSOD and now i get a Clock_Watchdog_Timeout in combination when i want to login in paypal or similar after i type my password...
i think it has nothing to do with HMPA because the PiD was = 4 and that was in the svchost
so what ever its causing that problem im sure it has something to do with my AV
sorry for bother you
after PiD check and whocrashed finally it was this corrupt or missing file = VIDEO_DXGKRNL_LIVEDUMP which was caused by an old nvidia driver which crashed my system with a BSOD Clock_Watchdog_Timeout everytime i logged in in paypal.....
new driver after DDU and no problem anymore for the case anyone get the same probs and sorry for off topic now.
Is unchecking Local Privilege Mitigation still the recommended setting in HMPA to allow for running a browser with Sandboxie?
See my post here for additional infos
Got a BSOD during a Macrium Reflect image backup, caused by HMPA.
Bug check: MEMORY_MANAGEMENT
Caused by driver: hmpalert.sys
What's been going on with HMP.A lately? I keep seeing people complaining about it causing bluescreens and all kinds of other problems.
I uninstalled HMPA...
No issues here.
Functional question from me please...
Windows 10 Pro with Defender has a default range of exploit setttings enabled. When HMPA is installed, are HPMA exploit protection settings -
a) a duplication / integration of W10 exploit settings?
b) separate to W10 exploit settings, but running in parallel? If one exploit is turned off in HPMA, the same exploit will need turning off in W10 ?
c) they disable and replace W10 exploit settings?
d) something else?
Thanks for any help!
I have reinstalled HMPA, as I got a Macrium image validation failure without it. Not sure what the BSOD was all about. Maybe a faulty target drive, but that BSOD is not reproducible here at this point.
Good to hear you got it nailed down, and no prob for the off topic, BSOD can be a beast.
There are two BSOD fixes pending, where do you see those people complaining? is that here or on other places we don't monitor?
Eh well ours are different and most of them inspect/protect both (hmpa & defender) some we bail-out because the OS has sufficient protection.
And different because we can allow/whitelist very fine-grained, where defender says "ok it's not working disable the whole protection" we can do it on a specific piece of code level per application.
In the past our head developer didn't call it EMET on steroids for nothing
You get the newest toys here, once most things are ironed out we release it to the home team and they can decide when to implement based on other changes / risk analysis in their product.