McAfee Antivirus Plus, here's the version information:
Security Center: Version 11.0, Build: 11.0.572 last update 8/11/2011
McAfee VirusScan: Version 15.0, Build 15.0.291, last update 8/18/2011
Recently, my desktop (Windows 7 Enterprise, 6GB memory) started having a problem where Windows Explorer would become non-responsive. The start menu (set to auto-hide) would not unhide, and one thread is running compute-bound (~12-15% of a 3.4Ghz I7-2600 (4 cores with hyperthreading)). Looking at the stack, there doesn't apear to be anything interesting, and certainly nothing to indicate that it might be McAfee.
HOWEVER, yesterday McAfee on my laptop updated (Win 7 also, 8GB memory), and required a reboot. Shortly after that reboot, Windows Explorer on the laptop hung in exactly the same way.
If I restart Explorer via Task Manager everything works fine for a while...the hang seems to happen about once/day on my desktop.
Has anyone else experienced a similar problem recently? McAfee folks, any suggestions for things to look at or for in order to figure out what might be causing this?
Thanks!
Stack trace of the compute-bound thread:
comctl32.dll!Ordinal222+0xd178
USER32.dll!PeekMessageW+0xba
USER32.dll!GetKeyState+0xee
USER32.dll!PeekMessageA+0x57
SHLWAPI.dll!Ordinal166+0x83
SHELL32.dll!ExtractIconW+0x2f8
SHELL32.dll!StgMakeUniqueName+0xdd585
SHELL32.dll!StgMakeUniqueName+0xdd6ce
SHELL32.dll!Ordinal733+0x586da
explorer.exe+0x3bb9f
explorer.exe+0x3844f
explorer.exe+0x12b0
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!SetWindowTextW+0x277
USER32.dll!IsDialogMessageW+0x169
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!IsDialogMessageW+0x19a
USER32.dll!GetWindowLongPtrA+0x83
USER32.dll!SendMessageW+0x5d
SHELL32.dll!SHChangeNotification_Lock+0xd3
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!SetWindowTextW+0x277
USER32.dll!IsDialogMessageW+0x169
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!KillTimer+0x1a
DUser.dll+0x10f4
DUser.dll+0x11fa
USER32.dll!KillTimer+0x61
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!PeekMessageW+0xba
USER32.dll!GetKeyState+0xee
USER32.dll!PeekMessageA+0x57
SHLWAPI.dll!Ordinal166+0x83
SHELL32.dll!ExtractIconW+0x2f8
SHELL32.dll!StgMakeUniqueName+0xdd585
SHELL32.dll!StgMakeUniqueName+0xdd6ce
SHELL32.dll!Ordinal733+0x586da
explorer.exe+0x3bb9f
explorer.exe+0x3844f
explorer.exe+0x12b0
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!SetWindowTextW+0x277
USER32.dll!IsDialogMessageW+0x169
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!IsDialogMessageW+0x19a
USER32.dll!GetWindowLongPtrA+0x83
USER32.dll!SendMessageW+0x5d
SHELL32.dll!SHChangeNotification_Lock+0xd3
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!SetWindowTextW+0x277
USER32.dll!IsDialogMessageW+0x169
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!KillTimer+0x1a
DUser.dll+0x10f4
DUser.dll+0x11fa
USER32.dll!KillTimer+0x61
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!PeekMessageW+0xba
USER32.dll!GetKeyState+0xee
USER32.dll!PeekMessageA+0x57
SHLWAPI.dll!Ordinal166+0x83
SHELL32.dll!ExtractIconW+0x2f8
SHELL32.dll!StgMakeUniqueName+0xdd585
SHELL32.dll!StgMakeUniqueName+0xdd6ce
SHELL32.dll!Ordinal733+0x586da
explorer.exe+0x3bb9f
explorer.exe+0x3844f
explorer.exe+0x12b0
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!SetWindowTextW+0x277
USER32.dll!IsDialogMessageW+0x169
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!IsDialogMessageW+0x19a
USER32.dll!GetWindowLongPtrA+0x83
USER32.dll!SendMessageW+0x5d
SHELL32.dll!SHChangeNotification_Lock+0xd3
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!SetWindowTextW+0x277
USER32.dll!IsDialogMessageW+0x169
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!KillTimer+0x1a
DUser.dll+0x10f4
DUser.dll+0x11fa
USER32.dll!KillTimer+0x61
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!PeekMessageW+0xba
USER32.dll!GetKeyState+0xee
USER32.dll!PeekMessageA+0x57
SHLWAPI.dll!Ordinal166+0x83
SHELL32.dll!ExtractIconW+0x2f8
SHELL32.dll!StgMakeUniqueName+0xdd585
SHELL32.dll!StgMakeUniqueName+0xdd6ce
SHELL32.dll!Ordinal733+0x586da
explorer.exe+0x3bb9f
explorer.exe+0x3844f
explorer.exe+0x12b0
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!SetWindowTextW+0x277
USER32.dll!IsDialogMessageW+0x169
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!IsDialogMessageW+0x19a
After further investigation, it now appears that the hang was caused by DisplayFusion (www.displayfusion.com). Curious that the problem only showed up recently after a McAfee update, as I've been running DF for several months without problem.
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: