mmc.exe(ver: 10.0.19041.1806) \ Event Viewer -- freeze && crash

The original post about this exact issue:

"https://www.tenforums.com/general-support/177315-microsoft-management-console-mmc-exe-version-10-19041-746-crashes.html"

... was posted over four-hundred days in the past, yielding six-hundred and eighty-three views, without any response\reply.

PRESENT DAY: The current MMC ver: 10.0.19041.1806 allows the 'freeze/crashing' to continue on two differently branded machines.

Problem Description: MMC\Event Viewer | Find (function), and/or the Filter (function) after first use, with any subsequent usage --of Event Viewers' --Find or Filter-- will freeze/crash 'both' MMC\Event Viewer; listed in the Task Manager as MMC. At this point if any further use of MMC\Event Viewer is needed, during this machine's current uptime, MMC needs to be force terminated.

NOTE-01: Terminating MMC then restarting MMC --does not resolve the above.
NOTE-02: Until we have an opportunity to test this, between logging-out/in, the only way this can temporarily be resolved is to reboot the OS. After-which this ill-behaved cycle repeats.

Additional information:

LENOVO T-440 -- A donated machine (2019), no clue how many previous users; or issues. It was this machine the MMC freeze/crash was first observed. I left it alone until -- 2021 when the entire machine's behavior became severely annoying.

ASUS TUF A15 -- During Feb-Mar/2021, approx five different, supposedly 'new' unused machines were swapped out; before the dust began to settle. Throughout the dust kicking-up, the MMC\Event Viewer freeze/crash; remained on this newer box running W-10(Pro). This must be a MicroSoft\Windows-10 issue.

At this point I download the available iso, based on my recognized 'Product Key' from MicroSoft, then performed a clean install of W-10(Pro); ridding the ASUS of the preloaded software. The MMC\Event Viewer --freeze/crash behavior remains. I do not see how this could be caused by anything but MicroSoft\Windows-10(Pro), yet I yield no internet search results of other users experiencing this freeze/crashing of MMC\Event Viewer, i.e. after using either the 'Find' and/or 'Filter' function.

<PAUSE> the above.

Having said everything above, while creating this post 'MMC\Event Viewer' was kind enough to present me with an 'Unhandled Exception'. Please see attached Event_Viewer_initiated.png. Look closely at the png, Task Manager is showing two instances of the aforementioned items.

If anyone is interested is assisting, I've retained dumps for both instances.

<RESUME> the original problem description.
Prior to the 'Unhandled Exception', the plan continues to be, video_capture the screen of Event_Viewer from the beginning to the freeze/crash; most likely no visible error dialog will generate. I'll follow-up with this video_capture once I'm sure the forum is agreeable. If I'm lucky, the included png and/or the dump files will do. Thank you all for taking the time to read.

OS Name Microsoft Windows 10 Pro
Version 10.0.19044 Build 19044
System Type x64-based PC

Respectfully,
IGT

dalchina said:

Hi, people only tend to respond if they think they can contribute something useful. Members are unpaid volunteers, so response and participation is - voluntary. No guarantees responses are given, or that resolution can be achieved. As you will know, we are fellow users, not in general MS employees.

@dalchina: I only mentioned the previous posting to alert readers how things 'may have' changed over time; e.g. updates and/or version numbers. It was not a remark/comment pointed at a lack of attention for that particular post. The forum has my apologies if the verbiage/sentiment was incorrect.

dalchina said:

This is a T-440s - FWIW I see no such crashes...
Tried Find and cancel, Filter.

Perhaps you could post a precise sequence for someone to try?

@dalchina: Your suggestion above is where my thought of providing a video_capture comes into play. I was hoping either someone else had also experienced, then resolved, or had more of a clue (than I), about how to debug this concern using the dmp files I've retained.

dalchina said:

Noted your screenshot shows a Net framework exception error. Is that a general case?
Also a snap-in error.
I'd suggest those need resolving. Have you added any snap-ins?

------------- Net framework error message screen OCR'd for search purposes ----
Unhandled exception has occurred in a component in your application.
If you click Continue, the application will ignore this error and attempt to continue.
lnvalidArgument=Value of '-1' is not valid for 'index'.
Parameter name: index.

@dalchina: The issues shown in the screen capture is the --cherry on the ice-cream cone--. This just happened to occur while I was confirming the ability to reproduce the issues with MMC\Event Viewer |Find | Filter (functions). I cannot reproduce the errors shown in the screen_capture; with any certainty.

Let's address your list: (annotated)
Noted your screenshot shows a Net framework exception error. Is that a general case?
--Not a general case. Don't remember ever seeing this previously.

Also a snap-in error.
I'd suggest those need resolving. Have you added any snap-ins?
-- I have not added any snap-in(s) or done any reconfiguring to mmc or group policy.

**** The fact that the concern with MMC\Event Viewers' Find && Filter function has been repeated/reproduced on two different branded machines: in the cases of the Lenovo T-440, initially we've been working with the OEM preload. Then we acquired the ASUS, there were four to five different machines. The first four using preloads, the fifth machine --first with a factory preload, then with an OS reinstall using an iso downloaded from MicroSoft. Finally, earlier this year, we replaced the Lenovo T-440's preload with MicroSofts' downloaded bare-bones iso; the issues remain after one-year of Win-10 updates, is very interesting\odd.

This is the reason for the post.

A video of the exact issue can be viewed at:

2022 07 24 07 29 01 - YouTube

... as you will see, once the 'cancel' button is clicked, its a wrap. I can repeat this all day long with the same result.

Have you tried the Clean Boot method on the offending machines to see if that identifies any problem programmes and does Reliability History show entries covering the freezes?
The Display Adapter driver is often a factor in freezes and replacing it with a new one,or later version if available,can help.

joeandmarg0 said:

Have you tried the Clean Boot method on the offending machines to see if that identifies any problem programmes and does Reliability History show entries covering the freezes?
The Display Adapter driver is often a factor in freezes and replacing it with a new one,or later version if available,can help.

@joeandmarg0: Hi,
Given this threads' initial text, detailing the number of machines and OS reinstall's performed with said hardware, I'm not understanding --why you're suggesting "the Clean Boot method on the offending machines". Please further explain "the Clean Boot method".

With regard to "The Display Adapter driver is often a factor in freezes ...", Assuming you've reviewed the video of the event attached to this thread, only MMC\Event Viewer freezes/crash; nothing else. Here again I'm not understanding; please offer more details.

Respect.

In the Tutorial section,search for Clean Boot.
This method helps to determine whether the cause is Windows or a third party programme
Trying to solve a problem requires a resolution of software or hardware.Checking Reliability History may assist.
Data transferred to the screen is controlled by the Display Adapter driver and if it is faulty,then the freeze.
Given the chequered history of the affected machines,the software appears to be the cause.
Ignore the number of machines involved,deal with one at a time.

joeandmarg0 said:

In the Tutorial section,search for Clean Boot.
This method helps to determine whether the cause is Windows or a third party programme
Trying to solve a problem requires a resolution of software or hardware.Checking Reliability History may assist.

It appears (to me), you did not see, or understand the part where a reinstall was performed with a downloaded, barebones copy of Win-10; from MicroSoft. I.E., no third-party software is installed.

Clean Boot?

joeandmarg0 said:

Data transferred to the screen is controlled by the Display Adapter driver and if it is faulty,then the freeze.
Given the chequered history of the affected machines,the software appears to be the cause.
Ignore the number of machines involved, deal with one at a time.

Clearly in the video_capture of the subject matter event, it can be confirmed that --another running program is responding to the mouse --notice the repositioning of the responding 'Task Manager' window, --further confirmed by the 'Task Manager' displaying "Microsoft Management Console" "Not responding". All taking place using the very same 'Display Adapter Driver'. With that in mind, I do not see how any 'Display Adapter driver' would select and freeze a native MicroSoft programs' display-stream --simultaneously with the 'Task Manager' listing a "Not responding" for the same process.

I'm not wanting to move away from this 'Event Viewer' discussion about freezing then crashing and/or indefinitely hanging, within this thread, however I would like to hear/read more of how you're reaching this/these conclusions.

I may very well be missing more than I thought.