*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D5, {fffff900c48fad58, 1, fffff9600031c44e, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!MulDeleteDeviceOrRedirectionBitmap+2a )
Followup: MachineOwner*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D5, {fffff900ce050f08, 0, fffff9600016decf, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!vCleanupPrivateFonts+6f )
Followup: MachineOwner