Hello all,
I got Total Protection 2013 back in June (umbrella'd in under my family's plan), and it's performed reliably with one exception--I've been experiencing Windows Explorer crashes due to File Lock's DLL being 'unloaded'. I've had this issue occuring intermittently since I installed Total Protection on my computer.
Typically, it would occur when I had two consecutive McAfee engine updates with no re-boot between them, but it has started occuring arbitrarily. My speculation was that it was related to issues with Explorer, but I've had nothing but clean scans since I installed Total Protection, and my computer is performing as it should. I'm running a Dell Inspiron N4110 with Windows 7 Service Pack 1 installed.
This is an example of one of the crashes, copied over from the Reliability Monitor--
Problem signature
Problem Event Name: BEX64
Application Name: Explorer.EXE
Application Version: 6.1.7601.17567
Application Timestamp: 4d672ee4
Fault Module Name: McPvNs.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 522de439
Exception Offset: 000007fee9734050
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 65d5
Additional Information 2: 65d5e11e3b403a4beaf5cea13462fca9
Additional Information 3: 4ef1
Additional Information 4: 4ef1392c0b777cb9c942816dd7a5eb58
My questions are--
1. Is this a common problem?
2. What is this typically connected to (i.e. Registry issues)?
3. What can I do to fix this?
Solved! Go to Solution.
We noticed this issue as well. The problem could be caused by the update process. With new update mechanism, the reboot is not required after update. In case of File Lock, most of components is updated to new version, but the McPvNs.dll loaded by Explorer is still running in old version util the machine is rebooted. Please try to reboot your machine to see if the problem goes away.
BTW, a new version of File Lock will be released soon which fixed couple of crashes in Explorer.
Sorry not experienced with file lock as we mods do not use it. Best to call tech support and ask them and if they cannot assist request an escalation call back.
Tech support listed under useful links tab above.
We noticed this issue as well. The problem could be caused by the update process. With new update mechanism, the reboot is not required after update. In case of File Lock, most of components is updated to new version, but the McPvNs.dll loaded by Explorer is still running in old version util the machine is rebooted. Please try to reboot your machine to see if the problem goes away.
BTW, a new version of File Lock will be released soon which fixed couple of crashes in Explorer.
<Bump>
I've been having issues with McPvNs.dll unloading and then crashing Windows Explorer whenever logging cuts out lately, as opposed to the StackHash error discussed on the other thread. Any news on that FileLock update?
Problem signature
Problem Event Name: BEX64
Application Name: Explorer.EXE
Application Version: 6.1.7601.17567
Application Timestamp: 4d672ee4
Fault Module Name: McPvNs.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 522de439
Exception Offset: 000007feeb664050
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 65d5
Additional Information 2: 65d5e11e3b403a4beaf5cea13462fca9
Additional Information 3: 4ef1
Additional Information 4: 4ef1392c0b777cb9c942816dd7a5eb58
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: