Solved Unhandled exception in Managed Code Snap-In (?????)

[450125]

This problem falls under the old vaudeville joke "Doc, it hurts when I do this / well then don't do this"...

Last night, for the second time in about a month, I got a BSOD during my normal restart Windows sequence I do at the end of the night (the BSOD occurs after the programs close, the screen blacks, then a normal Windows screen appears saying "Windows is shutting down").

I discovered it this morning and was in a rush, so I just turned the computer off and restarted it, figuring the details would be logged in the event viewer.

They weren't. No record of any abnormalities in the past hour, day, week, etc.

Just for grins though, I looked at other parts of the event viewer that I usually skip (normally I look at the main summary screen, and the System Log under Windows Logs, and nothing else).

Everything went fine, but when I went to the Application log under Windows Logs, I got "MMC has detected an error in a snap-in and will unload it" (a popup Windows error message).

The specific error is listed as "Unhandled exception in Managed Code Snap-In" and comes up in a window mentioning FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510} - "Value was either too large or too small for an Int64" - Exception Type "System.OverflowException" and then this:

at System.UInt64.System.IConvertible.ToInt64(IFormatProvider provider)
at Microsoft.Windows.ManagementUI.CombinedControls.EventsResultSet.GetCountOfRecordsInResult()
at Microsoft.Windows.ManagementUI.CombinedControls.EventsResultSet.Initialize(String channelPath, String Query)
at Microsoft.Windows.ManagementUI.CombinedControls.EventDetailControl.InitializeEventListView(Boolean refresh)
at Microsoft.Windows.ManagementUI.CombinedControls.EventDetailControl.InitializeResultView()
at Microsoft.Windows.ManagementUI.CombinedControls.EventDetailControl.RefreshControls()
at Microsoft.Windows.ManagementUI.CombinedControls.EventDetailControl.ExecuteRefreshAction()
at Microsoft.Windows.ManagementUI.CombinedControls.EventDetailControl.OnAction(ManagementAction action)
at Microsoft.EventViewer.SnapIn.MMCEventsResultView.RefreshResults()
at Microsoft.EventViewer.SnapIn.MMCEventsResultView.OnShow()
at Microsoft.EventViewer.SnapIn.FormControlBase.OnFormShow()
at Microsoft.ManagementConsole.View.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.ViewMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

I can't say this is a new error, because I may very well have never looked at the Application log in Event Viewer before today.

Googling some suggested fixes, I ran SFC /scannow, and that found nothing wrong.

Can someone guide me through what's happening, and suggested fix(es)?

 

[450125]

After I posted this, I did a lot more googling, and eventually - it took a while - found a thread elsewhere describing what I was experiencing.

It turns out that my application log file was at the maximum size, and even though I had the application log properties set to automatically overwrite the events as needed, oldest first, this was the problem. When I saved and cleared the log (if you click "clear" it will give you the option of saving the log before clearing), this problem was solved.

I still don't understand why I've gotten two BSODs in the last six weeks, during the Windows shutdown prior to a Windows restart.

But at least this weird problem with the unhandled exception has been fixed, so I am marking the thread solved.