BSOD - Shutting Down - mup.sys

[callumm]

Hello

I need some assistance with this BSOD. I was shutting down my pc (because of updates) and it happened.
I have taken a look at the Minidump and I couldn't find any definitive cause. Can you also report what you find so I can improve my analysing skills?

Thanks!

 

[Arc]

Hello

I need some assistance with this BSOD. I was shutting down my pc (because of updates) and it happened.
I have taken a look at the Minidump and I couldn't find any definitive cause. Can you also report what you find so I can improve my analysing skills?

Thanks!

That is a bugcheck code I am seeing for the first time.

BugCheck 103, {1, fffffa80086fb6f0, fffffa8003bf3910, fffffa8004056e40}

Probably caused by : mup.sys ( mup!MupCleanup+90 )

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

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: fffffa80086fb6f0, Irp Address if an IRP was used, NULL otherwise.
Arg3: fffffa8003bf3910, FILE_OBJECT Address whose MUP file context could not be found
Arg4: fffffa8004056e40, DEVICE_OBJECT Address

I followed Arg2 .... nothing very special.

 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 12, 0]   0  0 fffffa8004056e40 fffffa8003bf3910 00000000-00000000    
          Cannot read _DRIVER_OBJECT at fffffa8004055a60

            Args: 00000000 00000000 00000000 00000000

Same when I followed Arg4.

fffff80002e311d0: Unable to get value of ObpRootDirectoryObject
fffff80002e311d0: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa8004055a60) is for:
Cannot read _DRIVER_OBJECT at fffffa8004055a60

So nothing is coming out as a probable cause.

But Bug Check 0x103: MUP_FILE_SYSTEM (Windows Debuggers) gives a hint.
View attachment 337021
Hope it helps a little bit .... Driver Verifier may be employed to see if it catches anything.