|10 Jun 2015||#2|
MUP.sys == Multiple UNC Provider. It actually just provides an interface into the myriad of ways a system can access remote systems via UNC through the redirector (rdbss.sys). Whilst MUP can be the culprit, it is rarely the case. The dumps you've provided indicates that some driver is calling to another system via the redirector, which is going into MUP.sys with invalid data and crashing the box (I have seen this exact stack before in Windows 7):
1: kd> kn *** Stack trace for last set context - .thread/.cxr resets it # ChildEBP RetAddr 00 8dfaeab0 8c20db8f mup!MupCallSurrogatePrePost+0xca 01 8dfaeac8 8c20942b mup!MupStateMachine+0x65 02 8dfaeadc 82e92ef3 mup!MupiUncProviderCompletion+0x71 03 8dfaeb24 9c356f30 nt!IopfCompleteRequest+0x128 04 8dfaeb5c 9c382c2f rdbss!RxCompleteRequestEx+0x291 05 8dfaeb7c 9c37ebb7 rdbss!RxProcessException+0x11c 06 8dfaebe8 83030747 rdbss!RxFspDispatch+0x104 07 8dfaec00 82e9823b nt!IopProcessWorkItem+0x2d 08 8dfaec50 8302500f nt!ExpWorkerThread+0x10d 09 8dfaec90 82ecb699 nt!PspSystemThreadStartup+0x9e 0a 00000000 00000000 nt!KiThreadStartup+0x19
As always, before doing anything to your system, it would be recommended to create a restore point, just in case...
From the start screen, type 'verifier' to open verifier.exe, which should open 'Driver Verifier Manager'.
1. Select the option "Create custom settings (for code developers)" and click Next:
2. Select all checkboxes except for options "Randomized low resources simulation", "Power framework delay fuzzing", and "Systematic low resource simulation" and click Next:
3. Select the option "Select driver names from a list" and click Next:
4. Sort the list by provider, and select all items that are NOT from the "Microsoft Corporation" provider (you may have to select items both before *and* after the "Microsoft Corporation" items to get all non-OS drivers) - with one exception, mup.sys - and then click Finish:
5. Change your dump options from minidump to kernel dump
Reboot the computer for the changes to take effect. The next crash that happens should create a dump in \Windows called "Memory.dmp", which can be zipped and then uploaded/linked and shared for us to download and analyze.
|My System Specs|
|Thread Tools||Search this Thread|
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 05:37.