I have the situation kind of similar to this post, but direr.

Every time my computer wakes up from sleeping more than a couple of hours, it freezes for 5 minutes. If you reboot the computer, you have to get 2 minutes of the same freezes.

What is even more funny is that the freezes start only when you start being active. Typing in the password to enter the system or just moving your mouse after the sleep, for example.

The typical freeze goes like this - you can move your mouse, but the screen doesn't change even if you click on something. The window that was active becomes "Not Responding". After some time (15 sec - 1 min) the clicks that you've done, come into action. You have approximately 5-10 seconds of the computer responding to your actions and programs doing what they should do. Then the cycle repeats itself.

Based on the info from Process Monitor, the culprit is svchost.exe's "\Device\Mup NO MORE MATCHES".

As I've understood from the info of the post below, this \Device\Mup is related to remote files and similar stuff. If it's required to temporally sacrifice the ability to do something with files in local network, I'm OK with that, I just want my computer to not lag for 5 minutes each time I turn it on.

I did chkdsk and checked the hard drive with WD Life Diagnostic tool. Also I did virus check with KVRT and Malwarebytes.

Full info about this command.
Class: File System
Operation: DeviceIoControl
Path: \Device\Mup
Version: 6.3.9600.16384 (winblue_rtm.130821-1623)
Command line: C:\WINDOWS\system32\svchost.exe -k LocalServiceNoNetwork
Control: 0x1403a4 (Device:0x14 Function:233 Method: 0)

  • Fun fact, the freezes have stopped occurring once I changed the place of living. Device Mup's didn't disappear completely, they still happen once every second, but now computer doesn't lag when waking or powering up. – Ramid Oct 16 '18 at 20:31

The Microsoft definition for MUP defines it as :

The multiple UNC provider (MUP) is a kernel-mode component responsible for channeling all remote file system accesses using a Universal Naming Convention (UNC) name to a network redirector (the UNC provider) that is capable of handling the remote file system requests.

This seems to indicate that you have a some strange problem with network shares, or with your network in general.

Checks that you may do :

  • Undo any created network shares and verify
  • Check if the problem exists when booting in Safe Mode, to see if the problem is caused by some installed product.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.