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
---------
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
---------