Windows 10: MDE and BSOD seen due to MSMPENG.exe

Machine having BSOD due to MSMPENG.exe

:)

 

Programs Slow To Open Due To Windows Defender (MsMpEng)


This is something that I've noticed since Windows 8, but Windows Defender make some programs so slow to open. It's pretty noticeable on the programs that it does it on as it takes approx. 20-30 seconds to open them, even from an SSD, and if you look at Resource Monitor listed by CPU usage, you can see it's due to MsMpEng.exe running a scan before the program will open.

It would be understandable if it was doing it the first time the program had ever ran, or if the program wasn't signed, but that's not always the case. Canon DPP for example isn't signed, so presumably that's why Defender keeps scanning that, however here's an example of another program (SyncBackFree) that is signed, but yet Windows Defender still wants to keep scanning it on a daily basis despite nothing changing since previous scans.





Obviously I can add individual programs to the Windows Defender Exclusion list and exclude them from real-time protection, but what it is that Defender doesn't like with certain programs that is feels the need to keep scanning them daily? Is this a Microsoft problem, or is it down to the software not adhering to some sort of best practice policies Microsoft have laid out? There must me something that makes Defender treat it as potentially signed malware?

 

Overclocking / Undervolting guide for Vega 56 or 64?

Here's a quick laundry list:

List of software to use for overclocking and testing
Examples:
Wattman (and how to find and use it, like an overview, including profiles)
Unigine Valley or Heaven (use this for quick testing while changing settings in Wattman and checking for stability / artifacts) ...just suggesting this
How to monitor cores / mem speeds and temps during testing (I've seen screen overlays, and others using GPUz)

Step-by step overclocking in Wattman
Fan speeds
Power limit
Temp limit
Voltages
Core speeds
Memory speeds

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast: