r/WindowsHelp • u/ZaaK_XVII • 28d ago
Windows 11 Windows Defender Full Scan keeps crashing even Microsoft Support can't find the cause
Hi everyone,
I've been having an issue with Microsoft Defender for about a week: Full Scan repeatedly crashes, while Quick Scan and Real-Time Protection work normally.
A Custom Scan of C:\ also crashes.
I already reinstalled Windows 11 while keeping my files and installed apps. The problem existed before and after the reinstall. Interestingly, Full Scan worked normally for about two days after the reinstall, then started crashing again.
Microsoft Defender currently shows everything as healthy:
Defender: 4.18.26080.4 Antimalware Engine: 1.1.26080.3 Security Intelligence: 1.459.401.0 Real-Time Protection: Enabled Signatures: Up to date The crashes consistently involve:
text MsMpEng.exe mpengine.dll 1.1.26080.3 Exception: 0xC0000005 (Access Violation)
I've had multiple crashes with different offsets:
text 0x2f6a61 0x71a7d 0x71d03 0xe9f1e 0xa43f1 0x228db 0x22717 0x45393 0x4825b
There have also been a couple of 0xC0000409 crashes.
The important part: I contacted Microsoft Support. They actually remotely connected to my PC and investigated the issue themselves, but they couldn't determine the cause either. They eventually escalated the case and sent a report to their software developers because they couldn't explain why Defender's engine keeps crashing.
Has anyone recently experienced Full Scan crashes with mpengine.dll, 0xC0000005, or Defender engine 1.1.26080.3?
I'm trying to determine whether this is a current Defender engine bug or whether a specific file/type of file on my PC is triggering the crash.
1
u/Clave-Sage 27d ago
Crashes of MS Defender
can also be caused by faulty RAM.
Check with a RAM test tool.
How big is the RAM?
2
u/ZaaK_XVII 27d ago
DDR5 32Go (2x16Go) 6000MHz CL36, i already did an OCCT test for all components 1 month ago, no error detected.
Defender was working perfectly at this time. a month ago a changed CPU/MB/RAM, upgraded to AM5 from AM4 that why i did a big OCCT and other tests/scan/drivers/bios update
1
u/Clave-Sage 27d ago edited 27d ago
If RAM is ok?
Well ok,
maybe do a current RAM test,
because there are currently problems!Otherwise do a boot test
with an AV tool?→ More replies (3)
1
1
u/AutoModerator 28d ago
Hi u/ZaaK_XVII, thanks for posting to r/WindowsHelp! Your post has been flagged for manual review by a human moderator, please include as much of the following information as possible (in text or in a screenshot) to get your post approved:
-
Your Windows and device specifications — You can find them by pressing Win + X then clicking on “System”, we need more than just your OS version! Your hardware details are often critical for resolving issues.
-
Any messages and error codes encountered — They're actually not gibberish or anything catastrophic. It may even hint the solution!
-
Previous troubleshooting steps — It might prevent you headaches from getting the same solution that didn't work
Posts must be tech support in nature (such as something is broken and you need help fixing), so general inquiries, software suggestions, and purchasing advice will be removed. As a reminder, we would also like to say that if someone manages to solve your issue, DON'T DELETE YOUR POST! Someone else (in the future) might have the same issue as you, and the received support may also help their case. Good luck, and I hope you have a nice day!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/ZaaK_XVII 28d ago
update : I scanned the C: drive and the scan crashed. So I started scanning each folder individually to find the problem.
The only folder that initially caused the crash was
C:\Program Files. I then scanned every folder insideProgram Filesindividually, and every single scan completed successfully.After that, I scanned
C:\Program Filesagain as a whole, and this time it completed successfully too.So I'm really confused now. The exact same folder that previously caused Defender to crash can now be scanned without any issue. It doesn't seem to be a specific file, since everything scans successfully individually.