CLR20r3 viscosityservice.exe

Got a problem with Viscosity or need help? Ask here!


Posts: 7
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Mon Jul 08, 2019 10:07 pm
I did a little sweep of errors in my Event Viewer, and saw that Viscosity is frequently crashing (viscosityservice.exe).

Faulting Application Path: C:\Program Files\Viscosity\ViscosityService.exe

Problem signature
Problem Event Name: CLR20r3
Problem Signature 01: ViscosityService.exe
Problem Signature 02:
Problem Signature 03: 5cee4e8a
Problem Signature 04: System.Management
Problem Signature 05: 4.8.3752.0
Problem Signature 06: 5c7a241f
Problem Signature 07: 8a
Problem Signature 08: 51
OS Version: 10.0.18362.
Locale ID: 1033
Additional Information 1: c845
Additional Information 2: c8458de3129ac310566f5f5edb271f67
Additional Information 3: dfb9
Additional Information 4: dfb9e84192fc0b595ffdd113a23b8744

Extra information about the problem
Bucket ID: 587587e412f8fb159eefba9ee8dee772 (2229205532246206322)

Any ideas where to start troubleshooting?


Posts: 7
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Tue Jul 09, 2019 7:01 am
I seem to get the error each time I restart the computer. See screenshot.
Anmerkung 2019-07-08 230120.jpg
Anmerkung 2019-07-08 230120.jpg (80.07 KiB) Viewed 186 times


User avatar
Posts: 873
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Jul 09, 2019 8:49 am
Hi datevat,

These events usually come in a pair, is there a second event with more information being posted at roughly the same time to the Event Viewer? At a glance though it looks like the service is being forcibly terminated, for example by forcibly restarting when Windows prompts you after restarting that some applications are waiting to close.

If you're not doing this, please try repairing .NET -

If the problem still occurs, you may need to reinstall .NET.



Posts: 7
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Wed Jul 10, 2019 3:49 pm
I didn't find any other event. Source of the EventID is Windows Error Reporting.
Here is a bit more info from the Event Viewer:

Fault bucket 1374664618037830471, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: ViscosityService.exe
P3: 5cee4e8a
P4: System.Management
P5: 4.8.3752.0
P6: 5c7a241f
P7: 8c
P8: 3f
P9: System.Management.Management

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: eeae1afb-ea0e-4742-88aa-5b176c468f42
Report Status: 268435552
Hashed bucket: 39b2e4c2fb21e9649313ca2fd3716347
Cab Guid: 0

I tried repairing .NET, nothing changed.

I'm not sure I'm keen to completely reinstalling .NET, since there are no other indications that there is a problem.


User avatar
Posts: 873
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Wed Jul 10, 2019 5:52 pm
Hi datevat,

System.Management is the .NET interface to querying the system about devices and hardware. Usually if the fault is within Viscosity you would see an application stacktrace in Event Viewer as well, the ones you have posted are from the System itself. I understand that you may not be seeing other problems, however, very few pieces of software would be interfacing with your system like Viscosity does.

We used to see System.Management errors a lot before we forced Viscosity to use .Net 4.5.2 as there was a bug in earlier versions of .NET that was generally fixed by a reinstall. This is the first time we've actually seen this error crop up since we updated Viscosity to the newer version of .NET several releases ago now.

I'm afraid all we can recommend is a reinstall of .NET. This should have no impact on your system other than taking a little while to complete -

A device driver not exiting gracefully when you shut down your PC could also be causing this, we have seen hardware wifi switches on laptop take out multiple .NET applications in the past when flicked for example. The hardware errors in your log may also be related.

We will monitor for further reports of this happening. The good news though is this is most likely not effecting Viscosity as it should be recovering itself on startup again from ungraceful shutdowns, even though the situation is not ideal.

Eric Thorpe
Viscosity Developer



Posts: 7
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Thu Jul 11, 2019 9:40 pm
OK, I get it. I'll try to completely remove and reinstall .NET and will report back in a week or so.
6 posts Page 1 of 1