BSOD - MUP_BUGCHECK_NO_FILECONTEXT - Any Ideas?

Nov 12, 2018
6
0
10
First a little backstory....we have an OLD (i.e VB6....ugh, I know) piece of software that we still use on a daily basis (double ugh). When we publish any updates, we have an installer (also VB6) that uses the FileCopy command to "install" the update from a mapped network drive.

Now to the issue.... We have several machines that will sporadically BSOD with a MUP error (some Win 10, and a Win 8). Some always crash after the update. I should note that the error does not actually occur when running the updater but when trying to run the "updated" software itself. After the reboot, the file opens normally so I'm at a bit of a loss...

I've done some research and found this link which was informative, but due to the configuration leading to this error, I'm not exactly sure how to fix it: http://www.osronline.com/article.cfm?article=509

Any help is appreciated!

Below is the text from the dmp file as well as a link to the compressed version of the dmp itself(NOTE: Dump is from a Win 10 machine but even compressed its 258MB)

Compressed dmp file



Debugging Details:
----------------------------------

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MUP_FILE_SYSTEM (103)
MUP file system detected an error.
Arguments:
Arg1: 0000000000000001, MUP_BUGCHECK_NO_FILECONTEXT
Could not locate MUP file context corresponding to a file object.
Arg2: ffff820d1053da40, Irp Address if an IRP was used, NULL otherwise.
Arg3: ffff820d38128700, FILE_OBJECT Address whose MUP file context could not be found
Arg4: ffff820d228dc3f0, DEVICE_OBJECT Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Dell Inc.

SYSTEM_PRODUCT_NAME: Precision 3530

SYSTEM_SKU: 0820

BIOS_VENDOR: Dell Inc.

BIOS_VERSION: 1.4.2

BIOS_DATE: 08/31/2018

BASEBOARD_MANUFACTURER: Dell Inc.

BASEBOARD_PRODUCT: 0601X8

BASEBOARD_VERSION: A00

DUMP_TYPE: 1

BUGCHECK_P1: 1

BUGCHECK_P2: ffff820d1053da40

BUGCHECK_P3: ffff820d38128700

BUGCHECK_P4: ffff820d228dc3f0

IRP_ADDRESS: ffff820d1053da40

DEVICE_OBJECT: ffff820d228dc3f0

DRIVER_OBJECT: ffff820d228d03f0

IMAGE_NAME: mup.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: mup

FAULTING_MODULE: fffff80589790000 mup

CPU_COUNT: c

CPU_MHZ: a98

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x103

PROCESS_NAME: CorsiVisionSL.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: IN-LAPTOP-X278

ANALYSIS_SESSION_TIME: 12-31-2018 11:50:23.0937

ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

LAST_CONTROL_TRANSFER: from fffff805897a5359 to fffff8010e04c0a0

STACK_TEXT:
ffffc78a`d89a7698 fffff805`897a5359 : 00000000`00000103 00000000`00000001 ffff820d`1053da40 ffff820d`38128700 : nt!KeBugCheckEx
ffffc78a`d89a76a0 fffff801`0df3ae69 : ffff820d`228dc080 00000000`00000000 ffff820d`228dc080 ffff820d`1053da40 : mup!MupSetInformationFile+0x1bd9
ffffc78a`d89a7700 fffff805`876051f2 : ffff820d`00000000 ffff820d`00000040 ffff820d`38134901 00000000`0009e5f8 : nt!IofCallDriver+0x59
ffffc78a`d89a7740 fffff801`0df3ae69 : ffff820d`1053da60 fffff801`0dee02c4 00000000`20206f49 00000000`00000000 : FLTMGR!FltpDispatch+0xe2
ffffc78a`d89a77a0 fffff801`0df266a4 : 00000000`0019bc00 00000000`00000000 00000000`0009e5f8 00000000`00000008 : nt!IofCallDriver+0x59
ffffc78a`d89a77e0 fffff801`0df24003 : ffff820d`38128798 fffff801`0e3621fd 00000000`beaa0251 00000000`00000028 : nt!IopCallDriverReference+0xf4
ffffc78a`d89a7850 fffff801`0e05c743 : 00000000`0000036c 00000000`0009e5f8 ffffc78a`d89a79a8 00000000`00000008 : nt!NtSetInformationFile+0x6a3
ffffc78a`d89a7990 00007ff9`737fae84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009e5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`737fae84


THREAD_SHA1_HASH_MOD_FUNC: 450a9e0bad929aa1cc5eef3165a0b3637cad8064

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: acf95c717bc46a7cd131f496026b5c9f195a2e1b

THREAD_SHA1_HASH_MOD: 9bdfe05856ab4f1e4b9d3013ece5b3b293464f42

FOLLOWUP_IP:
mup!MupSetInformationFile+1bd9
fffff805`897a5359 cc int 3

FAULT_INSTR_CODE: d4bbcc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: mup!MupSetInformationFile+1bd9

FOLLOWUP_NAME: MachineOwner

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1bd9

FAILURE_BUCKET_ID: 0x103_mup!MupSetInformationFile

BUCKET_ID: 0x103_mup!MupSetInformationFile

PRIMARY_PROBLEM_CLASS: 0x103_mup!MupSetInformationFile

TARGET_TIME: 2018-12-31T14:19:46.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-12-14 01:53:05

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 6ff

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x103_mup!mupsetinformationfile

FAILURE_ID_HASH: {d4cdc580-56e8-b325-e515-45ec9c6a06ea}

Followup: MachineOwner
---------




 

Colif

Win 11 Master
Moderator
I always say I want to see errors I haven't seen before (most BSOD around here are the same ones) but I am not sure how much help I can be.

MUP.sys is part of windows
The file helps in the functioning of a part of the operating system called a Multiple UNC Provider (MUP). It is part of a software system that helps networked computers communicate with one another to share files and peripheral components such as printers and scanners.

This page might help - https://www.streetdirectory.com/travel_guide/126264/computers/what_the_heck_is_an_mupsys_error.html

If its caused by corrupted file system drivers, its possible this might help fix it:
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

Getting minidumps might help as well
Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and I will get someone to convert file into a format I can read
 
Nov 12, 2018
6
0
10
I hope I posted this right...



Lol, its just like the old Chinese Proverb..."Be careful what you wish for, lest it come true."

I didn't even think about running SFC, but it came back clean and my ImageHealthState when running Repair-WindowsImage was Healthy.

After reading the link you provided, things are making a bit more sense. We were running on two domains until the weekend before last and I never got the BSOD until the migration (I was already on the domain we were keeping). We've seen a few oddities post-migration (like mapped network drives controlled through Group Policy being disconnected first thing in the morning) so I'm guessing that connectivity to the DC is part of the problem. I checked my event lo and low and behold the error just before log dump creation was:

"The processing of Group Policy failed because of lack of network connectivity to a domain controller."

I've changed my config so the next blue screen will create a minidump instead of the full one. Hopefully when we finish our network cleanup this will no longer be an issue.

Thanks for your help!
 
tell your usb network driver to never sleep. (in device manager)
\SystemRoot\System32\drivers\rtux64w10.sys Mon Mar 26 01:15:30 2018

if you know the chip name of the usb thub network device you can get the current driver:
https://www.realtek.com/en/component/zoo/advanced-search/72?Itemid=276


rtux64w10 v10.24 (running)
intel wireless-AC 9560 was disconnected
Intel(R) Ethernet Connection (7) I219-LM (disconnected)
Fortinet Virtual Ethernet Adapter (NDIS 6.30) (disconnected)


some device in device manager is not configured: see service name
InstancePath is "ROOT\NET\0001"
ServiceName is "ftsvnic"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
StateHistory[00] = DeviceNodeUninitialized (0x301)

\SystemRoot\System32\drivers\pppop64.sys Tue Mar 22 15:01:28 2016
 
Nov 12, 2018
6
0
10
That does make some sense...I'm using a Thunderbolt 3 docking station for my network connection but I had already told it to never sleep. I doubt that's the issue as I got another BSOD and other people on the network are experiencing the same issue. Here's a copy of the Minidump file which was just generated... (I know it's been a while since my original post but it's been that long since this issue occurred).

Minidump
 

gardenman

Splendid
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/jbwa.html

File information:Mini.dmp (Mar 4 2019 - 15:36:25)
Bugcheck:MUP_FILE_SYSTEM (103)
Probably caused by:mup.sys (Process: CorsiVisionSL.)
Uptime:4 Day(s), 6 Hour(s), 30 Min(s), and 55 Sec(s)

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.
 

Colif

Win 11 Master
Moderator
circular references are fun, the only reference to CorsiVisionSL is this post. I don't know enough about this error to know how to fix it :(

i will attempt to get john's attention.

You could try posting on here, there might be more there that understand what is going on
 
Nov 12, 2018
6
0
10
Thanks @Colif. CorsiVisionSL is a custom internal piece of software written in VB6 (yeah....I know). There is an "updater" program that uses the "FileCopy" command to copy the .exe and any other required files from a network share. These BSODs are happening occasionally after running the updater and then launching CorsiVisionSL. I was thinking if it was a network issue, the problem would occur during the update and not when launching the program. My hope is that someone can help me pinpoint a specific issue so that we can address it as we're all a bit stumped.

I'll try posting on tenforums, too. Thanks.